<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - mpeg4 through vdpau randomly either correct or garbled (on same file!)" href="https://bugs.freedesktop.org/show_bug.cgi?id=73457#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - mpeg4 through vdpau randomly either correct or garbled (on same file!)" href="https://bugs.freedesktop.org/show_bug.cgi?id=73457">bug 73457</a> from <a class="email" href="mailto:fabrice@bellet.info" title="Fabrice Bellet <fabrice@bellet.info>"> Fabrice Bellet</a> <pre>Hi! I observe the same problem too. The jpeg file of the garbled output is very similar to what I see. Tested with upstream mesa/xorg, in a fedora 20 x86_64, [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 250E]. I made some traces at the libvdpau level (VDPAU_TRACE env vars), that I can provide if needed. They don't seem to present major differences between situations with and without corruption. I tried to serialize the vdpau calls with a mutex without more success, I played with the number of surfaces too, no difference. libefence didn't help. It looks like there may be a cache warmness effect at play, because it seems to me that --even if the problem occurs mainly in a random way-- it can more easily be triggered after a fresh boot, than after a couple of retries on the same file. Also another feeling is that the bug is more easily triggered with gstreamer-vaapi + vdpau, than with mplayer or vlc, maybe because gst can burst a bunch of hw decoding operations on different surfaces before switching to the rendering thread ? vlc and mplayer invoke vdpau in a more *ordered* way. I also confirm point 3 of the initial reporter : the corruption may extend to artifacts appearing *outside* the player window.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>