MediaMonkey forum

Hallo Sven,
seit einiger Zeit teste ich in einer eigenen Umgebung MM5.
Ich denke, erst jetzt ist mir und sehr vielen Anwendern die Bedeutung Deines AddOn bewußt.
Ich wünsche Dir viel Ausdauer für die Erstellung der MM5-Version.

Google hat übersetzt:
Hello Sven,
I've been testing MM5 in my own environment for some time.
I think it's only now that I and a lot of users are aware of the importance of your add-on.
I wish you a lot of perseverance in creating the MM5 version.

Erwin Hanzl wrote: ↑Sun Mar 27, 2022 11:58 am Hello Sven,
I've been testing MM5 in my own environment for some time.
I think it's only now that I and a lot of users are aware of the importance of your add-on.
I wish you a lot of perseverance in creating the MM5 version.

I really hope you are wrong and that people realized this long ago, https://www.mediamonkey.com/addons/browse/popular.
It's only been the most popular add-on forever. I really hope we see some MM5 compatible Discogs plugin sometime but..

MM is a waiting game, MM6 will be the bomb!

Why should I be wrong?
Yes, it was the most popular addon for MM4 and users happily accepted it.

And what do the MM5 developers deliver?
Again an external person programs this function for MM5 - free of charge in his spare time.

MM is a waiting game, MM6 will be the bomb!

Keep dreaming.

It's a minor thing right now, but when I hit a link in the lookup results interface, Internet Explorer opens.

I use Firefox exclusively and can't figure out how to get links to open there.

Is this a Windows setting or somewhere in the tagger code?

The tagger uses the INet Explorer for showing the result window. That's why the INet Explorer comes up if you hit a link.

Hanging (or extreme slowness)

Much of my library was organised and tagged when the Amazon data was still available to the MM tagger, so now I'm trying to add some new CDs i'm finding the experience a bit painful.

I installed Discogs Tagger 5.81 (in MediaMonkey 4.1.31.1919) but i'm finding that Discogs tagger is either really slow, or it ust plain locks up MM, to the point where the whole program is unresponsive and must be killed from the Task Manager.

As an example, selecting an (admittedly large) box set with about 75 tracks and then selecting "Auto-Tag from Web" with Discogs Tagger installed, the measured time to open the tagger window is around 3.5 minutes. Out of 5 attempts to use Discogs Tagger so far, all have ended in MM locking up and needing to kill the program.

Is this a known issue?, ideally with a known fix?

Hey Colin,

maybe an anti-virus program blocks the addon. Kaspersky is known for doing this.
https://www.mediamonkey.com/forum/viewt ... 13#p495913

Which anti-virus program you use?

Greetings,
Sven

Ah, interesting. I do use Kaspersky AV.

Not sure how AV would slow down an application like this rather than simply blocking it, maybe something to do with safety-checking network accesses and adding a lot of overhead?

Anyway, a couple more data points-

I swapped from MusicBrainz to Discogs as a data source, and while it was still very slow, I did manage to get a match for the CD box set I was working on ("Box" by AC/DC), and get as far as trying to tag the files without crashing.

However I then hit another problem, which I have run into before with the MediaMonkey tagger. It seems to be a feature/limitation of MediaMonkey itself not the Discogs extension?

Basically, if the auto-tagging incorrectly matches one track on a disc (in this case i think for Disc 1 it matched the Discogs info for track 5 with the local track 1, maybe based on very similar track length). This then throws all the other track data out of sync, if "let rip" the tagger would try to write track 3 data to local track 2 etc, making a real mess.

One would think you'd be able to simply drag+drop the auto-matched data to match up with the correct track, but that doesn't seem to be possible in MM (or is there a feature I haven't found?).

In the end I gave up with MM, downloaded MP3tag, and once I got my head around the basics of the interface, using the same source data from Discogs got the job done in 10 minutes.

The performance issue could well be down to Kaspersky AV (any idea to to tweak the AV to fix it?), but the track mismatch thing seems to be a "feature" of MM (true?). Maybe MM5 will be better, but from the forum postings MM5 still seems to be pretty immature itself when it comes to auto-tagging.

Ah, you tried to tag the CD Box Set from AC/DC, my problem child.

I tried this Box Set, too. And had the same problems.

Reason: MM always try to match the tracks while auto-tagging. With the CD Box Set it doesn't work. A workaround is to tag one CD after another.

How to tweak Kaspersky AV? I don't know, sorry. I use Defender from MS.

If I use Discogs Tagger with any number of tracks short of the full album, it won't match them properly. I've given up trying to find a pattern in this mess.

Hey, which version of Mediamonkey you have ?
You should use the newest version 4.1.31.1919

Yes i'm using the latest version

crap_inhuman wrote: ↑Thu Jul 07, 2022 9:29 am Hey, which version of Mediamonkey you have ?
You should use the newest version 4.1.31.1919

I am.

Sensei Le Roof wrote: ↑Fri Jul 08, 2022 1:41 pm

crap_inhuman wrote: ↑Thu Jul 07, 2022 9:29 am Hey, which version of Mediamonkey you have ?
You should use the newest version 4.1.31.1919

I am.

Could you send me the log file please?

Hopefully this is the right one: https://drive.google.com/file/d/1pAIlCC ... sp=sharing