Bug 63588

Summary: [IVB/HSW]CSC failed based on gst-vaapi
Product: libva Reporter: Yang Lianyue <lianyuex.yang>
Component: intelAssignee: xiaowei <xiaowei.a.li>
Status: VERIFIED FIXED QA Contact: Sean V Kelley <seanvk>
Severity: normal    
Priority: medium CC: lianyuex.yang, ouping.zhang, tienan.liu, yanx.du
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Yang Lianyue 2013-04-16 07:02:58 UTC 
System Environment:
--------------------------
Platform:HSW/IVB
Libva:        (staging) 5ec25c3d563d9ebd479a5ff978afe0a32f9cc00b
inter-driver: (staging) 1fd62ffd336293dce7d091bcea8399a40ccea21e

Test Steps: 
--------------------------
instruction code:
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
test log:
Start : image process: src fourcc: 842094158
End : image process: dst fourcc: 842094169
driver: input surface fourcc: 842094158(id:4000000)

Comments:
--------------------------
In the process of CSC in VPP, files are input from gstreamer to driver. Driver needs files with "NV12"(src fourcc:842094158), but the format of gstreamer supplied files is "YV12"(src fourcc:842094169).
Comment 1 ykzhao 2013-04-22 03:04:55 UTC 
Will you please describe the problem more clearly? What kind of conversion is expected? NV12->YV12?

Thanks.
Comment 2 Yang Lianyue 2013-04-22 04:27:43 UTC 
Gstreamer had set up "YV12", and driver output to 3D render as "NV12".
So it's a bug from driver.


(In reply to comment #1)
> Will you please describe the problem more clearly? What kind of conversion
> is expected? NV12->YV12?

Thanks.
Comment 3 xiaowei 2013-04-23 04:36:20 UTC 
patch submitted, please validate, thanks
Comment 4 Yang Lianyue 2013-04-26 06:18:33 UTC 
Test OK. Issue can't be reproduced. Close it.

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.