From: Cees v. E. <cee...@gm...> - 2010-06-20 15:40:20
|
Hi, I've tested the SVN on the production pc and it all worked 'fine'. Interfering the 3G signal wasn't possible but using the lan cable (disconnect/reconnect) the behaviour was quite ok. Now I have and CPU (Atom Z510 <http://ark.intel.com/Product.aspx?id=35469>) load of 70% , previously 55%. If the system is late under 100sec it tries to catchup or when late over 100 secs (Too much latency), this catchingup causes litle msec bumbs/glitshes in the backup-file. Maybe this is caused by the cpu load. One remaning item, setting the mp3 stream to mono was impossible. %mp3(mono=true, samplerate=22050, bitrate=24) didn't work Maybe a bug? I've used rev7368. grts, Ceesh On Wed, Jun 9, 2010 at 5:07 PM, David Baelde <dav...@en...>wrote: > Hey, > > 2010/6/8 Cees van Egmond <cee...@gm...>: > > I've added one testing manner by stopping the icecast server manually > after > > 1min and restarting after another 1min. > > This is what I tried on my laptop (everything local, nothing virtual) > and it worked fine. > > > Both way's showed that reconnecting by liquidsoap was possible by > > approaching the VMserver (with liquidsoap) via SSH (Putty). Only getting > to > > the logon thing was enough to let liquidsoap reconnect. > > Hope this makes it more clear, I don't see the logic. > > I don't see the logic either. Sounds more like a problem external to > liquidsoap, at least partially. I would be less surprised to see > liquidsoap take too long to attempt to reconnect, and that such a > frozen attempt gets awaken by your ssh connection, to fail and allow a > successful one next. But in your logs we see several failed attempts > that are not too slow, so it must be a different story. > > Hopefully, this weird behavior might be specific to the vmserver and > disappears on your real streaming server. The SVN version shouldn't > behave worse than 0.9.2 (snapshot) or even 0.9.1 (latest stable). > Since we are working on it, bugs get introduced sometimes, but there's > nothing that isn't fixed quickly. The main drawback, I think, is that > you might have to change your script every now and then because we > make changes at that level (some names aren't fixed yet, and clocks > will change a few things). > > HTH > -- > David > |