similar to: work on OggFile/OggStream

In the effort of reducing list traffic, I've consolidated two replies into one: On Tue, Nov 08, 2005 at 08:24:33PM -0800, Ralph Giles wrote: > > BTW, there are already a number of general "raw" video formats in > professional use; it's not just AVI we have as prior art. :) > I'd like to see some discussion of the merits of adopting one of those > if we

On Fri, Nov 11, 2005 at 07:17:53PM +1100, Erik de Castro Lopo wrote: > We're talking about a file header here. Even if the header is a kilobyte in > size, it will be completely **dwarfed** by the audio data following. So why > are you counting single bits like this? Why waste? You only have to read the header once for a stream, and libogg2 provides a convient bitpacker which can

On Wed, Nov 09, 2005 at 09:59:02AM +0800, illiminable wrote: > > While it's true there are a bunch of FOURCC's that represent non-raw > formats like DIVX etc, the ones which represent raw YUV types are pretty > well defined. Yes you certainly still need the width, height, aspect ratio > and frame rate. Since FourCC is an identifier for a different codec, what you are

(w. quotes from the xiphmeet: <http://westfish.xiph.org/~giles/200603_meeting.txt>, I've tried to strip it down to relevant stuff) <xiphmont> "Is there any interest in extending vcedit/libvorbisfile to do basic handling of Vorbis streams from concurrently multiplexed Ogg?" < xiphmont> Yes, but that work was *also* tied to OggFile from way back when, and one

----- Original Message ----- From: "Ian Malone" <ibmalone@gmail.com> To: "ogg-dev" <ogg-dev@xiph.org> Sent: Friday, March 10, 2006 5:24 PM Subject: Re: [ogg-dev] oggfile, skeleton and vorbis tools >> This is something we might want to extend skeleton to support, i know >> we've talked about this kind of thing before. So that skeleton can

On Wed, Mar 01, 2006 at 10:36:38PM +0000, Ian Malone wrote: > I assume what this all means is there's no desire for any kind of stop- > gap libvorbisfile that does the "vorbis out of any otherwise valid Ogg > stream"[1], and that anything along these lines will wait until Oggfile. Well, vorbis-only vorbisfile is what we're talking about. What Sylvia mentioned was that

illiminable wrote: > > ----- Original Message ----- From: "Ian Malone" <ibmalone@gmail.com> > To: <ogg-dev@xiph.org> > Sent: Friday, March 10, 2006 8:42 AM > Subject: Re: [ogg-dev] oggfile, skeleton and vorbis tools > > >> Re-reading Monty's email: when you talk about vorbis-only vorbisfile and >> the concurrent vorbis stream case do

Conrad Parker wrote: > On Tue, Mar 07, 2006 at 12:10:57PM -0500, Monty wrote: > >>On Wed, Mar 01, 2006 at 10:36:38PM +0000, Ian Malone wrote: >> >>>I assume what this all means is there's no desire for any kind of stop- >>>gap libvorbisfile that does the "vorbis out of any otherwise valid Ogg >>>stream"[1], and that anything along these

On Thu, Nov 10, 2005 at 10:13:19AM +1100, Erik de Castro Lopo wrote: > > a) There is no marker to distinguish little endian data > from big endian data. The original reason for this is because Ogg makes such a matter moot, since the bitpacker in libogg2 handles endian.. however, if a "chunk" packer is made available (similar to memcpy), this becomes important since

On Tue, Nov 15, 2005 at 09:44:43AM +1100, Jean-Marc Valin wrote: > > Sorry, but that fork took over now. As I mentioned in the last email, > your version needs to be renamed ArcPCM to reflect the fact that it's a > mix of Pulse Code Modulation with your ego. No. I started OggPCM, since it was never proposed to Xiph.org it remains my trademark until which time it is accepted by

On Fri, Nov 11, 2005 at 05:29:52PM +0800, illiminable wrote: > > (quote:"and thus the subject of FourCC labeling in OggStream's native video > interchange formats is closed.") > > ... doesn't sound like community debate to me. > > Maybe i missed the meeting where you became god here. If you are going to > make claims that you somehow are in charge

On Wed, Nov 09, 2005 at 01:14:08PM +0800, illiminable wrote: > > >I agree, which is why I wrote the OggPCM draft when we already have FLAC. > >These > >formats are not difficult to design or implement, and I think the added > >efficiency and simplicity will more than make up for it. > > Which i looked at... and i'm wondering why on earth it has a sync code

----- Original Message ----- From: "Ian Malone" <ibmalone@gmail.com> To: <ogg-dev@xiph.org> Sent: Friday, March 10, 2006 8:42 AM Subject: Re: [ogg-dev] oggfile, skeleton and vorbis tools > Re-reading Monty's email: when you talk about vorbis-only vorbisfile and > the concurrent vorbis stream case do you mean vorbisfile will need to be > able to choose?

On Tue, Mar 07, 2006 at 12:10:57PM -0500, Monty wrote: > On Wed, Mar 01, 2006 at 10:36:38PM +0000, Ian Malone wrote: > > I assume what this all means is there's no desire for any kind of stop- > > gap libvorbisfile that does the "vorbis out of any otherwise valid Ogg > > stream"[1], and that anything along these lines will wait until Oggfile. > > Well,

On Tue, Nov 08, 2005 at 04:59:33PM -0800, Arc wrote: > This is also interesting work in that, once we're done, we'll have a standard to > use for a compressed lossless format.. a FLAC for video, for editing or archival > purposes, similar to HuffYUV. Well, we're talking about an uncompressed format. OggMNG is already "FLAC for video". However, it doesn't do

On Wed, Nov 09, 2005 at 10:52:53AM +0800, illiminable wrote: > > "fourcc" 's of rgb types > http://www.fourcc.org/rgb.php I'm prowd to say that http://wiki.xiph.org/OggRGB supports all of these losslessly as well as PNG for non-indexed bitmaps. These are video formats, correct? Not just single frames? > raw yuv formats only > http://www.fourcc.org/yuv.php

I've noticed many people manually entering .. [[User:*|*]] on the talk pages to sign their contributions.. Just a friendly note that "--~~~~" is shorthand for your signature w/ timestamp. I just recently learned that, myself. In addition, I'd like to say how awesome our little community of hackers have been oven the past week. IRC, email, the lists, and the wiki have

On Tue, Nov 15, 2005 at 03:10:22AM +1100, Erik de Castro Lopo wrote: > That spec is being superceded by: > > http://wiki.xiph.org/index.php/OggPCM2 The project has been forked, not superceded. Work on OggPCM is continuing, the team working on OggPCM2 is free to submit their own draft but some are not welcome to continue work on OggPCM due to their recent social conduct. I'm

> If you want to limit the allowable values for the FourCC field, I don't have > an issue with that, but I think it's useful for decoders to be able to tell > easily whether or not they support the format (since most decoders will > operate on the well defined formats) and useful for encoders, since most data > sources are described by a fourcc (the exception being

In response to (and with the help of) John Koleszar I put together an early draft of OggYUV.. or rather, a list of header fields for it. http://wiki.xiph.org/index.php/OggYUV Feedback (on list or on wiki) is most certainly solicited, especially on the chroma subsampling list (how many different sampling methods do we need to reasonably support?) and if we've missed any fields to date.