[x264-devel] Re :Re: H.264 RTP Payload

[biplab raut]

Thanks Jingyi.
   
  Let me put one more question.
Can we use different size of payload data to transmit in a rtp packet. I mean if we have data to be sent as 250 bytes. If I fragment this data in to packets of size 100 bytes, then only 50 bytes of data is left for the last fragment. 
Can we send this 50 bytes of data in the next rtp packet withought padding? 
   
  Mukesh.
   
On Fri, 15 Jun 2007 11:26:47 -0400 x264-devel at videolan.org wrote
Yes. You can reuse NAL Header as part of NAL Fragmentation Units. The padding is aligned at DWORD (4 bytes) boundary.
   
  Thanks.
Jingyi Hu
 
   
  
From:  Awadhesh Reply-To:  x264-devel at videolan.orgTo:  x264-devel at videolan.orgSubject:  [x264-devel] Re: H.264 RTP PayloadDate:  Thu, 14 Jun 2007 14:42:00 +0530
  First of all, Thanks for the reply. 
   
  I went through the RFC 3984, But could not find whether we can reuse the NAL Header or not(point 2).
   
  Also It has not been mentioned how the padding is done.
  Can You please clarify me.
   
  Thanks.
  Mukesh. 
  On 6/14/07, Jirka Klaue wrote: 
> 1. I know that our encoder can fragment the NAL Unit and output the> fragmented NAL Unit. But Can we fragment the NAL Unit outside the
> encoder?>Yes. RFC-3984 will answer all your questions.> 2. If we can(As per 1st point)fragment the NAL Unit outside the> encoder, then we have to reuse the NAL Header produced by the
> encoder or a seperate Fragmentation indicator and header has to> added for fragmentation of the whole NAL Unit(along with NAL> headers) generated by the encoder?>> 3. Should the payload data(Fragmented Unit) be byte alligned?
>> 4. How the "Optional RTP padding" has to be done.>regards,  Jirka

       
---------------------------------
 Did you know? You can CHAT without downloading messenger.  Know how!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.videolan.org/pipermail/x264-devel/attachments/20070616/6083f90d/attachment-0001.htm