You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in using this library to host an RTSP server and have been doing my own research and creating scaffolding to do so.
I figure it's probably a good idea to create this issue to see if you (@scottlamb) had any plans on doing this already, and if not then to just track what needs to be done and hold relevant documentation.
My goal would be to create a server that is analogous to the client - it would provide an interface that can consume frames for the different streams and deliver them to listening clients.
It'd only implement functionality as far as the RTSP/RTP specifications describe (e.g. per my current understanding, that means no encoding/decoding for the different compression algos).
I'm interested in using this library to host an RTSP server and have been doing my own research and creating scaffolding to do so.
I figure it's probably a good idea to create this issue to see if you (@scottlamb) had any plans on doing this already, and if not then to just track what needs to be done and hold relevant documentation.
My goal would be to create a server that is analogous to the client - it would provide an interface that can consume frames for the different streams and deliver them to listening clients.
It'd only implement functionality as far as the RTSP/RTP specifications describe (e.g. per my current understanding, that means no encoding/decoding for the different compression algos).
References:
RFC 7798 (HEVC RTP payload format): https://datatracker.ietf.org/doc/html/rfc7798
RFC 2326 (RTSP protocol): https://datatracker.ietf.org/doc/html/rfc2326
The text was updated successfully, but these errors were encountered: