<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#c13">Comment # 13</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#c12">comment #12</a>) > Unfortunately yes it is. That is indeed very unfortunate. It complicates stuff a lot :-( I'd still like to see a solution that allows to support PAFF without copying around already-decoded frames/fields all the time. Do you have any ideas? Could we have the decoder put progressive content into progressive surfaces and interlaced content into interlaced surfaces (under the assumption that we will most likely want to deinterlace)? > That HEVC and VP9 only support progressive layout in the output format is > also only logical because those formats don't support interlaced content. At least HEVC does support interlaced content in theory, but as far as I understood it the (hw) decoder does not need special support for that. How would that work then, would we get top/bottom field as two separate quasi-frames?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>