New Mp3Tag 3.30 includes MB schema change

1

[2025-05-20] FIX: MusicBrainz schema change resulted in track numbers not being imported correctly.

https://www.mp3tag.de/en/changelog.html

3 Likes
2

I saw this. It’s a really odd bug. I wonder how reading the data was implemented that the recent changes (which only was about adding fields unrelated to track numbers) could trigger such wrong track number reading.

3 Likes
3
  • There are more things in heaven and earth, Horatio,
    Than are dreamt of in your philosophy.
    • Hamlet
4

The last time I had dealt with Mp3Tag tagging sources, the code for the MB source was using the XML API and regular expressions for parsing… So I’m not really surprised :face_with_peeking_eye:

I had even written an almost complete Mp3Tag source for the JSON API in 2019, but then I discovered Picard instead, registered an MB account and the rest is history :smiley:

8 Likes