summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2018-02-12 18:44:46 +0100
committerKevin Mitchell <kevmitch@gmail.com>2018-02-13 17:45:29 -0800
commit4107a8be6ccd843378414704e69225168e3494f9 (patch)
tree94408f8ea65db801e060ca695f0fd867ba39652b /DOCS
parent6b2b2b75b9f27af3d0e8b115cca75de8903d36a4 (diff)
downloadmpv-4107a8be6ccd843378414704e69225168e3494f9.tar.bz2
mpv-4107a8be6ccd843378414704e69225168e3494f9.tar.xz
vf_vavpp: select best quality deinterlacing algorithm by default
This switches the default away from "bob" to the best algorithm reported as supported by the driver. This is convenient for users, and there is no reason to use something worse by default. Untested.
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/interface-changes.rst1
-rw-r--r--DOCS/man/vf.rst6
2 files changed, 6 insertions, 1 deletions
diff --git a/DOCS/interface-changes.rst b/DOCS/interface-changes.rst
index c0ec882719..e18fec4c1d 100644
--- a/DOCS/interface-changes.rst
+++ b/DOCS/interface-changes.rst
@@ -75,6 +75,7 @@ Interface changes
- make --deinterlace=yes always deinterlace, instead of trying to check
certain unreliable video metadata. Also flip the defaults of all builtin
HW deinterlace filters to always deinterlace.
+ - change vf_vavpp default to use the best deinterlace algorithm by default
--- mpv 0.28.0 ---
- rename --hwdec=mediacodec option to mediacodec-copy, to reflect
conventions followed by other hardware video decoding APIs
diff --git a/DOCS/man/vf.rst b/DOCS/man/vf.rst
index 17df70f920..d979337e42 100644
--- a/DOCS/man/vf.rst
+++ b/DOCS/man/vf.rst
@@ -478,10 +478,14 @@ Available mpv-only filters are:
no
Don't perform deinterlacing.
+ auto
+ Select the best quality deinterlacing algorithm (default). This
+ goes by the order of the options as documented, with
+ ``motion-compensated`` being considered best quality.
first-field
Show only first field.
bob
- bob deinterlacing (default).
+ bob deinterlacing.
weave, motion-adaptive, motion-compensated
Advanced deinterlacing algorithms. Whether these actually work
depends on the GPU hardware, the GPU drivers, driver bugs, and