RE: [cobalt-users] Using RAQ 4 as a Broadcasting Server... Choking...

["Andy Brown" <andy.brown@xxxxxxxxxxxxx>]

<snip>
> I installed "shoutcast" dsp server/relay and I am 
> broadcasting from home location and bounce it off the server 
> and than re-broadcast the stuff to multiple users.


I used to run a shoutcast server, however not on a RaQ and found that
the biggest problem was line-drop.
To narrow it down to the RaQ or line, while you've got a stream going
and listeners connected ssh into the RaQ and do top and see how the CPU
and memory are performing. Hopefully CPU won't keep spiking too often
and memory shouldn't eat into swap space (A good server is one that
never dips into swap, although I haven't yet managed to get my RaQ's to
abide by this!)

Once you're happy its not the RaQ's cpu/memory dipping out it'd be worth
looking at the quality of your link. Since all it takes is a slight
slowdown occasionally on your line for a shoutcast stream to slow or
drop connection you need to make sure you're as few hops as possible
from a high-bandwidth pipe to the net, and also that you get good ping
response from your machine from various locations.

Personally I'd be looking closely at your net providers and see if its
something either caused by them or that they do on purpose (bandwidth
throttling to avoid peaking out their link a possibility???)

Hope that gives you a few pointers.
(PS: Near CD quality for a streaming audio channel is VERY high quality,
have you tried dropping the quality a little??)

Regards,

Andy
andy@xxxxxxxxxxxxxxxxxxxxx
HOWTO's PKGs and info --> http://www.raqpak.com/ <-- for Qube and Raq