Sorry if this appear dumb, but why not just throw everything away until you receive an I-Frame. If your GOP is so large that you feel the need for an out-of-sequence I-Frame than it would likely make more sense to reduce your GOP than to create a stream that may well confuse many receivers.
-----Original Message----- From: live-devel <live-devel-boun...@us.live555.com> On Behalf Of ?????? ???? ?????????? Sent: Sunday, March 10, 2024 7:29 AM To: LIVE555 Streaming Media - development & use <live-de...@us.live555.com> Subject: Re: [Live-devel] RTSP server on live555 start send client on I-Frame (h264) I want something a little different. ANY client that connected began to receive data only that included an I-frame. That is, somewhere to write or correct the logic, with the first packet, what if the data from the source includes an i-frame, send it, if it does not, then skip sending and wait for the next packet. All other subsequent packets are sent by default -----Original Message----- От: "Ross Finlayson" <finlay...@live555.com> Кому: "LIVE555 Streaming Media - development & use" <live-de...@us.live555.com> Отправленные: Среда, 28 Февраль 2024 г 14:41:20 Тема: Re: [Live-devel] RTSP server on live555 start send client on I-Frame (h264) > On Feb 28, 2024, at 9:20 PM, Худаев Илья <hud...@domination.one> wrote: > > I connected to several real IP cameras and saw that the first packages that I > received were NAL units with SPS, PPS and I-frame. Yes, and you could easily change the implementation of your video input source (which is your code, so I can’t help you with this) to do the same - for the FIRST CLIENT that connects each time. (But note again that having the SPS and PPS at the start of the stream doesn’t gain you anything, because they are already present in the SDP description that the client has already received.) But think: What do you want to happen if the server is already streaming to one client, and then a second (or a third, etc.) client connects later? Do you want to have the server handle the complexity of sending different data to each client? Right now, our server works by sending the exact same data (in fact, the exact same RTP packet) to each concurrent client. And that’s fine. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
