Open Czechball opened 3 years ago
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 contributors
and artist
should be mapped to "all artists" and "album artist", and whether these are even used consistently in their database. Maybe git blame
can tell why the contributors
field was chosen for the artist in the first place?
Right, so this is a Deezer related bug. I'll change the issue name
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?
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 contributors
section holds for different kinds of albums. The first problem here is figuring out the exact meaning of these API responses, that's not yet clear. See my comment above on interpreting the contributors
and artist
. Also, I'm not familiar with either the plugin or the deezer API. Maybe @rhlahuja can chime in here, he/she is the one who wrote the deezer plugin (see #3355).
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 compilation
flag in the response (although there's a type: album
field. Maybe, this shouldn't be tagged as compilation after all? What other values can type
have?).Thus, probably you'd need to read the API documentation and/or compare responses for regular albums and compilations to figure out how to approach this.
My guess for this specific album is that it should be tagged with an albumartist
of A. Skillz
(the artist
in the response rather than the first contributor
as it is now) and marked as a compilation (although I'm not sure how to infer this from the response. The number of contributors being larger than 1 might not be enough evidence). Does that sound correct to other people here?
In most cases, deezer api delivers a main tag in the contributors section. Like in this example: https://developers.deezer.com/api/explorer?url=album/302127 This makes it in the most use cases far more sophisticated over the spotify api. As this doesn't bother at all. I'm not actually sure how to handle it in this case. There have been a lot of contributors flagged as main. But as well, there is a contributor listed with ID 5080. I guess it is translated, but the ID should be sufficient to check if this is part of the contributors to flag the whole album as various artist.
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: