Renaming with Pseudo_Releases #619

New issue

Open

opened 2026-02-20 12:04:37 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 12:04:37 -05:00

Owner

Originally created by @Joleun on GitHub (Sep 22, 2019).

Is your feature request related to a problem? Please describe.
I'm unclear exactly as to what should be expected so some of this may be unintended rather than a feature request.

Addig a pseudo-release provides the tracklisting of that pseudo-release in Lidarr, while the title displayed remains that of the release group.

Renaming the files follows the same pattern: the tracks are renamed according to the pseudo-release, and the folder is renamed to that of the release group on Musicbrainz.

https://musicbrainz.org/release/00a6440d-fb57-4bbb-ab28-037d0584393b as an example gives the renaming result shown below:

It's not very consistent/useful as I'm wanting the translations provided by the pseudo-release.

As a side issue, it would be great if the release title displayed in Lidarr would change to that of the pseudo-release when that is the monitored release. The same applies to the artist, because that becomes very confusing when you have multiple such artists and can't easily identify which is is which.

Describe the solution you'd like

For the first point, the renaming to utilize the release title from the pseudo-release rather than the release group.

With the side issue, isn't it possible to change the release titles displayed/artist if a pseudo only profile is assigned to the artist?

Describe alternatives you've considered
There aren't any alternatives that I can see. At the artist level folder, I can create a folder named as I want, and edit the entry in Lidarr, but at album level, I don't believe that's possible without the files no longer showing in Lidarr.

The secondary issue also doesn't have an alternative. It's just confusing having all Japanese artists displayed last in Lidarr, and not knowing which is which other than bty random selection.

AB#311

Originally created by @Joleun on GitHub (Sep 22, 2019). **Is your feature request related to a problem? Please describe.** I'm unclear exactly as to what should be expected so some of this may be unintended rather than a feature request. Addig a pseudo-release provides the tracklisting of that pseudo-release in Lidarr, while the title displayed remains that of the release group. Renaming the files follows the same pattern: the tracks are renamed according to the pseudo-release, and the folder is renamed to that of the release group on Musicbrainz. https://musicbrainz.org/release/00a6440d-fb57-4bbb-ab28-037d0584393b as an example gives the renaming result shown below: ![2019-09-22 (11)](https://user-images.githubusercontent.com/44970798/65389552-6e0cd380-dd4f-11e9-8302-a1b6758f3a89.png) It's not very consistent/useful as I'm wanting the translations provided by the pseudo-release. As a side issue, it would be great if the release title displayed in Lidarr would change to that of the pseudo-release when that is the monitored release. The same applies to the artist, because that becomes very confusing when you have multiple such artists and can't easily identify which is is which. **Describe the solution you'd like** For the first point, the renaming to utilize the release title from the pseudo-release rather than the release group. With the side issue, isn't it possible to change the release titles displayed/artist if a pseudo only profile is assigned to the artist? **Describe alternatives you've considered** There aren't any alternatives that I can see. At the artist level folder, I can create a folder named as I want, and edit the entry in Lidarr, but at album level, I don't believe that's possible without the files no longer showing in Lidarr. The secondary issue also doesn't have an alternative. It's just confusing having all Japanese artists displayed last in Lidarr, and not knowing which is which other than bty random selection. [AB#311](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/311)

deekerman added the

Status: Info Needed

Type: Feature Request

labels

2026-02-20 12:04:37 -05:00

deekerman commented

2026-02-20 12:04:38 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jul 13, 2022):

Still an issue in v1?

@bakerboy448 commented on GitHub (Jul 13, 2022): Still an issue in v1?

deekerman commented

2026-02-20 12:04:38 -05:00

Author

Owner

@jaen commented on GitHub (Feb 17, 2024):

@bakerboy448 still an issue for me using 2.1.4.3941-ls131 FWIW

I wanted to try and clean up my tags and as an example I have picked the pseudo-release with English names for Macross Frontier OST (https://musicbrainz.org/release/c2e4099e-9828-4612-9bab-b2d5d2560dc3) and the rename didn't take this into account:

It also still doesn't work for metadata, as seen in the related ticket https://github.com/lidarr/Lidarr/issues/989.

@jaen commented on GitHub (Feb 17, 2024): @bakerboy448 still an issue for me using `2.1.4.3941-ls131` FWIW I wanted to try and clean up my tags and as an example I have picked the pseudo-release with English names for Macross Frontier OST (https://musicbrainz.org/release/c2e4099e-9828-4612-9bab-b2d5d2560dc3) and the rename didn't take this into account: ![image](https://github.com/Lidarr/Lidarr/assets/227236/f7e6fe7f-77af-4376-9b09-43b17362ee32) It also still doesn't work for metadata, as seen in the related ticket https://github.com/lidarr/Lidarr/issues/989.