diff options
author | Philip Langdale <philipl@overt.org> | 2016-10-09 09:18:14 -0700 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2016-10-15 17:44:23 +0200 |
commit | 0a81fe1cf9e62c26ebda1c209b3b69467991b252 (patch) | |
tree | 01eb15fdfe5500b0c384f62fffb5966b2e8c1e2d /DOCS | |
parent | 8956229ee46c187a5a1eb63c834219d0e9b84b83 (diff) | |
download | mpv-0a81fe1cf9e62c26ebda1c209b3b69467991b252.tar.bz2 mpv-0a81fe1cf9e62c26ebda1c209b3b69467991b252.tar.xz |
vd_lavc: Add hwdec wrapper for crystalhd
This hardware decodes to system memory so it only requires a wrapper.
Diffstat (limited to 'DOCS')
-rw-r--r-- | DOCS/man/options.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index d17aefe347..374cdaf1a5 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -625,6 +625,7 @@ Video :rpi-copy: copies video back to system RAM (Raspberry Pi only) :cuda: requires ``--vo=opengl`` (Any platform CUDA is available) :cuda-copy: copies video back to system RAM (Any platform CUDA is available) + :crystalhd: copies video back to system RAM (Any platform supported by hardware) ``auto`` tries to automatically enable hardware decoding using the first available method. This still depends what VO you are using. For example, @@ -711,6 +712,11 @@ Video ``rpi`` always uses the hardware overlay renderer, even with ``--vo=opengl``. + ``crystalhd`` is not safe. It always converts to 4:2:2 YUV, which + may be lossy, depending on how chroma sub-sampling is done during + conversion. It also discards the top left pixel of each frame for + some reason. + All other methods, in particular the copy-back methods (like ``dxva2-copy`` etc.) are either fully safe, or not worse than software decoding. |