6 commits

Author	SHA1	Message	Date
He Junyan	9b0f041ded	libs: dec: h265: Consider chroma_bit_depth to choose chrome type ... For some main-10 stream, sometime the luma is 8 bits while chrome is more than 8 bits, which cause using the wrong NV12 surface as the render target and decoding error. Fix #176	2019-06-28 16:49:51 +02:00
Wangfei	619abbdeb4	libs: dec: h265: add 422 chroma format support. ... Add main-422-10 profile which support 422 chroma format stream. Currently, this feature is only supported by media-driver in Icelake. https://bugzilla.gnome.org/show_bug.cgi?id=797143	2018-09-27 11:55:04 +02:00
Víctor Manuel Jáquez Leal	a07ff9641c	libs: remove unused header ... Since libgstvaapi is not distributed, there is no need to check for private header inclusion. Thus removing it. https://bugzilla.gnome.org/show_bug.cgi?id=786119	2017-08-13 18:08:19 +02:00
Víctor Manuel Jáquez Leal	3b8b2ff36c	libs: utils: move gstvaapisurface.h to private headers ... Since the utils don't expose API defined in gstvaapisource.h, it is moved to their private headers where they are used. https://bugzilla.gnome.org/show_bug.cgi?id=786119	2017-08-13 18:08:19 +02:00
Sreerenj Balachandran	61045041c4	Add 10 HEVC 10 bit decoding support ... Only supporting vaapidecode ! vaapisink combination for now. Missing dependencies: 1: No support for P010 video format in GStreamer 2: No support for P010 vaGetImage()/vaPutimage() in vaapi-intel-driver 3: As a result of 1&2 , we have no support for Vaapi Video memory mapping through GstVideoMeta. Right now we only set chroma format (YUV420 with more than 8 bits per channel) for surface pool and keeping GST_VIDEO_FORMAT as ENCODED. The underlying format of the surfaces is implementation (driver) defined, which is P010.	2015-12-08 16:14:11 +02:00
Sreerenj Balachandran	8c5f1b1c4b	HEVC: Add codec utility methods to core libgstvaapi ... Signed-off-by: Sreerenj Balachandran <sreerenj.balachandran@intel.com>	2015-04-13 14:53:46 +03:00