similar to: Flac woes

There are not bugs in flac, they are bugs in your Alesis HD24. What you are asking for are features to be added to flac to fix the bugs in your Alesis. flac is the wrong place to be addressing errors in your Alesis hardware. A better solution would be a stand-alone program which can patch the errors in your WAV files, possibly asking for your choice in which way to do so (there is more than

Hello, using flac 1.1.2 regularly failed recently to encode a specific set of WAV files I got from the Internet. Listen to these files with XMMS, Audacious works fine. See the following output: options: -P 4096 -b 4608 -m -l 8 -q 0 -r 3,3 Track01.wav: WARNING: found non-standard 'fmt ' sub-chunk which has length = 30 Track01.wav: ERROR: unsupported compression type 85 What could I do to

"Free Lunch" <freelunch@gmail.com> wrote: > I did a search on the error message and found someone else with a > similar problem and Josh's reply said: > > > but the wave file seems invalid. sample data is supposed to be > > padded to an even number of bytes. > > The gotcha here, as I have tried to explain in similar cases before, > is that we do

Okay.. I love flac but just had a rather serious failure that really shakes my confidence. It resulted in the near loss of a master audio recording. Fortunately, I have a backup. Though there may have been other cases where I have lost original material because I have been compressing a lot of originals and deleting them after doing a 'flac -t' on them. Basically, flac failed with a

i had the problem is flac 1.1.2 so upgraded to 1.1.4 but now the problem is just different. the wav file is from audacity, so i guess it is culprit for setting that format type 1 bit, but shouldn't this still work? i found in 1.1.2 (before i found 1.1.3 had the odd size fix judging by relnotes) that i could add a dummy byte to the end and this seems to fix my issue, just not cleanly. here

The commit http://git.xiph.org/?p=flac.git;a=commitdiff;h=99257e177eac96fa41a107b423080232f59ebe45 also requires some changes in write_iff_headers() function: currently flac don't write WAVEFORMATEXTENSIBLE header if decoder_session->channel_mask is equal to 0, 1 or 3. After the commit 99257e17 flac should do this for channel_mask equal to 0, 4 or 3. The patch fixes this.

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

Hi, In the last days I've been taking as reference the example found in examples/c/encode/file/main.c. With it I've been able to encode a 2ch, 16 bps, 44100 sample rate input WAV file to a FLAC file. Now I've been trying to modify this example to encode a 2ch, 24 bps, 96000 sample rate WAV file. I have to say I'm a bit lost on how I should read the input file in this case, and

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 Mittwoch 09 Mai 2001 02:53, you wrote: > > > first I should say that it MIGHT not be because the file is > > > large. the wave reader in flac is pretty rudimentary and if there > > > is any sub chunk between the wave header and data sub chunk flac > > > will give you that error. could you inspect the wav file to see > > > if that's the case?

Hi, there is an interesting case when the FLAC encoder (using 1.2.0) is given simple waves. Simple waves means: I have a list of {frequency, duration, pause} tuples that define the monophonic tune. In other words, exactly one frequency is played at a time. This is the original dataset from 1989 (driving a PC speaker back then): $ ls -l ihold.sd -rw-r--r-- 1 jengelh users 20616 Aug 14 00:57

Hello, I'm attempting to convert fairly large WAV files (90 - 800 MB each) using flac but the files do not work after the encoding. (The play fine in wav format) Command I'm using: flac --verify -8 file.wav Attempting to run the file with either flac123 or the default player for Ubuntu (Movie Player?) results in the extremely terse messages: Default Player: "An Error Occurred:

Thank you for the reply! I know that my system can play flac files, I've played others I've managed to convert using both of those programs. I'm only running into difficulty when it comes to these large WAV files. By "Does not work" I mean that they do not play, and instead I receive the errors I mentioned in my original post. I wasn't actually intending to use

hi. 1. I tried to encode some wav files with a size of 700MB - 1.1GB and got the message: "ERROR: no data sub-chunk". I used flac version 0.8 and 0.9. 2. It would be nice if flac displays the filename of the current used file. the reason: I started flac with a command like this: "flac -d 1.flac 1.wav; flac -d 2.flac 2.wav; flac -d 3.flac 3.wav; flac -d 4.flac 4.wav; flac -d

Hi FLAC team. I feel I have found a super high compression way of FLAC. I have tested a 1 hour WAV file of 440HTZ with a 5,25,50,75,100 normalize volume preset. This dramatically changes the compression size of the end FLAC file even though the WAV file size is identical for all 5 WAV files. Only the volume is different. When you renormalize the WAV to its original volume the file is still 100%

Thank you for writing and pointing out that one can have WAVE files without getting the warning, and that your library does it. I found out Goldwave (Windows software) writes 24-bit WAVE files that do not get the warning. (Good for them!) However, the flac executable from the flac reference software apparently produces WAVE files that do get the warning. Example annotated log: Encode a 24-bit

On Sun, Jun 08, 2003 at 02:06:18AM +0200, Paul Seelig wrote: > This is what i get when trying to encode a WAV file: > > ------------- snip ----------------- > [pseelig]/tmp > flac -o YouGotMail.flac YouGotMail.wav > > flac 1.1.0, Copyright (C) 2000,2001,2002,2003 Josh Coalson > flac comes with ABSOLUTELY NO WARRANTY. This is free software, and you > are welcome to

Dear All, I've sent yesterday this issue, but as it contained two screenshots, I'm not sure if it reached the list. I post it again with some updates. 1) I had encoded a WAV file three years ago. Examining the FLAC file with an HEX/text viewer, i find at the beginning, after some headers, it declares reference libFLAC 1.3.1 20141125. However, I'm pretty sure I didn't use that

Josh Coalson <xflac@yahoo.com> wrote: > --- Scott F <graue@oceanbase.org> wrote: > > > If I use flac to encode with the --replay-gain > > option, I get a warning about the --no-padding > > option... > > > > "NOTE: --replay-gain may leave a small PADDING block even with > > --no-padding" > > > > ...even though I'm

So let me get this straight... I can put a CD in my computer and copy it to my hard drive as a wav files. Then by using FLAC to "compress" said wavs into .flac files. Resulting in approx. half the file size. Then later I can convert the FLAC files back to wav and the end up with the EXACT wav file I had before ? If this is the case, then great, but can you really cut out half the