> On Mar 13, 2024, at 5:44 AM, Andy Hawkins wrote:
>
> 'Proprietary' was perhaps the wrong choice of word. The link between the two
> is SRT, which is an open standard.
OK, I’m somewhat aware of SRT, because I was at the IETF MOPS working group
meeting - described at the end of the “History”
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
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 tha
That's understandable, it was a couple of months ago.
I want to have a process that receives the contents of an RTSP stream into
buffers for each element of the stream, passes these buffers across a network,
and then at the other end uses these buffers as source data for another RTSP
stream. I
I’m sorry, but I’m missing the whole context behind this.
Remind us again: What are you trying to do? (I don’t mean the low-level
details of what you are trying to do with our code, but rather the high-level
description of what you are trying to do.)
And why is the existing “LIVE555 Proxy Serv
Coming back to this after a bit of a hiatus.
I've got this working in a single application. One side creates an RTSP client,
and starts all the individual streams, receiving the data into buffers. The
buffers for the H264 video stream appear to have been processed to provide H264
video frames.
