<div><font color="#3366ff">First of all, Thanks for the reply. </font></div>
<div><font color="#3366ff"></font> </div>
<div><font color="#3366ff">I went through the RFC 3984, But could not find whether we can reuse the NAL Header or not(point 2).</font></div>
<div><font color="#3366ff"></font> </div>
<div><font color="#3366ff">Also It has not been mentioned how the padding is done.</font></div>
<div><font color="#3366ff">Can You please clarify me.</font></div>
<div><font color="#3366ff"></font> </div>
<div><font color="#3366ff">Thanks.</font></div>
<div><font color="#3366ff">Mukesh.</font><br><br> </div>
<div><span class="gmail_quote">On 6/14/07, <b class="gmail_sendername">Jirka Klaue</b> <<a href="mailto:jklaue@tkn.tu-berlin.de">jklaue@tkn.tu-berlin.de</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> 1. I know that our encoder can fragment the NAL Unit and output the<br>> fragmented NAL Unit. But Can we fragment the NAL Unit outside the
<br>> encoder?<br>><br><br>Yes. RFC-3984 will answer all your questions.<br><br>> 2. If we can(As per 1st point)fragment the NAL Unit outside the<br>> encoder, then we have to reuse the NAL Header produced by the
<br>> encoder or a seperate Fragmentation indicator and header has to<br>> added for fragmentation of the whole NAL Unit(along with NAL<br>> headers) generated by the encoder?<br>><br>> 3. Should the payload data(Fragmented Unit) be byte alligned?
<br>><br>> 4. How the "Optional RTP padding" has to be done.<br>><br><br>regards,<br> Jirka<br><br><br>--<br>This is the x264-devel mailing-list<br>To unsubscribe, go to: <a href="http://developers.videolan.org/lists.html">
http://developers.videolan.org/lists.html</a><br><br></blockquote></div><br>