similar to: flac test mode is very useful

If md5sum --check did not return an error with a truncated file, then the file was likely broken to start with. I think the chances of a corrupted file generating the same md5sum is close enough to 0 that you will never see it in a life time. Also, you lost me on storing the md5sum value at the begging and the end? On Wed, Jul 29, 2009 at 4:44 AM, Dat Head <dathead2 at gmail.com> wrote:

On Dec 18, 2009, at 12:12 AM, Brian Willoughby wrote: > > On Dec 17, 2009, at 20:42, Ron Decline wrote: >> Anyway, as you and dathead2 suggested, I can just flac -d, then swap the channels on the wav with SoX, and then flac -a, I can then use metaflac to transfer the tags. Easy enough to write a script to do the work. > > > flac -a will analyze, not encode. Apart from

On Dec 17, 2009, at 11:02 PM, Brian Willoughby wrote: > > On Dec 17, 2009, at 19:00, Ron Decline wrote: >> On Dec 17, 2009, at 8:50 PM, dathead2 at gmail.com wrote: >>> On Dec 17, 2009, at 8:42 PM, Ron Decline <rutlecorps at gmail.com> wrote: >>> >>>> Is it possible to switch the Left / Right channel when encoding in FLAC? >>>> (I have

> On Dec 17, 2009, at 8:50 PM, dathead2 at gmail.com wrote: > > On Dec 17, 2009, at 8:42 PM, Ron Decline <rutlecorps at gmail.com> wrote: > >> Is it possible to switch the Left / Right channel when encoding in FLAC? >> (I have some flac files with incorrect left/right channel assignment that I would like to re-encode with flac) >> _____________________________

I was going to start storing the flac version number and options in an ENCODER meta field and with v1.1.2 if you did: flac foo.flac 2>&1 | grep options you could see the defaults options, in 1.2.1 it doesn't print the options (even if you give it a valid flac file name) i.e. options: -P 4096 -b 4608 -m -l 8 -q 0 -r 3,3 here was what i was going to do: metaflac

Correction, the flac command-line does create a 40-byte Vorbis comment by default. I just never noticed it before. I’ve been using —no-padding all these years for minimal file sizes without realizing that I could save another 40 bytes. Anyway, since metaflac can remove the Vorbis comment using the standard library, then you should be able to create a solution without modifying libFLAC. Brian

Great info. I found some descriptions of st5 (md5 fp) and ffp, where I assume that "fp" is just a Taper abbreviation for "fingerprint" - or signature as it's called in the flac header. However, I could not find these utilities or source code. What I found looked like instructions for a gui-based program. I think it would be easier to support Mac if st5 were

i'ld just like to have a car unit that you can put a USB stick in, a friend has one for mp3 and it is just what i want (but w/ flac support)- now that 4GB USB sticks are around you can get a lot on there in flac! > --- Brian Willoughby <brianw@sounds.wa.com> wrote: > > > are there any car stereo flac players?

In windows command line: I have a wav file and would like to see what the flac fingerprint would be. To do this I run flac to encode the wav file and write the flac file to the hard disk. I then run metaflac to read the flac file and display the fingerprint. Is there an existing way or other utility to do this without generating the flac file on the hard disk. I would think it could be quicker

I wasn’t suggesting that you run metaflac, but that you examine its source to see how it creates new FLAC files without the Vorbis comment. As far as I know, metaflac uses the standard libFLAC and creates files without the Vorbis overhead. My quick review of the source seemed to indicate that calling FLAC__metadata_object_new(FLAC__METADATA_TYPE_VORBIS_COMMENT) will create the comment, but I

wow, that was a mighty keen eye - you must really have been looking at it (thanx!) - that is just a typo, the example just above and below that line still show that the issue i'm having exists. an easy test anyone can do is: metaflac --version metaflac --show-sample-rate c:/any.flac metaflac --show-sample-rate /cygdrive/c/any.flac On Dec 13, 2007 5:43 PM, Christopher Brown

This is 1.3.1 on OpenBSD/amd64. The --no-utf8-convert option of metaflac(1) does not work for me: $ metaflac --no-utf8-convert --set-tag="Artist=?ou?l??ek" aladin.flac aladin.flac: ERROR: tag value for 'Artist' is not valid UTF-8 (You probably can't see the Czech letters properly in my mail, but that's beside the point.) Indeed, it is not valid UTF8 (it's LATIN2),

Harry Sack wrote: > > > 2007/3/29, Brian Willoughby <brianw@sounds.wa.com > <mailto:brianw@sounds.wa.com>>: > > There actually is no problem with 24-bit support, as I stated > earlier. So before people start chiming in with "me too" - I'd > like to request that you actually say what problem you're seeing, > along with a few

--- Dat Head <dathead2@gmail.com> wrote: > On Dec 28, 2007 12:37 PM, Dat Head <dathead2@gmail.com> wrote: > > I was going to start storing the flac version number and options > > in an ENCODER meta field and with v1.1.2 if you did: > > flac foo.flac 2>&1 | grep options > > you could see the defaults options, in 1.2.1 it doesn't print the >

Hello all I am using libFLAC in a corner application, compressing *a lot* of small signals. First is a general question: in our application we have signals in range 5-10 MHz, potentially 40MHz! Is there any potential problem with that?? The mac sample rate is limited in flac, but it doesn't really seem to be a problem. The output is stored as blob in a sqlite database, it *never *needs to be

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

Why isn't the compression level added in a metadata block by the flac encoder itself (just like the encoder version)? In this way all programs that read the file can see what compression level was used. thx 2007/7/4, Scot Thompson <scot.thompson@cox.net>: > > This has been asked many times. The answer is no. I suggest saving the > compression level into a tag for future

--- Brian Willoughby <brianw at sounds.wa.com> wrote: There are no uncompressed files here, so it's difficult to discover what you need to know. --- end of quote --- I've asked him for the uncompressed first track to see what the correct md5 should be --- Brian Willoughby <brianw at sounds.wa.com> wrote: This could be an uploading problem. There are still too many

Thanks for the info, Dave. Speed is a very important feature, but there might be some risk choosing the FFmpeg decoder. They've had trouble with their encoder in the past, which tells me it's possible your users might one day run into a valid FLAC that the FFmpeg decoder won't handle correctly. A better suggestion might be to start with libFLAC, optimize as needed, and