What kind of error checking is done with this program? Does it just decode the audio file quickly and detect breaks in the stream? perhaps someone can explain. Also how does checking a flac fingerprint differ from the error checking used by this program? Thanks
should i use the "rebuild stream" functionality in foobar? (does it reencode the file and thus have generationloss?)
I've been reinstalling my PC, hence the late reply.Quote from: SigHunter on 30 December, 2012, 06:34:45 AMshould i use the "rebuild stream" functionality in foobar? (does it reencode the file and thus have generationloss?)That's the only question I can answer, and it does not re-encode the audio, only rearranges the valid frames. It might discard anything unrecognised as valid MPEG audio or unknown tags, so if you're reliant on something non-standard embedded in a .mp3 file or even hoping to recover a bad frame somehow, make a backup of the file first.As to having thousands of sync errors, unless you're getting MP3 files from dubious sources I'd be suprised if it wasn't a change to some tagging standard or lame header (silent MP3-compliant frame) that occurred since 2007 that's being misinterpreted by old software that I've never used myself.I'd have expected foobar2000's console will probably report any genuine problems in any format for which it has a decoder, and I presume the file integrity component would do a test decode of every file (otherwise use the Decode Speed Test component and view the console). The console should report any errors worth knowing about, and despite the disclaimer for the File Integrity component, it says it decodes, so I'd have thought this would cause the same information to be logged in the console.