<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#c12">Comment # 12</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:ckoenig.leichtzumerken@gmail.com" title="Christian König <ckoenig.leichtzumerken@gmail.com>"> Christian König</a> <pre>(In reply to k.philipp from <a href="show_bug.cgi?id=105145#c11">comment #11</a>) > Is the interlaced format necessary in the first place? Unfortunately yes it is. The pixel shader used for de-interlacing needs to have access to the top/bottom field separately and that only works efficiently when they aren't mangled together. We could try to double the stride to work around that, but that isn't easily doable with the interface we have and we would stress the memory interface quite a bit more. Additional to that most hardware de-interlacer work only with that layout, .e.g it is actually the more natural one for MPEG2. And that's also the reason why for example NVidia hardware only works with that as well. That HEVC and VP9 only support progressive layout in the output format is also only logical because those formats don't support interlaced content.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>