similar to: Re: Welcome to the "Flac" mailing list

dd if=$file ibs=1 count=$(($(stat --printf='%s' $file)-2)) of=$file.new of course if you run this on one of the files that doesn't have the extra 2 bytes you're gonna lose something you didn't want to On 11/1/07, 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

that's why i asked the original poster if the files were odd size, i had that issue before with a 24 bit mono file and wrote this script to fix it: #!/bin/sh # # sfoddfix - Sound File ODD size FIXer # # NOTE: flac v1.1.2 pukes on files that have an odd byte count, this pads them files=${*:-*.wav} for file in $files do size=$(stat --printf='%s' $file) if [ $(($size%2)) -ne 0 ];

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

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

Hi, I'm having problems encoding certain WAV files to FLACs. I'm working for a download store so we get loads of different WAVs from hundreds of suppliers and generally they encode ok, but sometimes we are getting unexplained errors. I've looked through the archives for the last few months but I can't see any discussions that relate to this specific problem. This file:

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

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.

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

Erik de Castro Lopo wrote: > Err, thats a link to a post talking about flac's WAV reader being limited > to 4Gig files. Problem is, *all* WAV files greater than 4Gig are mal-formed. > Due to limitations in the way WAV files are specified, no valid WAV file > can ever be over 4Gig. And most don't work over 2 GB. The solution we (Xiph) have used in other projects (opusenc,

That's a handy command, but I'm certain it won't work 100% for the file in question. The chunks in that bad file claim the extra two bytes are part of the file, so a wav format parser could come up short. You have to edit existing data in the file in two places before shortening the file - truncating the file is not enough by itself. The real problem is that the file was

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 program for linux that could automatically take these bytes off, without running the risk of removing

On May 13, 2007, at 05:45, Harry Sack wrote: > If I encode 192 kHz sound @ 24 bit for some days (WAV file) and I > encode it to FLAC, I think you can have a very big file and 1.5 TB > is reached very quickly. > And in the future audio will even get bigger, when used for HD-DVD > en Blu-ray media and 5.1 channels is considered the 'minimum' > setting for surround

Brian Willoughby <brianw at sounds.wa.com> wrote: > Hello all, > > Is anyone here potentially up to the task of adding support for CAF > (the CoreAudio Format) into the flac command-line? ... > I've already made some recordings > that are so long that they cannot be uncompressed from FLAC to WAV or > AIFF because they would exceed 4 GB - the maximum file size for

On 5/13/07, Brian Willoughby <brianw@sounds.wa.com> wrote: > If we ever reach this 64 GigaSample limit, the fact that FLAC is a > stream should allow multiple FLAC headers to be concatenated in a > single file - although that might be tricky. I believe you can do this with Ogg FLAC. The Ogg container manages the multiple FLAC streams. Theoretically, we'll never see limit

Brian Willoughby wrote: > The ckSize field can be odd to represent the size of the valid data. > > However, the chunk itself must always be an even size. This requires a padding byte at the end of a chunk before the next chunk can begin, or before the end of file. The latter case is the one that most often occurs in buggy RIFF writing programs - the last chunk will have an odd ckSize and

yes I know I can do that, but my question is if there is software to edit FLAC files without having to uncompress to WAV/recompress to FLAC. 2007/7/23, Avuton Olrich <avuton@gmail.com>: > > On 7/23/07, Harry Sack <tranzedude@gmail.com> wrote: > > hi > > > > does somebody know software for editing FLAC files? So I just want to > cut > > some pieces

(2013/03/05 12:27), Cristian Rodr?guez wrote: > Nothing against you code, that's ugly ..but as it is a first step it can > be forgiven :-) > > I will just force flac to be built with 64 bit file offsets and just > reject any caller trying to include/link libflac into a non-lfs program > like > > http://ac-archive.sourceforge.net/largefile/off_t_headers.html > >

This patch should fix ticket https://sourceforge.net/p/flac/bugs/419/ and its duplicate https://sourceforge.net/p/flac/support-requests/152/ some programs write odd value to ckSize of RIFF chunk. Not sure is it correct or not, but flac should read them anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: odd_riff_size.patch Type: application/octet-stream

On Dec 14, 2014, at 10:02 AM, lvqcl <lvqcl.mail at gmail.com> wrote: > Currently the header of a decoded WAV file can be different to the > original WAV file because FLAC doesn't preserve 'fmt ' chunk. > > For example: create a 24-bit stereo .wav file with WAVEFORMATEXTENSIBLE > header with channel mask == 3. Encode it to .flac then decode back to .wav. > FLAC