similar to: OggPCM (uncompressed Ogg audio)

On Wed, Nov 09, 2005 at 05:33:37AM -0800, Arc wrote: > > Data pages are identified to be part of a logical bitstream through their > > serial number, so don't need any additional identifiers. Thus, Arc, I don't > > quite understand why you would require another 32 bits at the beginning of > > each data packet, when ogg pages are already covering that

Thanks Silvia for your response :-) It's good to get constructive discussion on this, and I've been hoping to have exactly this kind of criticism re: OggPCM for some time. On Wed, Nov 09, 2005 at 10:21:04PM +1100, Silvia.Pfeiffer@csiro.au wrote: > > Data pages are identified to be part of a logical bitstream through their > serial number, so don't need any additional

On Wed, Nov 09, 2005 at 09:31:29AM -0800, Ralph Giles wrote: > > > > I am open to eliminating it, if it can be shown that the act of reading or > > skipping this data complicates implementation or makes it less efficient, > > however, the decidion to do so should include several people (Monty, Ralph, etc) > > who haven't joined this discussion yet. > >

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

Moved off OggYUV thread as this is off-topic for it.. On Wed, Nov 09, 2005 at 04:51:51PM +0800, illiminable wrote: > > > >Um, data packets consist of a 32-bit header followed by PCM data. Where > >did you get the idea that "sync" data was in the packet? > > That's what the first 32 bits of "header" are. Um, no, the first 32 bits of the header is

Hi, this message is a cross-post to the Sursound and ogg-dev mailig list. The developers on the ogg-dev list are defining the Ogg/PCM format and on Sursound list there discussion about Amisonics file formats recently. I have not been able to follow both disussion, just skimmed through. But maybe you can work together to bring Ambisonics into Ogg/PCM? :) http://wiki.xiph.org/index.php/OggPCM

Hi all, I am trying to set up the codecs table in the wiki and we have played a bit with Dirac to find out what existing tools write into the header. The Schroedinger implementation by Fluendo uses (or used to use) "KW-DIRAC" as the identifier in the Ogg header. "BBCD" is the identifier of each of the Dirac data packages. More recently, I read that the Dirac Sequence header

This is getting very dangerous. We cannot take our flamewar to outside mailing lists without making a complete fool of ourselves. Arc, would you please refrain from doing so in future and rather come to an internal agreement beforehand? Arc, there are a few things you have missed: The discussion on OggPCM2 was friendly and constructive and there were no flame wars and the spec got much further

Hi Rene, we have discussed the issue of different formats per channel, e.g. different sampling rates. It was not clear whether with PCM sampling of devices this is actually a common (or even used) case. Do you know how multi-channel sound is sampled? Is it created with different widths/rates on different channels? If it is not a common case, we can leave the solution to different streams and

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

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 all, Siliva contacted me about this OggPCM proposal and asked me to join in. For those who don't know me, I am the main author and maintainer of libsndfile and therefore know quite a bit about how uncompressed audio is stored in sound files. However even I would not consider myself an expert; there are areas to do with channel assignments that I know I am ignorant of. I am also quite

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, I'd support the view of freezing the main header, since it helps in actually getting some implementation happening and it seems fully agreed on by everyone. FAIK, Zen has already started an implementation and if you, Conrad, implement, too, there is enough code to do validation. What do you expect now to make it an "officially frozen" specification? Publish it on the main

Arc wrote: > Does endian vary widely for raw audio codecs, Well there are really only two endian-nesses, big and little. WAV is usually little endian but there is also a (very rare) big endian version. AIFF is usually little endian but also supports big endian encoding. CAF, AU, IRCAM and a number of others support both endian-nesses equally. > or would it be reasonable > to settle

(second try at sending this) --- This is getting very dangerous. We cannot take our flamewar to outside mailing lists without making a complete fool of ourselves. Arc, would you please refrain from doing so in future and rather come to an internal agreement beforehand? Arc, there are a few things you have missed: The discussion on OggPCM2 was friendly and constructive and there were no flame

On Thu, Nov 10, 2005 at 01:35:47PM -0800, Arc wrote: > > "Please don't make determination of the data format depend on > > multiple fields. Instead use an enumeration so that something > > like little endian 16 bit PCM can be specifed as OGG_PCM_LE_PCM_16 > > and big endian 64 bit doubles can be specified as OGG_PCM_BE_FLOAT_64. > >

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