-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
beets fails to detect compilations when importing metadata from Deezer #4057
Comments
Here is the deezer api response if someone is going to look into this in detail: http://api.deezer.com/album/43959881. A first step would probably to research how deezers |
Right, so this is a Deezer related bug. I'll change the issue name |
Yes, but I don't know whether it's simply beets not interpreting the deezer data very well, or whether the deezer response is hard to interpret unambiguously in the first place. |
Hi, I'd like to look into this. Just to make sure I understand the issue, is it specifically with compilation videos from the Deezer API? Where the 'Contributors' section holds multiple artists instead of, say, just a 'Various Artists' tag? |
Not really, I think. I don't know what the A first step would really be to figure out whether there's an unambiguous way of telling that we're dealing with a compilation or whether we need a heuristic for that. There doesn't seem to be a My guess for this specific album is that it should be tagged with an |
In most cases, deezer api delivers a main tag in the contributors section. I just stumbled across this issue as I was kind of disappointed as I noticed the deezer plugin tends to set all mentioned artist as albumartist.. |
Problem
Beets is interpreting compilations as albums and is putting all artists into folder names, resulting in extremely long paths
Standard import command:
Led to this problem:
Full -vv output
Setup
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: