summaryrefslogtreecommitdiffstats
path: root/DOCS/man/input.rst
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-11-13 22:41:41 +0100
committerwm4 <wm4@nowhere>2015-11-13 22:41:41 +0100
commitf0feea55918e133ba3e6871e2bb1cbd9610cb2d1 (patch)
tree2a6d808fab4b5b3de03f7588037b2dd8b2408ac2 /DOCS/man/input.rst
parentdef87f1e5f693ed24b5c8f62e8e86dbaebe4d993 (diff)
downloadmpv-f0feea55918e133ba3e6871e2bb1cbd9610cb2d1.tar.bz2
mpv-f0feea55918e133ba3e6871e2bb1cbd9610cb2d1.tar.xz
command: rename vo-missed-frame-count property
"Missed" implies the frame was dropped, but what really happens is that the following frame will be shown later than intended (due to the current frame skipping a vsync). (As of this commit, this property is still inactive and always returns 0. See git blame for details.)
Diffstat (limited to 'DOCS/man/input.rst')
-rw-r--r--DOCS/man/input.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst
index 108c7a0de2..50ac4dbfbf 100644
--- a/DOCS/man/input.rst
+++ b/DOCS/man/input.rst
@@ -921,6 +921,11 @@ Property list
(which can happen especially with bad source timestamps). For example,
using the ``display-desync`` mode should never change this value from 0.
+``vo-delayed-frame-count``
+ Estimated number of frames delayed due to external circumstances in
+ display-sync mode. Note that in general, mpv has to guess that this is
+ happening, and the guess can be inaccurate.
+
``percent-pos`` (RW)
Position in current file (0-100). The advantage over using this instead of
calculating it out of other properties is that it properly falls back to