Lidarr unable to match albums from Deemix
TheMinecraftGuyGuru opened this issue · 1 comments
Describe the bug
When downloading many certain albums I get an error from Lidarr after its been downloaded that "One or more albums expected in this release were not imported or missing" I have 14 pages of these sitting in my queue, there are others that import fine however
To Reproduce
Steps to reproduce the behavior:
try importing any of these albums:
| | Against the Current | Infinity | FLAC | | - | |
| | Afrojack | Keep It Low | FLAC | | - | |
| | Akon | Smack That | FLAC | | - | |
| | A$AP Rocky | Cocky | FLAC | | - | |
| | 5 Seconds of Summer | Want You Back | FLAC | | - | |
| | AWOLNATION | The Best | FLAC | | - | |
| | Alec Benjamin | Mind Is a Prison | FLAC | | - | |
again I have 14 pages of these, this is just an example
Expected behavior
it should import them
System info (please complete the following information):
- OS: Ubuntu Server, running Portainer for management
- Container engine 20.10.23
docker-compose.yml (please complete the following information):
version: "3"
services:
lidarr:
image: youegraillot/lidarr-on-steroids
container_name: lidarr
restart: unless-stopped
volumes:
- /dockerconfig/lidarr-steroids/config:/config
- /dockerconfig/lidarr-steroids/config_deemix:/config_deemix
- /mnt/torrents/deemix_downloads:/downloads
- /mnt/media/music:/music
networks:
- WAN
- tunnel
networks:
tunnel:
external: true
WAN:
external: true
This is not an LoS issue, but a Lidarr / user issue. Each album has different versions available. You must have them set to automatically select, or switch which album you desire, before searching.
Lidarr matches albums based on as many criteria as it can, but often tracks won't match from various services due to length or naming changes, different versions of songs, unknown releases, etc, giving Lidarr insufficient confidence to act.
You can see this happen by hovering over the indicator in your Queue window.
It's inconvenient, and everyone has to deal with it, but it is not an LoS issue. It is a core Lineage issue, related to how its Metadata source (Musicbrainz) works. Raise an issue upstream if you suspect your report can lead to resolution.