Update: if I scan a different set of MP3s, which were created using LAME 3.99, they show a different invalid character at the end of the LAME version. They should just say "LAME3.99r":
I don't use the Library on my Mp3tag, and never have, and yet I still got the invalid characters on mine.
Will this still be fixed? I think it's still a bug, because it's not reasonable to expect all users who upgrade to 2.87 and use the new %_tool% field to have to toggle their library settings in order to get it to display the info correctly, right?
What I found:
Library off:
Reading the files initially: garbage characters
Moving the selection along the files list: garbage characters vanish
Library on:
Reading the files initially: garbage characters
Moving the selection along the files list: garbage characters vanish
Now the contents of the library is read, no more garbage characters.
I switched off the library.
the short picture shows the initial situation
the longer picture shows the situation after I moved the file selector a couple of files to the top.
For those files the tools column got updated and the garbage characters disappeared.
That there are garbage characters in the first place looks indeed not right.
You're all way too fast in talking to each other It's not IRC or WhatsApp here.
I can confirm the issue and it has nothing to do with the Library (but with certain memory initialization situations, which will differ from instance to instance).
I'll fix it later today and will release a new version (most likely as hotfix to v2.87 and not as beta).