Interesting to read that intensive programs can cause more clock drifts... On Fri, Oct 2, 2009 at 12:32 PM, Romain Beauxis <[email protected]> wrote: > Yep. Liquidsoap relies on the local time to check whether it is late or not. > If you do a small change on the local time, liquidsoap may deal with it, but > if the change is too important, it will either catchup a lot of data at once > or simply gets stuck in an impossible situation is you set the new time in the > past.
Let me be precise about how liquidsoap "deals with it": it doesn't do anything special, just realizes that it's: - too late, in which case it starts streaming fast for a moment - too early, in which case it will freeze for a moment With a small change in the clock, this will be unnoticed, but it's nevertheless very necessary, so that liquidsoap keeps in perfect sync with the real time, which is what matters (in theory) for the remote machines (icecast server, harbor clients, direct listeners, whatever). With a big clock change, liquidsoap will burn your CPU, or freeze for a long time, which will be very noticeable. And it's usually useless, because the time difference has already been "taken into account", e.g. in the form of an icecast disconnection. Cheers, -- David ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
