..I found a small bug with the umlauts....

You're running v3.00 alpha, right?

This is UTF-8 that's being displayed as iso8859-1.

When migrating to v3, your player database is being converted
from iso8859-1 to UTF-8. That alone could cause touble for
third party apps.

But things can even get more confusing. I don't think
the tag files that are used to reconstruct the player database
are converted themselves, leaving them iso8859-1 encoded.
But newly uploaded tag files may be UTF-8 encoded, so I'm
not sure how emplode and jemplode cope with this.

Pim