Rockbox Development > Feature Ideas
Streamline playlist handling
Chronon:
--- Quote from: jim234567 on June 13, 2011, 01:59:13 AM ---Chronon, I did not mean to suggest you had said it should go in the Database itself or anywhere else, I was simply pointing out that you seemed to understand where I was coming from. Seems no one else here does though so I guess I'll just have to leave it at that.
--- End quote ---
I know. I just wanted to clarify what I was saying.
Don't be put off by the criticism. Every feature that gets added to Rockbox rightly gets met with a healthy dose of criticism. Especially for features to be added to the core binary it must be shown that the feature provides additional functionality and benefits that outweigh the costs of added binary size.
--- Quote from: bluebrother on June 13, 2011, 02:00:09 AM ---To put it in your words, you seem to be pretty adamant to accept that there are ways to achieve what you want. There's no need to resave all playlists, and putting all playlists on the player into a single folder is for sure a bad idea for all those people that intentionally split them across folders. So you're basically saying to make things more like the way you prefer it we should make it worse for all people that have a different approach.
While I can see that there are possibilities to improve things the suggestions you made are simply to short sighted and therefore not acceptable.
--- End quote ---
So, how about a plugin that processes playlists containing relative paths and saves a copy with absolute paths in the playlist catalog? This makes it happen for those who opt-in only.
sideral:
--- Quote from: jim234567 on June 12, 2011, 06:29:59 PM ---
--- Quote ---Where do you put playlists in for this? A playlist has no metadata so it cannot be indexed for the database. That's simply a fact. So you end up with using a file browser to select the playlist file you want to use, and that's exactly what Rockbox does. If there really is a sensible way to "index" a playlist file please explain it to me.
--- End quote ---
I'm only suggesting it handle it like other players do.
When it's scanning your files ("Refreshing", to use Sansa's word for it), it automatically takes any playlist file it finds, (I assume scans it and generates whatever code it needs for it internally) and then shows it under a heading called "Playlists" on it's menu where it can easily be found by the user.
--- End quote ---
As others have explained, a playlist scan would be a poor fit for the database as it is designed today; a file-based solution is much simpler and more robust. That said, I'm certainly open to considering new metadata types for the database, including playlists and cuesheets.
My view differs from bluebrother's in that I regard playlists as plain metadata. A playlist is similar to an album in that it references an ordered collection of tracks. If the database could store N:M relations (which it currently cannot), it would be trivial to add a query to the Database menu that listed all playlists, and then the tracks in a playlist.
--- Quote from: jim234567 on June 12, 2011, 06:29:59 PM ---What it could simply do is upon finding a playlist file, it can scan it, then simply create a new file for itself the same name as the list scanned, and drop it in the Playlist folder automatically. Very simple. Then when the user opens Playlists on the main menu, he/she would see it already there, all he has to do is select it, and it will load and play.
--- End quote ---
I agree this would be simple, non-database solution to your problem. This scan could be achieved by a simple plugin or perhaps even a Lua script. Rockbox has a plugin-autorun mechanism (disabled by default) that could be used to run this automatically after each boot (not sure though whether it can pass a script name to the Lua plugin).
Navigation
[0] Message Index
[*] Previous page
Go to full version