[FFmpeg-trac] #10122(ffmpeg:new): No connection timeout using ffmpeg on windows

FFmpeg trac at avcodec.org
Mon Dec 26 21:29:43 EET 2022

#10122: No connection timeout using ffmpeg on windows
             Reporter:  Promes1984  |                     Type:  defect
               Status:  new         |                 Priority:  normal
            Component:  ffmpeg      |                  Version:  git-master
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
 Summary of the bug: using ffmpeg on windows there is no connection timeout
 when the camera is not available during connecting.
 How to reproduce:
 my command: ffmpeg -hide_banner -loglevel verbose -y -timeout 10
 -rtsp_transport tcp -i rtsp://admin:password@
 -t 600 -acodec copy -vcodec copy -metadata title="CAM1" -f segment
 -reset_timestamps 1 -segment_time 60 -segment_atclocktime 1
 -segment_format mkv -strftime 1 C:\temp\%Y%m%d_%H%M%S.mkv
 shorter command: ffmpeg -timeout 10 -y -rtsp_transport tcp -i
 rtsp://admin:password@ -t 600 -acodec copy
 -vcodec copy C:\temp\dummy.mp4
 ffmpeg version 2022-12-21-git-eef763c705-full_build-www.gyan.dev Copyright
 (c) 2000-2022 the FFmpeg developers
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.

 Using linux parameter "-stimeout <milliseconds>" helps.
 On the latest windows build this parameter is not available and results in
 "Unrecognized option 'stimeout'.".

 I also got told to use "-timeout <seconds>" in combination with
 "-rtsp_flags listen".
 This results in error "[rtsp @ 0000027f58623fc0] Unable to open RTSP for
 listening. rtsp://admin:password@ Error number
 -10049 occurred" even if the camera is available and usable with vlc.
Ticket URL: <https://trac.ffmpeg.org/ticket/10122>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list