extragear/multimedia/amarok

Ian Monroe ian.monroe at gmail.com
Tue Feb 17 23:07:39 CET 2009


On Tue, Feb 17, 2009 at 3:23 PM, Seb Ruiz <ruiz at kde.org> wrote:
> 2009/2/18 Casey Link <unnamedrambler at gmail.com>:
>> Future TODO:
>>
>> * Make the auto timecode icon different from the manual timecode (diff
>> color, shape, etc)
>> * Restrict the number of  auto timecodes to 1 per track
>> * Start playing a track at its auto-timecode instead of the beginning
>> * Sync to media devices (https://bugs.kde.org/show_bug.cgi?id=184707)
>>
>> Potentially Controversial TODO:
>> * Allow Toggling of auto timecodes (per track OR for the whole app?)
>> * Allow configuration of the minimum length threshold (currently 10 minutes)
>>
>>
>> Any opinions? I know most are against adding configuration options..
>> I'd like some feedback before I go adding them
>
> Whilst I haven't looked at the code for this, I'd like this to be a
> Meta specific attribute. I think it should be on by default for
> podcasts, and off for all other Meta types except for some distinct
> cases (Audiobook .aa files for example). It would be bad to force this
> upon all the listeners of long epic tracks where a resume doesn't
> necessarily make sense (i'm thinking dream theatre epics, long cue
> files, classical symphonies etc).
>

Yea I think auto-resume for just any track doesn't make sense. Today I
was listening to a 30-minute symphony track and then it was 15:00 so I
switched to NPR. It would really annoy me to have that symphony
started 18 minutes in the next time I play it. But equally I couldn't
care at all if some bookmark was set for it or not.

For podcasts and confirmed audio books (eg .aa like Seb says or a
relevant genre set) auto-resume makes a lot of sense.

So: setting a bookmark is always OK, auto-resume needs to be done only
in specific cases though.

And of course I hate the notion of new options. :)

Ian


More information about the Amarok-devel mailing list