https://bugs.freedesktop.org/show_bug.cgi?id=105145
GitLab Migration User changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #14 from tempel.jul...@gmail.com ---
Unfortunately, VAAPI deinterlacing inside mpv --vo=gpu still doesn't work
because this is still missing. :(
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #13 from k.phil...@gmail.com ---
(In reply to Christian König from comment #12)
> 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
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #12 from Christian König ---
(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
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #11 from k.phil...@gmail.com ---
Hi again,
> The PR got merged.
I do have a patch ready (it's just a few lines anyway), but vaapi has not seen
a release yet so it is unclear which API version it should depend on. Also we
have
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #10 from tempel.jul...@gmail.com ---
The PR got merged.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #9 from k.phil...@gmail.com ---
(In reply to Christian König from comment #8)
> (In reply to k.philipp from comment #7)
> > I did think about that, but it has the problem of breaking deinterlacing on
> > all clients that do *not* set
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #8 from Christian König ---
(In reply to k.philipp from comment #7)
> I did think about that, but it has the problem of breaking deinterlacing on
> all clients that do *not* set
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #7 from k.phil...@gmail.com ---
(In reply to Christian König from comment #6)
> But checking the documentation once more
> VA_SURFACE_ATTRIB_USAGE_HINT_VPP_READ actually sounds exactly like what we
> need.
>
> E.g. we switch over to
https://bugs.freedesktop.org/show_bug.cgi?id=105145
Christian König changed:
What|Removed |Added
Resolution|NOTOURBUG |---
https://bugs.freedesktop.org/show_bug.cgi?id=105145
Christian König changed:
What|Removed |Added
Severity|major
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #5 from k.phil...@gmail.com ---
(In reply to Christian König from comment #4)
> (In reply to k.philipp from comment #3)
> > Also, that VAAPI has to weave the first few textures before they've been
> > exported once is not very nice.
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #4 from Christian König ---
(In reply to k.philipp from comment #2)
> Since we can do weaving on the Kodi side anyway (for VDPAU), would it be
> enough to add flags, say VA_EXPORT_SURFACE_TOP_FIELD
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #3 from k.phil...@gmail.com ---
OK, scratch that. Our VAAPI weave implementation uses legacy GL features, and
we're not very keen to accommodate for fields in separate textures in our
general shaders.
Here's what we'll do instead
https://bugs.freedesktop.org/show_bug.cgi?id=105145
--- Comment #2 from k.phil...@gmail.com ---
This "interlaced" data layout - what does it mean exactly? Does it just mean
fields in separate surfaces or is there anything else going on additionally? I
couldn't find any docs on this in mesa.
https://bugs.freedesktop.org/show_bug.cgi?id=105145
Christian König changed:
What|Removed |Added
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=105145
Bug ID: 105145
Summary: vaExportSurfaceHandle interaction with surface
interlaced flag prevents switching on vaapi
deinterlacing dynamically
Product: Mesa
17 matches
Mail list logo