To set this up would require modifying the code in the pypo python code and would also be tricky because it would have to account for things like multiple disconnects and the calendar getting out of sync. For instance say you had 1 hour long track and disconnected on accident it would have to restart at the beginning each time.
Ok, now i get it, thanks. I guess that the most problematic thing is the calendar getting out of sync, probably restarting the current song isn’t the right way to make sure we don’t have an already started track fading in. Probably waiting for its end, replacing the remaining time with some default, like custom selected jingles could be an idea.
It could definitely be done but it would take learning how the LibreTime playout module communicates with LiquidSoap and might be a bit of work to program.
I definitely want to at least understand a bit of how the LibreTime playout module communicates with LiquidSoap, also because i would like know if the parallel stream of the current show and the MasterSource is something that is an abstraction of libretime or something that liquidsoap has as a concept/feature. I imagine that track metadata is also sent to liquidsoap from the playout code right? I’m currently trying to find out why returned icecast metadata has only StreamTitle without Vorbis specific data (Icy-MetaInt, like artist name and song name), maybe it’s the right place.