@toots I'm curious what that would look like and where to begin on that front.
I can definitely have the web application itself handle the schedule triggering
for these types of playlists, but the problem is that it introduces a kind of
bizarre set of pathways in the code. It would basically mean writing to LS
directly for most playlist scenarios, and then checking specifically for a
track-sensitive scheduled item and instead using the request queue.
I'm also worried that the request queue method wouldn't preserve other settings
applied to the playlist, i.e. if it was merged into a single track, I'm not
aware of a way to say, via Telnet, "play from this playlist" rather than just
"play this specific song".
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/779#issuecomment-493473285
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
