> On Jan 27, 2022, at 9:51 AM, Zhang, David via live-devel
> wrote:
>
>
> From: "Zhang, David"
> Subject: RTSP server status code reference
> Date: January 27, 2022 at 9:51:27 AM GMT+13
> To: "live-devel@lists.live555.com"
>
>
> Hi, our software is preparing to map ResultCode from live555
Lllmllm) l p l}l p you p pl p
P0lp0
L
L
you
0
L
Original Message
From: live-devel-requ...@us.live555.com
Sent: 26 January 2022 20:00:00 GMT
To: live-de...@us.live555.com
Subject: live-devel Digest, Vol 218, Issue 13
Send live-devel mailing list submissions to
--- Begin Message ---
Hi, our software is preparing to map ResultCode from live555 rtsp server to our
own code, we found that we will get not only RTSP status code but also some TCP
error codes. Is there a comprehensive list of ResultCode we will get for all
scenarios?
Thanks
David Z
--- End Me
> On Jan 27, 2022, at 2:37 AM, Victor Vitkovskiy
> wrote:
>
> 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?
Yes.
> I thought that if frame is bigger then buffer then I ne
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 fNumTruncat
> On Jan 27, 2022, at 1:39 AM, Victor Vitkovskiy
> wrote:
>
> Hello Ross,
>
> Yes, I know that OutPacketBuffer::maxSize=3 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
Hello Ross,
Yes, I know that OutPacketBuffer::maxSize=3 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.
I am trying to use fNumTruncatedBytes to proceed somehow big frames accor
> On Jan 26, 2022, at 10:28 PM, Victor Vitkovskiy
> wrote:
>
> Hello Ross,
>
> Thank you for information.
>
> I have tried like you said, but I have this error:
> MultiFramedRTPSink::afterGettingFrame1(): The input frame data was too large
> for our buffer size (30480). 26917 bytes of tra
Hello Ross,
Thank you for information.
I have tried like you said, but I have this error:
MultiFramedRTPSink::afterGettingFrame1(): The input frame data was too large
for our buffer size (30480). 26917 bytes of trailing data was dropped!
Correct this by increasing "OutPacketBuffer::maxSize"
> On Jan 26, 2022, at 8:43 PM, Victor Vitkovskiy
> wrote:
>
> Hello Ross,
>
> I have one question regarding the copying data to output buffer when I am
> implementing own FramedSource.
> There is an fTo buffer that has a maximum size fMaxSize, this fMaxSize is
> taken from OutPacketBuffer:
10 matches
Mail list logo
