similar to: Odd number of samples in a stereo wave file

This topic is possibly more appropriate on the flac-dev list, since most flac users are not going to be interested in the details of WAVE format errors. Assuming it's ok to keep talking about it here... Ben, you've stumbled upon one of the common shortcomings of specifications. There are often assumptions which are not spelled out, or there are pieces which are vague. In some

I'm new to the mailing list but am interested in picking up a thread from earlier in the month but which I thought had become confusing so I am starting again. I should admit from the beginning that I am a colleague of Alex Brims who started the original thread. The thread in question related to a wav file with an extra two bytes at the end causing a partial sample error in the reference

I'm new to the mailing list but am interested in picking up a thread from earlier in the month but which I thought had become confusing so I am starting again. I should admit from the beginning that I am a colleague of Alex Brims who started the original thread. The thread in question related to a wav file with an extra two bytes at the end causing a partial sample error in the reference

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

Not sure if this belongs here or in flac-dev. I am subscribed to both, so flop it over if fits better over there. Looking at the Changelog for FLAC 1.2.1 (17-Sep-2007), it says: "With the new --keep-foreign-metadata in flac, non-audio RIFF and AIFF chunks can be stored in FLAC files and recreated when decoding." Where can I find more detail on what is a

On 16/11/2007, Brian Willoughby <brianw@sounds.wa.com> wrote: > It would actually be punitive to expect the flac code to expect and > adapt to nonsensical WAVE files. You say "punitive". I say it would be "reliable". One missing byte is a huge burden and nonsensical? People post on this list looking for solutions. They don't want to become experts in the WAV

Martin, I do not believe that there is any need for code specifically supporting Ambisonics. FLAC supports conversion to and from other audio formats which hold multiple channels. Ambisonics B-format involves channels WXYZ, C-format is UHJ or BHJ, G-Format can be any number of channels, but typically 5.1 on DVD. You can work with Ambisonic recordings by either using individual mono

Sampo Syreeni <decoy at iki.fi> wrote: ... > [I]n > well-designed and matched protocol environments, if you expect to see > some array of differing protocols, you will also see an easy way of > discerning those protocols from each other. Before engaging in any sort > of decoding endeavor. > > File names, resource fork types or IFF/RIFF block types do not seem to > be

Yes, WavPack is second in my list. FLAC doesn't preserve every chunk? I thought it did. I only gave a quick try but it seemed to have preserved even the most obscure chunks. Let me check: it even seems to preserve "MIDI note associated to marker", which is a very unknown metadata used by SoundForge (& even defined in a buggy way), so I assumed it was saving them

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

---------- Forwarded message ---------- From: Martin Leese <martin.leese at stanfordalumni.org> Date: Mon, 20 Dec 2010 21:42:04 -0700 Subject: To: flac-dev at xiph.org Erik de Castro Lopo wrote: > Can someone please remove this moron > spammer [Gourav Tewatia] from this list. And also delete their four posts from the archive (otherwise the SPAM links will be picked up by search

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

On Wed, Jul 22, 2009 at 7:24 PM, Martin Leese<martin.leese at stanfordalumni.org> wrote: > Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > >> Martin Leese wrote: >>> Anyway, calling alloc()s with no corresponding >>> free()s is a memory leak. Not good code. >> >> The alloca() function allocates space on the stack and >> that

On 10/21/07, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote: > On 10/21/07, Martin Leese <martin.leese@stanfordalumni.org> wrote: > > Either "OggPCM" or "OggPCM Draft2" needs > > to be deleted. It really doesn't matter which, > > but I would suggest that "OggPCM" takes the > > big sleep. Just give time for me (or Sempo)

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

On August 9, 2013, Silvia Pfeiffer wrote: > On Thu, Jul 25, 2013 at 6:36 AM, Martin Leese wrote: ... >> Should Speex and CMML be removed from >> the Wiki Sidebar > Don't remove Speex - it's still very much in use. > > We probably want to add Daala to the list of video codecs: > https://wiki.xiph.org/Daala > > We probably want to remove CCML from the

On Sat, Nov 29, 2008 at 2:20 PM, Josh Coalson <xflac at yahoo.com> wrote: > --- Martin Leese <martin.leese at stanfordalumni.org> wrote: >> Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: >> ... >> > Whats more, the sndfile-convert program can also convert >> > from FLAC to the following file formats that support 63 bit >> > file

On 7/23/13, Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote: > On Wed, Jul 24, 2013 at 3:59 AM, Martin Leese >> ... >>>> Information about Metadata >>>> has been collected together in the Xiph Wiki >>>> at: >>>> https://wiki.xiph.org/Metadata >> Page updated. See what you think. > > M3F is also not used anywhere

Apologies for cross-posting ... This project is looking for a maintainer. To quote from the Goose web site: "Goose is a LGPLed C++ library dedicated to statistical computation. The two design goals of this project are: To create a useful and complete system that takes advantage of C++'s features to improve the clarity of statistical code and that is easier to use for programmers. To

Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Martin Leese wrote: >> Anyway, calling alloc()s with no corresponding >> free()s is a memory leak. Not good code. > > The alloca() function allocates space on the stack and > that allocation is automatically freed when the function > that did the allocation returns. > > The Linux man page is quite