Closed patrickelectric closed 1 week ago
Just quoting from the PR that added it on MCM side:
Tested and working with both rtspsrc and ffplay: * [x] `rtsp://` -> both UDP and TCP * [x] `rtspu://` -> UDP * [x] `rtspt://` -> TCP * [x] `rtsph://` -> TCP tunneled via HTTP * [x] `rtspth://` -> TCP w/ TLS * [x] `rtspuh://` -> UDP w/ TLS * [x] `rtspsh://` -> TCP tunneled via HTTP w/ TSL Note: a drawback of this approach is that despite the scheme used in the endpoint, the RTSP client would always use rtsp:// instead.
Tested and working with both rtspsrc and ffplay:
rtspsrc
* [x] `rtsp://` -> both UDP and TCP * [x] `rtspu://` -> UDP * [x] `rtspt://` -> TCP * [x] `rtsph://` -> TCP tunneled via HTTP * [x] `rtspth://` -> TCP w/ TLS * [x] `rtspuh://` -> UDP w/ TLS * [x] `rtspsh://` -> TCP tunneled via HTTP w/ TSL
Note: a drawback of this approach is that despite the scheme used in the endpoint, the RTSP client would always use rtsp:// instead.
rtsp://
Maybe we keep showing it to the user as rtsp://<IP>:<PORT>/<PATH>, but we add an additional dropdown that has the options as human-readable descriptions.
rtsp://<IP>:<PORT>/<PATH>
Just quoting from the PR that added it on MCM side: