System Environment: ---------------------------------------- Platform: HSW/IVB/SNB Libva: (master)ffb82f3a85e424b869c2c1ce48251b3305e2cd61 Intel-driver: (master)01f7c2c6c5ae6321f3b3cfebc89f73dcb50b30af Gst-vaapi: (0.4) c74b317807efde38575c75a3c91da8b1dd2448b6 Bug Info: ---------------------------------- Vaapidownload can not dump the YUV file with I420 format. Reproduce steps: --------------------------------- xinit& gst-launch-0.10 filesrc location=/root/media_tools/Mux_Stream/H264_640x368_frame300.MP4 ! qtdemux ! vaapidecode ! vaapipostproc ! video/x-surface,type=vaapi,format=\(fourcc\)I420 ! vaapidownload ! video/x-raw-yuv,format='(fourcc)'I420 ! filesink location=HW.yuv 0:00:00.011581863 2518 0xa22e60 ERROR GST_PIPELINE ./grammar.y:614:gst_parse_perform_link: could not link vaapipostproc0 to vaapidownload0 libva info: VA-API version 0.34.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /opt/X11R7/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_34 libva info: va_openDriver() returns 0 WARNING: erroneous pipeline: could not link vaapipostproc0 to vaapidownload0 Actually result: There is something wrong with "Vaapidownload".
Created attachment 80978 [details] [review] postproc-fix-bug-vaapipostproc-format-support modified src cap template format to 'Any', so we can set fourcc to driver manually.
Created attachment 80978 [details] [review] [review] postproc-fix-bug-vaapipostproc-format-support modified src cap template format to 'Any', so we can set fourcc to driver manually. ------------------------------------- It's my mistake , this patch has nothing to do with this bug,but relates to another bug.
this bug relates to bug63951,the patch 'postproc-fix-bug-vaapipostproc-format-support' is added for that patch, and it's fixed.So now this bug is also fixed.
gst-launch-0.10 filesrc location=/home/Mux_Stream/H264_640x368_frame300.MP4 ! qtdemux ! vaapidecode ! vaapipostproc ! video/x-surface,type=vaapi,format=\(fourcc\)I420 ! vaapidownload ! video/x-raw-yuv,format='(fourcc)'I420 ! filesink location=HW.yuv the bug is fixed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.