summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2016-05-23 23:46:58 +0200
committerwm4 <wm4@nowhere>2016-05-23 23:46:58 +0200
commit6bd021e4ee30275ba6fe7d2e306909b57fd368dd (patch)
tree4daef10351ce7c5ab8fcddabfa649f7ad8f99d4c /DOCS
parente293e411b51f4f115022e794ae9eb7bd1c40cb14 (diff)
downloadmpv-6bd021e4ee30275ba6fe7d2e306909b57fd368dd.tar.bz2
mpv-6bd021e4ee30275ba6fe7d2e306909b57fd368dd.tar.xz
manpage: adjust dxva2 description
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/man/options.rst9
1 files changed, 6 insertions, 3 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst
index b583e63b38..f46990f404 100644
--- a/DOCS/man/options.rst
+++ b/DOCS/man/options.rst
@@ -656,9 +656,12 @@ Video
either BT.601 or BT.709, a forced but correct RGB conversion is
performed. Otherwise, the result will be incorrect.
- ``dxva2`` is not safe. It uses either BT.601 or BT.709 for forced RGB
- conversion, and which colorspace is used is driver-dependent. This can
- give incorrect results even with completely ordinary video sources.
+ ``dxva2`` is not safe. It appears to always use BT.601 for forced RGB
+ conversion, but actual behavior depends on the GPU drivers. Some drivers
+ appear to convert to limited range RGB, which gives a faded appearance.
+ In addition to driver-specific behavior, global system settings might
+ affect this additionally. This can give incorrect results even with
+ completely ordinary video sources.
All other methods, in particular the copy-back methods (like
``dxva2-copy`` etc.) are either fully safe, or not worse than software