search for: number_page_segments

Hello All, When going through the Ogg format, I have a basic question. As per the RFC the Ogg format encapsulates the logical stream. Now consider the scenario where a raw mono stream is being encoded with Opus Codec. The stream is 48KHz and the length of the stream being encoded is worth 20ms of data. This makes it 960 half words (considering 16 bit format). Now if the final output is say 100

...mething like (assuming 100 half words is what > is encoded evry time) > > 100, Data.... 20 times before the next Page Segment is started!!! No. The segment table contains the lacing values for all packets on the page, followed by the data for all packets. So it would look more like: 20 (number_page_segments) 100, 100, 100 ... (20 times, the segment_table), data, data, data, ... (again, 20 times). It may be easier for you to work from some examples. I'd recommend looking at the code in opus-tools: <https://git.xiph.org/?p=opus-tools.git>. This gets all of these details correct.

...at >> is encoded evry time) >> >> 100, Data.... 20 times before the next Page Segment is started!!! >> > > No. The segment table contains the lacing values for all packets on the > page, followed by the data for all packets. So it would look more like: > > 20 (number_page_segments) 100, 100, 100 ... (20 times, the segment_table), > data, data, data, ... (again, 20 times). > > It may be easier for you to work from some examples. I'd recommend looking > at the code in opus-tools: <https://git.xiph.org/?p=opus-tools.git>. This > gets all of these detail...

...r 2002 <p> sequence number is increasing on each logical bitstream separately. 7. CRC_checksum: a 4 Byte field containing a 32 bit CRC checksum of the page (including header with zero CRC field and page content). The generator polynomial is 0x04c11db7. 8. number_page_segments: 1 Byte giving the number of segment entries encoded in the segment table. 9. segment_table: number_page_segments Bytes containing the lacing values of all segments in this page. Each Byte contains one lacing value. The total header size in bytes is given by: heade...

...r 2002 <p> sequence number is increasing on each logical bitstream separately. 7. CRC_checksum: a 4 Byte field containing a 32 bit CRC checksum of the page (including header with zero CRC field and page content). The generator polynomial is 0x04c11db7. 8. number_page_segments: 1 Byte giving the number of segment entries encoded in the segment table. 9. segment_table: number_page_segments Bytes containing the lacing values of all segments in this page. Each Byte contains one lacing value. The total header size in bytes is given by: heade...

...r 2002 <p> sequence number is increasing on each logical bitstream separately. 7. CRC_checksum: a 4 Byte field containing a 32 bit CRC checksum of the page (including header with zero CRC field and page content). The generator polynomial is 0x04c11db7. 8. number_page_segments: 1 Byte giving the number of segment entries encoded in the segment table. 9. segment_table: number_page_segments Bytes containing the lacing values of all segments in this page. Each Byte contains one lacing value. The total header size in bytes is given by: heade...

...r 2002 <p> sequence number is increasing on each logical bitstream separately. 7. CRC_checksum: a 4 Byte field containing a 32 bit CRC checksum of the page (including header with zero CRC field and page content). The generator polynomial is 0x04c11db7. 8. number_page_segments: 1 Byte giving the number of segment entries encoded in the segment table. 9. segment_table: number_page_segments Bytes containing the lacing values of all segments in this page. Each Byte contains one lacing value. The total header size in bytes is given by: heade...