[Bug 792039] h26{4,5}parse: expose chroma format and bit depth in caps

[GStreamer (GNOME Bugzilla)]

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

--- Comment #6 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
(In reply to Tim-Philipp Müller from comment #4)
> Why is it not enough to pick decoders based on supported profiles here?

It's a hint to the decoder so it can reduce the size of the first output buffer
allocation. If you only look at the profile, you endup always allocating that
buffer as if it was going to be the higher depth supported. In general this
field can be ignored. I only expect to see this appear in fixed caps to be
honest.

In the specific figure, we have limited RAM considering we are handling 8 x 4K
streams. In addition to that, we are still using CMA, so allocating memory
takes a lot of time. By guessing better the output allocation, we end up not
having to reallocated and copy later on, saving in startup latency and RAM at
the same time.

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