Possibility to tag by artist "area"? (Artist country of origin)

MusicBrainz Picard
21

Would it help to slow down the rate at which MusicBrainz is queried? That would increase loading times for releases, but might help if the problem is caused by rate limiting in the first place.

22

I don’t think that would make a difference.

I did take a look at the code and found something that might be causing (or contributing to) your problem. In some cases the country code is being returned by the api as an ISO-3166-2 code, and the plugin only checked for ISO-3166-1 codes. I’ve updated the plugin to now check for both ISO codes, and submitted the update for inclusion in the “official” Picard plugins. Until it has been accepted and merged, it can be downloaded from my fork of the github repo and installed manually. If you decide to give it a try, please let me know if it addresses the problem. Thanks.

2 Likes
23

I’m afraid I’m still getting a lot of releases without the artist country, even with version 0.4. It might happen slightly less? An option to clear the cache would help, because then I could retry the ones that don’t get the country information one by one without having to remember which ones they are after a restart.

But maybe I’m the only one having this problem when looking up multiple releases?

24

How many releases at a time are we talking here? It shouldn’t matter, but it might help me reproduce it here, which I haven’t been able to do yet. Also, do you ever run into it if you only load one release at a time?

I’ve created an Issue for tracking this in my plugin repository, so we may want to move further discussion there.

4 Likes
25

It already happens when I drag two releases from the file browser panel to the cluster panel. If I drag releases from file browser to cluster panel one by one and wait until the previous release has been loaded before I drag another one, it seems to be all right.

3 Likes
26

Okay, thanks for clarifying. I’ll have to dig a bit deeper into how Picard handles the request queue when there are multiple releases loading simultaneously. It looks like it may be signaling that a release’s loading is complete when there are still outstanding related requests in the queue.

3 Likes