From 5441a12a1ea9fe617c987df475865dc3f2abb237 Mon Sep 17 00:00:00 2001 From: wm4 Date: Thu, 25 Jan 2018 17:36:43 +0100 Subject: manpage: mention --network-timeout is broken with RTSP Not much we can do, too hard to work around. Fixes #3361. --- DOCS/man/options.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'DOCS') 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=`` Select RTSP transport method (default: tcp). This selects the underlying network transport when playing ``rtsp://...`` URLs. The value ``lavf`` -- cgit v1.2.3