-
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
Fetch remixer
field from MusicBrainz
#4428
Comments
Sounds like a reasonable thing to add! Hopefully it shouldn't be too hard (the place to do it is in |
I am currently working on this. It is my first time contributing to beets so I might take some time to get familiar with the codebase and structure. |
Awesome! Let us know with a Discussion post if you have any code-level questions we can answer. |
So after looking at the example given by @TypicalFence I can see the remixer field on the musicbrainz website. However, looking at the JSON or XML that is available from the muiscbrainz website I can't find the remixer mentioned anywhere except for the title. I don't know how to proceed since to me it seems like this information isn't available through the api queries beets makes at the moment. Is this the case or am i missing something? |
@Bootjewolf I just went over the musicbrainz api docs. The remixer tag is a artist relation. Now for that to work for the requests that you posted we need to include This leaves us with the following url: https://musicbrainz.org/ws/2/release/7c7f7ddf-c021-4ee8-993d-d1c330b4a36a?inc=aliases%2Bartist-credits%2Blabels%2Bdiscids%2Brecordings%2Bartist-rels%2Brecording-level-rels&fmt=json You can find this in the api docs here. The api is rather complicated tbh. |
Thank you! I will have another look at it this coming week. |
According to my tests I have successfully implemented it in PR #4549. |
Problem
Musicbrainz seems to have a field called
remixer
for remixes, this info isn't written to my files.Example: https://musicbrainz.org/release/7c7f7ddf-c021-4ee8-993d-d1c330b4a36a
Using it for the artist field, similarly to the
artist_credit
option would also be nice.According to the Picard docs there would even be a proper place to store it in ID3.
Setup
The text was updated successfully, but these errors were encountered: