Folk vs (80)Folk

[adrian]

(19-06-2014 05:23)simoncn Wrote:  

(18-06-2014 21:56)adrian Wrote:  I am completely confused about what is going on. The problem is mp3 files. They appear to have ID3v2.4 tags. I'm working under Linux and tried id3, id3v2, and id3tool and none of them find the tag. The eyeD3 program and easy tag (like puddletag) show the tags but don't give any indication that there is a numerical id, nor do they give any indication that the "(80)Folk" files are any different from the "Folk" files. The only way I have found to tell the files apart is to use MinimServer.

For ID3v2.4, the (80) genre notation is no longer valid. It seems that the tagging program that wrote the ID3v2.4 tags isn't aware of this difference between ID3v2.3 and ID3v2.4. Here is the relevant extract from the ID3v2.4 spec:

TCON
The 'Content type', which ID3v1 was stored as a one byte numeric value only, is now a string. You may use one or several of the ID3v1 types as numerical strings, or, since the category list would be impossible to maintain with accurate and up to date categories, define your own. Example: "21" $00 "Eurodisco" $00

I examined my files with "od" to figure out what is going on. They have ID3v2.4 headers. The file with the problematic tag is using encoding 01 for the tag, UTF-16 with BOM. The file with the good tag is using encoding 03, UTF-8. The bad tag is literally the text string "(80)Folk". If I use easytag instead of puddletag it corrects this to "(80)", still a text string, even when I enter "Folk" as the genre text string to set the tag. Easytag also recodes to UTF-8, but that doesn't seem to help anything.

In any case, it's clearly a tagging software issue, so I've posted on the puddletag forum about it.