small follow up: -the transient disconnections appear to have magically disappeared -the metadata are now always properly filled in
I recently decided to tweak just a few settings in the liquidsoap script file and miraculously it worked! (it's now been a full day without any of the problems mentioned above): -I've put the smart_crossfade just after the call to request.dynamic. eat_blank, skip_blank -and compress, optionally- are now all located after smart_crossfade in the script. -The eat_blank and skip_blank thresholds are decreased from -30 to -35 and -40, respectively. -the smart_crossfade conservative parameter is put to false (I doubt it is related because I tried to switch its state before but I report it anyway). -The duration of each track is not computed on-the-fly but fetched using the ANNOTATE variable 'duration'. I don't know to which extent it is the combination of these specific settings or only one change in the script that solved the problems (I'll try to investigate this wkend maybe, shuffling a bit the script content). bye -- best regards, sincèrement, J.Lorec <julien_AT_ddcr_DOT_biz> Public PGP key: http://host.ddcr.biz/okay_awright/julienATddcrDOTbiz.asc okay_awright a écrit : > Thanks for your input. > > I will definitely try to help you dumping the transaction between > Liquidsoap and the Winamp Shoutcast Source plugin ASAP. > But I won't be able to do it just right now though. > > I must imperatively pinpoint and fix the source of the latency affecting > the running Liquidsoap instance on the production box first. This is > becoming really urgent and I have to dedicate all my spare time on this > pressing issue. But I'll get back to you with data very soon. > > see you (and thanks again for your prompt support.) > > Romain Beauxis a écrit : >> Le Thursday 06 November 2008 19:51:02 okay_awright, vous avez écrit : >>> regarding the ICY protocol issue, set("harbor.icy",true) was already put >>> in my conf file, and this is the problem indeed. >> Ok, I see, sorry I read too fast. >> >> It's interesting because we didn't test ICY support in harbor very >> intensively, and also because ICY protocol is not documented, so any details >> are welcome. >> >> Would you know how to capture the traffic with wireshark for instance ? >> An ASCII dump of the TCP stream when connecting to the harbor with ICY would >> be a perfect help.. >> >> Romain > -- best regards, sincèrement, okay_awright <okay_awrightATddcrDOTbiz> Public PGP key on request ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
