diff options
author | wm4 <wm4@nowhere> | 2015-04-23 19:35:15 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2015-04-23 19:37:02 +0200 |
commit | 90d7e51643273a14dfb9a4db622abb7da4e0aa5f (patch) | |
tree | 3001aff8d97622f092c813bc7f71cb967bd2a7b6 /DOCS | |
parent | e9ca0b1522a799e9d52e6aafc58fc316398f40b6 (diff) | |
download | mpv-90d7e51643273a14dfb9a4db622abb7da4e0aa5f.tar.bz2 mpv-90d7e51643273a14dfb9a4db622abb7da4e0aa5f.tar.xz |
demux_mkv: attempt to fix rounded timestamps
There is some potential for breakage. If it happens, this might have to
be disabled by default.
Diffstat (limited to 'DOCS')
-rw-r--r-- | DOCS/man/options.rst | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index ef914982a7..47f4c15152 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -2112,6 +2112,18 @@ Demuxer will be slower (especially when playing over http), or that behavior with broken files is much worse. So don't use this option. +``--demuxer-mkv-fix-timestamps=<yes|no>`` + Fix rounded Matroska timestamps (enabled 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: if the timestamps does + not deviate more than 1 frame (as implied by the framerate), the timestamp + is rounded to the next frame, which should undo the rounding the muxer + did. + + This can break playback if the framerate value stored in the file is too + high. + ``--demuxer-rawaudio-channels=<value>`` Number of channels (or channel layout) if ``--demuxer=rawaudio`` is used (default: stereo). |