similar to: Ogg and Vorbis questions

Hi John, all, I still have at least 3 issues: 1) What are we trying to achieve with the "source-ID"? 8 [uint] Source ID (Unique amongst all OggPCM streams in the physical stream) Are we trying to separate the different channels that may be interleaved with each other inside the flat multi-channel sample stream? Interpretation 1: ----------------- So, would each channel be in a

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>

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

I've just committed an image flip for compatibility with VP3 lossless transcode. Thanks to mau and derf for verifying that this was needed. It's a little hacky on the decode side; suggestions for improvement are welcome. Since this is a bitstream change, and we're still a ways from having a complete spec (which is the gating item for beta 1 and the bitstream freeze) we're

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

Hi All, I'm interested in incorporating support for the OggVorbis file format in a future update to my MP3 search engine, AudioPhilez (http://www.audiophilez.com). To be able to do this, I need some simple information. I would greatly appreciate it if you could help me out here: 1. Will a standard MP3 decoder find 'sync' in an .OGG file? My spider searches for sync (11 bits on) and

Hi, I recognize the main name behind CMML here :) Does the redesigning of CMML allow overlapping clips ? This is the main reason of my current ramblings about seeking. While karaoke was one of the initial goals behind kate, it is just a way the format can be used with (in fact, the format itself does not refer to karaoke at all, but styles and motions). At the moment, it is a fairly versatile

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

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

as per yesterday's discussion at #theora -- It has been suggested that we devise a method such that we will be able to add certain features to the bitstream (interlace, exotic color subsampling, clip length flag for download, etc), in such a way as to not obsolete streams encoded previously. Rillian's suggestion, which is pretty much standard practice, is to add a bitstream revision

On Fri, Aug 15, 2008 at 8:42 PM, Ian Malone <ibmalone at gmail.com> wrote: > 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >> Hi all, >> >> The IETF has a final draft of our RFC at >> ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes >> from 3534 to 5334 - funny!). >> >> If you have anything in need of change,

Hi, last week's thread about getting closer to a release fizzled out. The mailing list discussion and the TheoraTodo wiki item suggest the following are required for release: 1. freeze the theora logical bitstream format 2. complete the reference implementation tools 3. stablize the libtheora API 4. complete the documentation I'd like to suggest this as

We are working on OggVorbis encoder. In the porting effort we are trying to convert it to fixed point code (both 32 and 24 bit fixed point). Now the issue is how we do the testing. What should be the criteria for our testing. Does anybody has any idea how compliance testing (i.e. some objective tests) is done at encoder side? What is the criteria of testing at the encoder side? If anybody

I have made a patch to support libvorbis to allow parsing a vorbis bitstream in an ogg bitstream containing additional bitstreams. The patch is attached in the given ticket http://trac.xiph.org/ticket/925#preview from my experiment it successfully decodes a normal vorbis file and a vorbis+skeleton+cmml file. thanks in advance for reviewing it. -------------- next part -------------- An HTML

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, would you be interested in a patch to support kate bitstreams ? Kate is a bitstream format for text data that can be muxed in ogg, here presumably alongside a Theora video. It can be used to carry subtitles, and several separate streams can be muxed concurrently (eg, for subtitles in several languages). More info about Kate can be found there: http://wiki.xiph.org/index.php/OggKate Note

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