08-24-2024, 04:07 PM
@Bjørn Roar
I don't know the Tag&Rename program so I looked it up. Appears to be available for MS-Windows only
My recurrent complaint about many GUI-based tagging programs is that they obscure what is actually present in a file. This includes popular programs, such as Mp3tag, which can actually handle many metadata representations yet require users to click through menu trees to find the details. (Every time a user presents to us a FLAC file with an ID3 tag stuck on it, I know it's likely to have been tagged using Mp3tag with its default settings.)
I checked on my Linux box this morning: the Linux-only Kid3 tag editor does a decent job revealing the presence of multiple tags---ID3v1.0, ID3v2.x, RIFF INFO chunk, etc. The Kid3 effort provides both a GUI-based editor and a CLI-based editor. Here's a screen shot from the GUi for one of your "bad" files
I'm sure there are other appropriate tools, and I can imagine scripting bulk deletions of specific RIFF chunks, but I'm too far removed from MS-Windows these days to know what to suggest.
Regards,
Kent
I don't know the Tag&Rename program so I looked it up. Appears to be available for MS-Windows only
My recurrent complaint about many GUI-based tagging programs is that they obscure what is actually present in a file. This includes popular programs, such as Mp3tag, which can actually handle many metadata representations yet require users to click through menu trees to find the details. (Every time a user presents to us a FLAC file with an ID3 tag stuck on it, I know it's likely to have been tagged using Mp3tag with its default settings.)
I checked on my Linux box this morning: the Linux-only Kid3 tag editor does a decent job revealing the presence of multiple tags---ID3v1.0, ID3v2.x, RIFF INFO chunk, etc. The Kid3 effort provides both a GUI-based editor and a CLI-based editor. Here's a screen shot from the GUi for one of your "bad" files
I'm sure there are other appropriate tools, and I can imagine scripting bulk deletions of specific RIFF chunks, but I'm too far removed from MS-Windows these days to know what to suggest.
Regards,
Kent
