Comment 5 for bug 5465

Suddenly I had the time to take a look into the offending MP3 file with the hex editor. Apparently when the ID3v2 tag is written, it does not touch the ID3 tag (this may be by design). So, Nautilus and RhythmBox are both reading the persistent ID3 information though the ID3v2 information has been updated.

Suggestion: For files that persist old ID3 information, use a generic ID3 tag editor to update the tag information with the updated ID3v2 information manually.

For the developers, any new technology should be backwards compatible for at least a few steps. When software utilizes an ID3v2 technology, it should persist this information in a reasonable way to the outdated (but sometimes used) ID3 technology.

Hopefully, this will be addressed, but admittedly it is a minor headache.