Metadata search horribly slow

[RPGCoder]

Hey all. I've just purchased and installed dbPoweramp R13.3 Reference and I've run into a problem with metadata access. Once I place a disc in the drive, CD Ripper doesn't seem to attempt to get the metadata itself, so I click on the Meta button. This causes the application to enter a "Not Responding" state until it finally returns with the metadata. This delay is usually about 1.5 minutes, which obviously is kind of a big bottleneck. I purchased PerfectMeta access a couple of days ago, so that's not the issue.

One of my co-workers who also uses CD Ripper has no problems with this, and he's running the same OS (Win 7) and running all of the same security software. His delays are no more than 10 seconds. I've been searching the net and these forums for other people having the same issue, but I haven't had any luck. Any ideas what could be causing this delay?

Thanks,
Dan

[Spoon]

Re: Metadata search horribly slow

Try disabling providers one by one until the culprit provider is known.

[RPGCoder]

Re: Metadata search horribly slow

All Media Guide appears to be the culprit. With only that source checked, clicking Meta causes a delay of about 1 minute, and when it completes it returns no information. It's almost like it has timed out or something. MusicBrainz takes about 15 seconds, but the other sources are nearly instant. I ran ActivateAMG.exe about a week ago, and it successfully activated the 1 year subscription on my machine, so I don't know what's going on.

Dan

[RPGCoder]

Re: Metadata search horribly slow

I just ran across this forum post containing security software issues:

http://forum.dbpoweramp.com/showthread.php?t=12018

I'm using Trend Micro Security Agent, but I don't know if it would have any of the same issues.

Dan

[Spoon]

Re: Metadata search horribly slow

Try disabling your security software briefly as a test.

[RPGCoder]

Re: Metadata search horribly slow

Unfortunately, turning off Trend Micro and disabling the firewall didn't work. I've discussed this with our IT department (ironically, with someone who has no troubles accessing AMG), and he's currently at a loss for what's going wrong.