In MultiFramedRTPSink we have :
Boolean MultiFramedRTPSink::isTooBigForAPacket(unsigned numBytes) const {
// Check whether a 'numBytes'-byte frame - together with a RTP header and
// (possible) special headers - would be too big for an output packet:
// (Later allow for RTP extension header!) #####
numBytes += rtpHeaderSize + specialHeaderSize() +
frameSpecificHeaderSize();
return fOutBuf->isTooBigForAPacket(numBytes);
}
I need to add an RTP Extension header to my on demand rtsp server and am
trying to figure out how to implement it.
In the above comment, is frameSpecificHeaderSize() a placeholder for the "
Later allow for RTP extension header!" or would there be a new function,
i.e numBytes += rtpHeaderSize + specialHeaderSize() +
frameSpecificHeaderSize() + rtpExtensionHeaderSize();
I see where subclasses like JPEG use the specialHeader but maybe I am not
understanding the distinction between packet and frame and thus exactly
what is a frame specificHeader vs a specialHeader.
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
