I will give a little background... For more than 10 years until now im using Shoutcast 1.9.5/1.9.8 win32 on my machines. "What's working, d'ont touch". Now im changing to ice 2.4.2. The flexibility of the ice is great. but, because of the things that "hidden" from the eye im little bit afraid to make changes that will be dramatic for the listeners. So, for the beginning, at least I want to start with what I use to have and know to work with my machines. As the most of you guys qnow, the shoutcast always was "closed system". So I will try: mp3 @ 128kbps: 1. "Source buffer": when I stop the encoder (closing down), the buffer at the listener side remains full for several seconds (8...10), and only than he START to fall down to zero. So I think/guess that there is a buffer between the encoder to the server (Maybe...!) If there is, maybe it can help in some cases of unstable connection between the encoder to the server. 2. Burst/Queue size: with my stream monitor I measured that the burst size of the shoutcast (1.9.8) is 256K. And that whats lead me to the next question...someone knows what is the queue size that the old shoutcast working? Again, the issue here is not to talk about shoutcast and what she can do. My goal at this time of startig with ice is to continue with what I was have until now and from that to make changes (or not). If someone can help with that I will be glad for sure :) Thanks for reading... Good evening, On Wed, 2015-12-02 at 16:51 +0200, Yaniv Sharon wrote:> Hi, > > There is a way to increase the source buffer? > > (Not the buffer from icecast to listener, the buffer from the encoder > to server)There is no 'source buffer'. Maybe you can tell us what problem you face / what your goal is? I think we can help you better if we understand your problem a bit better. Have a nice day! -- Philipp. (Rah of PH2) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast-dev/attachments/20151207/1ca6e11e/attachment.htm
Maybe others can address shoutcast issues... Regarding buffering ... The client has a buffer. The moc client, for example, defaults to Prebuffering=64 and InputBuffer=512 (both KB). After source stops sending the stream, either after playlist finish (no repeat), file finished, error, or stop (via ctrl-c maybe), there are still packets in the network being routed to both the server and the client. This client buffer then would remain full until all stream packets delivered (ideally intime for a continuous playback). The more between hops would imply longer client buffer full after source client shutdown. These packets are most likely in the network interface queues, and, depending on router(s) queuing discipline (qdisc) traffic control / shaping setting, may be delayed, possibly until some other higher priory traffic completes. On Mon, 2015-12-07 at 01:18 +0300, Yaniv Sharon wrote:> I will give a little background... > For more than 10 years until now im using Shoutcast 1.9.5/1.9.8 win32 > on my machines. "What's working, d'ont touch". > > Now im changing to ice 2.4.2. > The flexibility of the ice is great. > but, because of the things that "hidden" from the eye im little bit > afraid to make changes that will be dramatic for the listeners. > > So, for the beginning, at least I want to start with what I use to > have and know to work with my machines. As the most of you guys qnow, > the shoutcast always was "closed system". So I will try: > > mp3 @ 128kbps: > > 1. "Source buffer": when I stop the encoder (closing down), the buffer > at the listener side remains full for several seconds (8...10), and > only than he START to fall down to zero. So I think/guess that there > is a buffer between the encoder to the server (Maybe...!) If there is, > maybe it can help in some cases of unstable connection between the > encoder to the server. > > 2. Burst/Queue size: with my stream monitor I measured that the burst > size of the shoutcast (1.9.8) is 256K. And that whats lead me to the > next question...someone knows what is the queue size that the old > shoutcast working? > > Again, the issue here is not to talk about shoutcast and what she can > do. My goal at this time of startig with ice is to continue with what > I was have until now and from that to make changes (or not). > > If someone can help with that I will be glad for sure :) > > Thanks for reading... > > Good evening, > > On Wed, 2015-12-02 at 16:51 +0200, Yaniv Sharon wrote: > > Hi, > > > > There is a way to increase the source buffer? > > > > (Not the buffer from icecast to listener, the buffer from the > encoder > > to server) > > There is no 'source buffer'. Maybe you can tell us what problem you > face / what your goal is? I think we can help you better if we > understand your problem a bit better. > > Have a nice day! > > -- > Philipp. > (Rah of PH2) > > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev
Good morning, On Mon, 2015-12-07 at 01:18 +0300, Yaniv Sharon wrote:> I will give a little background... > For more than 10 years until now im using Shoutcast 1.9.5/1.9.8 win32 > on my machines. "What's working, d'ont touch". > > Now im changing to ice 2.4.2. > The flexibility of the ice is great. > but, because of the things that "hidden" from the eye im little bit > afraid to make changes that will be dramatic for the listeners. > > So, for the beginning, at least I want to start with what I use to > have and know to work with my machines. As the most of you guys qnow, > the shoutcast always was "closed system". So I will try:I think you're over complicating stuff here. Most beginners do this. Over configurating the server and breaking it that way. The defaults of Icecast2 are very carefully chosen and work on very wide range of setups. Also Icecast2 is not Shoutcast. You can not directly compare them in terms of specific settings. The engine is very different and many concepts are very different as well. I suggest you to set up a Icecast2 server with just defaults but changed passwords (please do not add a <mount> or alter any other settings but the passwords). Then set up a test stream to it and try it out yourself and with some of your users. Test it for a few days. If you got a specific problem in that test phase we can discuss it here and solve that specific problem. I think that will work better then trying to make a apple look like a banana. You can't grow a healthy tree out of that! Wish you a good day! -- Philipp. (Rah of PH2) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part Url : http://lists.xiph.org/pipermail/icecast-dev/attachments/20151207/5b442642/attachment.pgp
I understand. about shoutcast / icecast It's something like "you can't compare cucumbers to tomatoes" :-) OK... The (default?) values at the configuration file are: <queue-size>524288</queue-size>burst-on-connect>1</burst-on-connect<<burst-size>65535</burst-size> Let's drop the hardware & bandwidth factor (I have enough from that for the amount of listeners that I serve, almost overkill) Can you tell what is the recommended values for 128Kbps? (mp3) p.s: both of the values are in kilo BYTE, is that correct? Thanks... -----Original Message----- From: Philipp Schafft [mailto:lion at lion.leolix.org] Sent: Monday, December 07, 2015 12:59 PM To: Yaniv Sharon Cc: Icecast-dev at xiph.org Subject: Re: [Icecast-dev] source buffer Good morning, On Mon, 2015-12-07 at 01:18 +0300, Yaniv Sharon wrote:> I will give a little background... > For more than 10 years until now im using Shoutcast 1.9.5/1.9.8 win32 > on my machines. "What's working, d'ont touch". > > Now im changing to ice 2.4.2. > The flexibility of the ice is great. > but, because of the things that "hidden" from the eye im little bit > afraid to make changes that will be dramatic for the listeners. > > So, for the beginning, at least I want to start with what I use to > have and know to work with my machines. As the most of you guys qnow, > the shoutcast always was "closed system". So I will try:I think you're over complicating stuff here. Most beginners do this. Over configurating the server and breaking it that way. The defaults of Icecast2 are very carefully chosen and work on very wide range of setups. Also Icecast2 is not Shoutcast. You can not directly compare them in terms of specific settings. The engine is very different and many concepts are very different as well. I suggest you to set up a Icecast2 server with just defaults but changed passwords (please do not add a <mount> or alter any other settings but the passwords). Then set up a test stream to it and try it out yourself and with some of your users. Test it for a few days. If you got a specific problem in that test phase we can discuss it here and solve that specific problem. I think that will work better then trying to make a apple look like a banana. You can't grow a healthy tree out of that! Wish you a good day! -- Philipp. (Rah of PH2)