[FFmpeg-trac] #6984(undetermined:new): RTSP protocol options are inconsistent with HTTP protocol options

FFmpeg trac at avcodec.org
Thu Jan 25 19:51:25 EET 2018

#6984: RTSP protocol options are inconsistent with HTTP protocol options
             Reporter:  gjdfgh       |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
 Summary of the bug:

 The RTSP protocol has a "timeout" option, like the HTTP protocol. But it
 has very different semantics, which makes it a problem for API users,
 which try to provide a generic timeout option.

 The differences are:
 - the "timeout" option is in seconds instead of microseconds
 - the "timeout" option enables listen mode and breaks any client usage

 There is a "stimeout" option that does what you'd expect for "timeout",
 but since it has a different name and requires being aware of the protocol
 being used anyway, this does not help.

 A proper solution would rename "timeout" to something else, and "stimeout"
 to "timeout".

 How to reproduce:
 % ffmpeg -timeout 6000000 -i
 rtsp:// -f null -
 This should not fail. Happens with any ffmpeg version from current git
 master to releases from a few years ago. Full uncut console output
 available on your shell terminal.

 In addition, the "user-agent" option should be named "user_agent".

Ticket URL: <https://trac.ffmpeg.org/ticket/6984>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list