Hi: I am running Liquidsoap (currently version 1.11) on a Raspberry Pi for a simple live streamer/archiver from an audio input. I am also running a local Icecast server on the Pi, to which Liquidsoap connects, which is then relayed by another, larger server. I have done this because I've noticed that archiving breaks if Liquidsoap loses connection to a remote Icecast server for any reason. A friend wants to set up a similar system in a very remote location on an unlimited LTE data connection where incoming ports aren't an option, so the local Icecast trick won't work without some workarounds involving tunneling and other scary things.
So, my questions are these: Is there a way within Liquidsoap itself to insure that Liquidsoap continues to archive what would be streamed if the connection drops? If not, what is the best strategy for piping a live Alsa audio input through another application that does the archiving, then back to Liquidsoap for streaming? I am currently addressing the audio device as hwplug:1,0, and other applications can't simultaneously record from this input while Liquidsoap has the device open. I currently rotate archives once an hour at the top of the hour. I could do this with SoX, I suppose, but not sure how to avoid glitches when the process launches for a new archive. Maybe there is a better way that doesn't require restarting the process. Thanks for any help. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
