"Add To Playlist" patch

[dunno]

Thank you hardeep for all your work with this feature, Linus committed it today, great :-)

[Assimalyst]

In CVS at last, Woohoo!!! 

Great work everyone!!

[dunno]

Hardeep, i still get "error accessing playlist file" when trying to save a edited playlist by saving it to the default directory, i.e. same playlist from which the file was edited/removed from.

there seems to be no way to edit a playlist, within playlists, and saving it using rockbox, the only way i could edit a playlist, removing files, was to do it via my pc.

[hardeep]

Use a different name.  There's a problem with overwriting the playlist from the viewer.

[Sweet Spot]

So, this is the same patch, which is the playlist catalogue one right ? It's just been so long since I've inquired about it. Anyway, since this has been committed, I have to ask about its functionality. The last working version of this that I was using was back in about February or so. I have it backed up, so going back isn't a problem...

The way it worked was, when you opened an artist's folder, you'd long press the selected album, and would then be presented with the options of:

Playlist
Playlist Catalogue
rename
cut
etc...
 You'd choose playlist catalogue and would then be presented with two options:

Add to playlist
Add to NEW playlist

Adding to new playlist would then proceed to add the tracks in that album folder and you'd have to save the playlist manually. After which, you could then choose add to playlist with any single song or any album folder, and you'd have your OTG playlist.

Now however, when I choose Add to new playlist, I get the message, "playlist doesn't exist". Well, duuuh, I know that, and that's why I'm trying to create a NEW one. So, what's the deal with this now ?

[LinusN]

Re-read that message. It says "/Playlists doesn't exist". It means that the directory where the playlists are to be stored doesn't exist.

[Mmmm]

Maybe it would be better if the mesage read "playlist directory doesn't exist" to avoid confusion. Or is it customisable? I haven't had a chance to have a proper play with it yet!

[Febs]

Would someone be kind enough to write a short description of what this patch does and how it operates, and post it either in this thread or on the patch tracker?  It doesn't have to be anything fancy, just a basic rundown that I can use to write an entry for the manual for this feature without having to read through 9 pages of posts.

[Sweet Spot]

Re-read that message. It says "/Playlists doesn't exist". It means that the directory where the playlists are to be stored doesn't exist.

Alright, I'll accept that but, previously, as in older builds with this same patch, using the method that I described, actually just added which ever tracks I selected and allowed me to save those tracks in the root directory. So, essentially, it was next to the "root" playlist, as were any other playlists I chose to create. Why all of a sudden has this functionality changed ? It seemed pretty simple the way it was.

So please tell me then, what has to be done now in order to actually work with this ?

[Sweet Spot]

 So using the literal translation of what you said Linus, I created a directory named "playlists.m3u", that didn't work. Next I tried just "playlists", and that of course as you know ...worked.

This is how it goes, for those of you who need to know (I'll post it in an edit so that no one else bothers)


It's actually very simple, but a bit different from how it was done before, which is why I was confused. Rather than saving the playlist name after adding the files, you are to save the playlist name before hand.

Step one:

1) Create a directory in the root folder called "Playlists" (no quotation marks)

2) To create a NEW playlist, select the files or album folder of your choice, long click the select button, and choose "playlist catalogue"

3) Now from the 2 choices, select "Add to new playlist"

4) If you're only adding music to an already existing playlist, then choose "add to playlist", upon which you'll be shown your existing playlists.

So yeah, pretty damned simple, yet I had no idea why I couldn't access the function due to a slight change in its mechanics, and no explaination of it.

[LinusN]

I just took the latest patch from the tracker and committed it. I'm not really sure why it doesn't just create the directory if it doesn't exist. I'll have a chat with hardeep about that.

[Assimalyst]

Would someone be kind enough to write a short description of what this patch does and how it operates, and post it either in this thread or on the patch tracker?  It doesn't have to be anything fancy, just a basic rundown that I can use to write an entry for the manual for this feature without having to read through 9 pages of posts.

Hope this is of use:

The Playlist catalog allows for a track to be appended to a playlist. 

To use it a 'Playlists' folder must be created in the root directory of the player.

When a track is playing in WPS, or by selecting the track in browser / tagcache view, access the context menu and the option for 'Playlist catalog' will appear.

Selecting playlist catalog allows you to 'View Catalog', which lists all the playlists in the catalog, which can then be selected and played.

Selecting 'Add to playlist' lists all the playlists in the catalog, one of these can then be selected and the  currently playing file (from WPS) or the selected track (from browser) is appended to the selected playlist.

Selecting 'Add to New Playlist' does the same as 'Add to playlist', but creates a new playlist then appends the file to it.

When adding a number of successive tracks to playlists in the catalog the playlist that was last added to is listed at the top, then the rest are listed alphabetically.

The playlist catalog can also be 'viewed' from the main menu -> Playlist options -> Playlist catalog

HTH

[ravenlark]

Anyone know what happened to options, Add Shuffled and Shuffle Playlist ?

[LinusN]

You can also configure which directory the playlist catalog should use for storage. Create a file in .rockbox called playlist_catalog.config. So far it can only contain one item:

Code: [Select]

dir: <path_to_your_directory>
For example:

Code: [Select]

dir: /MyPlaylists
I believe this configurability is why Hardeep decided not to automatically create the directory if it doesn't exist, since the config file may be wrong.

[dropandhop]

Assimalyst,

Thanks for the description of how this all works.  Should someone get this information to Dominik (or whoever else might be responsible), so that this information can find its way into the manual?

Thanks!
A