Quote:
Originally Posted by spidergawd
What happens if you use flac's "test" function?
flac -t *.flac
If the checksums in the header don't match the checksums of the audio data, it will fail the test. If it passes, then that would sound like something messing with TLH, especially if
metaflac --show-md5sum *.flac
produces the same values as in the ffp file.
I don't use Windows or TLH, I use Slackware Linux and have had to edit and re-write my ffp-checking shell script every time I come across an ffp file with weird text formatting or other simple things that can screw it up, but that doesn't sound like your situation since TLH wouldn't use formatting that TLH can't understand. IMO if your files pass flac's test and also pass the md5 check, I'd consider the files good and chalk this up to a fluke or bug.
Good luck
|
I used the "test" function in FLAC frontend, and in every case (all files in all four shows from the same uploader) I got:
"ERROR: MD5 signature mismatch"
The weird thing is that TLH will generate a new ffp that is identical to the one contained in the fileset.
No members have liked this post.