Just joining the conversation... What order of magnitude do you recommend
setting the NAL unit size to ? MTU size ? 64kB ? More ?
________________________________
From: live-devel <live-devel-boun...@us.live555.com> on behalf of Ross
Finlayson <finlay...@live555.com>
Sent: Thursday, March 10, 2022 5:36:56 PM
To: LIVE555 Streaming Media - development & use <live-de...@us.live555.com>
Subject: Re: [Live-devel] [Mirasys] Live555 RTSP server questions
Congratulations - you’ve discovered datagrams! They sometimes get lost.
You can try to (1) reduce the rate at which datagrams get lost, and/or (2)
reduce the *effect* of a datagram getting lost.
For (1):
- Do you have one or more middleboxes - somewhere between your server
and client - that might be dropping packets?
- You could try increasing the OS’s internal buffer size for the
transmitting socket (for the server) and/or the receiving socket (for the
client). By default, this is set to 50 kBytes for each socket - which is
usually enough. However, you could try increasing it. (grep
“increaseSendBufferTo” and “increaseReceiverBufferTo” in the code.)
For (2):
- You could reconfigure your encoder to decrease the *size* of your
H.265 NAL units (so that they will fit in fewer RTP packets, making it less
likely that the loss of a single RTP packet will cause the whole NAL unit to be
unusable). I.e., you could encode each key frame as a series of ‘slice’ NAL
units, instead of just one (ridiculously large) NAL unit.
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
