diff options
| author | Dudemanguy <random342@airmail.cc> | 2023-10-15 09:36:56 -0500 |
|---|---|---|
| committer | Dudemanguy <random342@airmail.cc> | 2023-10-25 16:16:37 +0000 |
| commit | 7aed492ccc48fd32084d7dfe65a50b5b90d8411a (patch) | |
| tree | 3361dcf55e770918e1f1646ab4d4db172a678833 /DOCS/man/mpv.rst | |
| parent | dac977193cccbf7e2e999cf0c4b0292314839c4c (diff) | |
| download | mpv-7aed492ccc48fd32084d7dfe65a50b5b90d8411a.tar.bz2 mpv-7aed492ccc48fd32084d7dfe65a50b5b90d8411a.tar.xz | |
options: rename --fps to --container-fps-override
This better reflects what it actually does. As a bonus, script writers
won't be misled into thinking that fps displays the actual video or
display fps.
Diffstat (limited to 'DOCS/man/mpv.rst')
| -rw-r--r-- | DOCS/man/mpv.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/DOCS/man/mpv.rst b/DOCS/man/mpv.rst index dd42c73412..636d4bbdc3 100644 --- a/DOCS/man/mpv.rst +++ b/DOCS/man/mpv.rst @@ -1094,7 +1094,8 @@ this with ``--untimed``, but it will likely break, unless the stream has no audio, and the input feeds data to the player at a constant rate. Another common problem is with MJPEG streams. These do not signal the correct -framerate. Using ``--untimed`` or ``--no-correct-pts --fps=60`` might help. +framerate. Using ``--untimed`` or ``--no-correct-pts --container-fps-override=60`` +might help. For livestreams, data can build up due to pausing the stream, due to slightly lower playback rate, or "buffering" pauses. If the demuxer cache is enabled, |