Icecast Streaming Media Server

[Anonymous]

Hi there,

this is the second time we have had this issue,

at some point ( after days of working smoothly) the oddcast (standalone) reduces the bitrate from 128 to 116 , and users cannot connect to the icecast anymore. A re-connect solves the problem.

Since we are trying to set up a 24/7 system here this is quite an issue we would like to solve

Perhaps anyone has had this experience too.

the oddcast log only displays a slow reduction
04/13/08 10:15:27 Info(MainWindow.cpp:703): 129 Kbps (/test/stream1.mp3)
04/13/08 10:15:32 Info(MainWindow.cpp:703): 127 Kbps (/test/stream1.mp3)
04/13/08 10:15:37 Info(MainWindow.cpp:703): 123 Kbps (/test/stream1.mp3)
04/13/08 10:15:42 Info(MainWindow.cpp:703): 116 Kbps (/test/stream1.mp3)
04/13/08 10:15:47 Info(MainWindow.cpp:703): 117 Kbps (/test/stream1.mp3)
04/13/08 10:15:52 Info(MainWindow.cpp:703): 116 Kbps (/test/stream1.mp3

exactly at this time users cannot connect to stream anymore. The icecast server is still running for many other streams and we haven't got access to the icecast errorlog

any ides?

[karlH]

icecast does not care about the bitrate of mp3 so changes to that won't affect the new connections. Only the error log will indicate the reason for new listeners are being rejected, possible the return code that a listener receives. The only time I've heard of mp3 bitrate changes affecting listeners is with windows media player which is usually a reason why people stick with CBR.

karl.