[Bug 797100] videoaggregator: allocation query management makes buffering suboptimal when using dynamic/live pipelines

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=797100

Nicolas Dufresne (ndufresne) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicolas at ndufresne.ca

--- Comment #3 from Nicolas Dufresne (ndufresne) <nicolas at ndufresne.ca> ---
The trade-off is the following. If you are using a downstream allocation, it's
possible you'll be holding on a dead object by using it's pool. I don't think
we have a mechanism to know right now if the downstream element have changed.
It comes back to the "pool reclaiming" problem.

Also, if the new downstream offer a pool that works in zero copy and you were
not yet operating that way, you also endup in sub-optimal situation if you skip
allocation. Though, if the caps haven't change, and you already have an optimal
allocation, the serialized query is particularly harmful.

That of course does not prevent that we may have a bug in the new allocation
code that may be making everything worst (e.g. sink pad can't queue while src
pad thread is blocked).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.