[Live-devel] Need the OutPacketBuffer be that larger(fLimit)?

[Ross Finlayson]

>   So, my question is, need the outpacketBuffer be that larger, up to 60816 bytes?

In general, "OutPacketBuffer::maxSize" should be at least as large as the largest single frame of data that you expect to feed into your "RTPSink" (subclass) object.  This will usually be larger than the network packet size, in which case our code (i.e. our implementation of the appropriate RTP payload format) will fragment each frame of data - as appropriate - so that it fits properly into outgoing RTP packets.

However, H.264 is an exception to this, because we implement its RTP payload format somewhat differently.  For H.264, we place a separate 'fragmenter' object (a "H264FUAFragmenter") in front of the "RTPSink"; this 'fragmenter' object delivers 'fragment' NAL units that are small enough to fit into an outgoing RTP packet.

NOTE, HOWEVER, that "H264FUAFragmenter" uses "OutPacketBuffer::maxSize" to figure out how big to make *its own* internal buffer, and this buffer needs to be at least as large as the largest H.264 NAL unit delivered by your data source (encoder) - so you should not reduce "OutPacketBuffer::maxSize", just because you are only delivering H.264.


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20120424/b7ca5542/attachment.html>