<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:ckoenig.leichtzumerken@gmail.com" title="Christian König <ckoenig.leichtzumerken@gmail.com>"> <span class="fn">Christian König</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - 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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTOURBUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105145#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - 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 <span class="vcard"><a class="email" href="mailto:ckoenig.leichtzumerken@gmail.com" title="Christian König <ckoenig.leichtzumerken@gmail.com>"> <span class="fn">Christian König</span></a>
</span></b>
<pre>Yeah, that is a design issue with vlVaExportSurfaceHandle.
E.g. vlVaExportSurfaceHandle can only export surfaces when they are in the
progressive memory layout because VA-API doesn't supports interlaced layouts.
To not run into issues with that limitation we reallocate the backing store for
the surface and copy from the interlaced presentation to the progressive layout
on the first vlVaExportSurfaceHandle.
Now post processing is only possible if you got the interlaced format, cause
otherwise extracting the odd/even fields costs to much time.
What we could try to do is to reverse what is done in vlVaExportSurfaceHandle
before post processing, e.g. copy from progressive to interlaced. But that
usually means we lag for quite a number of frames (because of the extra copy)
until all surfaces are in interlaced format again.
Not sure what to do here except for fixing VA-API.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>