From: Paul Louden <paulthenerd_at_gmail.com>
Date: Sun, 26 Dec 2010 20:06:09 -0600

On 12/26/2010 6:21 PM, sideral wrote:
> Here's another thought. As I mentioned before, I view the autoresume
> position as a per-track feature (hence, it has its place in the
> database), whereas bookmarks take snapshots of playlists. Arguably,
> what you want for your audiobooks is a bookmark, not a resume point for
> each track. You shouldn't be using autoresume for your audiobooks at
> all (that is, enable autoresume for your Podcasts directory only).
>
> (I know that right now, bookmarks don't work when taken from a
> database-generated playlist. That should be fixed -- by someone
> else. ;-)

I don't see why "bookmarks" and "resume points" should be different in
the end - there's a bookmark on stop function. It would make sense to
replace the existing bookmark function with a better one that has the
capability of the necessary automatic resuming behaviour.

There really shouldn't be two separate ways of storing the last position
in a track, and while that's necessary now, I think the goal should be
to incorporate the two features into one, not make them explicitly
separate, actually.
Received on 2010-12-27