[gstreamer-bugs] [Bug 503262] queue2 in/out rate updating not needed when queue full/buffering

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=503262

  GStreamer | gst-plugins-base | Ver: HEAD CVS




------- Comment #3 from Tommi Myöhänen  2007-12-13 11:21 UTC -------
To further clarify this issue, here are some steps how this problem might
occur:

1. queue2 remains full for a while during playback. (The reason could be e.g.
badly demuxed file causes demuxer to block for a while or something else)

2. while the queue2 is full, no data flows in but time elapses -> byte_in_rate
drops

3. when byte_in_rate drops, cur_level.rate_time increases, because of the way
it is calculated

4. next when data starts flowing out again, cur_level.rate_time might have
increased well over max_level.rate_time and so queue2 still refuses to accept
more data just because it was full for a while. And because no data is accepted
byte_in_rate keeps dropping further. Recovery from this will happen when enough
bytes have flown out of queue2.

Another issue is that if byte_in_rate/byte_out_rate are to be used to estimate
network bandwidth/stream byterate, then we could exclude these special cases
where data is not flowing through the queue "normally" i.e. when queue2 is full
(no data flowing in) and while buffering and paused (no data flowing out).
Because during these special cases the in/out rates don't actually reflect
bandwidth/stream byterate. Using average values makes these problems less
significant, but I think the accuracy of the avg values could be improved this
way.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=503262.