MediaMonkey forum

Released a new version of the Discogs Tagger

Here are the changelog:
- Added option to replace a ´ and ` with a '
- Added option to search at Metal-Archives.com
- Removed issues with multi-disc albums, need MediaMonkey Version 4.1.28.1905 or above

@TroubleClef : Please use this new version and the Mediamonkey Version 4.1.28.1905 or above. Please give me feedback if the issues are gone or not..

TLD wrote: ↑Fri Feb 14, 2020 1:02 pm

DJSamhein wrote: ↑Thu Feb 06, 2020 7:03 am -Bug: On releases that have the same song name on different discs (e.g., release 5788257), if we select the option to tag disc# and track# all instances of that song name will get the same one. In this example, the song "Blood Of Love" in disc 1 and 2 will both be tagged as disc 2. Same with the other ones that have the same name.

I've been dealing with this since the Amazon links broke.

Usually I make note of which song(s) it did this for, and adjust them accordingly.

Sometimes it's made worse by the fact that the same song appears many times - such as a single with multiple versions (acoustic, "DJ X", etc.) where they all get tagged with the last entry matching the title.

Software can't tell which it should match, so "last in" - I don't see this as something easily fixed unless the software _checks_ the existing track# before fixing it... and if the title already doesn't match, you'll run into the same problem.
"In The Wee, Small Hours Of The Morning" doesn't match "In The Wee Small Hours Of The Morning" as an example...

- TLD

This issues should be solved, too. Please give me feedback about it. Thank you!
Don't forget to update Mediamonkey, too. Version 4.1.28.1905 or above. Still Beta, get it from here : https://www.mediamonkey.com/forum/viewt ... 60#p466979

A big Thank you to the devs !! Cheers

The disc# issue seems to be fixed with the last version, but it introduced a new bug: Unselecting the right-most checkbox (so it won't change the track name) stopped working. screenshot

This new version of MM also seems to hang up on certain operations, mostly on auto-DJ or expanding library nodes, but that's not your issue. However, it might force me to downgrade the version until it's fixed.

DJSamhein wrote: ↑Thu Apr 16, 2020 10:04 am The disc# issue seems to be fixed with the last version, but it introduced a new bug: Unselecting the right-most checkbox (so it won't change the track name) stopped working. screenshot

This new version of MM also seems to hang up on certain operations, mostly on auto-DJ or expanding library nodes, but that's not your issue. However, it might force me to downgrade the version until it's fixed.

Thank you for your feedback. I will now look into this.

I released a fixed Version. Thank you for reporting the bug!

Yes, it seems that it's all working nice. I will probably downgrade the version, though. Auto-DJ went from a 3-5sec delay to a 1min+ delay.

Watch out for the dreaded curly quote characters also.

dypsis wrote: ↑Fri Apr 17, 2020 1:04 am Watch out for the dreaded curly quote characters also.

Could you please post this char ?

Looks like the latest version of Discogs Batch Tagger 2.5.4 is triggering Norton 360. Norton blocks the download and says its a heuristic virus.

Is there a way to check this if it is a false positive?

jeffkarl wrote: ↑Fri Apr 17, 2020 2:20 pm Looks like the latest version of Discogs Batch Tagger 2.5.4 is triggering Norton 360. Norton blocks the download and says its a heuristic virus.

Is there a way to check this if it is a false positive?

Hi,

sadly it is a neverending story. I send this Addon many times to the antivirus companys to check and whitelist it. But a few days later, the next false positive alarm comes up.
I'm the dev of this addon and i assure that there is no virus, trojan or whatever in it.

The addon is written with AutoIT, and many virus are written with this programming language, too. So the heuristic search sometimes says, that the addon is possibly infected. But it isn't.

You can upload the file to virustotal.com. It check the file against many antivirus programs.
I just upload the MMIP-File and 7 antivirus engines found "something", the other 56 found nothing.

In the EXE-File from the Addon 16 engines found mostly generic (with the heuristic scan), 57 engines didn't detect malware or whatever.

I hope, my statement could help you.

crap_inhuman wrote: ↑Fri Apr 17, 2020 6:16 am

dypsis wrote: ↑Fri Apr 17, 2020 1:04 am Watch out for the dreaded curly quote characters also.

Could you please post this char ?

‘’“”

FYI
For False Positive Norton is one of the worst AV I have found and tested over my 25+ years experience which is proven by Virus Total site

To be honest any third party AV will bottleneck your PC for at least 10-15% if you have Fast CPU and on lower end with Slower CPU and HDD even more.

personally only way to be safe from Viruses (99% of Wild Viruses must have Internet connection, ransomware as I have researched do not activate till they successfully upload cryptokey to remote server) is to have dedicated firewall PC, Router or an app that specifically blocks inbound/outbound traffic.

As CP said it is never ending battle.

FYI: "heuristic" word is modern way to say "it is doing something that we do not know what it do, so it is better to block it than say we can't determine what it is." or "if we truly scan file behavior we will make your PC crawl, unless you do our job and send us samples we will not flag it as safe".

Hi,
So I found another bug:
When the album on discogs has less tracks than the album you have, the track numbers are all screwed up. screenshot
In this case it starts trying to change my tracks from track 3 (as if it counted the unselected ones) and once it reaches track 10 it tags properly. Maybe because I use leading zero?

So since I updated this extension to 5.73 I have been receiving this error each time I run the script:
...or something like that as I translated the error text to English. There is more but the error dialogue is too small to show it.

I am using the newest Beta of MM and have tried completely uninstalling both the add-on and MM itself (including deleting .ini files and database, etc.) as well as running it in portable mode, but still get the same error each time.

Unfoldingdrama wrote: ↑Wed Apr 22, 2020 6:26 am So since I updated this extension to 5.73 I have been receiving this error each time I run the script:

Code: Select all

Error #1006 - Microsoft VB Script compile error
There is no ')'
trackName = Replace(trackName, "., "'")

...or something like that as I translated the error text to English. There is more but the error dialogue is too small to show it.

I am using the newest Beta of MM and have tried completely uninstalling both the add-on and MM itself (including deleting .ini files and database, etc.) as well as running it in portable mode, but still get the same error each time.

I'm using the latest script and I have no errors. Maybe try enabling that option (in tools/options->discogs tagger->replace `or ´with ") to see if the error persists?