Discogs Tagger 5.71 (Updated: 2019-09-23)

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Discogs Tagger 5.71 (Updated: 2019-09-23)

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by TLD » Fri Jan 24, 2020 11:35 pm

crap_inhuman wrote:
Fri Jan 24, 2020 5:19 am
And here are the next bad News.... Microsoft announces, that they will disable Internet Explorer 11 on Windows 10 Machines and replace it with Internet Explorer Edge. Okay, no one use the IE 11, but for Discogs Tagger it is a must-have. Without Internet Explorer it will not work.
IE Edge doesn't have the needed COM Interface.
If it comes to that, M$ may end up in hot water because they're removing software and functionality from working machines without advising users. It's one thing to update software for security - it's another to remove your choices. Although IE11 is only used in certain circumstances without hacking at the OS, or using it in an enterprise environment (read: PRO version or a company's hardware, not an individual's) that could still end up hurting them, at least in the short term.
(And with the EU so prickly about there being options and your being able to opt out, I'm sure it won't be done there... not automatically.)

- TLD

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by TLD » Fri Jan 24, 2020 11:27 pm

Note to all:
Discogs had updated the ciphers across the board to their servers - including the API services - which is what was causing the problems.

They have reverted the changes to the API services, which has restored functionality for the tagger in MM4 on Windows 7 (& Windows 8 presumably)

You can view the threads here... https://www.discogs.com/forum/thread/809378
And here... https://www.discogs.com/forum/thread/809470

- TLD

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by crap_inhuman » Fri Jan 24, 2020 9:30 pm

Thank you for the log files. The error occurs when the script try to load the information of a master release. Some releases doesn't have a master release, like the zero cult album.

You could insert a new line at 6744 Return, so the master release would not be loaded.

..i just read that Discogs reverted the change of the ciphers. The tagger should be working again without changing a line. :D

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by DJSamhein » Fri Jan 24, 2020 9:17 am

crap_inhuman wrote:
Fri Jan 24, 2020 7:52 am
Okaaay... would you please send me the Discogs.log File from the "Metallica Load" try and 1-2 logs from the Zero Cult try?
Got you 5 files here.
First one is a direct tag from the zero cult album (via context menu). Second is manual search. Third is one of the other results in the manual search.
Fourth is metallica manual search and fifth is the direct tag from the album. Hope it helps.

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by crap_inhuman » Fri Jan 24, 2020 7:52 am

Okaaay... would you please send me the Discogs.log File from the "Metallica Load" try and 1-2 logs from the Zero Cult try?

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by DJSamhein » Fri Jan 24, 2020 7:24 am

So, after a few experiments, the mystery thickens:
I tried tagging the album "Deep In Your Mind" by Zero Cult. It only has one result and it loads fine.
I then tried manually searching for "Zero Cult Deep In Your Mind". It returned 10 results (from other artists, compilations, etc) and most of them load fine. After checking them individually, it seem like all the ones that load correctly are single release ones.
I then tried to search "Metallica Load" and it didn't load, generating the error.

This leads me to think that there is some way to load albums that doesn't generate the error. Single release albums load correctly, so there must be something done differently with those, though I can't really say what the solution is.
But I hope this will help you pinpoint it.

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by crap_inhuman » Fri Jan 24, 2020 6:08 am

DJSamhein wrote:
Fri Jan 24, 2020 5:57 am
I was going to say they fixed it because I was able to load an album on discogs tagger, but I realized that it only worked because in this particular case there was only one result returned.
When this happens I expect that the script simply loads the master details and doesn't query for album details, which is when the error occurs.
The script always load the the album details from the selected release. There must be another reason. I'm at work and could not look into the code now. :(
DJSamhein wrote:
Fri Jan 24, 2020 5:57 am
What I find strange is that the master details connection works fine, which leads me to think that the methods used for master and for release are different. Can the release connection be changed to use the same method as the master?
The methods should be the same. But i need to check it.
DJSamhein wrote:
Fri Jan 24, 2020 5:57 am
As for the end of IE and its requirement for the script, I expect that there are plenty of scripts that use IE engine and that there will be some solution further along the road, either by recoding to use Edge (I doubt M$ will natively support other browsers like that) or by providing an alternative that will allow coders to preserve their code (kinda like they already did with command line, when they detached it from the OS but maintained the funcionality)
I would be happy, if there is a simple solution :)

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by DJSamhein » Fri Jan 24, 2020 5:57 am

