From dfe846f9de30e2606a38afb6ca6de755e84df3df Mon Sep 17 00:00:00 2001 From: Niklas Haas Date: Fri, 25 Feb 2022 22:07:56 +0100 Subject: vo_gpu_next: add support for hardware decoding There are two major ways of going about this: 1. Expose the native ra_gl/ra_pl/ra_d3d11 objects to the pre-existing hwdec mappers, and then add code in vo_gpu_next to rewrap those ra_tex objects into pl_tex. 2. Wrap the underlying pl_opengl/pl_d3d11 into a ra_pl object and expose it to the hwdec mappers, then directly use the resulting pl_tex. I ultimately opted for approach 1 because it enables compatibility with more hardware decoders, specifically including ones that use native OpenGL calls currently. The second approach only really works with cuda_vk and vaapi_pl. --- DOCS/man/vo.rst | 4 ---- 1 file changed, 4 deletions(-) (limited to 'DOCS') diff --git a/DOCS/man/vo.rst b/DOCS/man/vo.rst index cd995df3c7..1843a56e4f 100644 --- a/DOCS/man/vo.rst +++ b/DOCS/man/vo.rst @@ -262,10 +262,6 @@ Available video output drivers are: the same set of features as ``--vo=gpu``. See `GPU renderer options`_ for a list. - Currently, this only supports Vulkan, OpenGL, D3D11 and no hardware - decoding. Unlike ``--vo=gpu``, the FBO formats are not tunable, but you can - still set ``--gpu-dumb-mode=yes`` to forcibly disable their use. - Should generally be faster and higher quality, but some features may still be missing or misbehave. Expect (and report!) bugs. See here for a list of known differences and bugs: -- cgit v1.2.3