Source of Corruption Options

[windmiller]

Ive been using Second Copy to backup my Flac, Ogg, MP3 collection for the last year. I ran flactester on the backed up files this morning and about half of my music collection is coming back as corrupt. The thought of losing this music is nauseating and I am trying to find out if its possible to pinpoint what caused the corruption or what kind of corruption it is?

The error I get in Flactester is .FLAC__FILE_DECODER_ALREADY_INITIALIZED.
I did some searching on this error but didnt come up with much. I did find this..

FLAC__file_decoder_init() was called when the decoder was already initialized, usually because FLAC__file_decoder_finish() was not called.

This post has been edited by windmiller: Aug 4 2006, 17:14

[bryant]

Josh will be able to answer more definitively, but that sounds more like a bug in flactester than corrupt files (based on the error message, anyway.)

I would copy one of the supposedly corrupt files to your C: drive and test it with the command-line FLAC decoder to see if it's really corrupt.

[windmiller]

I wondered the same thing based on the error, I have had corrupt FLAC files before but never with this error.

Would opening the file in the Flac frontend accomplish the same thing as using the command line?

This post has been edited by windmiller: Aug 4 2006, 19:50

[Cosmo]

Would opening the file in the Flac frontend accomplish the same thing as using the command line?

Yes. The frontend just creates and runs a batch file. You can open go.bat (in the frontend install folder) to see exactly what commands it ran.

[windmiller]

I opened a few suspect files in the Flac Frontend and am showing FLAC_FILE_DECODER_ERROR_OPENING_FILE. Here is the weird part, the files that are corrupt have uppercase filenames and also include Umlauts (Ё) above the O and the U while the files that are not corrupt are using normal case, first letter upper and the rest lower.
Just to clarify this isnt a bunch of junk files downloaded off of P2P or something.

After getting home and having a bit of time to look at this, I retagged the "corrupt" files and rescanned them them using flactester and the Flac Frontend and neither utilites return errors on the first two albums I have retagged.
I thought I had been very careful to set both MP3Tag and Tag&Rename to make sure not to write ID3V1 or ID3V2 tags to the Flac/Ogg tag and so far they dont seem to be. Starting to retag all "corrupt" files...have I just lost it completely.

This post has been edited by windmiller: Aug 5 2006, 00:34

[windmiller]

I think this issue may have been caused in part by being remoted in and then RDP in to my server. Not sure why but for anyone using Flactester.exe check it with the Flac Frontend before having a heart attack