Bug 456 - Streaming low bitrate audio can result in long buffering times
: Streaming low bitrate audio can result in long buffering times
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming To SlimServer
: 5.x or older
: PC All
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-07-22 14:30 UTC by Jim Knepley
Modified: 2008-12-18 11:51 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Knepley 2004-07-22 14:30:28 UTC
(cut-n-paste'd from Dean's posting to the dev' list)

You are right, this is a definite problem for many streams.  Some low bitrate
streams do allow substantial prebuffering and will start up quickly, but some do
not.
  In general, we don't know the bitrate of the stream (it might be VBR) but we
do have two ways to guess:

1.  The inclusion of a bitrate header "icy-br" may indicate the intended bitrate.
2.  Measure the rate of data as it comes in.

Either way, I think that the best measure would be to max out the pre-buffering
time at some duration, say 10 seconds, and start playing even if the buffer
isn't full.  If it runs out, then it's likely that the station isn't going to be
able to sustain playback in any case.

And including a warning saying that we're buffering is a really good idea and
shouldn't be that hard to implement...

Could you create a bug on https://bugs-archive.lyrion.org with your thoughts (and
mine) so we can track this and make sure it gets fixed?

thanks,

dean

On Jul 22, 2004, at 9:31 AM, Jim wrote:

> I've been working with the Live365 plugin and I've come across a shortcoming
in Slimserver...
>
> The size of the streaming buffer is constant (eight seconds of 128kbps), and
the player stays in a "buffering" state until it fills half the buffer.
>
> For low bandwidth streams, this can lead to very long delays (upwards of 15
seconds) during buffering where no sound is output, and there's no indication of
what's happening.
>
> The research I've found on dynamically recalculating buffer sizes based on
traffic patterns involves math that's beyond my skills to implement, and it
possibly unnecessary anyway.
>
> So to my question: how does the SqueezeBox know what the stream bitrate is? If
a program could get that, as long as we're looking at CBR streams, the buffer
size could be dynamically and easily computed to minimize buffering delay on a
per-client basis.
>
> Alternately, a "Buffering: xx% complete" message on the display would at least
give some indication of activity, but then you're looking at a message instead
of listening to music...
>
> Jim
>
> _______________________________________________
> Developers mailing list
> Developers-8kkgcvHRObwvDzVnOqYaopqQE7yCjDx5@public.gmane.org
> http://lists.slimdevices.com/lists/listinfo/developers
>
Comment 1 Blackketter Dean 2005-03-11 14:35:20 UTC
Please confirm and reopen if not fully addressed.
Comment 2 Chris Owens 2006-06-16 14:40:27 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Comment 3 Chris Owens 2008-12-18 11:51:23 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.