I am trying to determine exactly what the difference in Burst-on-Connect is between SHOUTcast and Icecast2. There are a number of players that are having difficulty with the Icecast2 Burst-on-Connect feature. To determine where the problem might be, I tried to lower the burst-size to 32768, but doing so will not allow sources to connect to the Icecast2 server. Anyone know what accepted values are here? I am also going to try to learn what the SHOUTcast method of sending this burst is, since all players I have tested do not seem to have a problem with it. I will supply this information if successful. -greg. __________________________________________________________________________ Greg J. Ogonowski VP Product Development ORBAN / CRL, Inc. 1525 Alvarado St. San Leandro, CA 94577 USA TEL +1 510 351-3500 FAX +1 510 351-0500 greg@orban.com http://www.orban.com
On Mon, 21 Feb 2005 22:09:40 -0800, Greg J. Ogonowski <greg@orban.com> wrote:> I am trying to determine exactly what the difference in Burst-on-Connect is > between SHOUTcast and Icecast2. There are a number of players that are > having difficulty with the Icecast2 Burst-on-Connect feature.I'm pretty sure the only difference here is the size of the initial burst. There are lots of other differences between the servers, though.> > To determine where the problem might be, I tried to lower the burst-size to > 32768, but doing so will not allow sources to connect to the Icecast2 server. > > Anyone know what accepted values are here?Any value is acceptable here. Zero or negative disables the feature, any positive value should work. If there's a positive value that fails, that's a severe bug, please report it (http://bugs.xiph.org). Mike
On Tue, 2005-02-22 at 06:09, Greg J. Ogonowski wrote:> I am trying to determine exactly what the difference in Burst-on-Connect is > between SHOUTcast and Icecast2. There are a number of players that are > having difficulty with the Icecast2 Burst-on-Connect feature. > > To determine where the problem might be, I tried to lower the burst-size to > 32768, but doing so will not allow sources to connect to the Icecast2 server.A change in burst-size does not affect source clients connecting, only where listeners start in the queue of stream data. A value of 32768 is perfectly ok. BTW <burst-on-connect>1</burst-on-connect> is just an alias for <burst-size>65536</burst-size> Something else will be stopping the source connecting> Anyone know what accepted values are here?it's in bytes, so any value >= 0> I am also going to try to learn what the SHOUTcast method of sending this > burst is, since all players I have tested do not seem to have a problem > with it. I will supply this information if successful.The burst for icecast is just send more data as quick as you can, I can't imagine what is different for shoutcast. If shoutcast uses 1Meg for burst then test icecast with <burst-size>1048576</burst-size> (and a queue size larger than 1Meg), see how that works out. karl
At 12:09 AM 2/22/2005, you wrote:>I am trying to determine exactly what the difference in Burst-on-Connect >is between SHOUTcast and Icecast2. There are a number of players that are >having difficulty with the Icecast2 Burst-on-Connect feature.do you have a list of these players ? Are the problems format specific ?>To determine where the problem might be, I tried to lower the burst-size >to 32768, but doing so will not allow sources to connect to the Icecast2 >server.that doesn't seem right...burst-on-connect should only apply to connecting clients, not sources...are you sure all you changed was the burst-size ? oddsock
oddsock wrote:> At 12:09 AM 2/22/2005, you wrote: > >> I am trying to determine exactly what the difference in >> Burst-on-Connect is between SHOUTcast and Icecast2. There are a >> number of players that are having difficulty with the Icecast2 >> Burst-on-Connect feature. > > > do you have a list of these players ? Are the problems format specific ?I've tried out all sorts of clients, and the only one I found that seemed to have a problem with burst-on-connect was VLC. Perhaps there are others I didn't try, or perhaps the problems did not manifest themselves in my tests, but VLC is the only problematic client I'm aware of. Joel