Environment: -------------- Platform: SNB Libva (staging) c59c512df262cdc44fb6e9101621f246eda176df Inter-drvier (staging) 3bd6f3b3611dd9a39a3075f82cf938fa08e22884 Gst-vaapi (qa) 036540b91979e65795fe3430f763f7c1969f74f0 Kernel: (drm-intel-nightly) 032e254cefb0485c95aceca269be499b91f48aa0 Bug Info: -------------- CANL1_TOSHIBA_G.264 decoding failed. Setting pipeline to PAUSED ... 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 Pipeline is PREROLLING ... decode: 1, 0:00:00.000000000 size:0 ** (gst-launch-0.10:2283): CRITICAL **: gst_vaapi_window_x11_new: assertion `height > 0' failed decode: 2, 0:00:00.000000000 size:0 decode: 3, 0:00:00.000000000 size:0 Reproduce steps: ---------------- 1. xinit& 2．gst-launch-0.10 playbin2 video-sink="vaapisink sync=false" uri=file:///home/gst_AVC_conformance/Base_Ext_Main_profile/CANL1_TOSHIBA_G.264 Comments: ---------------- Below files can reproduce the issue. CANL1_TOSHIBA_G.264 CVMAQP2_Sony_G.jsv CVSE3_Sony_H.jsv CVCANLMA2_Sony_C.jsv CAMACI3_Sony_C.jsv CVNLFI1_Sony_C.jsv CVFI1_Sony_D.jsv CVMAPAQP3_Sony_E.jsv CVMAQP3_Sony_D.jsv CACQP3_Sony_D.jsv
Libva (staging) c59c512df262cdc44fb6e9101621f246eda176df Inter-driver (staging) 3bd6f3b3611dd9a39a3075f82cf938fa08e22884 Gst-vaapi (qa) e7d517323fd98608918de1211dc42f795b48765f Platfrom: IVB Below files decode failed. CVMAQP2_Sony_G.jsv CVSE3_Sony_H.jsv CVCANLMA2_Sony_C.jsv CAMACI3_Sony_C.jsv CVNLFI1_Sony_C.jsv CVFI1_Sony_D.jsv CVMAPAQP3_Sony_E.jsv CVMAQP3_Sony_D.jsv CACQP3_Sony_D.jsv
Issue still can be reproduced in gstream-vaapi master branch (cb0da4ed7acbb51f2d5dba34c0b37b2c5ad8bff4)
Add testfile profile for your information: CAFI1_SVA_C.264 video stream type:AVC resolution:720x480 profile:Main level:3.0 aspect ratio:3x2 chroma format:4:2:0 frame count:33 interlace: yes bitrate type: VBR CVMAQP2_Sony_G.jsv video stream type:AVC resolution:192x128 profile:Main level:3.1 aspect ratio:3x2 chroma format:4:2:0 frame count:17 interlace: yes bitrate type: VBR
Hi, you will have to narrow down further the issue for CANL1_TOSHIBA_G.264 because it works here: Ivy Bridge, and media stack from git master branches (libva, VA driver, gstreamer-vaapi).
Libva (master) 9f4dedc4de014cc665c32dfbac1c017f9396b563 Inter-driver (master) 63db874e9c924f086bcd3518cc0f3d8c6df9ecec Gst-vaapi (master) cb0da4ed7acbb51f2d5dba34c0b37b2c5ad8bff4 Platform : IVB Issue still can be reproduced. BTW, we apt-get install gstreamer,gst-plugins-{base,good,bad,ugly} on ubuntu 12.04, not upstream.
platform: SNB IVB libva: (staging) 38c94cd922473095814ed9a9f99ad98fcc9c285d inter-driver: (staging) c0ef9d99df37ae45589fecb898727be495e50304 Test with the latest gstream-vaapi code in qa branch, Issue can be reproduced. but when using gst-launch-0.10 playbin2 video-sink="vaapisink sync=false" uri=file:///home/AVC_conformance/Base_Ext_Main_profile/CANL1_TOSHIBA_G.264, file can be decoded correctly.
Make correction: platform: SNB IVB libva: (staging) 38c94cd922473095814ed9a9f99ad98fcc9c285d inter-driver: (staging) c0ef9d99df37ae45589fecb898727be495e50304 Test with the latest gstream-vaapi code in qa branch, Issue can be reproduced. but when using gst-launch-0.10 filesrc location=/home/AVC_conformance/Base_Ext_Main_profile/CANL1_TOSHIBA_G.264 ! h264parse ! vaapidecode ! vaapisink sync=false file can be decoded correctly.
now test with the latest gstream-vaapi code in qa branch , this issue will not be reproduced.
I thought this issue is the same as 55305, but now I find that maybe there are someting different about this issue. I'll recheck it.
Issue can't reproduced but still lost frames #Bug 55305.
How it was tested to see frame lost?
Created attachment 72329 [details] patch
(In reply to comment #11) > How it was tested to see frame lost? We test frame lost by attachment patch.
Now this issue is just like #Bug 55305, we won't fix 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.