Closed prok0403 closed 7 years ago
I always found it tricky to get stable behaviour from darkice when the connection to the server is flakey or drops. I suggest to always stream to a local icecast, while the remote icecast uses this instance as relay.
This also has the possibility that you can configure the relay on the remote server as a fallback mountpoint with on-demand option active, so you only have traffic when you have at least one listener.
Obviously this makes it impossible to have a recording only when your connection drops, but I would suggest anyway to have a permanent recording that you perhaps rotate automatically and save away when wanted/needed.
Thanks for the suggestion you made Daniel! I will install a local Icecast server.
At the moment darkice fails to connect to a remote icecast server after startup, we expect darkice to stream to the local icecast server we installed. But darkice fails to start if that is the case. So after startup we think Darkice is streaming (a PID file is created), but isn't. The problem is that if there is no remote icecast server available we want at least darkice will dump the stream, what he is not doing unfortunately Someone who recognize this and is there a way how to fix this issue?
Kr Kees