Having 2 (or more) version of the same album release. #482

Owner

Originally created by @iAmRenzo on GitHub (Apr 7, 2019).

I have the same (international) versions of an album. But I can't manage to keep them both in Lidarr. Is this something for a future version?

AB#336

Originally created by @iAmRenzo on GitHub (Apr 7, 2019). I have the same (international) versions of an album. But I can't manage to keep them both in Lidarr. Is this something for a future version? [AB#336](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/336)

deekerman added the

Type: Enhancement

Priority: Low

Status: Accepted

labels

deekerman commented

Author

Owner

@texke commented on GitHub (Apr 7, 2019):

+1 for this feature :-)

@texke commented on GitHub (Apr 7, 2019): +1 for this feature :-)

deekerman commented

Author

Owner

@Qstick commented on GitHub (Apr 10, 2019):

Yea it’s planned

@Qstick commented on GitHub (Apr 10, 2019): Yea it’s planned

deekerman commented

Author

Owner

@Popupkiller commented on GitHub (Nov 15, 2019):

Any progress on this? I have 2 versions of an Arctic Monkeys album. International and Japanese release.

@Popupkiller commented on GitHub (Nov 15, 2019): Any progress on this? I have 2 versions of an Arctic Monkeys album. International and Japanese release.

deekerman commented

Author

Owner

@paclv commented on GitHub (Mar 15, 2021):

Any word on this??? I have multiple Albums that have multiple versions!

Thanks

@paclv commented on GitHub (Mar 15, 2021): Any word on this??? I have multiple Albums that have multiple versions! Thanks

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Mar 15, 2021):

when there is an update to share an update will be shared or a pull request or commit referencing this issue.

The spiel:
The main development team is split across 3 apps: Radarr, Readarr, and Lidarr.
There are only 2 or 3 active developers who work on this, and of those 2 or 3 exactly zero work on this fulltime and have other life commitments.

@bakerboy448 commented on GitHub (Mar 15, 2021): when there is an update to share an update will be shared or a pull request or commit referencing this issue. The spiel: The main development team is split across 3 apps: Radarr, Readarr, and Lidarr. There are only 2 or 3 active developers who work on this, and of those 2 or 3 exactly zero work on this fulltime and have other life commitments.

deekerman commented

Author

Owner

@sdnew123 commented on GitHub (Apr 5, 2022):

I understand that it's considered a low priority, but I would also like to throw my hat in the ring requesting a feature allowing multiple versions of the same album be able to be listed individually in Lidarr.
Being a network engineer, I understand that there are so many hours in the day and only so many people available to work on features and I appreciate the fine work the team has done on Lidarr.
I'm not trying to add any sense of urgency and I thank you for your attention.

@sdnew123 commented on GitHub (Apr 5, 2022): I understand that it's considered a low priority, but I would also like to throw my hat in the ring requesting a feature allowing multiple versions of the same album be able to be listed individually in Lidarr. Being a network engineer, I understand that there are so many hours in the day and only so many people available to work on features and I appreciate the fine work the team has done on Lidarr. I'm not trying to add any sense of urgency and I thank you for your attention.

deekerman commented

Author

Owner

@nobodyspecial commented on GitHub (Jul 16, 2022):

I'd like to request this as well. I didn't think it would be an issue but I keep running into it more and more.

@nobodyspecial commented on GitHub (Jul 16, 2022): I'd like to request this as well. I didn't think it would be an issue but I keep running into it more and more.

deekerman commented

Author

Owner

@iAmRenzo commented on GitHub (Dec 21, 2022):

I am picking up on Lidarr again and saw my own post from 3 years ago... still nothing on this?

@iAmRenzo commented on GitHub (Dec 21, 2022): I am picking up on Lidarr again and saw my own post from 3 years ago... still nothing on this?

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (Jan 9, 2023):

It requires effectively an entire rewrite of the app.
It will not be anytime soon

@bakerboy448 commented on GitHub (Jan 9, 2023): It requires effectively an entire rewrite of the app. It will not be anytime soon

deekerman commented

2026-02-20 01:03:57 -05:00

Author

Owner

