From 6b745769b1fd15ba03edad3fe381abb745bf9907 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 28 Oct 2017 19:59:08 +0200 Subject: vd_lavc: add support for nvdec hwaccel See manpage additions. (In ffmpeg-mpv and Libav, this is still called "cuvid". Libav won't work yet, because it has no frame params support yet, but this could get fixed soon.) --- DOCS/man/options.rst | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'DOCS/man/options.rst') diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index 5c4882883a..7cd399d4f1 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -695,6 +695,8 @@ Video :rpi-copy: copies video back to system RAM (Raspberry Pi only) :cuda: requires ``--vo=gpu`` (Any platform CUDA is available) :cuda-copy: copies video back to system RAM (Any platform CUDA is available) + :nvdec: requires ``--vo=gpu`` (Any platform CUDA is available) + :nvdec-copy: copies video back to system RAM (Any platform CUDA is available) :crystalhd: copies video back to system RAM (Any platform supported by hardware) :rkmpp: requires ``--vo=gpu`` (some RockChip devices only) @@ -723,6 +725,12 @@ Video deinterlacing. ``cuda`` should always be preferred unless the ``gpu`` vo is not being used or filters are required. + ``nvdec`` is a newer implementation of CUVID/CUDA decoding, which uses the + FFmpeg decoders for file parsing. Experimental, is known not to correctly + check whether decoding is supported by the hardware at all. Deinterlacing + is not supported. Since this uses FFmpeg's codec parsers, it is expected + that this generally causes fewer issues than ``cuda``. Requires ffmpeg-mpv. + Most video filters will not work with hardware decoding as they are primarily implemented on the CPU. Some exceptions are ``vdpaupp``, ``vdpaurb`` and ``vavpp``. See `VIDEO FILTERS`_ for more details. -- cgit v1.2.3