On Fri, 22 Mar 2013 04:54:23 -0400, David Baelde <[email protected]>  
wrote:

> Hi kronos,
>
> On Thu, Mar 21, 2013 at 11:30 PM,  <[email protected]> wrote:
>> We are running six streams from a single script (128, 96, 64 and 32 kbps
>> mp3; 64 and 32 kbps ogg - all Icecast 2.x) under LS 1.0.0.
>
> The first question is whether you need those six outputs to belong to
> the same script. Otherwise, the best way to isolate them is to run six
> separate scripts.


Prior to upgrading from LS 0.93 to LS 1.0.0, we ran three scripts: 128  
kbps mp3, 96 kbps mp3, and one with 32, 64 kbps mp3 and ogg. It worked  
well without many catchups or restarts. After upgrading, these problems  
did not re-appear so we consolidated all streams into one. At that time,  
our IP upgraded to FreeBSD 8.x. After that, the single script started  
showing catchups (around 1 sec +) after every new source was loaded and  
began playing. So, to answer the question, no, we could run six scripts  
(with an increase in memory consumption).


>
> If your six streams share a common source, then it makes sense to use
> clocks. I can help you install them, but I need the relevant portion
> of the script, ie. where the six streams start to differ.


The six streams differ only in the bitrate outputs, port number, and mount  
points. 'Common source' would be the separate shows - I've provided a  
sample of Friday's switch:

            ({08h00-08h15}, moap),
            ({08h15-08h20}, msc),
            ({08h20-08h30}, mmlp),
            ({08h30-09h00}, hcmbt),
            ({09h00-09h30}, rarrc),
            ({09h30-10h00}, twop),
            ({10h00-10h30}, sfs),
            ({10h30-10h50}, jvsd),
            ({10h50-10h55}, gly),
            ({10h55-11h00}, mmel),
            ({11h00-11h40}, csr),
            ({11h40-12h00}, cosm),
            ({12h00-13h00}, yap),
            ({13h00-13h30}, btg),
            ({13h30-14h00}, atdp),
            ({14h00-15h00}, mh),
            ({15h00-15h10}, codm),
            ({15h10-15h20}, hsip),
            ({15h20-16h00}, csoc),
            ({16h00-16h45}, wotc),
            ({16h45-17h00}, ifhs),
            ({17h00-17h40}, csr2),
            ({17h40-18h00}, cosm2),
            ({18h00-18h30}, cil),
            ({18h30-19h00}, jily),
            ({19h00-19h30}, gsm),       
            ({19h30-19h50}, jvsd2),
            ({19h50-20h00}, emed),
            ({20h00-20h30}, rarrc2),
            ({20h30-21h00}, lmac),
            ({21h00-22h39}, sp),
            ({22h39-23h00}, mfts),
            ({23h00-23h01}, eod)

>
> Using clocks will isolate streams, so that if the problem causing the
> catchup is limited to only one stream, then only that stream's output
> will be reset.


I'm not clear whether you mean isolate streams using clocks in a single  
script or multiple scripts (i.e., one for each stream).

No soundcard input, brand-spanking new disks.

The relevant part of the script would then seem to be the output section:




       # == ICECAST MP3 32 OUTPUT ==


            output.icecast(%mp3(bitrate=32, mono),
              host="ruralcatholicradio.com",
              port=8014,
              password="",
              mount="icmp3-32",
              name="Rural Catholic Radio",
              description="Classic Roman Catholic prayers, meditations, and  
music - 32 kbps",
              genre="Christian, Catholic, Prayers, Music, Meditations,  
Religious",
              public=true,
              url="http://www.ruralcatholicradio.com:8014/icmp3-32";,
            mean(radio))

>
>> I have attempted to isolate the problem, but have determined it
>> cannot be CPU, memory, bandwidth, nor network lag.
>
> Do you have a soundcard input somewhere? could it be the disk?
>
> Cheers,


-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to