Streams only start buffering after the channel has been selected in mixer and faded-in (Liquidsoap 2.1)
With Liquidsoap 1.4 the flow for playing streams with input.http
was like this:
- Stop stream channel to ensure any previous stream gets disconnected
- Set stream URL to channel
- Call
channel.start
- Liquidsoap connects to the stream
- The stream starts buffering, the scheduler waits for a configured timeout at minimum
- The scheduler fades the channel in at a planned timestamp
- Since the stream is allready buffered, audio starts playing instantly
After migrating to Liquidsoap 2.1 following happens:
- The stream only seems to be buffering, after the channel has been faded in.
- So, after the fade-in has happened, it takes another 15-30seconds until the stream starts actually playing.
That's why I'm suspecting the signal to buffering a stream is passed to input.http
when the source
is actually selected in the chain of sources. In my case it's the mix
source which triggers the buffering.
Other things I have tried:
- Extending the buffering timeout did not change the behaviour