diff options
| author | wm4 <wm4@nowhere> | 2018-01-25 17:36:43 +0100 |
|---|---|---|
| committer | Kevin Mitchell <kevmitch@gmail.com> | 2018-01-25 20:18:32 -0800 |
| commit | 5441a12a1ea9fe617c987df475865dc3f2abb237 (patch) | |
| tree | 2f677fd0ad392f44b9ac06171a0a47f06f869e98 /DOCS | |
| parent | 3deef308c8e57ca1fa6bdd60abd6a3213d7eb3c6 (diff) | |
| download | mpv-5441a12a1ea9fe617c987df475865dc3f2abb237.tar.bz2 mpv-5441a12a1ea9fe617c987df475865dc3f2abb237.tar.xz | |
manpage: mention --network-timeout is broken with RTSP
Not much we can do, too hard to work around.
Fixes #3361.
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/man/options.rst | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/DOCS/man/options.rst b/DOCS/man/options.rst index 2acc8d8239..95b29f3d25 100644 --- a/DOCS/man/options.rst +++ b/DOCS/man/options.rst @@ -3969,6 +3969,16 @@ Network special value 0 (default) uses the FFmpeg/Libav defaults. If a protocol is used which does not support timeouts, this option is silently ignored. + .. warning:: + + This breaks the RTSP protocol, because of inconsistent FFmpeg API + regarding its internal timeout option. Not only does the RTSP timeout + option accept different units (seconds instead of microseconds, causing + mpv to pass it huge values), it will also overflow FFmpeg internal + calculations. The worst is that merely setting the option will put RTSP + into listening mode, which breaks any client uses. Do not use this + option with RTSP URLs. + ``--rtsp-transport=<lavf|udp|tcp|http>`` Select RTSP transport method (default: tcp). This selects the underlying network transport when playing ``rtsp://...`` URLs. The value ``lavf`` |