2020-01-03, 00:16
Today I was investigating an issue in connection with the new boxset feature (I'll post about that seperately) and for that I had a look in the MySQL database, specifically in the "albums" table. Many albums of which I am sure I had tagged (in foobar2000) did have empty fields in the columns strMusicBrainzAlbumID and strReleaseGroupMBID. I've checked the files and sure enough they were tagged correctly.
Next, I had a look at the quirks of id3v2.4 (which is what I use) that can be toggled in foobar, like padding for faster writing or some uses of TPE2 and TXXX. After each change, I scanned one album I had selected into the library again. The MBIDs still wouldn't be picked up.
Next, I decided to use a different tagging scheme. I tagged with both id3v2.4 and APEv2. To cut a long story short, my MBIDs are ONLY scanned into Kodi when APEv2 tags are present AND in advancedsettings the instruction <prioritiseapetags>true</prioritiseapetags> is present. id3 tags seem to be ignored, at least where MBIDs are concerned.
Can anybody confirm this behaviour? It's the same in Leia and Matrix.
Next, I had a look at the quirks of id3v2.4 (which is what I use) that can be toggled in foobar, like padding for faster writing or some uses of TPE2 and TXXX. After each change, I scanned one album I had selected into the library again. The MBIDs still wouldn't be picked up.
Next, I decided to use a different tagging scheme. I tagged with both id3v2.4 and APEv2. To cut a long story short, my MBIDs are ONLY scanned into Kodi when APEv2 tags are present AND in advancedsettings the instruction <prioritiseapetags>true</prioritiseapetags> is present. id3 tags seem to be ignored, at least where MBIDs are concerned.
Can anybody confirm this behaviour? It's the same in Leia and Matrix.