From 8f2d9db79fc2f542b2973f245cc6b93fd35c1d80 Mon Sep 17 00:00:00 2001 From: wm4 Date: Mon, 10 Aug 2015 18:38:36 +0200 Subject: demux_mkv: disable timestamp fixup code again This doesn't work too well if sections of the file change to a different framerate. It lowers our chances to guess the correct FPS in the display sync code. For normal playback, this (probably) doesn't help that much anyway, except that the "estimated-vf-fps" property will regress in the simplest mkv case. This will be fixed with the next commit. The now disabled code will probably be removed; it's not useful anymore. --- DOCS/man/options.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'DOCS/man/options.rst') diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index a7783b965e..4e60e64c22 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -2179,7 +2179,7 @@ Demuxer as partial files). ``--demuxer-mkv-fix-timestamps=`` - Fix rounded Matroska timestamps (enabled by default). Matroska usually + Fix rounded Matroska timestamps (disabled by default). Matroska usually stores timestamps rounded to milliseconds. This means timestamps jitter by some amount around the intended timestamp. mpv can correct the timestamps based on the framerate value stored in the file: the timestamp is rounded -- cgit v1.2.3