Dear peter,<br>I am talking about decoder only. I will explain u my problem more clearly.<br><br>Right now our decoder works properly with our encoder. Now we need to make this decoder standardised in the sense that it should accept any other bitstream(for example i want to decode JM encoders output with my decoder).
<br><br>After reading the syntax elements as per baseline standard I need to check whether this is implemented or not in my decoder and return the error still needs to be implemented. the intent was that the code shouldnot crash in such situations instead return proper error code.
<br><br>I went through the section that u told me. But my doubts were,<br>i dont understand what 0_0_0 signify in name of MB type. Also in table 7.13 mb_types for P slices, what do we mean by inferred type.<br><br>Also tell me can we idetify the prediction mode from mb_type itself?
<br><br>thanks in advance,<br>mahesh.<br><br><div><span class="gmail_quote">On 8/7/07, <b class="gmail_sendername">List, Peter</b> <<a href="mailto:Peter.List@t-systems.com">Peter.List@t-systems.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="blue" lang="DE">
<div>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB">Dear Mahesh,</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB">if you are talking about
a DECODER intra 4x4 is a must, if you want to be standard conform in all cases
(for any profile). </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB">If you are talking
about ENCODERS you don't need to implement intra-4x4 but only use
intra-16x16 (resulting in very poor intra performance).</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB">I don't understand
what you mean with:</span></font></p><span class="q">
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;" lang="EN-GB">But we want to decode any standard bitstream that is
as per standard but return the error code accordingly . <br>
<br>
</span></font></p></span>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB">About mb_type read in "Recommendation
H.264" (ISO/IEC 14496-10) paragraph 7.4.5</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB">Peter</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-GB"> </span></font></p>
<div style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0cm 0cm 0cm 4pt;">
<div>
<div style="text-align: center;" align="center"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="2" width="100%">
</span></font></div>
<p><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">Von:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;"> mahesh k
[mailto:<a href="mailto:maheswarreddy.k@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">maheswarreddy.k@gmail.com</a>] <br>
<b><span style="font-weight: bold;">Gesendet:</span></b> Dienstag, 7. August 2007
11:22<br>
<b><span style="font-weight: bold;">An:</span></b> Mailing list for x264
developers<br>
<b><span style="font-weight: bold;">Betreff:</span></b> Re: [x264-devel]
Regarding disabling 4x4 in JM code</span></font></p>
</div><div><span class="e" id="q_1143fb44a94c6eff_3">
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
<p style="margin-bottom: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">thanks for ur reply. Plz
tell me whether intra 4x4 is must in base line profile or it is an optional.<br>
Can't we run the baseline profile decoder without 4x4 as per standard?<br>
I need this because at present we have not implemented this 4x4 mode But we
want to decode any standard bitstream that is as per standard but return the
error code accordingly . <br>
Also I am confused with the syntax element mb_type. <br>
What values does mb_type should have if i need to check whether this is an 4x4
or 16x16.<br>
Also plz tell me in clear about this mb_type and ma_mde.<br>
If possible refer some good document on this. <br>
<br>
Thanks in advance.</span></font></p>
<div>
<p><span><font face="Times New Roman" size="3"><span style="font-size: 12pt;">On 8/7/07, <b><span style="font-weight: bold;">List,
Peter</span></b> <<a href="mailto:Peter.List@t-systems.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Peter.List@t-systems.com</a>>
wrote:</span></font></span></p>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br>
> mahesh k wrote:<br>
> > I want a baseline ecoded bit stream in which intra4x4 predition mode<br>
> > should not be present.<br>
><br>
> Note (but you probably already know it): of course intra4x4 is part of <br>
> baseline.<br>
<br>
Also note that intra4x4 is NOT some fancy add on for intra-coding like<br>
some people think 4x4 motion estimation is.<br>
Intra4x4 is the basic intra coding mode! It is usually used for the<br>
majority of intra-macroblocks. Intra-16x16 is only used for very uniform <br>
macroblocks like blocks from a blue sky or something like that.<br>
Regards, Peter<br>
_______________________________________________<br>
x264-devel mailing list<br>
<a href="mailto:x264-devel@videolan.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">x264-devel@videolan.org </a><br>
<a href="http://mailman.videolan.org/listinfo/x264-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mailman.videolan.org/listinfo/x264-devel</a></span></font></p>
</div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
</span></div></div>
</div>
</div>
<br>_______________________________________________<br>x264-devel mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:x264-devel@videolan.org">x264-devel@videolan.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mailman.videolan.org/listinfo/x264-devel" target="_blank">
http://mailman.videolan.org/listinfo/x264-devel</a><br><br></blockquote></div><br>