Picard Tagger Button doesnt work in any browser on Windows 10

I recently upgraded to windows 10, and have just started to ‘attempt’ tagging more vinyl rips using Picard. Since having windows 10, the tagger button in Firefox, Edge, and Chrome no longer works. I even turned off my firewall, but this made no difference. Is this is known issue and is there a work around? I’ve tried using the scan facility, but that is unreliable at best; it’s very rare to get a 100% successful track scan rate, so this is not a solution or workaround. I just need the tagger button to work as it used to do.

Thanks.

Are you using MusicBrainz over HTTPS? If so, it’s a known issue and not related to Windows 10 at all, but rather a security measure in Firefox itself, to prevent/mitigate certain types of attacks. I thought it was a known issue, but I can only really find one related ticket in our system:
https://tickets.musicbrainz.org/browse/MBS-6785

1 Like

works for me with https, win10 and chrome
edit: also works in firefox, no matter https or http

sry i have no idea why this does not work for you.

1 Like

Thanks Freso, HTTPS may be my problem. I’ve got the HTTPS everywhere plugin installed into all my browsers, so this could be the problem, I’ll try removing it for a test.

Ok, more testing has revealed that the problem is caused by ‘NoScript’ addon I have installed in my browsers. Its a javascript blocker. When I deactivate it, Tagger button works. Strange thing is that NoScript is reporting that it is not blocking anything (which is the reason I hadn’t considered it as a potential cause). So the bug is with NoScript, not Picard. I think perhaps it may be something to do with connecting to loopback address at 127.0.0.1.

4 Likes

Ah, indeed. I just added the below to Settings→Advanced→ABE→USER (or SYSTEM possibly, not sure what the difference between the two is exactly):

Site ^http://127\.0\.0\.1:800\d/.*$
Anonymize GET from musicbrainz.org beta.musicbrainz.org

Site LOCAL
Accept ALL from LOCAL
Deny

And it seems to work. Make sure the MB specific rule is earlier than/before the Site LOCAL one, as the first matched rule will be used.

5 Likes

I’m using Chrome on Windows 10 and I thought it wasn’t working for me as well. Turns out there just isn’t any feedback on your “tagger” click. I made the mistake of trying to work with hundreds of albums at once so it was hard to see if anything happened - try having a go with a single file/album to see if it works.

FWIW…I use ScriptSafe and HTTPS errrrrywhere

2 Likes

https://tickets.musicbrainz.org/browse/PICARD-715

1 Like

As a workaround (for people who are having problems with the green tagger button), you should be able to copy the URL to a release in MusicBrainz and paste it into the search bar in Picard.

4 Likes

Hi, I tried everything on here and nothing seems to work.
When I click the ‘‘tagger’’ button, nothing happens.

Can anyone help?
Many thanks!

That’s a very old thread you have found. Don’t even know if any of that makes sense now.

Can you see the " ?tport=8000 " on the end of the link in the URL bar?

In the Picard OPTIONS \ ADVANCED \ NETWORK

Is Browser Integration ticked? And is the port set to 8000?

Do you have any extra third party firewalls setup by your Anti-Virus software?

1 Like

Sorry to do some grave digging but maybe it helps some other users. I’m using Firefox with the Ublock Origin browser plugin. When using the filter list “block outsider intrusion into LAN” it prevents the communication to Picard.

To fix this without disabling the filter list you can add the following line to static rules:

@@||127.0.0.1:8000^$domain=musicbrainz.org
6 Likes