Hello Ross, So, if I understood correctly, if OutPacketBuffer::maxSize is smaller then frame, then all that is more then this value will be lost in any way?
I thought that if frame is bigger then buffer then I need to pass this buffer part by part in each doGetNextFrame call using fNumTruncatedBytes value to define how much data is still remained to send. But according to your last email this fNumTruncatedBytes parameter is useless if upper level components just lose all data that is bigger than OutPacketBuffer::maxSize. Best regards, ----------------------------------------- Victor Vitkovskiy Senior software developer mailto: [email protected] www.mirasys.com -----Original Message----- From: live-devel <[email protected]> On Behalf Of Ross Finlayson Sent: Wednesday, 26 January 2022 14:48 To: LIVE555 Streaming Media - development & use <[email protected]> Subject: Re: [Live-devel] [Mirasys] Live555 RTSP server questions EXTERNAL > On Jan 27, 2022, at 1:39 AM, Victor Vitkovskiy > <[email protected]> wrote: > > Hello Ross, > > Yes, I know that OutPacketBuffer::maxSize=30000 is not enough for handling > 56Kb frame, I just trying to handle a situation when OutPacketBuffer::maxSize > is set to lower value then a frame that we need to send. What you’re doing is correct. However, you’re seeing the error message ("The input frame data was too large for our buffer size…”) ***precisely because*** you had to truncate the data. That’s what the error message means. Therefore, set "OutPacketBuffer::maxSize” to a large enough value so that you won’t need to truncate (i.e., lose) any data. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
