https://bugs.freedesktop.org/show_bug.cgi?id=92220
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #14 from Christian König ---
(In reply to Peter Frühberger from comment #13)
> So @Christian happy for pointers on how to get it going.
Yeah, completely agree with you. Software workarounds are very common in OpenGL
and nothing
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #13 from Peter Frühberger ---
If I was to decide, I would suggest:
>2. Add an extra step to the drivers using shaders to split the frame up into
>>separate fields in vlVdpVideoSurfaceGallium
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #12 from riaasm at yahoo.com ---
I think option 3 would be the most suitable solution, since this would
advertise exactly what the hardware does. I'm not sure if this is practical
though, since it seems to me like creating a new GL
https://bugs.freedesktop.org/show_bug.cgi?id=92220
Christian König changed:
What|Removed |Added
Priority|medium |low
Severity|normal
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #10 from riaasm at yahoo.com ---
So if I understand this correctly, all versions of UVD can perform frame-based
interop. I assume that the UVD hardware was created to perform frame-based
interop, but after the GL_NV_vdpau_interop
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #9 from Alex Deucher ---
(In reply to riaasm from comment #6)
> For example, if someone can confirm that the interop functionality is not
> available in UVD1 and UVD2, but partial interop is available in UVD2.2 and
> full interop is
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #8 from Alex Deucher ---
(In reply to Rainer Hochecker from comment #5)
> I think option 1. is good enough. This is done by setting the environment
> variable, right? We can force using the mixer if this variable is set.
Correct.
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #7 from Alex Deucher ---
(In reply to riaasm from comment #4)
> I understand that you can't enable a GL extension if there's no support for
> it in the hardware, but I think this specific GL extension doesn't require
> anything
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #6 from riaasm at yahoo.com ---
Option 1 is a good workaround, but it needs to be done manually. Option 2 is of
course the easiest for userspace programs since they would not have to change
anything, but it might not be practical. I
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #5 from Rainer Hochecker ---
(In reply to Alex Deucher from comment #3)
>
> I guess there are 3 options:
>
> 1. Force the option but limit it to cases where you are only using the
> output surface via the interop extension. This
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #4 from riaasm at yahoo.com ---
I understand that you can't enable a GL extension if there's no support for it
in the hardware, but I think this specific GL extension doesn't require
anything specific in the hardware.
>From what I
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #3 from Alex Deucher ---
You can't really enable a GL extension if there is not support for the entire
thing. Early versions of UVD did not support field based output. The
extension provides access to both the raw decoded video
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #2 from Peter Frühberger ---
>From Kodi POV we like to have a best practice to cope with such devices. For
now we check for the extension and if found use the methods it defines.
As those cards don't expose this extentions we exit
https://bugs.freedesktop.org/show_bug.cgi?id=92220
riaasm at yahoo.com changed:
What|Removed |Added
Summary|GL_NV_vdpau_interop |GL_NV_vdpau_interop
15 matches
Mail list logo
