Bug 68009 - [gst-vaapi-master ]Low ssim value when decoding some AVC files
Summary: [gst-vaapi-master ]Low ssim value when decoding some AVC files
Status: CLOSED MOVED
Alias: None
Product: libva
Classification: Unclassified
Component: gst-vaapi (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: haihao
QA Contact: Sean V Kelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-12 08:41 UTC by zhenxiang.li
Modified: 2014-02-17 02:13 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description zhenxiang.li 2013-08-12 08:41:13 UTC 
Environment:
--------------
Platform:          IVB
libva:             (staging)bc49c42bcbfb24286c06b3e7cdb171b2a01c6f80
intel-driver:      (staging)232ef48766c1f91a87a3d41f951fd2ac26dcf2ae
gstreamer:         (1.0)c329cc3aeb9fd8614cae38a8eab50958229a9502
gst-plugins-base:  (1.0)ffc5262119c9277fcc0c5455e0fdc727338ce3a7
gst-plugins-bad:   (1.0)61885ba1bcb6f2ff21d3909d83aca46fec3da8d9
gst-plugins-good:  (1.0)c52279fed1f72fa7d4e18008b490a988ac04b8dd
gst-plugins-ugly:  (1.0)3baded20ffcabb9e0077e009bba8002400698271
gst-plugins-vaapi: (master)a15d5839b6f49b4acef623e4bad1b5f869d21aa7

Bug Info:
--------------
Low ssim value when decoding avc files are as follows: 
CVWP2_TOSHIBA_E.264
CABA3_TOSHIBA_E.264
CVWP3_TOSHIBA_E.264
FRExt_MMCO4_Sony_B.264
CVCANLMA2_Sony_C.jsv
CABAST3_Sony_E.jsv
CABASTBR3_Sony_B.jsv
MR6_BT_B.h264
MR8_BT_B.h264
FRExt1_Panasonic.avc
FRExt3_Panasonic.avc
cama3_vtc_b.avc
cama2_vtc_b.avc
cama1_vtc_c.avc
FRExt2_Panasonic.avc
FRExt4_Panasonic.avc

one of the results is:
CVWP2_TOSHIBA_E.264	FAIL	0.923078	0.996102	0.126152	0.90257	0.478192	0.93592	90	91	0
Comment 1 zhenxiang.li 2014-02-17 02:13:31 UTC 
Bug 724518(https://bugzilla.gnome.org/show_bug.cgi?id=724518) - [gst-vaapi-master ]Low ssim value when decoding some AVC files 
was filed on gnome, so close this bug.

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.