Burst on connect
- Thread starter tking
- Start date
I was specifically referring to burst on connect rather than burst size, which from my testing looks like it is disabled?
burst-on-connect - With this enabled, a connecting client will be sent a burst of audio data from the stream. This will have the effect of reducing the startup time for the stream from the perspective of the listener. This is due to the fact that most media players have local buffers that must be filled before the stream begins to play. This may introduce a small latency in the stream (difference in time between when the source plays a clip and the listener hears a clip). If this latency is important to you, then you can disable this feature. The latency is bitrate-dependent, but as an example, for a 128kbps stream, the latency between the source and the player is ~ 1.5 secs without burst on connect, and with burst on connect the latency is 3 secs.
burst-size The burst size is the amount of data (in bytes) to burst to a client at connection time. Like burst-on-connect, this is to quickly fill the pre-buffer used by media players. The default is 64 kbytes which is a typical size used by most clients so changing it is not usually required. This setting applies to all mountpoints.
burst-on-connect - With this enabled, a connecting client will be sent a burst of audio data from the stream. This will have the effect of reducing the startup time for the stream from the perspective of the listener. This is due to the fact that most media players have local buffers that must be filled before the stream begins to play. This may introduce a small latency in the stream (difference in time between when the source plays a clip and the listener hears a clip). If this latency is important to you, then you can disable this feature. The latency is bitrate-dependent, but as an example, for a 128kbps stream, the latency between the source and the player is ~ 1.5 secs without burst on connect, and with burst on connect the latency is 3 secs.
burst-size The burst size is the amount of data (in bytes) to burst to a client at connection time. Like burst-on-connect, this is to quickly fill the pre-buffer used by media players. The default is 64 kbytes which is a typical size used by most clients so changing it is not usually required. This setting applies to all mountpoints.
Attachments
burst-on-connect = enable burst with default buffer size (64KB IIRC).
burst-size = enable burst and use a specific burst buffer size, so it's the same as burst-on-connect, but provides more control.
We use the latter as it's more flexible. Setting burst-size to 64KB is the same as enabling burst-on-connect.
burst-size = enable burst and use a specific burst buffer size, so it's the same as burst-on-connect, but provides more control.
We use the latter as it's more flexible. Setting burst-size to 64KB is the same as enabling burst-on-connect.
