Picard 2.0.2 released! Signed macOS releases!

Tags: #<Tag:0x00007f35105cd4a0>


I’m giving up on this. The results are so erratic that it’s gonna be pretty much impossible for me to draw up some coherent report.


@hiccup, we have a PR(https://github.com/metabrainz/picard/pull/920) to improve upon this. It will be released with 2.0.3. Also are you sure you are using Load As NAT plugin correctly? It provides a context menu option to load appropriate releases iirc.


I haven’t tested it on Vista either but we build Picard on a win10 machine. I have personally tested it till win 7. Not sure about Vista.

Python version is irrelevant for the installer. It ships with the required version of Python with it. (However I have noticed py3.6 builds of Picard don’t work on win7, which is why we use py3.5 in the package). The minimum required version to run picard is py3.5.


Thanks for getting back to me @samj1912. If you check that other thread you’ll see that I have now done a test on 64-bit Vista for you. And got a Python error. I wonder if 64-bit Python even works on Vista now it is an abandoned platform?

I am happy to do any tests you want on there if it helps.

This was version 2.0.2 so it was still installing to C:\Program Files (x86)\

(I did try manually changing that to C:\Program Files\ without any change of the Python issue)

This Vista PC will be around for a while, so happy to throw any tests at it you want.


I was wrong in pointing at Picard for the terrible loading times for singles.
The culprit is the wikidata-genre plugin. Without it single releases load at a normal speed.

I notice no differences when using the ‘load as non-album tracks’ plugin.
And I can’t find any context menu that you are mentioning for it, but since loading times are back to normal, I don’t think I would have much use for it anyway…

So, case closed, all is hunky-dory again.
The worst part is, I am pretty sure I already knew about this problem with the wikidata-genre plugin.
(and that with certain releases it even makes Picard crash)
I must have completely forgotten about it.

Thank you @samj1912 for the suggestions and for looking into this!


The “Load as non-album track” plugin does no additional lookup, just some tag trickery to make a track behave like if you loaded the recording directly as NAT (non-album track). You find it in the Plugins context menu of any loaded track on the right pane, see this animation:


What it basically does is loading the selected track’s recording as a NAT and then move any files matched to that track over to the NAT recording. It also removes all tags that are album specific. It is useful if you e.g. have single files that might be from different albums and compilations and you don’t want to tag them against a specific release.


Thanks for the great explanation outsidecontext. I’m going to give the plugin another shot soon.