summaryrefslogtreecommitdiffstats
path: root/DOCS/man/vo.rst
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-01-23 20:56:11 +0100
committerwm4 <wm4@nowhere>2015-01-23 20:56:25 +0100
commita0a40eb2872d137898e6f96b8d46490f2e63071f (patch)
tree2e665b1ce92a6984c5498e8faaa38e0d6b2d7e92 /DOCS/man/vo.rst
parentd76dbbd41427a12f03dac7ccc99d8c864b228d6b (diff)
downloadmpv-a0a40eb2872d137898e6f96b8d46490f2e63071f.tar.bz2
mpv-a0a40eb2872d137898e6f96b8d46490f2e63071f.tar.xz
vo: fix disabling/enabling smoothmotion at runtime
vo.c queried the VO at initialization whether it wants to be updated on every display frame, or every video frame. If the smoothmotion option was changed at runtime, the rendering mode in vo.c wasn't updated. Just let vo_opengl set the mode directly. Abuse the existing vo_set_flip_queue_offset() function for this. Also add a comment suggesting the use of --display-fps to the manpage, which doesn't have anything to do with the rest of this commit, but is important to make smoothmotion run well.
Diffstat (limited to 'DOCS/man/vo.rst')
-rw-r--r--DOCS/man/vo.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/DOCS/man/vo.rst b/DOCS/man/vo.rst
index f177bd4fde..4a02b7cfa8 100644
--- a/DOCS/man/vo.rst
+++ b/DOCS/man/vo.rst
@@ -585,6 +585,9 @@ Available video output drivers are:
vsync behavior can lead to bad results. If the framerate is close to or
over the display refresh rate, results can be bad as well.
+ .. note:: On systems other than Linux, you currently must set the
+ ``--display-fps`` option, or the results will be bad.
+
``smoothmotion-threshold=<0.0-1.0>``
Mix threshold at which interpolation is skipped (default: 0.0 – never
skip).