[Live-devel] Retrieving buffers of data from an RTSP derived stream

[Andy Hawkins]

Hi,

Thanks for the response.

'Proprietary' was perhaps the wrong choice of word. The link between the two is SRT, which is an open standard.

I'm not sure that using RTP / RTSP for the link between sites would necessarily work for us. We're often faced with unreliable network links, and the SRT protocol does a good job of handling lost / out of order data.

I appreciate that the SRT link may be beyond the scope of this mailing list, but would appreciate any assistance you can provide in extracting the data from the individual RTP streams, and being able to recombine this into an RTSP stream later.

Thanks

Andy


________________________________
From: live-devel <live-devel-bounces at us.live555.com> on behalf of Ross Finlayson <finlayson at live555.com>
Sent: 12 March 2024 16:12
To: LIVE555 Streaming Media - development & use <live-devel at us.live555.com>
Subject: Re: [Live-devel] Retrieving buffers of data from an RTSP derived stream

OK, it sounds like you’re basically trying to reproduce most of the functionality of the existing LIVE555 Proxy Server, which I spent a *lot* of time developing, so I’m not going to spend any more time helping you effectively reinvent that.

Also, reviewing your earlier emails, you mentioned that you wanted to pass the data between your receiving RTSP client and your RTSP server using a “proprietary network protocol”.  'Proprietary’ things are off-topic for this (public) mailing list.  (However, if your company would like to hire me as a consultant for your project, then let me know via separate email.)

Personally, I think that your best solution would be to figure out how to use RTSP/RTP everywhere, rather than trying to use your own protocol in-between (this protocol would end up having to reproduce much of the functionality of RTSP/RTP, including signaling, framing, timestamping (and audio/video time synchronization)).

I.e., rather than trying to do:
        RTSP server (media source) -> your-own-RTSP-client -> your-own-protocol -> your-own-RTSP-server -> RTSP clients
figure out how to do:
        RTSP server (media source) -> (unmodified) LIVE555 Proxy Server -> RTSP/RTP -> (unmodified) LIVE555 Proxy Server -> RTSP clients
or, even better:
        RTSP server (media source) -> (unmodified) LIVE555 Proxy Server -> RTSP clients


Ross Finlayson
Live Networks, Inc.
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.live555.com%2F&data=05%7C02%7Candy.hawkins%40uniguest.com%7C9ac0f76713b240906a1808dc42aff417%7C9b0e98ba45ed42abb699c61412572c2c%7C0%7C0%7C638458570703057424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=HDnqxwih%2FPhhJGKu2THa5SMX%2B0CfEKCSqSE3ZSN1Xvk%3D&reserved=0<http://www.live555.com/>


_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.live555.com%2Fmailman%2Flistinfo%2Flive-devel&data=05%7C02%7Candy.hawkins%40uniguest.com%7C9ac0f76713b240906a1808dc42aff417%7C9b0e98ba45ed42abb699c61412572c2c%7C0%7C0%7C638458570703065202%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=89NNH%2BwmhL3rxxJUIpqDT1Rv2F4%2FQZVl9W%2BPyvFgp%2Fk%3D&reserved=0<http://lists.live555.com/mailman/listinfo/live-devel>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20240312/6f9aad58/attachment.htm>