Hi, I am using ffmpeg to convert proxy rtsp (generated from live555RTSPProxyServer with rtsp-over-tcp option) to hls using following command:
ffmpeg -fflags nobuffer -rtsp_transport tcp -i rtsp://127.0.0.1:8554/proxy > -vsync 0 -copyts -vcodec copy -movflags frag_keyframe+empty_moov > -strftime 1 -an -hls_flags append_list -f segment -segment_list_flags > live -segment_time 10 -segment_format mpegts -segment_list > /tmp/proxy/index.m3u8 -segment_list_type m3u8 -segment_list_entry_prefix > http://localhost/proxy/%s.ts Although I'm using tcp as rtsp_transport option, sockstat of live555RTSPProxyServer shows a large number of closed udp connections and this is causing an increase in CPU Usage. Let me know if I'm missing something here. On Thu, Feb 27, 2020 at 11:49 AM Siddhant Agarwal < siddhant.agar...@staqu.com> wrote: > I am using FFMPEG to convert Live RTP Url stream to HLS. Incase there is a > 404 File not found on an RTSP Url, I create a new subprocess of ffmpeg > which eventually creates a new socket connection. This has led to socket > leakage and reached the ulimit. > > Thanks > > On Thu, Feb 27, 2020 at 11:10 AM Ross Finlayson <finlay...@live555.com> > wrote: > >> >> >> > On Feb 27, 2020, at 6:17 PM, Siddhant Agarwal < >> siddhant.agar...@staqu.com> wrote: >> > >> > Hi, >> > >> > I am using Live555 with the "-t" flag. >> >> OK, by this I presume that you mean that you’re running >> *live555ProxyServer* (not ‘LIVE555’) with the “-t” flag, and that the “404 >> File not found” is occurring on the ‘back-end’ stream. >> >> Yes, the “LIVE555 Proxy Server” keeps the RTSP connection open. (This is >> regardless of whether or not it was run with the “-t” flag.) This is >> because it keeps trying to access the ‘back-end’ stream, in the hope that >> it will become available in the future. You can see this quite clearly if >> you add the “-V” flag to live555ProxyServer. >> >> There is no bug here. >> >> >> Ross Finlayson >> Live Networks, Inc. >> http://www.live555.com/ >> >> >> _______________________________________________ >> live-devel mailing list >> live-devel@lists.live555.com >> http://lists.live555.com/mailman/listinfo/live-devel >> >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
