I just wrote many thousand sof audio files using the technique described here:
The idea was simply disable unicode, then press CTRL+A then CTRL+S and all tags are rewritten without unicode.
Because I'm working with a whole library of music as a security I exported all tags before hand, including the %_md5audio% calculation, and again afterwards.
The idea being that the audio data should be unaffected and hence the %_md5audio% unchanged. Alas for a good many files the %_md5audio% value did change!
There are more songs affected than I can easily compare by listeningv, but a spot check reveals no audible change to the file.
Why is it that writing tags affects the MD5 hash of the audio part. I am forced to suspect that either:
- MP3 tag is altering the audio unintentionally!
- MP3 tag is calculating the MD5 hash on the audio part incorrectly.
Logic would suggest that if only the tags are altered and not the audio part, that the MD5 hash of the audio should be unchanged and this is the main aim of looking at that hash!
Is there a bug here? Or is it an interpretation problem?