<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically" href="https://bugs.freedesktop.org/show_bug.cgi?id=105145#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically" href="https://bugs.freedesktop.org/show_bug.cgi?id=105145">bug 105145</a> from <a class="email" href="mailto:k.philipp@gmail.com" title="k.philipp@gmail.com">k.philipp@gmail.com</a> <pre>(In reply to Christian König from <a href="show_bug.cgi?id=105145#c8">comment #8</a>) > (In reply to k.philipp from <a href="show_bug.cgi?id=105145#c7">comment #7</a>) > > I did think about that, but it has the problem of breaking deinterlacing on > > all clients that do *not* set VA_SURFACE_ATTRIB_USAGE_HINT_VPP_READ (which I > > assume to be most) since there is - correct me if I'm wrong - at present no > > code to un-weave a decoded frame to fields and go back to interlaced/field > > mode, causing the initial issue in the first place. > > Yeah, we can't do this without at least adding this frame to field > conversion. > > How about VA_SURFACE_ATTRIB_USAGE_HINT_EXPORT then? The VA-API hints seem to > describe the use case instead of the effect, so that would match. I filed a PR with libva (<a href="https://github.com/intel/libva/pull/196">https://github.com/intel/libva/pull/196</a>), we'll see how it goes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>