Open GadgetAngel opened 5 years ago
HI GadgetAngel,
Till now it is work like liv555 behave, The TCP is decided calling RTSP SETUP and doesnot depend on RTSP url
Using vlc this is done by the flag --rtsp-tcp,
using ffmpeg -rtsp_transport tcp
, motioneyz seems based on gstreamer, there is probably a way to ask for an RTP over TCP.
Another way is to modify the behaviour of live555 in order to answer to RSTP DESCRIBE with an RTP over TCP SDP depending on some flags in the URL.
Best Regards, Michel.
Your description says this server will do tcp for rtsp but how do that?
Background: I am using a raspberry pi 3B+ , Buster OS, raspberry pi NOIR camera V2, using the offical v4l2 driver.
here is my command: v4l2rtspserver -F 10 -H 360 -W 480 -P 8555 /dev/video0
and the rtsp URL I am using is: rtsp://192.168.1.27:8555/unicast
When I use motionEyeOS, the only way it would see the rtsp stream is if I choose UDP rtsp. I like to look at my rtsp streams with displaycameras server but he requires all rtsp streams to be TCP so I can not see the stream. How can I force v4l2rtspserver to output rtsp withTCP?