summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorrcombs <rcombs@rcombs.me>2020-10-03 20:09:21 -0500
committerJan Ekström <jeebjp@gmail.com>2020-11-22 17:37:43 +0200
commit4dcaf70b9653cd04c2159fac6545f25f8e1cbcf9 (patch)
treefa5e26b9da6df70ccf7e5ecf71578810861c0cb8 /DOCS
parent2409300d408704af347b52b5d2ec58d517cf35a3 (diff)
downloadmpv-4dcaf70b9653cd04c2159fac6545f25f8e1cbcf9.tar.bz2
mpv-4dcaf70b9653cd04c2159fac6545f25f8e1cbcf9.tar.xz
Revert "options: disable vsfilter blur compat by default"
This reverts commit 3d17e19c2c5ca80f916411e7e61126cac8443baa. The effect of turning off this setting is that mpv doesn't tell libass what the video stream's resolution is. This happens to result in some files having their transforms scaled in ways that give higher performance (as described in #7435) because libass happened to guess a video resolution that resulted in transforms yielding smaller bitmaps, but it's just as easy for the opposite to happen depending on the resolutions and effects involved. The option's name is also somewhat misleading: setting the storage size affects blur, but it also affects stroke (which is far more important for the vast majority of scripts) and 3D transforms (which look very screwy when done wrong).
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/man/options.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst
index 8b437bdfa8..50ff3ec665 100644
--- a/DOCS/man/options.rst
+++ b/DOCS/man/options.rst
@@ -2379,7 +2379,7 @@ Subtitles
``--sub-ass-vsfilter-blur-compat=<yes|no>``
Scale ``\blur`` tags by video resolution instead of script resolution
- (disabled by default). This is bug in VSFilter, which according to some,
+ (enabled by default). This is bug in VSFilter, which according to some,
can't be fixed anymore in the name of compatibility.
Note that this uses the actual video resolution for calculating the