<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - tearing on radeonsi vdpau deinterlacer" href="https://bugs.freedesktop.org/show_bug.cgi?id=84944#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - tearing on radeonsi vdpau deinterlacer" href="https://bugs.freedesktop.org/show_bug.cgi?id=84944">bug 84944</a> from <a class="email" href="mailto:warpme@o2.pl" title="warpme@o2.pl">warpme@o2.pl</a> <pre>(In reply to Christian König from <a href="show_bug.cgi?id=84944#c13">comment #13</a>) > > Page flipping operations are tear free, so what we see here is that without > deinterlacing the graphics stack uses page flipping and with deinterlacing > it uses glamor with of course results in badly tearing of the video. Indeed - infrastructure for flipping seems to be ready: [837858.379] (II) RADEON(0): KMS Pageflipping: enabled [837858.379] (II) RADEON(0): SwapBuffers wait for vsync: enabled [837858.389] (II) RADEON(0): Output HDMI-0 using monitor section Monitor1 > > The question is why the heck do we fallback to a copy operation with glamor > when deinterlacing is enabled? If You believe we should do some tests with added debug outputs - I'm more than happy to do so :-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>