Hi, On Wed, May 23, 2012 at 1:23 AM, kostas mitro <[email protected]> wrote: > The problem is when the system boots and the liquidsoap starts playing the > first track the cpu is 100% only for liquidsoap until the track changes.
This is really weird. It's normal that startup is costly, because liquidsoap prepares some files in advance. But that doesn't explain why the 100% CPU period would last exactly during the first track. If you confirm this, please file a bug report: we should fix it. > output.icecast.lame(...) By the way, it's cool to hear that liquidsoap runs OK on small machines like your NAS. However, you may want to give it a break. You have a fairly old version of liquidsoap, but with the more recent ones you can use output.harbor() instead of output.icecast(). This has two effects: (1) clients can connect directly to liquidsoap, without icecast in the middle and (2) more importantly, liquidsoap doesn't encode anything when no client is connected. I think it would also be cool to find a way to make liquidsoap stop its inputs when no client is connected, to avoid useless disk activity. This should be doable with on_(dis)connect handlers but I have never done it. Have fun! -- David ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
