[gstreamer-bugs] [Bug 503262] New: 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
           Summary: queue2 in/out rate updating not needed when queue
                    full/buffering
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ext-tommi.myohanen at nokia.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


I think queue2 byte_in_rate shouldn't be updated when the queue2 is full, i.e.
when no data flows to queue2. If queue2 stays full for a while for some reason
it will cause increase in cur_level.rate_time making it "even fuller" and might
unnecessarily prevent data flowing in. Furthermore if byte_in_rate is to be
used to estimate available network bandwidth then queue2 fullness shouldn't
affect it.

Also if byte_out_rate is to be used to estimate stream byterate, then it could
be updated only when pipeline is playing, i.e. not when buffering and paused.


-- 
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.