You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This specific symptom is trivially solvable with a special case, but that's missing the point. This is indicative of a much broader metadata issue. We should not be a canonical source of metadata at all. MusicBrainz has solved that problem far better than we ever could. We should instead tie tracks in our library to MusicBrainz releases. That would solve the Oranges/Lemons confusion as well as hugely improve search, let people see track titles in actual Japanese if they wanted to and ease @theshillito's unending quest for royalty information.
I have no idea how to properly approach doing this. Trusting some search algorithm seems super dangerous. Gamifying metadata issue reporting, while fun, would be both difficult and likely to lead to weirdness.
Because of #99, we do already have an unreliable function for tying tracks to MusicBrainz releases. Perhaps that would be a good place to start.
https://nkd.su/artist/Oranges/ https://nkd.su/artist/Lemons/
This specific symptom is trivially solvable with a special case, but that's missing the point. This is indicative of a much broader metadata issue. We should not be a canonical source of metadata at all. MusicBrainz has solved that problem far better than we ever could. We should instead tie tracks in our library to MusicBrainz releases. That would solve the Oranges/Lemons confusion as well as hugely improve search, let people see track titles in actual Japanese if they wanted to and ease @theshillito's unending quest for royalty information.
I have no idea how to properly approach doing this. Trusting some search algorithm seems super dangerous. Gamifying metadata issue reporting, while fun, would be both difficult and likely to lead to weirdness.
Because of #99, we do already have an unreliable function for tying tracks to MusicBrainz releases. Perhaps that would be a good place to start.
Also, #78.
The text was updated successfully, but these errors were encountered: