Bug 63938

Summary: [Gst-vappi-0.4]Vaapidownload can not dump YUV 4:2:2 format
Product: libva Reporter: Liu Tienan <tienan.liu>
Component: intelAssignee: Zhao Halley <halley.zhao>
Status: RESOLVED NOTOURBUG QA Contact: Sean V Kelley <seanvk>
Severity: normal    
Priority: medium CC: lianyuex.yang, ouping.zhang, zhenxiang.li
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Liu Tienan 2013-04-26 02:57:27 UTC 
System Environment:
----------------------------------------
Platform: IVB
Libva: staging branch 2b25c3439781f0b7162011627a8ad3bb6288d1bb
Intel-driver: staging branch 5bd630d4ea732818728b0a464f45739c86e08be3
Gst-vaapi: 0.4 branch dd40042d447a0b696a75172bd3ed6cd1bad23377


Bug Info:
----------------------------------
Vaapidownload can not dump the YUV file with 422 format. But it works well when dump the yuv file with 420 format.

Reproduce steps:
---------------------------------
xinit&
gst-launch-0.10 filesrc location=/home/gst_AVC_conformance/Mux_Stream/H264_640x368_frame300.MP4 ! qtdemux ! vaapidecode ! vaapipostproc ! video/x-surface,type=vaapi,format=\(fourcc\)YUY2 ! vaapidownload ! video/x-raw-yuv,format='(fourcc)'YUY2 ! filesink location=HW.yuv

Actually result: After the above steps, there is no "HW.yuv". But the cmd (2) works. So there is something wrong with "Vaapidownload".

(2)  gst-launch-0.10 filesrc location=/home/gst_AVC_conformance/Mux_Stream/H264_640x368_frame300.MP4 ! qtdemux ! vaapidecode ! vaapipostproc ! video/x-surface,type=vaapi,format=\(fourcc\)YV12 ! vaapisink
Comment 1 Liu Tienan 2013-04-26 03:04:24 UTC 
*** Bug 63937 has been marked as a duplicate of this bug. ***
Comment 2 haihao 2015-11-19 03:15:21 UTC 
This is a gst-vaapi related bug, please try the latest gstreamer-vaapi, please file a bug against https://bugzilla.gnome.org/enter_bug.cgi?product=gstreamer-vaapi if you still experience this issue.

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.