From 1cd25117522180c763527909d3dad8b5a79d5913 Mon Sep 17 00:00:00 2001 From: Kevin Mitchell Date: Mon, 7 Mar 2016 20:03:44 -0800 Subject: manpage: document dxva2 option for hwdec Also mention dxva2-copy along with vaapi-copy. --- DOCS/man/options.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'DOCS/man/options.rst') diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index eb1b1a60c0..51ec16fff2 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -580,6 +580,8 @@ Video :vaapi: requires ``--vo=opengl`` or ``--vo=vaapi`` (Linux only) :vaapi-copy: copies video back into system RAM (Linux with Intel GPUs only) :videotoolbox: requires ``--vo=opengl`` (OS X 10.8 and up only) + :dxva2: requires ``--vo=opengl:backend=angle`` or + ``--vo=opengl:backend=dxinterop`` (Windows only) :dxva2-copy: copies video back to system RAM (Windows only) :rpi: requires ``--vo=rpi`` (Raspberry Pi only - default if available) @@ -596,9 +598,10 @@ Video forcing it with ``--vo=opengl:backend=x11``, but the vaapi/GLX interop is said to be slower than ``vaapi-copy``. - The ``vaapi-copy`` mode allows you to use vaapi with any VO. Because - this copies the decoded video back to system RAM, it's likely less efficient - than the ``vaapi`` mode. + The ``vaapi-copy`` and ``dxva2-copy`` modes allow you to use hardware + decoding with any VO or backend. Because these copy the decoded + video back to system RAM, they're likely less efficient than the ``vaapi`` + or ``dxva2`` modes respectivley. .. note:: -- cgit v1.2.3