<div><span class="gmail_quote">On 1/13/07, <b class="gmail_sendername">Loren Merritt</b> <<a href="mailto:lorenm@u.washington.edu">lorenm@u.washington.edu</a>> wrote:</span><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Yes, 2 calls of <=32 bits is better. What's the largest number you need<br>to encode with bs_write_ue?
</blockquote>
<div> </div>
<div>Either the bit rate (in bps) divided by 64, or the vbv buffer size (in bits) divided by 16. Given that both these values are given in units of 1000 to x264, I was considering rounding them both up to the next multiple of 1024, which would reduce the size they'd be encoded in.
</div>
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">>>> - move the version info SEI header after the SPS and PPS headers<br>>>> (required for Scenarist to identify the stream as an H264 ES)
<br>>><br>>> Bugs should be fixed where the bug is. This is a bug in Scenarist, so out<br>>> of principle I won't work around it in x264.<br>><br>> Could it be a requirement of the HD DVD spec that H264 streams start with
<br>> AUD, SPS, PPS? I don't have access to that spec...<br><br>Conceivably, but I won't believe it until someone has a copy of the spec.<br></blockquote>
<div>Well, no chance of me getting it... I'll take out that part of the patch.</div>
<div> </div>
<div>Ian<br> </div>