GNOME Bugzilla – Bug 720737
vaapisink: add system memory caps to template caps
Last modified: 2014-01-15 10:27:09 UTC
This is a follow-up to bug #703271. Since vaapisink supports raw YUV buffers, then this must be signalled in the static templates too. Next, the CAPS query will make it possible to fine tune the exact set of supported formats.
Created attachment 264537 [details] [review] expose the raw video formats in static caps template Expose all raw video formats in the static caps template since the vaapisink is supporting raw data. We will get the exact set of formats supported by the driver dynamically through the _get_caps() routine.
Per previous comment, gst_vaapisink_get_caps_impl() needs some arrangements to avoid duplicates from the template pad caps. e.g. remove formats from what we get from the template pad caps, or don't actually use gst_static_pad_template_get_caps() but rather build clean caps that only mention the first series for caps with memory:VASurface feature.
commit dd6751ed47c8c7c2d69c25cbeb2d064d8fa96d66 Author: Sreerenj Balachandran <sreerenj.balachandran@intel.com> Date: Wed Oct 9 13:47:54 2013 +0300 vaapisink: expose the raw video formats in static caps template. Expose all raw video formats in the static caps template since the vaapisink is supporting raw data. We will get the exact set of formats supported by the driver dynamically through the _get_caps() routine. https://bugzilla.gnome.org/show_bug.cgi?id=703271 https://bugzilla.gnome.org/show_bug.cgi?id=720737 Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>