Hello, I'm trying to establish a radio station using Icecast but I need a recommendation about a problem. I hope you can give me some tips about the issue. My case is: my icecast server and ice cast client are in different locations and connection between these two is not so healthy. Sometimes network problems causes client to loose connection with server and this causes server to broadcast silence to the listeners. I want to get rid of this. What I wonder is if IceCast Server buffers some amount of time before broadcasting it to the listeners. I mean the stream data in the buffer can be broadcasted to listeners when connection between server and client is lost. I think if there is such kind of implementation it can help me on solving this issue. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20080610/6226a9a9/attachment.htm
How long are these interrupts caused through network failure? Does your client (streamer) not reconnect automatically? From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf Of Taner Sener Sent: Tuesday, June 10, 2008 12:25 PM To: icecast at xiph.org Subject: [Icecast] Buffer in IceCast Hello, I'm trying to establish a radio station using Icecast but I need a recommendation about a problem. I hope you can give me some tips about the issue. My case is: my icecast server and ice cast client are in different locations and connection between these two is not so healthy. Sometimes network problems causes client to loose connection with server and this causes server to broadcast silence to the listeners. I want to get rid of this. What I wonder is if IceCast Server buffers some amount of time before broadcasting it to the listeners. I mean the stream data in the buffer can be broadcasted to listeners when connection between server and client is lost. I think if there is such kind of implementation it can help me on solving this issue. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20080610/fd6e1c50/attachment.htm
Taner Sener wrote:> My case is: my icecast server and ice cast client are in different > locations and connection between these two is not so healthy. Sometimes > network problems causes client to loose connection with server and this > causes server to broadcast silence to the listeners. I want to get rid > of this. What I wonder is if IceCast Server buffers some amount of time > before broadcasting it to the listeners. I mean the stream data in the > buffer can be broadcasted to listeners when connection between server > and client is lost. I think if there is such kind of implementation it > can help me on solving this issue.The only backdating/reserving of stream data is done for the initial burst. In these cases it's difficult to handle well if you truly lose the connection, you can of course increase the source timeout and/or have a huge burst size (eg 1 Meg). These may be all you need but it really does depend on the circumstances leading up to the source client disconnection. karl.
Thanks Karl, I will test these two parameters. Regards On Tue, Jun 10, 2008 at 4:42 PM, Karl Heyes <karl at xiph.org> wrote:> Taner Sener wrote: > > My case is: my icecast server and ice cast client are in different >> locations and connection between these two is not so healthy. Sometimes >> network problems causes client to loose connection with server and this >> causes server to broadcast silence to the listeners. I want to get rid of >> this. What I wonder is if IceCast Server buffers some amount of time before >> broadcasting it to the listeners. I mean the stream data in the buffer can >> be broadcasted to listeners when connection between server and client is >> lost. I think if there is such kind of implementation it can help me on >> solving this issue. >> > > The only backdating/reserving of stream data is done for the initial burst. > In these cases it's difficult to handle well if you truly lose the > connection, you can of course increase the source timeout and/or have a huge > burst size (eg 1 Meg). These may be all you need but it really does depend > on the circumstances leading up to the source client disconnection. > > karl. > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20080610/40ac040f/attachment.htm