Closed hydrosIII closed 2 weeks ago
Hi and thanks for reporting. We are currently looking at this operator so hopefully we should be able to get back to you soon.
Hi, We are facing this issue with the normal buffer operator also.
Same issue with version 2.1.4 Liquidsoap 2.1.4
I can confirm the same issue with rolling release liquidsoap 2.2.0+git@f3df74f81
I get:
14:06:50 [adaptativo:3] Buffer emptied, start buffering...
14:06:50 [mksafe.2:3] Switch to safe_blank.2 with transition.
14:06:50 [source:4] Source replay_metadata gets down.
Issue solved with new change introduced in liquidsoap version 2.2.4-1 about managing long running streams. @toots Thank you very much for your hard work. I made a small donation to the project.
Thank you!
We have a server playing a stream from the internet. We have some clock issues and latency issues so we have implemented buffer.adaptative as a solution however, sometimes the buffer gets emptied. That is normal, the only problem is that is not starting again, but it is stalling the entire program. So we have a script to restart liquidsoap every x hours. We are always trying to restart liquidsoap before the buffer gets full, so it does not gets emptied.
The number of hours when the buffers get emptied varies, but is after 3 hours of running. We are restarting every 4 hours liquidsoap.
The desired behaviour is that after the buffer gets emptied it restarts and the program continue to run, so we can at least restart the program every 12 hours or so. Or do not restart it at all.
Is there any mistake in the usage of the buffer? Maybe this is a config option? Is there a way to ensure that it will restart after it gets emptied?
The relevant lines of the log are:
We do not have more logs even if we set to the max debug.
Liquidsoap version: Liquidsoap 2.1.3. Installed trough .deb package. Debian buster.
The relevant script:
The relevant line is this: