Rockbox mail archiveSubject: Re: Automatic multi-resume feature for podcasts and audiobooks (FS#11748)
Re: Automatic multi-resume feature for podcasts and audiobooks (FS#11748)
From: Paul Louden <paulthenerd_at_gmail.com>
Date: Wed, 15 Dec 2010 20:51:21 -0600
At the request of IrcNick Soap, I'm going to write my counter proposal.
I really don't want this to descend into a "his idea vs my idea" kind of
situation. What I'd like us to do is try to decide as a group what sort
of playback situations auto-resume should address (playlist full of half
complete files, primarily individual files or single files in a list of
related files that shouldn't be resumed, etc) and how we want to address
them (highly configurable, "one size fits all" or somewhere in between) etc.
My personal preference is this:
I would like Rockbox to attempt to resume any file that is the first
file you select to play back. Basically, when I click "select" or
"right" on a music file (button names may vary by player) that file
should attempt to resume, but nothing else in the auto-generated
playlist should. Resume state is only saved if I stop playback or the
player triggers an automatic stop by something forcing playback to stop.
If I skip to the next track in a playlist, that does not result in the
updating of the resume point (possibly this should be treated as an
explicit message from the user that the file is complete, as this is
what it would mean if I ever intentionally skipped tracks on the chapter
I've selected in an audio book, or skip to the next podcast in a series).
Some additional features which could add flexibility:
A "return to resume point" option in the context menu that, before a
file ends, returns to the resume point the file was started from.
A "stop without saving resume point" option in the context menu that
stops playback without generating a resume point.
A "queue for resuming" option in the context menu that queues up a song
in such a way that when it is reached in the playlist it would resume.
This would allow most of the functionality of in-playlist resumes
without it ever being an "implicit" behaviour that happens to users
rather than happening when users explicitly ask for it, and allows a mix
of multi-part long audio and collections of single incompletely listened
to files without one or the other not working with the feature.
Received on 2010-12-16