Add support for musicbrainz short name #1599

Open
opened 2026-02-20 01:16:50 -05:00 by deekerman · 4 comments
Owner

Originally created by @6cUbi57z on GitHub (Apr 14, 2021).

Is your feature request related to a problem? Please describe.

I have quite a few soundtracks from Anime and other Japanese artists. When Lidarr imports these, it uses the main name from Musicbrainz which is usually using Kanji characters. This makes it difficult to search or even know who the artist is.

Describe the solution you'd like

There is usually a romanised name in the short name field which would be much easier to search. Obviously there would need to be an option for this so that it can be selected only for specific artists or maybe profiles?

I realise this only addresses the issue for artists, however, this seems to be solved for albums and tracks via bootleg and pseudo-releases.

Describe alternatives you've considered

Learning kanji (may take a while)

Additional context

Example artists:

AB#148

Originally created by @6cUbi57z on GitHub (Apr 14, 2021). **Is your feature request related to a problem? Please describe.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> I have quite a few soundtracks from Anime and other Japanese artists. When Lidarr imports these, it uses the main name from Musicbrainz which is usually using Kanji characters. This makes it difficult to search or even know who the artist is. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> There is usually a romanised name in the short name field which would be much easier to search. Obviously there would need to be an option for this so that it can be selected only for specific artists or maybe profiles? I realise this only addresses the issue for artists, however, this seems to be solved for albums and tracks via bootleg and pseudo-releases. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> Learning kanji (may take a while) **Additional context** <!-- Add any other context or screenshots about the feature request here. --> Example artists: - https://musicbrainz.org/artist/9ac83e0c-6a90-41cf-b06f-527ed0a79ffe - https://musicbrainz.org/artist/c7b20a7d-bf0e-45f8-9ea4-6ddcae9c49dd [AB#148](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/148)
Author
Owner

@6cUbi57z commented on GitHub (May 6, 2021):

Actually I've just noticed Musicbrainz has an alias section on artists and release groups which can set names by locale. It may be better to have this as part of the edit dialog for each artist and release so that the user can select the best name to use for their use case and select a default based on locale (if available).

Aliases example: https://musicbrainz.org/artist/1b4414e5-b699-4c77-82b5-4669c9e69a59/aliases

@6cUbi57z commented on GitHub (May 6, 2021): Actually I've just noticed Musicbrainz has an alias section on artists and release groups which can set names by locale. It may be better to have this as part of the edit dialog for each artist and release so that the user can select the best name to use for their use case and select a default based on locale (if available). Aliases example: https://musicbrainz.org/artist/1b4414e5-b699-4c77-82b5-4669c9e69a59/aliases
Author
Owner

@dbvcode commented on GitHub (Jun 8, 2021):

I have the same issue with Japanese artists.
And using the locale seems like a good idea, however,

the real issue is searching for it, as some results include the Japanese name, other the English version of it.
So the problem besides the cosmetic appearance of the dashboard is actually the problem of not finding the actual results!

@dbvcode commented on GitHub (Jun 8, 2021): I have the same issue with Japanese artists. And using the locale seems like a good idea, however, the real issue is searching for it, as some results include the Japanese name, other the English version of it. So the problem besides the cosmetic appearance of the dashboard is actually the problem of not finding the actual results!
Author
Owner

@6cUbi57z commented on GitHub (Nov 3, 2021):

I had a bit of a look at this see if it is something I would be able to help out with. Unfortunately it looks like the information isn't provided by the Lidarr metadata API so I believe that would need updating first which is well beyond my abilities. Then it would need some thought into how this is implemented into Lidarr.

I've also realised this presents an additional problem as some stereo systems can't display the characters and will display boxes instead.

@6cUbi57z commented on GitHub (Nov 3, 2021): I had a bit of a look at this see if it is something I would be able to help out with. Unfortunately it looks like the information isn't provided by the Lidarr metadata API so I believe that would need updating first which is well beyond my abilities. Then it would need some thought into how this is implemented into Lidarr. I've also realised this presents an additional problem as some stereo systems can't display the characters and will display boxes instead.
Author
Owner

@6cUbi57z commented on GitHub (Jan 2, 2022):

I've now seen this is a duplicate of #682

@6cUbi57z commented on GitHub (Jan 2, 2022): I've now seen this is a duplicate of #682
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Lidarr#1599
No description provided.