Hello, I recently updated the vaapi/intel-driver from 1.0.17 to 1.0.19, but I'm not experiencing issues with hw-accelerated MPEG2 decoding. From time to time garbled bars appear in the picture, mostly when scene changes occur. So I presume it has something to do with reference picture decoding. Anyway, I checked and it seems that the issues was introduced from 1.0.17 to 1.0.18 (read: the issue also appears with 1.0.18). The CPU is a Intel Core i5 M 450, so the GPU should be an Arrandale IIRC. I'm using xf86-video-intel-2.20.15 as DDX and mplayer-vaapi (built from sources) as player. The source is a BluRay (How to Train Your Dragon). Rendering is done via the Xv backend. Greets, Tobias
"but I'm not" <- this should of course read "but I'm _NOW_"
Ah, sry, another correction needed: The stream is H264, and _not_ MPEG2. Can a admin please change the title?
Created attachment 72289 [details] picture showing an example of image corruption I also updated intel-driver to git, since there were some changes concerning H264. Not fixing anything though.
More corrections. I wasn't really awake then I entered the bug: The issue is introduced between 1.0.16 and 1.0.17. I also did a proper bisect this time, and the faulty commit is: h264: fix scan for bit offset to macroblock (4bbfe67d2098f4f2aaeb3c5ab2cd930d2acb1c26)
Created attachment 72301 [details] naive fix for the issue So this is how I (naively) fixed the issue for now. No idea if this is correct at all, but it removes the image corruption completly for me.
Pushed. Thanks for your patch.
Hi, what version of mplayer-vaapi (and FFmpeg) were you using? BTW, n == (i - j) :)
The fix is needed for the following case: xx xx 00 00 03 aa bb cc 'aa' is the last byte of slice_header.
(In reply to comment #7) > Hi, what version of mplayer-vaapi (and FFmpeg) were you using? It's built from the latest checkout of the gitorious repo. You remember that your build script forces a specific ffmpeg version?
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.