similar to: --keep-foreign-metadata question

On 9/26/07, Josh Coalson <xflac@yahoo.com> wrote: > --- Martin Leese <martin.leese@stanfordalumni.org> wrote: ... > > Where can I find more detail on what is a > > "non-audio" RIFF chunk? > > it is any riff chunk that is not "fmt " or "data" > > > Ambisonic ".amb" files are WAVE-EX files with > > a

On 3/22/07, Brian Willoughby <brianw@sounds.wa.com> wrote: ... > But to return to your question, exactly what kind of "support" are > you looking for? I wasn't looking for any particular support, but just to see what support was there (if any). ... > I do not believe that there is any need for code specifically > supporting Ambisonics. FLAC supports conversion to

On 2/28/07, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote: > On 2/28/07, Ralph Giles <giles@xiph.org> wrote: > > Well, there are todo pages at wiki.xiph.org, but I meant more in the > > community folklore sense. My point is a roadmap doesn't help much unless > > there are people committed to making things happen. That's been the > > problem with a

On 2/28/07, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote: > On 2/28/07, Ralph Giles <giles@xiph.org> wrote: > > Well, there are todo pages at wiki.xiph.org, but I meant more in the > > community folklore sense. My point is a roadmap doesn't help much unless > > there are people committed to making things happen. That's been the > > problem with a

Hi, I have posted this three times to the flac-dev, vorbis-dev, and ogg-dev mailing lists. I wanted to see what code there was currently to support Ambisonics. So I downloaded the code from the xiph download page for libogg-1.1.3, libvorbis-1.1.2, vorbis-tools-1.1.1 and flac-1.1.4, but wasn't able to find anything. If it exists then I missed it, so could somebody please point me to it.

"Alex Brims" <alex.brims@gmail.com> wrote: > Ok, we actually worked this out - there were 2 extra bytes doing nothing at > the end of the files. Opening the file in SoundForge and saving it (without > changing it) took off the extra bytes and allowed the file to convert to > FLAC. > > Thanks to everyone who emailed me suggestions. > > Is there a decent

"Gabriel I." wrote: > Greetings, > > I apologize if I posted this in the wrong list, I wasn't sure where to post > it, but seeing as the tags are called "vorbis comments" I thought vorbis, > rather than ogg-dev, would be the right choice. (actually, I'm not even a > developer anyway) Hi Gabriel, I doubt whether the Xiph community would promote a

>Yesterday I have finished writing the ambisonic pan filter for oggenc. May I ask what this "pan filter" is? I made some tentative suggestions for coupling Ambisonic B-format in a post "Vorbis Ambisonic coupling" on 4feb07 I gather from the last monthly meeting, that some of you, including Monty, had problems with the phase behaviour of B-format. Would anyone like a

lvqcl wrote: > Martin Leese wrote: >> Note that the channel order may not be defined. > > IMHO it doesn't matter in this place of documentation (which describes > default channel assignments for FLAC). Your proposed wording was: 0000-0111 : (number of independent channels)-1. The channel order follows SMPTE/ITU-R recommendations. The assignments are as follows: The

"Didier Dambrin" <didid at skynet.be> wrote: ... > I like FLAC on the paper because of its metadata preservation, in that riff > tag, which is critical for my needs. Try using WavPack, http://www.wavpack.com/ This can losslessly compress 32-bit floating point WAVE-EX files, and faithfully preserves every chunk (which FLAC does not do). It is also free. Regards, Martin --

Where can I find the Header file or whatever which specifies the "Mapping" flag. In feb - apr 2007, there was a lot of discussion about Ambisonics and Monty kindly stated that Mapping = 1 ; Denotes and Ambisonic file as opposed to = 0 which is 1 speaker/ 1 channel Has this been written explicitly into the standard? Which standard should I be looking at?

Ian Malone <ibmalone@gmail.com> wrote: > It depends what your aim is. The mapping type > in the vorbis setup header is meant for > this[1],[2]. Of course a nonzero mapping type will > cause a lot of players to give up, but so will > including the XML stream. I believe this is how > is was intended multi-channel would be handled. Thanks for the response, and for the

Brian Willoughby <brianw at sounds.wa.com> > Isn't there a standard option to place FLAC data within an Ogg > container? I don't use it myself, but I understand that it is quite > popular. Would it be possible to interleave multiple FLAC blocks > this way? In other words, can Ogg suffice as the second level of > grouping that you refer to? Etienne was asking for

Erik de Castro Lopo <mle+xiph@mega-nerd.com> wrote: > Martin Leese wrote: > > So what is "OggPCM"? I started this thread > > because I was puzzled why someone was > > changing a draft instead of the document > > itself. > > The original OggPCM was started by a person who really didn't > lnow what they were doing and wouldn't listen to

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

On 10/25/18, Rodger Combs wrote: > >> On Oct 25, 2018, at 12:47, Martin Leese <martin.leese at stanfordalumni.org> >> wrote: ... >> An alternative approach is to only define >> popular layouts. For more obscure layouts, >> such as 2.1 and Mid/Side, assume that the >> person doing the encoding knew what they >> put in, and so knows what will come

Brendan Bolles wrote: > Hey everyone, according to Wikipedia's 4-year-old information, there is no > standard for putting metadata into an Ogg file. True. > That metadata must be > included in the codec. More generally, in a stream in the Ogg file. Codecs are streams, but so are things like Ogg Skeleton. Information about Metadata has been collected together in the Xiph Wiki

On 7/23/13, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > On 23 Jul 2013 15:17, "Martin Leese" <martin.leese at stanfordalumni.org> > wrote: ... >> Information about Metadata >> has been collected together in the Xiph Wiki >> at: >> https://wiki.xiph.org/Metadata > > That page is a bit outdated. It has CMML in it which we

"Kurosawa, Taku" wrote: > Hi Martijn, > > Sorry for the late reply again, > The application we are preparing this time is not exactly similar to > Replaygain. > > Replaygain as we understand is something which normalize the loudness at > content provider side, but our application takes different approach. It is > designed to normalize the loudness at player

Rodger Combs wrote: > I've run into some issues using Opus with source files in channel layouts > other than the default 8. For instance, 2.1 isn't supported, so I have to > either downconvert to 2.0 or upconvert to 5.1 (which usually involves adding > empty channels, which prevents the playback device from upconverting to the > native layout). > To address this,