Support and General Use > Audio Playback, Database and Playlists

"Add To Playlist" patch

<< < (27/29) > >>

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:

--- Quote from: Febs on July 20, 2006, 09:20:56 PM ---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.

--- End quote ---

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: ---dir: <path_to_your_directory>
--- End code ---

For example:


--- Code: ---dir: /MyPlaylists
--- End code ---

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page