I was going to say they fixed it because I was able to load an album on discogs tagger, but I realized that it only worked because in this particular case there was only one result returned.
When this happens I expect that the script simply loads the master details and doesn't query for album details, which is when the error occurs.

What I find strange is that the master details connection works fine, which leads me to think that the methods used for master and for release are different. Can the release connection be changed to use the same method as the master? If possible, it would seem that would fix everything.

As for the end of IE and its requirement for the script, I expect that there are plenty of scripts that use IE engine and that there will be some solution further along the road, either by recoding to use Edge (I doubt M$ will natively support other browsers like that) or by providing an alternative that will allow coders to preserve their code (kinda like they already did with command line, when they detached it from the OS but maintained the funcionality)

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by crap_inhuman » Fri Jan 24, 2020 5:19 am

DJSamhein wrote:
Fri Jan 24, 2020 4:34 am
According to this post, discogs changed their security certificate to use ciphers that aren't supported by win 7.
It's not likely that they will change it. Which means that any system below windows 8 will have to be upgraded to continue using discogs tagger.
We can wait for further development and see if discogs will revert their changes, but I wouldn't count on it.
Thanks for your Explanation.

I think discogs will not revert their changes.

And here are the next bad News.... Microsoft announces, that they will disable Internet Explorer 11 on Windows 10 Machines and replace it with Internet Explorer Edge. Okay, no one use the IE 11, but for Discogs Tagger it is a must-have. Without Internet Explorer it will not work.
IE Edge doesn't have the needed COM Interface.

If we come to this Point, the only way to use Discogs for tagging our music files is DiscogsBatchTagger.
Some antivirus programs do a false positive while scanning the addon. Therefore i will publish the source-code of the addon, so everybody can see that there is no malware or whatever in the code

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by DJSamhein » Fri Jan 24, 2020 4:34 am

According to this post, discogs changed their security certificate to use ciphers that aren't supported by win 7.
It's not likely that they will change it. Which means that any system below windows 8 will have to be upgraded to continue using discogs tagger.
We can wait for further development and see if discogs will revert their changes, but I wouldn't count on it.

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by crap_inhuman » Thu Jan 23, 2020 4:26 pm

Thanks for posting this problem.

I have found the cause here : https://www.discogs.com/de/forum/thread/809470

There is still no solution, except installing Windows 10 :(

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by ndmushroom » Thu Jan 23, 2020 2:12 pm

OK, something really weird is happening. For the last 3 days, I'm getting the msxml6.dll error (Error #2146697211 - msxml6.dll System cannot locate the resource specified
File: "\DiscogsWebTag.vbs, Line: 6755, Column: 1)

I've tried everything: running an earlier version of the script, running the latest one, revoking and re-granting access to the app in Discogs, uninstalling and re-installing MM, rebooting the PC and doing everything all over again, but nothing works. Then today I discovered that, while the error appears when I launch the search, when I browse between the search results most don't work, but some do.
Initially I thought it must be Discogs (the site) behaving erratically again, but it's been 3 days and I'm the first one to complain, so I guess that's not it.
I've uploaded the script log here: https://we.tl/t-6PGYzLqehq. Could you have a look and see if you make anything of it?

Re: Discogs Tagger 5.71 (Updated: 2019-09-23)

by Peke » Fri Nov 22, 2019 7:43 pm

Hi,
If someone encountered an issue they are removing some features till unknown https://www.discogs.com/track

Re: Selected Tracks not appearing

by crap_inhuman » Thu Oct 17, 2019 8:09 am

dmcc0 wrote:
Tue Oct 15, 2019 5:52 pm
Hi,

New MM user here. Downloaded the Discogs tagger V5.71 and all was gong well, but suddenly my selected tracks are not appearing in the tagger window any more. I do everything else; search, change the options etc. but all a bit pointless if I can't apply to the tracks. I've tried re-installing the tagger, but no change. Musicbrains tagger is the same too.
Hi, you can't see the tracks in the lower part of the window?

The tracks you selected are in the mediamonkey database? You need to add the tracks into mediamonkey. Maybe this is the problem.

Re: Options still only amazon

by crap_inhuman » Thu Oct 17, 2019 8:03 am

d ross wrote:
Sat Oct 05, 2019 4:49 pm
May be stupid but...
Installed add-on. On "extensions" window, does not allow options.
When I use auto-tag from web on track, I get auto-tag screen which defaults to music=brainz, but when I select options, it only shows me amazon options.
How do I switch to discogs?
Hi,
sorry for the late answer. Please try to reinstall the addon. This should help.

Top