[Live-devel] BufferPacket

[Flavio Oliveira]

Hi Ross,

I did a Live Wrapper, and I am receiving just the Payload data (without
RTP Header, but I can get the header fields). So the buffer into bPacket
filled at time  "MultiFramedRTPSource::networkReadHandler" calls 
"bPacket->fillInData(source->fRTPInterface)" now contains only the
playload data. 

But we know some audio/video format may need some data from RTP header
to decode the payload. So, what are the informations needed by what
payloads? 

Other question...an application like "zinf" need which information to
play a payload? we believe only and just only the payload, sequence
number and timestamp, is it right? 

Flavio


On Wed, 2005-05-04 at 14:56 -0700, Ross Finlayson wrote:
> >I noticed that some payload formats are using class called
> >BufferedPacket and ReorderingPacketBuffer.
> >I was wondering that each RTP packet payload could contain frames
> >preceded by a special Header, and it could need some informations
> >in the RTP header such as Timestamp and Sequence Number for
> >Interleaving processing. Could be it the reason for use that class?
> 
> Yes.  To implement reception of some RTP payload formats with special 
> headers, we subclass "BufferedPacket" (and reimplement the virtual function 
> "nextEnclosedFrameSize()) and "BufferedPacketFactory" (and reimplement the 
> virtual function "createNewPacket()").  See, for example, the 
> implementations of: "MPEG4GenericRTPSource" and "AMRAudioRTPSource".
> 
> (Note, however, that "ReorderingPacketBuffer" is used only within 
> "MultiFramedRTPSource" (the base class for all RTP payload format reception 
> implementations), and is *not* subclassed anywhere.)
> 
> 
> 	Ross Finlayson
> 	LIVE.COM
> 	<http://www.live.com/>
> 
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live.com
> http://lists.live.com/mailman/listinfo/live-devel