Re: [Live-devel] Stream handling

2024-06-19 Thread Ross Finlayson
> On Jun 19, 2024, at 1:48 PM, Lutz Fiebach wrote: > > The second question is aimed at since this is a raw stream, let's first > manually take the appropriate frames SPS, PPS or VPS and create a > H264VideoStreamDiscreteFramer and a H264VideoRTPSink. […] > I wonder whether this is necessary o

Re: [Live-devel] Stream handling

2024-06-19 Thread Flavio Alves
Hi Lutz, In my work I had to implement a RTSP server which provides several different live sources on the same RTSP server, changing the endpoint. I implemented a component matching the video source and the live555 source together. The video source works on a different thread and sends the trigge

Re: [Live-devel] Stream handling

2024-06-19 Thread Lutz Fiebach
Thank you for your reply, that answers the first part. I wasn't aware of this, and our current implementation actually works by creating a new instance of the DeviceSource for each client and the encoder copies the data to each client queue. 10 clients = 10 queues. I will change this. The second

Re: [Live-devel] Stream handling

2024-06-19 Thread Ross Finlayson
> On Jun 19, 2024, at 12:30 PM, Lutz Fiebach wrote: > > Maybe you can also give me some advice regarding the stream handling. > I just want to know if it is the right way to use a FramedSource, store all > clients in a map with the required information and then copy the nal frames > for all act

[Live-devel] Stream handling

2024-06-19 Thread Lutz Fiebach
Hello, I am opening a new conversation in the hope that this time I will receive the mails from the mailin list. First of all, thank you for pointing out the end timestamps, we have now removed that. Maybe you can also give me some advice regarding the stream handling. I just want to know if i