similar to: Ogg spec clarification

Hi, Is it expected that an Ogg logical bitstream might logically serve as the physical bitstream from which other logical bitstreams might be demuxed? I am not sure that I really see the point of doing this, but it would certainly be possible within the current spec. The trouble is that there are any number of ways to do the low-level muxing of several streams into one logical stream, with

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>

On Sat, 2006-07-15 at 14:35 -0700, Ralph Giles wrote: > On Sat, Jul 15, 2006 at 02:17:22PM -0500, Joe Wreschnig wrote: > > > I'm working on support for tagging Speex files for Mutagen[0] and part > > of the specification at [1] is confusing me. It says the first page > > should have granulepos 0 and packetno 0. Does this really mean page > > sequence number 0,

(Sending again after subscribing, I guess the moderator is on vacation.) I'm working on support for tagging Speex files for Mutagen[0] and part of the specification at [1] is confusing me. It says the first page should have granulepos 0 and packetno 0. Does this really mean page sequence number 0, since the Ogg format doesn't number packets? If it doesn't mean page sequence number,

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

Hi, I have some questions: 1) in the sources of the encoder_example (and of course in oggenc.c, too) I see a lot of dependance on ogg. I want to get totally rid of ogg and use the vorbis bitstream alone. From this reason stems the second question: 2) is there a definition of the vorbis bitstream somewhere? I don't need to know every single detail, just the informations necessary to

Hi, I need to encode some extra information in my sound files, in a separate logical stream. Some day I'd like this to be streaming, so for each page, I need to know whether it's a vorbis page or one of my own extra-info pages. I've read the "Ogg logical bitstream framing" document, but at the Ogg level the only "structured" info is the page header, and that

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

>From the top of vorbisfile.c: /* A 'chained bitstream' is a Vorbis bitstream that contains more than one logical bitstream arranged end to end (the only form of Ogg multiplexing allowed in a Vorbis bitstream; grouping [parallel multiplexing] is not allowed in Vorbis) */ Is this paragraph talking about multiple streams in a single Vorbis stream in an Ogg, or is it talking

Hi, The documentation at http://www.xiph.org/ogg/vorbis/doc/oggstream.html tates that "Each chained logical bitstream must have a unique serial number within the scope of the physical bitstream" Doesn't this mean that the sequential multiplexed streams have same serial number? I am confused looking at the following code segment in vorbisfile.c

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

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

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

> You don't have to parse the whole file, just enough to find all the > chain boundaries. That can still take some time, of course. Don't you have to parse the whole file to find those ? Technically, if you find two packets with the same serialno, it is possible that they'd be *different* logical streams just happening to have the same serial, which would be OK if there was

Why ov_open_callbacks(fd_, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) takes so long to open OGG file? The OGG file has just 210 MB. It takes a lot of time open the file. I am working on OGG audio recorder and player. Thanks in advance! With kind regards, Pavel

Hello Monty, Sorry for the wrong subject title last time. A little more clarification needed. When reading bit-by-bit, there is no MSb/LSb, just 'first bit' and 'last bit'. The Huffman tree is traversed from 'first bit' to last bit'. This is a conceptual layer above the bitpacker; all you need to know is what order the bits come out, which happens to be LSb-first.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiya folks, I've been hacking on an audio metadata library (creatively called TagLib) which we'll be using in KDE in the next release ( == I need to get around to finishing it). I've got the Vorbis comment implementation working, but just wanted to clarify a couple of things: *) The vendor ID -- "vendor" is ambiguous here. Is