Environment: -------------- Platform: HSW Libva: (staging) b8d3cf092c9b07cfd909552a3c160b7db3b5a91d Intel-driver: (staging) 2ac15d815cfd4d43aff75bebf6cd82039b227399 Gst-vaapi: (qa) ba9ff142d2f5c8bed64c00938d8b07d3ffb8e519 Bug Info: -------------- raw stream encoded by gst can’t be decoded correctly Stream playback too fast. Steps: -------------- 1. xinit& 2. gst-launch-0.10 -v filesrc location=/home/encoder/encoderbitstreams.bak/SOCCER_704x576_30_orig_02.yuv ! videoparse format=i420 width=704 height=576 ! vaapiupload direct-rendering=0 ! vaapiencodeh264 ! filesink location=/tmp/test.h264 3. gst-launch-0.10 filesrc location=/tmp/test.h264 ! h264parse ! vaapidecode ! vaapisink sync=false
Just to be certain, can you also see an error when you simply bypass GST and instead attempt to encode first the YUV and then decode the output? In other words, take gst out of the loop and verify there is first not a problem with the driver. Thanks, Sean
(In reply to comment #1) > Just to be certain, can you also see an error when you simply bypass GST and > instead attempt to encode first the YUV and then decode the output? In > other words, take gst out of the loop and verify there is first not a > problem with the driver. Thanks, Sean It is OK when we encode raw stream with avcenc, and the encoded file can playback normally.
Hi Wind, Any update on this issue? Thanks, Jocelyn
Sorry,I didn't try this file yet. How to get the file? If the playback is only too fast, normally it's because of the <sync=false>, it should not be a bug.
Wind, Please double confirm with QA.
I tried the file on IVB and everything is ok. As I said before, when <sync=false> set, hw would try its best to decoding frames, the video may be played back like fastforward. This should not be a bug. <sync=false> would not check timestamps and won't sync the video, if someone wants a normal playback, need encode data into a container file like mp4, mkv, ts, avi...then play the file with <sync=true>.
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.