<div dir="ltr">Hi, Ralph:<div><br></div><div style> That's really helpful, thank you very much!</div><div style><br></div><div style>Best Regards,</div><div style>Johnslion</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Tue, Apr 9, 2013 at 12:18 AM, Ralph Giles <span dir="ltr"><<a href="mailto:giles@thaumas.net" target="_blank">giles@thaumas.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 13-04-08 4:34 AM, Johnslion Woo wrote:<br>
<br>
> Does anybody know is it allowed for the OGG segment including more<br>
> than one Vorbis frame? Or should I consider about that?<br>
<br>
</div>Vorbis frames (packets) are split into ogg segments, not the other way<br>
around. If the packet is < 255 bytes, it just goes in a single segment<br>
by itself.<br>
<br>
So if you have a sequence of packets with lengths of 24, 156, 720 and<br>
203 bytes, those would be divided and packed into segments of length:<br>
<br>
24, 156, 255,255,210, 203<br>
<br>
You know where the boundaries between the packets are because they're<br>
where the segment length values in the lacing table are less than 255.<br>
<br>
The point of segmentation is it provides a sort of unary encoding of the<br>
packet boundaries. You can pack up to 255 segments into an ogg page, and<br>
use the lacing table to find the boundaries. This design gives a good<br>
tradeoff between header overhead and read complexity.<br>
<br>
Does that answer your question?<br>
<span class="HOEnZb"><font color="#888888"><br>
-r<br>
<br>
</font></span></blockquote></div><br></div>