Playlist management

[BobWs]

Hi,
Thanks for this great project. I'm testing your docker image at the moment and I was wondering if there are any plans for some playlist management like e.g. Airsonic has?

[epoupon]

Hello!
Currently playlists are managed only via the Subsonic API.
I don't use playlists myself but I can add this feature if you really want it :)
As I said in another issue, LMSv1 had them so that's not big deal to implement.
I guess the biggest issue will be to find a UI that is as simple/easy as possible.

What I got at this time was this:

• You fill the playqueue with whatever you want. And then you can save your current playqueue to a playlist (add or erase an already existing one)
• You can load a playlist in your playqueue.

Would that be OK for you?

[BobWs]

Yes, please if it is not to much trouble to implement this!

What I find important in playlist management is that I can create playlists (via the API is fine by me) and that I can export them as m3u or m3u8 and also be able to import playlists. And finally also to share playlists. These are basically the functions that I'm using with Airsonic.

[epoupon]

Would making the playlist "public", i.e. making it available for others (but others cannot modify, just copy), be ok to share playlists?

[BobWs]

Would making the playlist "public", i.e. making it available for others (but others cannot modify, just copy), be ok to share playlists?

Yes that would be okay. Thanks!

[Ke1i]

What I got at this time was this:

• You fill the playqueue with whatever you want. And then you can save your current playqueue to a playlist (add or erase an already existing one)
• You can load a playlist in your playqueue.

Would that be OK for you?

This would be awesome! I prefer the web interface than UltraSonic for some reasons. Ability to save/load playlists would be great.

Thanks for the beautiful piece of software. It has turned out to be one of my favorite things to host :)

[epoupon]

Thanks @Ke1i , I am glad this is useful for some people :)
I will add playlist management soon, likely just after #20

[northorsouth]

Hi! I just started using LMS and would appreciate this feature as well.

[FabioC4]

Yes!

A playlist feature would be amazing, even better if we could import from outside (for example, an Itunes exported playlist).

i'm running LMS on a Pi Zero W flawlessly.

[epoupon]

Hi!
As this feature is in high demand, I am planning it for the next release :)

By the way, how did you install LMS on your Pi Zero W? I thought armv7 packages would not work on armv6-based systems.

[FabioC4]

Hi!
As this feature is in high demand, I am planning it for the next release :)

By the way, how did you install LMS on your Pi Zero W? I thought armv7 packages would not work on armv6-based systems.

hahah me too, all the music streaming solutions require v7 or docker armv7 but tried LMS and all good.

I installed it with the normal Debian Buster packages, and it was pretty straightforward, no errors, java issues or deprecated packages. Amazing.

[yllekz]

Chiming in because I use a lot of playlists (m3u in particular) and these are generally standard fare for music. I would love if the app could at least read these files and have them available.

[epoupon]

About playlist import, maybe somebody here can answer this:

1. I have the feeling it only makes sense if you are admin (admin is supposed to have direct access to the files, i.e. knowing their locations. Regular users are likely to have no clue about file paths).
   What do you think?
2. What about relative file paths? Do we have to check the path starting with the scanned root directory, or should try we to match the files in any directory? (but what about same named tracks?)

[Ke1i]

Where would these playlists be imported from?
Here's what I was thinking:

• A user can create any number of playlists.
• Playlists will be available to that particular user that created them and to any other user he/she wishes to share these playlists with.
• File paths for the songs inside a playlists don't have to be absolute.

An example playlist would therefore look like:

Sleep sounds.playlist
-/sleep_sounds_1.ogg
-/sleep _sounds_2.ogg
-/Nature/Rain/01.soft.rain.mp3
-/Nature/Forests/06.rain.forest.mp3

"/" being the root folder of the music library specified by the admin during setup- it can be anything from the operating system point of view. But as long as LMS sees it as the root folder of the music library, then it'll be easier for shared playlists.

(Edit: Added more details)

[b4too]

Hello ! I stumbled upon this topic as I was looking for this exactly, I understand it is implemented as it was unpinned ? I am currently hosting it and cannot find a way to save playlists, what am I missing ?
I tried ampache, airsonic and jellyfin and so far LMS is my favorite ! If only playlists, genre and custom css were implemented it would be only better imho :)

[epoupon]

Hi!
I usually pin issues I am currently working on or willing to work on next.
If nothing is pinned, this just means some untracked change is in progress :)

Playlists can be loaded/edited/saved thanks to the subsonic API, but there is no UI for them yet.
Unfortunately I won't use playlists for myself, so this is a low priority subject for now, that's why I unpinned it.

[alexxroche]

I need playlists. To that end I've written a playlist importer that everyone is welcome to try, and epoupon can have/use/merge or rewrite in a proper language and remove all of the bugs that I've almost certainly included in my script.

[jgdye]

For what it's worth, the lack of a rudimentary playlist UI is all that is holding me back at the moment. I would say that it would be worthwhile to implement the simple UI you mentioned at the start, where it's just the ability to save the current queue, browse existing playlists, and load a playlist to the queue, and hold off on importing until you have the time/information you need to determine what would be needed for a satisfying import.

[epoupon]

Indeed you are right, we can iterate from a very basic but handy support

[epoupon]

For what it's worth, the lack of a rudimentary playlist UI is all that is holding me back at the moment. I would say that it would be worthwhile to implement the simple UI you mentioned at the start, where it's just the ability to save the current queue, browse existing playlists, and load a playlist to the queue, and hold off on importing until you have the time/information you need to determine what would be needed for a satisfying import.

That is what is done for 3.30.0 :)