Rockbox Development > Feature Ideas
config per directory?
Confuseling:
--- Quote from: saratoga on September 08, 2010, 09:54:54 PM ---Buffering doesn't really matter to gapless or crossfade. Rather its about efficient use of the hard disk. On a typical hard disk based player you can only read the disk about twice an hour, so you have to figure out what config you're going to need a while in the future, load all of them, and then switch to them later.
--- End quote ---
I had no idea it was so long - thanks for the clarification.
I still think the point stands, in that the vast majority of people probably don't mix audiobooks / podcasts and music in one playlist, which is undoubtedly the main use case for this. I don't know whether the people that do jump back and forth between them a lot, but I suspect not.
For people who are going to delve into the manual to find a feature like this, they can find a warning about battery life / hard disk wear there. If they use it for different styles of music, they're going to be doing it in full knowledge of the risks.
If it proved popular for such uses, worry about reading ahead then. I like Llorean's suggestion though - don't really know enough about shuffling to know whether Torne's point is fatal. Couldn't you just honour any apparently contradictory requests, and let the user sort it out?
gevaerts:
Is per-directory config really that involved?
Is there a reason why a simple callback for PLAYBACK_EVENT_TRACK_CHANGE events (using add_event()) that checks the path of the playing file (to see if it changed since last time), checks if there's a config file there (with a specific name), and loads that config file if it's there, can't work? (except for the callback possibly being calld in an unsuitable thread, but that can be fixed easily)
Of course this would only load config files, so the user has to make sure that each such config file contains all settings that might have been changed in a previous directory. It wouldn't be too hard to also have "directory leaving" config files to make handling that a bit easier, but I think that that might not always work well.
torne:
gevaerts: that would mean spinning up the disk on every directory change... and either way, the fact that some of the desired per-directory config settings affect playback order (shuffle, repeat) is fairly significant..
gevaerts:
--- Quote from: torne on September 09, 2010, 07:20:45 AM ---that would mean spinning up the disk on every directory change...
--- End quote ---
Yes, unless dircache is enabled (in which case there's only a spin up for loading a file). That's no worse than some other settings we have (auto-change directory...)
I imagine this entire thing would be a setting though(one which is probably not very suitable for per-directory config files :)) .
If the system would support looking in parent directories (similar to the album art search), I imagine most use cases (the ones that want e.g. different settings for audiobooks and music) won't really suffer from these extra spin ups (again, assuming dircache). Only people who want per-album setiings or similar would notice.
--- Quote from: torne on September 09, 2010, 07:20:45 AM ---Either way, the fact that some of the desired per-directory config settings affect playback order (shuffle, repeat) is fairly significant..
--- End quote ---
Yes, definitely. I think it's a case of Don't Do That Then. People *can* do stupid things if they want to, and I think this wouldn't be the first case.
torne:
Controlling shuffle is one of the things the original poster in this thread (and people who've asked for similar things before) *specifically asked for*, and it's an obvious and logical thing to want if you normally listen to music on shuffle but also have audiobooks... so I don't think it's as simple as just saying don't do that :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version