3 commits

Author	SHA1	Message	Date
Víctor Manuel Jáquez Leal	9845ec68dc	va: add vapostproc element ... Video postprocessor for VA-API Funcionalities: resize frames, change format, import buffers, apply filters (such as denoise, sharpen, orientation, if driver offers them). Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1529>	2020-09-23 18:19:22 +02:00
Víctor Manuel Jáquez Leal	f7cfb422f1	va: context: instanciate VA display through GstContext ... Add all the machinery to instanciate VA display through GstContext, thus all va elements can share the same display and the user can set a custom one.	2020-08-03 19:33:01 +02:00
Víctor Manuel Jáquez Leal	79d11c2022	va: VA-API H.264 decoder and infrastructure ... New plugin with an element for H.264 decoding with VA-API. This novel approach, different from gstreamer-vaapi, uses gstcodecs library for state handling. The code is expected to looks cleaner because it uses VA-API without further layers or wrappers. * It uses the first supported DRM device as default VA display (other displays will be supported through user's GstContext) * Requires libva >= 1.6 * No multiview/stereo profiles neither interlaced streams because gstcodecs doesn't handle them yet * It is incompatible with gstreamer-vaapi * Even if memory:VAMemory is exposed, it is not handled yet by any other element * Caps templates are generated dynamically querying VAAPI, but YV12 and I420 are added for system memory caps because they seem to be supported for all the drivers when downloading frames onto main memory, as they are used by xvimagesink and others, avoiding color conversion. * Surfaces aren't bounded to context, so they can grow beyond the DBP size, allowing smooth reverse playback. * There isn't yet error handling and recovery. * 10-bit H.264 streams aren't supported by libva. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1379>	2020-06-28 11:47:35 +02:00