similar to: AW: packets and OGG pages

>Searching for 'vorbis' to find the packet boundary is wrong however. >The lacing values in the Ogg page header tells you exactly where the >division is. OK, so given the fact that a page can also contain multiple packets this means that the lacing values of one page could be like the following example: 255 255 189 (something less than 255, indicating that a new packet starts

Thanks for your replys. >packets don't always begin at the >start of a page OK, since I only want to read / write the Vorbis comments, I can limit it to the Vorbis header packets. http://xiph.org/vorbis/doc/Vorbis_I_spec.html stats that the comment header always begins on the second ogg page. Since the length of the precedent identification header is fixed, this even is a fixed offset

OK, I've found the answer for one of my previous question myself in the meantime. The comment header can of course be split over more than 1 ogg page since the comment header can be greater than 64K. It also seems to be possible that both comment AND setup headers are placed on a single ogg page only (as stated in the Voribs specs). Due to the fact that the first audio packet also begins on

>That would be great! We always need help improving our documentation. OK. I'm going to start writing this lib now, and as soon as it works well I'm going to write specs about how to tag vorbis files. I'll let you know then. Maybe I have to ask you some further questions during development. Let's see. Thank you so far, Mathias

Hello all, my name is Mathias, I'd like to ask about some details of the OGG format because I'm quite new to it. I'd like to write a native .NET library for reading and writing Vorbis comments. It's going to be open-sourced as soon as it's finished. So here it goes: 1) When packing (Vorbis) packets to OGG pages, does a new packet always begin on a fresh OGG page? Within the

On Wed, Mar 14, 2007 at 12:23:47PM +0000, Mathias Kunter wrote: > OK, since I only want to read / write the Vorbis comments, I can limit it to the Vorbis header packets. > http://xiph.org/vorbis/doc/Vorbis_I_spec.html stats that the comment header always begins on the second ogg page. Since the length of the precedent identification header is fixed, this even is a fixed offset into the

On 15/03/07, Ralph Giles <giles@xiph.org> wrote: > On Wed, Mar 14, 2007 at 12:23:47PM +0000, Mathias Kunter wrote: > > > > In contrast to that, http://www.ietf.org/rfc/rfc3533.txt stats the following: > > "Ogg Vorbis provides the name and revision of the Vorbis codec, > > the audio rate and the audio quality on the Ogg Vorbis bos page. > > It also uses

Hi all, Here are some thoughts on Vorbis framing, which may make it easier to stream Vorbis in real time. The suggested changes also move more audio data closer to the beginning of each page. A note in the Vorbis framing spec suggests a simple 'bandwidth limited' mode whereby important information is placed at the front of each page and the end of each page is discarded. When operating

On Wed, Aug 13, 2008 at 3:05 AM, ogg.k.ogg.k at googlemail.com wrote: > And that's the canonical way AFAIK. Comparing times computed from > the granpos you get from pages you get from a bsearch requires good > knowledge of the codec, whereas comparing granpos can seek within > any codec. No. it's in general impossible to calculate the granulepos that corresponds to a

Hi, I'm currently trying to implement the Ogg specification in pure Java from scratch. (I know, something like that does exist, but that's a rewrite from C, at least that's my impression). I'm a bit confused with the number of lacing values/segments in a page, and the maximum length a page can have. The specification says, that there can be 255 segments in a page, 255 bytes each

Hello Versions 10,11,12 and X3 aren't working yet. The only one who works (nearly clean) is Version 9. But you need some additional native dlls and wine until version 0.9.22. Version 0.9.23 - 25 have a strong regression. Roland ----- Urspr?ngliche Mail ---- Von: "news@swwwk.com" <news@swwwk.com> An: wine-users@winehq.org Gesendet: Dienstag, den 14. November 2006, 07:15:16

On 3/15/07, Conrad Parker <conrad@metadecks.org> wrote: > On 15/03/07, Ralph Giles <giles@xiph.org> wrote: > > On Wed, Mar 14, 2007 at 12:23:47PM +0000, Mathias Kunter wrote: > > > > > > In contrast to that, http://www.ietf.org/rfc/rfc3533.txt stats the following: > > > "Ogg Vorbis provides the name and revision of the Vorbis codec, > >

Hi, I need another clarification regarding the standard. In floor0 header decode (setup), the point no.7 says that if any of [floor0_order], [floor0_rate], [floor0_bark_map_size], floor0_amplitude_bits], [floor0_amplitude_offset] or [floor0_number_of_books] are less than zero, the stream is not decodable But as we see, all those values are read as unsigned integers. Now I'm not able to

Hello, I'm still working on the native .NET ogg tagging library. It already works well for non-multiplexed ogg vorbis, ogg flac and native flac files. Concerning multiplexed files, I've got two short questions: 1) Is it valid to insert an "empty" page into the stream which simply contains the binary value 0 for the page_segments counter, and which therefore contains no segment

Hello, Hope everyone is enjoying their holiday! We setup two asterisk servers (From CVS on Wednesday) and set up IAX between the two. Right now they both reside on a switch with a static 192.168.0.x IP address. The first Server is .5 and the second is .30. Our dialplan seems to be working, however on the console we get a flurry of NOTICE and WARNING messages. NOTICE[1116941120]: File

Hi there. I mentioned in my before postings that I had compile errors because of some automake incompatiblity. Now after installing redhat 8 these are fixed, and the ogg directory compiled fine, but vorbis gave me an error while it wanted to make a pdf file. (!! Why the hell would a make want to create a pdf?!?) These are some parts of the error log as the whole is too long: ... cp

Hi all, just letting you know that I am about to submit the final version of the Ogg 1.0 file format Internet-Draft to the IETF. It is due by today (March 3, Monday - Internet Draft final submission cut-off at 09:00 ET) for the next IETF meeting and I expect they will promote it to RFC status at the meeting. Please send any last-minute changes to me. Cheers, Silvia. <p><p>

Hi all, just letting you know that I am about to submit the final version of the Ogg 1.0 file format Internet-Draft to the IETF. It is due by today (March 3, Monday - Internet Draft final submission cut-off at 09:00 ET) for the next IETF meeting and I expect they will promote it to RFC status at the meeting. Please send any last-minute changes to me. Cheers, Silvia. <p><p>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I thought I would separate this out into a separate mail since it's not comment specific stuff -- There seem to be a couple of inconcistanies in the Ogg spec as regards to lacing values: *) "The raw packet is logicaly divided into [n] 255 byte segments and a last fractional segment of < 255 bytes." However, in the wild, I've

Monty, I recently noticed half a patch in my libogg tree, and thought I'd forward it for discussion. I did this some time ago when were were talking about the long pages issue. The basic idea is to allow pages to grow up to 100% above the flush threshold if this allows us to end at a packet boundary. This reduces the frequency of pages with spanning packets which should be some assistance to