#musicbrainz

zas: I have a problem with picard and a (large) release. Just open picard and in the search bar, make it load the 607cc05a-e462-4f39-91b5-e9322544e0a6 release. The track 1 of CD04 doesn't have any work uuid tag, but if you open https://musicbrainz.org/recording/00a904b0-6743... in a browser, you can see it has a "recording of" work related. I did a quick debugging and it seems the server is not returning

the work relations.

maybe musicbrainz does not send work relations in the json output when a release has too many tracks?

antlarr: I don't remember the details right now, but something like this is exactly what's happening

so there's no way to tag those files correctly? :(

large releases like this used to cause issues on the server, and the server was changed to omit the details in these cases. I don't exactly know where the threshold is, though.

outsidecontext: I see, thanks for the information!

unfortunately no way around this. maybe Picard should offer an option to download track details on a track by track basis in these cases (which would of course take a while. 548 tracks would take over 9 minutes to query completely due to the request limit of one request per second.

hmmm, that would be a nice solution since I'm not in a hurry :)

I'll try to give it a try to implement that

I would be happy to see this. could actually be done in a plugin :)

you really like plugins :D

but also Picard itself should probably indicate if a release was loaded incompletely (not sure how to detect this). I'll add a ticket

yes, that's true

Hey! How can I become a mentor for MetaBrainz Foundation at Google CodeIn 2019?

...

seriously what

interesting

We've gotten like 30 mails asking to be a mentor

From people we've never seen before

I'm pretty sure by now that some unis or whatnot are asking students to become mentors

?!?!

but... that's not how it works

it doesn't make any sense

hench my "what"

Yeah

I dunno

hello folks

hey, an irsc question..

i added isrcs from the CD which were extracted as TbDCR1900059 (etc)

however, it looks like that was an error and they're actually GBDCR1900059 (etc) on deezer https://api.deezer.com/album/107271852/tracks

should the weird ones be kept since they're actually written like that on the CD?

it looks like TB is an unassigned country code..

Tunecore used to assign their own weird "ISRCs", but I guess this is not that case and just an actual error

In which case I'd correct it

(and maybe leave an annotation explaining the issue)

i'm conflicted since, they're still useful for lookups though?

asking an auto-editor to fix them since i think changing an isrc isn't an auto-edit for unprivileged users

I can approve them if needed

If we had a way to indicate "this is listed here but it's basically a search hint" I'd say keep them, but since we can't, it feels confusing

edits submitted

Oh, it seems we don't really do editing ISRCs, we just add + remove

So nothing to approve, but I'll yes-vote the removals

Might be worth looking through the rest of the database for those ISRCs, IIRC there are also some that start with a Q

https://github.com/kepstin/magicisrc/blob/maste... - there's a few assigned codes starting with Q

QM, QZ are both valid. I think one of them got assigned to the US because they were running low on numbers