I used GRIP to convert my music CDs to FLAC, Now I have numerous errors Options

[NavyJay]

I used GRIP in Linux to convert my music CDs to FLAC. I didn't realize it at the time, but I have numerous CRC mismatches in the encoded files where physical scratches were located. Normally, I don't ever notice these errors during playback in Amarok or on my Squeezebox.

Since I recently bought an iPod, I had to convert all my FLAC files to MP3 using flac and lame on the command line. These mp3 files contain silent breaks anywhere there were CRC mismatches in the flac file. The same effect occurs when I use winamp to convert FLAC to mp3 in Windows. I know it's theoretically possible to interpolate through the errors, because we are oversampling with the FLAC format (~900 kbps vs. 320 kbps). But, how can I decode through errors while interpolating to get rid of silent breaks in my music??? This must be how Amarok and Slimserver deal with errors, so why is it not an option in the flac binaries?

-J

[NavyJay]

If you're looking for a flame war, look elsewhere. I'm not interested.

I'm getting this "nonsense" from years of experience as a signal processing engineer. I'm sure in other areas these terms have parallel meanings. But here, in the signals sense I'm using them correctly. Why do you think mp3s are lossy? Because it resamples (and compresses) using either constant or variable bit rates that are DECIMATED and filtered versions of the original.

I'd still appreciate some suggestions for existing software that will avoid inserting zero padded samples in places having CRC mismatches.

Thanks,

J

[greynol]

I'd still appreciate some suggestions for existing software that will avoid inserting zero padded samples in places having CRC mismatches.

Application of interpolation is not very interesting when the typical amount of data lost due to a single instance of corruption in a flac file is about a tenth of a second.

This post has been edited by greynol: Nov 10 2007, 06:14