Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dean Roddey]

Hey, I was wondering if you guys could add export of the playlists to the XML data? Our CQC users would very much like to have access to the playlists they've created, but we can't present them since that data isn't exported. It seems like it would be pretty straightforward, since they are just lists of song entries.

You could always make it a configurable option to avoid breaking existing programs, and put them in a separate major XML element to distinguish them.

Even easier perhaps would be to just spit out a number in each of the song entries as you spit them out, and then a playlist could be nothing but a list of the numbers of the songs that make up that playlist, to avoid a lot of redundant data generation. Or you could not even generate the number and have the order that they appear in the file be the implicit number. We could just build a vector collection that ponts to each item as we load it, and then building the playlist would be a very quick process of breaking out the numbers and do a direct index into that vector for the actual entry.

This would be a lot of help for folks like us who are working through the exported XML, for what seems like a fairly small development effort.

[Matt]

Does File > Export Playlist or File > Export All Playlists help you or does it need to be per-file data?

This gets a little tricky because a file can be in a playlist multiple times so a simple list of playlist IDs isn't really enough.

[Dean Roddey]

It would be way nicer if it was in the same XML file as the other export stuff, and even more so if the user could indicate an image to use, and indicate what genres he wanted them to show up in.

But in the short term, just getting them into the export XML would be a good start.

It doesn't seem like a file being in a playlist would be a problem. If, during the export, you assign an incrementing count to each track as you spit it out (not the playlists but while outputing the other content.) Then the playlists would have to be made up of those files (right?), so the playlist could be just a list of space separated indices into the linear list of tracks. It wouldn't matter if the same number was in a playlist more than once, would it? If the playlist is nothing but a collection of pointers to other (non-playlist) tracks, it seems you could have a playlist that was just the same song over and over and it wouldn't matter much.

If they can apply attributes to songs in the playlist that are stored as part of the playlist data, then I could see the problem since you could have the same file in a playlist multiple times or in multiple playlists and set different info on them.