[Bug 734412] multiqueue: The buffering logic can lead to a pipeline stuck in PAUSED forever

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=734412
  GStreamer | gstreamer (core) | unspecified

--- Comment #6 from Thibault Saunier <tsaunier at gnome.org> 2014-08-11 08:25:06 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
> > Review of attachment 282767 [details] [details]:
> > 
> > > Otherwise your patch looks good, just not sure if that's the correct solution as it basically disables buffering completely for such pipelines.
> > 
> > It does not disable buffering completely, it will just not buffer in a quite
> > rare case where we have one single queued emptied while the other is full. It
> > will most probably buffer when that full single queue get s a little bit
> > emptied.
> 
> Ok, so we would start buffering when that single queue gets a bit emptied...
> but is something going to send buffering=100% once it's full again on probably
> the next buffer? And does it even make sense to buffer for such a short amount
> of time then? You would always jump between buffering and no-buffering.

It will send buffering=100% when the most emptied queue ready.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.