Hi, On Sat, Apr 23, 2011 at 1:04 PM, domenico d'agostino <[email protected]> wrote: > 23/04/2011 11:55:13 [clock.wallclock_main: 2] Too much latency! > Resetting active sources ...
This is a normal consequence of stressing liquidsoap. More precisely, if it doesn't have enough computational resources (e.g. CPU) it'll lag, and eventually reset its outputs to avoid absurd latencies. This can be tweaked through the root.max_latency setting (which should maybe be reset to clock.max_latency, or made a parameter of clock(), but this is off-topic). > 23/04/2011 11:58:22 [pf_u120: 2] Connection failed: > Could not read data from host! I can't say much about this error. What is pf_u120? If it's an icecast output, it might be a little weird that it can't reconnect because of the stress. Cheers, -- David ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
