Lidarr not using Artists as Credited in release for searches yielding no results #2633

Open
opened 2026-02-20 02:10:34 -05:00 by deekerman · 0 comments
Owner

Originally created by @ItsME6969 on GitHub (Jan 17, 2023).

Is there an existing issue for this?

  • I have searched the existing open and closed issues

Current Behavior

A significant number of artists change names in the middle of their careers especially in the Hip-Hop genre. So I was searching a release that I know exists both on usenet and trackers and lidarr wasn't yielding any results. So I look at the logs and see that lidarr is searching using the New Name instead of the original one credited on the cover of the release.

Expected Behavior

Use the Original Stage Name for the search which should be available from the MusicBrainz API.

Steps To Reproduce

Find an Artist who's changed names
https://www.google.com/search?q=artists+who+changed+their+names+mid+career

All their old releases can't be found because lidarr is searching using new names

Environment

- OS: Linux
- Lidarr: 1.1.2.2892
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: Chrome
- Database: Sqlite 3.40.1

What branch are you running?

Nightly

Trace Logs?

2023-01-17 13:47:35.1|Info|ReleaseSearchService|Searching indexers for [NEWNAME - ALBUMNAME (2003)]. 7 active indexers
2023-01-17 13:47:35.1|Debug|Torznab|Downloading Feed http://my.ip.add.ress:port/api/v2.0/indexers/indexer/results/torznab/api?t=search&cat=3000&extended=1&apikey=(removed)&offset=0&limit=100&q=NEW%20NAME%20ALBUM%20NAME
2023-01-17 13:47:35.1|Trace|HttpClient|Req: [GET] http://my.ip.add.ress:port/api/v2.0/indexers/indexer/results/torznab/api?t=search&cat=3000&extended=1&apikey=(removed)&offset=0&limit=100&q=NEW%20NAME%20ALBUM%20NAME

AB#4754

Originally created by @ItsME6969 on GitHub (Jan 17, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior A significant number of artists change names in the middle of their careers especially in the Hip-Hop genre. So I was searching a release that I know exists both on usenet and trackers and lidarr wasn't yielding any results. So I look at the logs and see that lidarr is searching using the `New Name` instead of the original one `credited` on the cover of the release. ### Expected Behavior Use the Original Stage Name for the search which should be available from the MusicBrainz API. ### Steps To Reproduce Find an Artist who's changed names https://www.google.com/search?q=artists+who+changed+their+names+mid+career All their old releases can't be found because lidarr is searching using new names ### Environment ```markdown - OS: Linux - Lidarr: 1.1.2.2892 - Docker Install: Yes - Using Reverse Proxy: No - Browser: Chrome - Database: Sqlite 3.40.1 ``` ### What branch are you running? Nightly ### Trace Logs? 2023-01-17 13:47:35.1|Info|ReleaseSearchService|Searching indexers for [`NEWNAME` - ALBUMNAME (2003)]. 7 active indexers 2023-01-17 13:47:35.1|Debug|Torznab|Downloading Feed http://my.ip.add.ress:port/api/v2.0/indexers/indexer/results/torznab/api?t=search&cat=3000&extended=1&apikey=(removed)&offset=0&limit=100&q=NEW%20NAME%20ALBUM%20NAME 2023-01-17 13:47:35.1|Trace|HttpClient|Req: [GET] http://my.ip.add.ress:port/api/v2.0/indexers/indexer/results/torznab/api?t=search&cat=3000&extended=1&apikey=(removed)&offset=0&limit=100&q=NEW%20NAME%20ALBUM%20NAME [AB#4754](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/4754)
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#2633
No description provided.