Hi Andy, I'll assume that you're using a recent liquidsoap, 1.0 or close to it, featuring clocks. With your setup, if you didn't do anything special, the icecast and ALSA outputs are attached to the same clock (which would be the ALSA clock, because ALSA insists on belonging to this particular clock). As a result, a lag in one output results in a lag for the other.
This could explain that when you restart the remote server, ALSA becomes silent for a while: due to the lag, it looses synchronization (it should complain about xruns in the logs). However, this bad situation should stop when icecast realizes that it has lost its connection (timeout on send + failed attempt to reconnect immediately). Some info from your logs may help clarifying the situation. In any case, you can minimize these problems by separating your outputs in two clocks, with a buffer in between. This is described in http://savonet.sourceforge.net/doc-svn/clocks.html Hope this helps, -- David ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
