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.
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
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?
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
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
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
Hi, Bob. Hope you’re keeping well!
A quick query: is it possible to obtain (and/or assign to tags) 3-letter ISO country codes (a.k.a. ISO 3166-1 alpha-3), such as CAN, GBR, and USA?
Your expertise would be much appreciated.
Regards,
Jason
It’s possible, but I don’t think we actually have the list stored anywhere that would be available to the code. The list mapping the two character code to the three character code would have to be included in the plugin. Not a difficult task, but unfortunately I don’t have time right now to work on it.
2 Likes
@rdswift Thank you for the plugin and the time you dedicate to this effort!
I have been successful at using this plugin and the sample script you provided to create an album artist country tag. This works well on Albums with a dedicated Album Artist. I would like to use a script on compilations and extract the country of the artists on individual tracks. I’ve tried the following script but it doesn’t seem to work. I think I’m missing something but I can’t seem to figure it out. Any guidance you or anyone could provide would be appreciated. Thanks.
$set(_tmp,_artist_$getmulti(%musicbrainz_artistid%,0)_)
$set(grouping,Country: if2($get(%_tmp%country),$get(%_tmp%begin_country),$get(%_tmp%end_country),null))
It’s possible that the extra calls to the MusicBrainz server for the track artist details has not completed before your script is assigning the values. To check if this is the case, try manually re-running your script (from the right-click context menu) on a track and see if the “grouping” value is updated.
I think that worked. When I first load the album the script does not always work. But if I refresh the album / reload the data and rerun the script it seems to work. I may need to do this a couple of times. I plan on scanning my albums one at a time so this approach may be tolerable. The albumartist script seems to be more consistent. Thanks for your help! If you happen to have any tips for my workflow to make this more consistent that would be great. Regardless I appreciate your time!
It’s actually a bug in my plugin that I’ve been trying to address for a couple of years now. Unfortunately I haven’t found a solution that works yet. I’ve been occupied lately with work on Picard 3, but hope to get back to working on cleaning up this and some other issues soon.
4 Likes