bernhard.bockelbrink
My feedback
3 results found
-
3 votes
An error occurred while saving the comment An error occurred while saving the comment bernhard.bockelbrink
commented
I doubt that you could have an automatic fallback, because I don't see how to prevent mangling a lot of band names erroneously along the way. But a manual fix would work here, and maybe even a selection of replacements using regex might make sense, because that would also have
to apply to "The Fall", and "A Flock of Seagulls", and "Die erste weibliche Fleischergesellin nach 1945".To keep the number of manual fixes manageable, you'd have apply every manual fix to all instances of an artist's name in the collection automatically.
-
2 votesbernhard.bockelbrink
supported this idea
·
-
1 votebernhard.bockelbrink
shared this idea
·
In your first comment in 2014 you pointed out that MusicBrainz does not have a Sort Name every artist. As you can clearly see from the following search, this is still a significant problem:
https://musicbrainz.org/search?limit=25&method=direct&page=2&query=Die&type=artist
There is a now a Sort Name for each artist, but for a significant number of artists in this test search the value is just plain wrong, it's simply the artist name. So automatically setting ARTISTSORT from MusicBrainz would lead to a lot of duplication (all the artists where Sort Name is actually the same as artist name), and erroneous data in the cases where Sort Name would actually be different.
If Bliss were to check with MusicBrainz and point out any differences between Sort Name and ARTISTSORT in the local file, nothing is gained, because those differences might be exactly because the data on MusicBrainz is wrong. You'd have to fix it in MusicBrains first.
Since there's no way to fix this automatically, I suggest autopopulation of ARTISTSORT/ALBUMARTISTSORT from Musicbrains if and only if Sort Name is different from artist name, and keeping it empty otherwise, so that we don't end up with erroneous data. Correctness trumps consistency, doesn't it?
For that to be of use Bliss might introduce a computed tag "RELEASE ARTIST" which evaluates tags in the following order and takes the first one that is not empty
* ALBUMARTISTSORT
* ALBUMARTIST
* ARTIST SORT
* ARTIST