Closed gammaw closed 5 years ago
@gammaw Are you on the latest rolling-release update, rather than the latest release version?
@SlvrEagle23 my installation is on commit #59c896a, which is the latest commit on the master branch.
@SlvrEagle23 it seems to be the transition's fault. If I remove the transition part in my custom Liquidsoap config (see below) then there is no error but also there is no fading. Like I said it did work with 0.9.4.1. Why is that?
radio = switch(track_sensitive=false, [
#Monday
({1w and 16h-17h}, once(playlist_szmuti_csorba)),
...
({true}, radio) ])
@SlvrEagle23 problem solved. The jingle playlist must be a custom playlist. I had it as an Azura playlist because I'm using it also between songs in Azura playlists. And it worked like this in 0.9.4.1. Anyway, now I have to jingle playlists one custom and one Azura sharing the same songs.
We have custom playlists (scheduled shows) that interrupt standard playlists (in-between music) at specific times. We know that Azuracast 0.9.4.1 introduced interruption but our custom playlists come with nice fading and other features.
The problem now is that on a 0.9.4.2 Docker installation (running on ubuntu-16-x86-64) the station starts, plays music from a standard playlist but then (at a specified time) Liquidsoap fails to start a custom playlist and stops. Here is the Liquidsoap log:
I compared the generated Liquidsoap config in 0.9.4.1 and 0.9.4.2 and noticed that the latter introduced "cue cuts".
In 0.9.4.1 a playlist config looks like this:
in 0.9.4.2 like this:
What are cue cuts, why are they needed? Do they have to do with the error? If not, do you have any idea where the error comes from?
Another detail may also be relevant: I'm using a fresh installation on a new VPS. I have v0.9.4.1 on another machine where things work well. The two VPSs should be identical except the Azura versions.
Btw, our custom Liquidsoap config is something like this: