Open uyjulian opened 3 years ago
Hmm, this is quite complicated feature, as it would require RTSP and RTP to be tunneled through the Neos' session protocol. Video streams are generally pretty bandwidth heavy and this would require the host to forward the stream to every connected user, which would easily saturate most people's connections with only a few users.
I'm not sure this is something we'd commit engineering effort towards, certainly not in near-term. With the video encoding I do want to add a relay service that will handle the bulk of the bandwidth, so that might get reused for this as well, but we'll have to see.
I'd just recommend setting up your video stream in a way that it's accessible through a public API and ensuring you have sufficient bandwidth for everyone.
I would be down to host a relay for a rtsp stream until this has been implemented @uyjulian
I see. I don't think this is an issue for me as I already have another solution.
I suggested this feature as a connivence for those that are not technically inclined as I am.
For my current setup, I have the firewall set to port forward to one machine providing RTSP stream.
Another machine on the same network would be the host, and that would be another port forward entry in the firewall.
The Neos video player would be pointing to the public IP:port.
Since I have wired gigabit connection, there should be plenty of bandwidth for others to connect.
Allow forwarding of RTSP audio and/or video streams to other connected users on the session.
This feature would be useful when the RTSP stream is only accessible on the local network or machine. #142 would not be needed since it is just forwarding the stream.