@SuperBenji99 commented on GitHub (Jan 26, 2023):

I signed in just to chime in that I'd also love for this to be fixed. I have several albums with multiple versions and would love a clean way for Lidarr to handle them.

@SuperBenji99 commented on GitHub (Jan 26, 2023): I signed in just to chime in that I'd also love for this to be fixed. I have several albums with multiple versions and would love a clean way for Lidarr to handle them.

deekerman commented

Author

Owner

@romanr commented on GitHub (Mar 12, 2023):

Will it work if there was reward/bounty system, users pledge money and it gets developed sooner?

@romanr commented on GitHub (Mar 12, 2023): Will it work if there was reward/bounty system, users pledge money and it gets developed sooner?

deekerman commented

Author

Owner

@Krojack commented on GitHub (May 1, 2023):

Oof... 4 years ago said it was planned. I would assume it won't be added at this point, and yes I understand this is a project done by people on their own time. My point is, if it's still planned then make a post stating this and if some work has been done. Doesn't matter if it's still very early or near complete. Just don't say it's planned and go dark for 4 years. I would rather an update saying it's no longer planned than leaving us hanging.

I've ran into this several times over the past few days now and this is the only way I can prevent Lidarr from overwriting albums.

Have 2 directories

music/_sorted
music/_other

The _sorted folder is added as a Root Folder to Lidarr while _other isn't. I put what I consider the primary album into _sorted so Lidarr can manage it. Other albums that fall within the same release group have to go into _other where Lidarr can't touch them. It's a dirty way but it works. I add both _sorted and _other to my Plex music library.

So I need to manually manage the _other folder like the old days.

All of the following have an Instrumental version as well. Lidarr gets them confused.

Coldplay - A Rush of Blood to the Head (example)
Coldplay - Everyday Life
Coldplay - Ghost Stories
Coldplay - Mylo Xyloto
Coldplay - Parachutes
Coldplay - Viva La Vida
Coldplay - X&Y

Also this one today:

Black Eyed Peas - The Time (Dirty Bit) (link) I have the digital media 1 track version and the 5 track version. All the songs are different.

This one might be possible to break it off into it's own release-group in Musicbrainz but that seems like a mess for many others like the Coldplay versions. I'm pretty sure people would vote against those changes for Coldplay anyways.

@Krojack commented on GitHub (May 1, 2023): Oof... 4 years ago said it was planned. I would assume it won't be added at this point, and yes I understand this is a project done by people on their own time. My point is, if it's still planned then make a post stating this and if some work has been done. Doesn't matter if it's still very early or near complete. Just don't say it's planned and go dark for 4 years. I would rather an update saying it's no longer planned than leaving us hanging. I've ran into this several times over the past few days now and this is the only way I can prevent Lidarr from overwriting albums. Have 2 directories - music/_sorted - music/_other The `_sorted` folder is added as a Root Folder to Lidarr while `_other` isn't. I put what I consider the primary album into `_sorted` so Lidarr can manage it. Other albums that fall within the same release group have to go into `_other` where Lidarr can't touch them. It's a dirty way but it works. I add both `_sorted` and `_other` to my Plex music library. So I need to manually manage the `_other` folder like the old days. All of the following have an Instrumental version as well. Lidarr gets them confused. - Coldplay - A Rush of Blood to the Head ([example](https://musicbrainz.org/release-group/120c786d-a3b2-3c19-b4ff-2b7b3b4435bf)) - Coldplay - Everyday Life - Coldplay - Ghost Stories - Coldplay - Mylo Xyloto - Coldplay - Parachutes - Coldplay - Viva La Vida - Coldplay - X&Y Also this one today: - Black Eyed Peas - The Time (Dirty Bit) ([link](https://musicbrainz.org/release-group/ec019fb4-3025-4dba-8096-2828cb4b6ece)) I have the digital media 1 track version and the 5 track version. All the songs are different. This one might be possible to break it off into it's own release-group in Musicbrainz but that seems like a mess for many others like the Coldplay versions. I'm pretty sure people would vote against those changes for Coldplay anyways.

deekerman commented

Author

Owner

@bakerboy448 commented on GitHub (May 1, 2023):

