[Icecast] IceCast KH - question

Live Mix - Arvy arvy2013 at livemix.com.br
Mon Jun 10 16:43:24 UTC 2013

Hello Thomas and Karl, thank you for your answer and time.

We've tested with several listeners and different connections, using 
WinAmp and JW Player. For about 15 minutes, everything is ok. After 
15-18 minutes, WinAmp starts do blink that "red square" (packet loss or 
instability), and after about 20 minutes sounds starts to "pop", with 
small cuts, and then starts to cut a lot. I think the problem is 
progressive: more time, more cuts.

We use SAM Broadcaster to encode AAC+ HE 48k. We're using the latest 
IceCast KH version, Win32.

Other datail: all users have always "Lag: 0" on Admin interface

If you want to listen what happens, if you can and have time (very 
appreciated) the stream is http://mp4.livemix.com.br/livemix - if 
possible using WinAmp. Wait about 15-20 minutes to see the problem.

Any ideas I really appreciate, because we have about 100-200 listeners 
at same time we really don't know what to do :(

Thanks a lot,

> On 06/06/13 17:13, Live Mix - Arvy wrote:
>> Hi there,
>> we use IceCast KH on our webradio, no commercial. We have an issue that
>> we dont know where to look. When listening using WinAmp (but in other
>> players too like JW Player), after 70 or 90 minutes, we realize that the
>> "green square" on top of WinAmp becomes a "red square". About 60 minutes
>> after start, sometimes the "red square" blinks, and then more
>> frequently. It happens with different internet connections and
>> providers. Until 60 minutes, the broadcast is perfect.
>> Can you give me an idea where to look or solve this issue? It's related
>> to Icecast, or encoder, or internet connection, etc?
> My initial guess would be the encoder sending rate being mismatched 
> with the samplerate.  When a player reports an issue it needs to be 
> clear on what it is relating to, but I suspect it will be down to a 
> starvation of the incoming data.
> Any issue within icecst here would should as an increased lag value 
> for that listener on the admin page, icecast will send a lot faster 
> than the source but is still subject to certain limits like CPU or may 
> be a per-mount limit (limit-rate is set).
> If it is affecting multiple listeners at different locations at a 
> consistent offset into the stream then the sending rate from the 
> source is suspect. May be a 44k/48k mismatch or a bad clock on the 
> source client.
> karl.

Live Mix

More information about the Icecast mailing list