Thanks for the inputs. I needed your suggestions on steps I would need to follow to feed these NAL units into the H264RTPSink. For starters
a) I am only going to be concerned with 1 NAL unit. As u mentioned ; i could discard working on aggregation packets and just feed a single NAL unit into packet. Would this involve just making a H264 framer class and read a NAL unit and package it into a frame which i give as input to the H264RTPSink. Please correct my understanding. b) What would be drawbacks of not using aggregation packets? c) Is there anything else I would need to implement? Thanks, Brian On 8/16/07, Ross Finlayson <[EMAIL PROTECTED]> wrote: > > > - skim through RFC 3984 RTP Payload Format for H.264 > Video<http://www.rfc-archive.org/getrfc.php?rfc=3984> > > > > You really shouldn't have to do this, because the library already > implements this RTP payload format (using the "H264VideoRTPSink" class). > All you need to do is feed NAL units to it. However... > > > > > - Aggregation packets (STAP) are packets designed to hold together > many small NALs, to increase network efficiency > > > > Yes, we currently don't create these 'aggregation packets' (a special kind > of NAL unit) ourselves, so if you want to use these, you'll need to create > them yourself. However, it's usually uncommon to have sequences of small > NAL units > > > > > - fragmentation packets (FU) are packets designed to break huge NALs > (like IDR/key frames) into network size packets > > > > No, you don't have to implement these yourself. Our "H264VideoRTPSink" > class automatically does this for you. > > -- > > > 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
