[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105145

--- Comment #12 from Christian König <ckoenig.leichtzumerken at gmail.com> ---
(In reply to k.philipp from comment #11)
> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20180611/f144dd9d/attachment.html>