I am brand-new to Rockbox (and already love it!), but was very surprised when it treated my audiobooks and podcasts like any other music tracks.
I have done some reading on other posts (such as
http://forums.rockbox.org/index.php/topic,23404.0.html and those linked within that discussion), and do not see where the following has previously been suggested. Llorean (a fellow Texan -- yeehaw!) said that "Rockbox can't magically "know" which settings to load for which files," but I think there might be a way...
Within my Sansa Fuze v2's original firmware, if a track has the genre Audiobook or Podcast it is synced to the relevant folder and given special treatment, i.e. automatically bookmarked, cross-fade turned off, etc. It seems that Rockbox could automatically apply similar .cfg defaults based on those special genres as well, to avoid having to change .cfg when you switch from music to one of those.
I realize I'm new here and the discussion has probably been had and I just didn't find it...but if not, maybe a new feature idea?
Post Merge: April 06, 2011, 01:16:26 AM
Well, I have done some more snorkeling and found another relevant discussion on this topic here:
http://forums.rockbox.org/index.php/topic,25667.0.htmlI apologize if my original post came across at all as unappreciative or condemning of y'all developers -- y'all have done a great piece of work, and do a fine job of balancing features with functionality!
I do not have experience developing this type of system or working at the hardware level. But from my software background, it seems as if there should be a non-.cfg-level solution available. At its simplest we're talking about changing a handful of settings (cross-fading, bookmarking, shuffling, maybe EQ) when files of a certain type (specifically podcast and audiobook) are played. It seems that something like a macro should be able to change those -- basically automating what you would otherwise do manually before listening to those files.
I agree that the path of the previous conversations -- as extensive as implementing .cfg files recursively throughout the folder hierarchy -- was too much. If Podcasts and Audiobooks were treated as separate from the database itself, or at least as unique options (filters? views?) within the database (again, I'm coming from the Sansa Fuze original firmware paradigm), then these macros (or whatever) would run only when you launched from the podcast or audiobook view, and not worry about it if someone puts audiobook files in the middle of a shuffled playlist with music.
But that may be where my understanding breaks down -- maybe there's no such thing as a macro and those settings can't be changed without going the .cfg route. Thanks y'all for listening.