Bug 69252

Summary: [IVB/HSW/BYT]Low Y/U/V PSNR when NV12 to RGBX
Product: libva Reporter: zhenxiang.li <zhenxiang.li>
Component: intelAssignee: haihao <haihao.xiang>
Status: RESOLVED INVALID QA Contact: Sean V Kelley <seanvk>
Severity: normal    
Priority: medium CC: ouping.zhang, shengyanx.zhao, shuang.he, xunx.fang, zhenxiang.li
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description zhenxiang.li 2013-09-12 07:10:18 UTC 
Environment:
--------------
libva(master): 3003999c6e5717ff94be3e2a5ec7dff08c8cad5c
intel-driver(master): d22d367eb36ae127ffebaf4cf32495593e469cd3
Gstreamer:
(0.10)76fc67b18c38e7f6c9cfacc4e4d0ed11d3b2c548
gst-plugins-base:
(0.10)1e1e6eaf3f0dd11f6618154d9739cbe3e007d206
gst-plugins-bad:
(0.10)05183675077d502aaf0e7483656f5610bb4d0f43
gst-plugins-good:
(0.10)5af6f5bfb6c3619a9ccc3b1681579aeb90e8b89a
gst-plugins-ugly:
(0.10)5ddd97ff27ffeb03298be3a02ed18e8c2674d365
Gst-vaapi:
(0.4)408cb29a7d864eb4c7e9c0ef56ad9e37cd676c29

Reproduce steps:
--------------
cmd: 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\)RGBX ! vaapidownload ! video/x-raw-rgb ! filesink location=HW.yuv
or
run csc_all.sh locates in folder /media_tools/CSC

Data:          Y_PSNR   U_PSNR   V_PSNR
ivb: NV12_RGBX 43.57655 48.23267 39.01258
hsw: NV12_RGBX 50.04727 54.10113 45.60858
sgb: NV12_RGBX 1000.00000 1000.00000 1000.00000
Comment 1 ykzhao 2014-03-28 02:55:11 UTC 
When doing the conversion from NV12 to RGBX, it will firstly do the upsampling from NV12 to YUV444 implicitly and then transform it to RGB format. During the upsampling, the interpolation is needed. In such case the different interpolation will affect the test result. The PSNR of RGBX depends on how to evaluate the interpolation.

So this bug is marked as invalid as it involves the upsampling interpolation.

Thanks.

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.