[Bug 793338] videometa: add support for encoder parameters to ROI meta

[GStreamer (GNOME Bugzilla)]

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

--- Comment #4 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
(In reply to Hyunjun Ko from comment #3)
> In gstreamer-vaapi, we're using GstCustomEvent to achieve roi encoding
> because
> GstVideoRegionOfInterestMeta is not enough to use all suppored parameters
> for vaapi encoders.

Which this proposal is about, we also have time to revert back to something
more "standard" in gstreamer-vaapi before the release. The custom event has
some design issues. You must send an event to remove them, you cannot have two
ROI on the save rectangle with two different meaning, no hierarchy, it cannot
be exercised from gst-launch-1.0 (which means it will get low validation).

What we are experimenting on the gst-omx side, is adding a property for the
"default" value. You can then from gst-launch-1.0 combine facedetect that
always attach ROI and this to exercise the API manually.

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