search for: segment_t

Hi, There is something I don't understand about the page_segment and segment_table values in the documentation. As I understand it, the segment table consist of as many bytes as specified in page_segment, PLUS one trailing byte with a value between 0 and 254. I've looked at some files that has a Comment tag so large, that it is spread over two pages. Here, the first Page...

...alues follows [...] A packet of 255 bytes is terminated by a lacing value of 0." Is this value of 0 included in the "page_segments" value in the case that it occurs? i.e. is it safe to assume that the number of lacing values in the header will be equal to the number of values in the segment_table? Given the above, scanning for a value of < 255 doesn't seem to be safe. Thanks again, - -Scott - -- The fact that an opinion has been widely held is no evidence whatever that it is not utterly absurd. - --Bertrand Russell -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux...

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

How would one implement the following scheme with minimal use of resources: Every Vorbis packet should be preprocessed to a certain extent, that is, the beginning of every audio packet should be parsed and some decoding steps executed. The result of this predecode as well as the rest of the packet should then be sent as output for final processing. I have skimmed through the standard, and as far

...coded 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.

..., 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. > ____________________________...

...| page_sequence_number | 16-19 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | CRC_checksum | 20-23 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |page_segments | segment_table | 24-27 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | 28- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Regards, Silvia. -----Original Message----- From: ogg-dev-bounces@xiph.org on beh...

..._sequence_number | 16-19 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | CRC_checksum | 20-23 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |page_segments | segment_table | 24-27 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | 28- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The LSb (least significant bit) comes first in the Bytes. Fields wi...

..._sequence_number | 16-19 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | CRC_checksum | 20-23 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |page_segments | segment_table | 24-27 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | 28- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The LSb (least significant bit) comes first in the Bytes. Fields wi...

..._sequence_number | 16-19 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | CRC_checksum | 20-23 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |page_segments | segment_table | 24-27 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | 28- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The LSb (least significant bit) comes first in the Bytes. Fields wi...

..._sequence_number | 16-19 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | CRC_checksum | 20-23 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |page_segments | segment_table | 24-27 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | 28- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The LSb (least significant bit) comes first in the Bytes. Fields wi...