<div>was this change commited to the svn ?</div>
<div>If so , I probabyl missed it some how.</div>
<div>Any way , I agree that this is what we should do.</div>
<div> </div>
<div>thanks</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 1/19/06, <b class="gmail_sendername">Måns Rullgård</b> <<a href="mailto:mru@inprovide.com">mru@inprovide.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Måns Rullgård <<a href="mailto:mru@inprovide.com">mru@inprovide.com</a>> writes:<br><br>> <a href="mailto:shauli.rozen@gmail.com">
shauli.rozen@gmail.com</a> said:<br>>> Hi all.<br>>><br>>> I think there might be a problem in the settingd of the VUI.<br>><br>> My head starts hurting badly whenever I read that section in the spec. The
<br>> issue was raised on the jvt-experts lists some time ago, and an explanation<br>> was given. See <a href="http://www.via.ecp.fr/via/ml/x264-devel/2005-09/msg00016.html">http://www.via.ecp.fr/via/ml/x264-devel/2005-09/msg00016.html
</a><br>> for a copy of the thread that I posted here.<br>><br>> In light of this, I think you are right. We are setting the value<br>> incorrectly. The problem is that some other encoders and decoders<br>> are making the same mistake.
<br><br>I've corrected the way x264 writes this info. There's no reason to<br>knowingly write incorrect data. Hopefully it won't cause too much of<br>an inconvenience.<br><br>I've also committed the corresponding fix to libavcodec with a
<br>workaround for streams encoded by old x264 versions.<br><br>--<br>Måns Rullgård<br><a href="mailto:mru@inprovide.com">mru@inprovide.com</a><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>