when there is an update to share one will be shared.....this requires effectively an entire rewrite of the app.
You have 2-3 people working on Radarr, Prowlarr, Readarr, Lidarr, Whisparr, associated metadata backends, associated update servers, and contributing upstream to Sonarr in their rather limited free time.

if it's still planned then make a post stating this

No post is required. If this was not planned it would be closed.

Multiple comments have been provided over the last several years.
https://github.com/Lidarr/Lidarr/issues/729#issuecomment-1375797211 .... as recently as Jan/2023
https://github.com/Lidarr/Lidarr/issues/729#issuecomment-799833848
https://github.com/Lidarr/Lidarr/issues/729#issuecomment-481901541

and if some work has been done. Doesn't matter if it's still very early or near complete.

Some work in Radarr for v5 has started.

Just don't say it's planned and go dark for 4 years.

the update is there is no update.... it is still planned
This is also plainly untrue.

I would rather an update saying it's no longer planned than leaving us hanging.

The issue is not closed....thus not not planned.
Multiple comments have been provided over the last several years.
https://github.com/Lidarr/Lidarr/issues/729#issuecomment-1375797211 .... as recently as Jan/2023
https://github.com/Lidarr/Lidarr/issues/729#issuecomment-799833848
https://github.com/Lidarr/Lidarr/issues/729#issuecomment-481901541

Users asking for monthly updates on a request that is extremely complicated and requires nearly a ground-up rewrite absolutely does not make the issue be worked on any faster.....if anything it's the opposite and further down the pile.

Continual status update requests or similar noise will likely result in this issue being locked like the equivalent Radarr issue.

@bakerboy448 commented on GitHub (May 1, 2023): when there is an update to share one will be shared.....this requires effectively an entire rewrite of the app. You have 2-3 people working on Radarr, Prowlarr, Readarr, Lidarr, Whisparr, associated metadata backends, associated update servers, and contributing upstream to Sonarr in their rather limited free time. > if it's still planned then make a post stating this No post is required. If this was not planned it would be closed. Multiple comments have been provided over the last several years. https://github.com/Lidarr/Lidarr/issues/729#issuecomment-1375797211 .... as recently as Jan/2023 https://github.com/Lidarr/Lidarr/issues/729#issuecomment-799833848 https://github.com/Lidarr/Lidarr/issues/729#issuecomment-481901541 > and if some work has been done. Doesn't matter if it's still very early or near complete. Some work in Radarr for v5 has started. > Just don't say it's planned and **go dark for 4 years.** the update is there is no update.... it is still planned This is also plainly untrue. Multiple comments have been provided over the last several years. https://github.com/Lidarr/Lidarr/issues/729#issuecomment-1375797211 .... as recently as Jan/2023 https://github.com/Lidarr/Lidarr/issues/729#issuecomment-799833848 https://github.com/Lidarr/Lidarr/issues/729#issuecomment-481901541 > I would rather an update saying it's no longer planned than leaving us hanging. The issue is not closed....thus not not planned. Multiple comments have been provided over the last several years. https://github.com/Lidarr/Lidarr/issues/729#issuecomment-1375797211 .... as recently as Jan/2023 https://github.com/Lidarr/Lidarr/issues/729#issuecomment-799833848 https://github.com/Lidarr/Lidarr/issues/729#issuecomment-481901541 Users asking for monthly updates on a request that is extremely complicated and requires nearly a ground-up rewrite absolutely does not make the issue be worked on any faster.....if anything it's the opposite and further down the pile. **Continual status update requests or similar noise will likely result in this issue being locked like the equivalent Radarr issue.**

deekerman commented

Author

Owner

@ryanherd commented on GitHub (Oct 20, 2024):

Following - organising my digital files and running into cases where I have UK version vs Int, or some cases where a Bonus Disc vs UK are very different but meta thinks they're the same and making me choose just one to import.

@ryanherd commented on GitHub (Oct 20, 2024): Following - organising my digital files and running into cases where I have UK version vs Int, or some cases where a Bonus Disc vs UK are very different but meta thinks they're the same and making me choose just one to import.

deekerman commented