similar to: AW: packets and OGG pages

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

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

Ralph, thanks for your help. >>Since the length of the precedent identification header is fixed, this even is a fixed offset >>into the logical ogg stream. >This will work for all the vorbis-only files I've seen (because no one >pads the first packet). You should really implement a proper ogg parser, >but by all means get a hack working first. I will of course use 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 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, > >

>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

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

Hi Arc, illi, I think it would be advantageous if we take the emotion out of this discussion , so let's just argue technically. My experience with xiph is that we are a very friendly community and trying to help each other and listen, so let's keep that culture up. I think we all agree: it is a good idea to have an media mapping for ogg for uncompressed PCM. As for what is required in a

Hi John, I'm forwarding this email to the relevant developer lists at Xiph.Org, where the format was created and where the experts gather. I'm certain there is a design reason for putting the bos pages of all logical bitstreams together at the start. My guess is that with digital media you usually have a delay time for setting up the decoders for a specific format and by clustering

Hi John, I'm forwarding this email to the relevant developer lists at Xiph.Org, where the format was created and where the experts gather. I'm certain there is a design reason for putting the bos pages of all logical bitstreams together at the start. My guess is that with digital media you usually have a delay time for setting up the decoders for a specific format and by clustering

HOgg 0.4.1 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the fourth public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly 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

Howdy, yeah, I've finally collected all your feedback on my I-D on the Ogg encapsulation format, many thanks to all of you! Below, I've listed the changes that I have made to the previous version and the attachment contains the complete new I-D. If there are any more change requests, please send me wording proposals as it's easier to include. :) Monty, in case you are doing any

Howdy, yeah, I've finally collected all your feedback on my I-D on the Ogg encapsulation format, many thanks to all of you! Below, I've listed the changes that I have made to the previous version and the attachment contains the complete new I-D. If there are any more change requests, please send me wording proposals as it's easier to include. :) Monty, in case you are doing any

HOgg 0.4.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the third public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

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>

Hello, I've mainly finished the native ogg Vorbis tagging .NET library. It already works well for reading and writing the vorbis comments for the files I tested. The library only rewrites the entire file if it has to, and adds 2 K padding in this case so that further changes of the comments won't make it nescessary to rewrite the whole file again. I found out foobar2000 also does it this

Hello, > (1) Split the content into chain segments > (2) extract the first and last data packet from each segment, for all tracks > (3) recover / calculate the granulepos values for the first and last data packets (*) > (4) convert the granulepos values from the first and last data packets into time values > (5) take the largest difference between start and end time as the total

Another spin-off discussion. The scheme used on <http://wiki.xiph.org/index.php/Metadata> was to packetize XML (split it up into packets at the root level, each of which was self contained (the terminology has temporarily abandoned me), and have the bos packet as the opening <?xml &c. stanza, the eos a </xml>. It is probably more sensible to include a magic number identifying