Problem getting AMG to work in Batch Ripper

[riptastic]

I am currently trialling the software, but am having some real difficulty getting AMG to work with batch ripper; currently it does seem to want to use it as one of the lookup databases.

I have gone through the forums but still haven't found an answer so I was hoping someone could help.

The things I have tried so far:
* made sure that the allow dbpoweramp to access internet box is click in the dBpoweramp config
* I have made sure that AMG is selected in the Meta Providers menu
* I have tried turning off my firewall completely (exiting, not just disabling it). This is Trend Microsystem

The AMG lookups still says 400 lookups remaining, and when trying to rip using AMG as the sole meta data provider it only comes up with the message "no meta data available" and the cd is rejected. AMG works fine in CD Ripper, so really am stuck on what might be causing the problem. Does anyone have any ideas??? I have spent ages trying to figure this out

[Spoon]

Re: Problem getting AMG to work in Batch Ripper

maybe install Wireshark and capture the network packets, look at CD ripper with just AMG then look at batch ripper. It might show what is going on.

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

I'm also having a problem. CD Ripper has no problem getting metadata and album art and it's being sourced from AMG, GD3, MusicBrainz and FreeDB. So getting a connection to their servers is not an issue.

The same album in Batch Ripper gets metadata only from MusicBrainz and FreeDB - nothing from AMG or GD3.

This is a brand new download of Batch Ripper today and I have a registered copy of dBpoweramp Reference R14 purchased about a week ago.

The Meta Providers options are set to ALL active providers and including Intelligent Meta. AMG has 400 (non-commercial) lookups remaining. The User Name/Password fields for AMG are currently blank which I understand is correct until I run out of free lookups - correct?

Hopefully this is just a configuration issue but based on everything I've seen in the forum I have no idea what it might be so any help would be appreciated.

The whole reason for buying dbPoweramp was to re-rip a very large collection in batch mode. And yes, I know that after 400 lookups I'll have to buy more lookups from AMG but at the moment I'd just like to get one to properly work in Batch Ripper.

Thanks in advance.

[Spoon]

Re: Problem getting AMG to work in Batch Ripper

Blank user name is correct for AMG on trial yes. Try installing Wireshark and see if AMG is being looked up at all in Batch Ripper.

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

Spoon:
I've installed Wireshark and have run two tests.

The first, only freedb is selected as a meta supplier. It works and in Wireshark I found what I "think" is the relevant TCP traffic between them at 195.214.216.38 to my computer.

However when I select only AMG as a meta source it fails right away (reject 1: no meta data) and I don't see anything that looks like outgoing traffic to an IP address.

There is SSDP protocol traffic to a destination called ff02::c as follows:

Frame 6: 208 bytes on wire (1664 bits), 208 bytes captured (1664 bits)
Ethernet II, Src: HonHaiPr_69:5e:1e (00:22:68:69:5e:1e), Dst: IPv6mcast_00:00:00:0c (33:33:00:00:00:0c)
Internet Protocol Version 6, Src: fe80::6092:5d63:58bf:1385 (fe80::6092:5d63:58bf:1385), Dst: ff02::c (ff02::c)
User Datagram Protocol, Src Port: 57851 (57851), Dst Port: ssdp (1900)
Hypertext Transfer Protocol
M-SEARCH * HTTP/1.1\r\n
Host:[FF02::C]:1900\r\n
ST:urn:Microsoft Windows Peer Name Resolution Protocol: V4:IPV6:LinkLocal\r\n
Man:"ssdp:discover"\r\n
MX:3\r\n
\r\n

To be honest I'm not totally sure what I should be looking for but I'm getting the impression that I simply never make the conection to AMG. Is there a specific protocol batch ripper uses to connect to AMG I should focus on?

If it helps:
- Windows 7 64 bit
- no proxy server
- accessing from Canada (surely AMG doesn't block foreign IP addresses?)
- behind a Linksys router

[Spoon]

Re: Problem getting AMG to work in Batch Ripper

If you wireshark just AMG in CD Ripper it will show what it should look like (it is all TCP).

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

Spoon:
As suggested, I ran Wireshark with CD Ripper set to only query AMG and there is TCP traffic to IP 64.92.236.52 which resolves to Macrovision/Allmusic. Plus a DNS request to my DNS provider (OpenDNS) to resolve image.gslb.allmusic.com

The same query via Batch ripper fails almost instantaneously and the Wireshark capture shows shows nothing at all similar and no TCP or DNS requests.

From what I can tell, Batch Ripper doesn't even try to connect to 64.92.236.52 or to send out a request to OpenDNS to get an IP address for AMG.

I also tried uninstalling Batch Ripper, downloading a new copy and reinstalling it - no change.

Hope this gives you some clues. I appreciate your quick responses.

[Spoon]

Re: Problem getting AMG to work in Batch Ripper

Try running batch ripper in an account with admin access rights.

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

Spoon:

The account I am using has admin privileges but to be safe I've also used the Windows 7 "Run as administrator" option.

Also, I tried creating a specific Windows firewall rule for batch ripper.

Nothing has worked so far.

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

Oh yes - I also just temporarily removed my firewall/router and changed my DNS provider on the chance one or the other might be involved.

Batch ripper still not querying AMG

[rudolffischer]

Re: Problem getting AMG to work in Batch Ripper

Same problem here. Other Metadata sources show up in batch ripper, but AMG remains blank. AMG works fine in (single) cd ripper.

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

Spoon:

It's been about a week - any progress on a solution?

FWIW - I also tried disabling Microsoft Security Essentials, plus uninstalling dbPoweramp and batch ripper and then reinstalling.

Batch ripper still refuses to connect to AMG.

[w0067814]

Re: Problem getting AMG to work in Batch Ripper

Spoon,

As I stated on my other thread regarding robot scheduling, I have also suffered problems with album art missing in batch ripper.

Reading this thread I have checked my wireshark logs in both batch ripper and the standard cd ripper. When running batch ripper I deselected all but one of the meta sources. When either AMG or GD3 are selected as the only source the lookup fails instantly and there is no data sent (and I mean, not a single byte on the wire!), however when other sources such as freedb are selected there is all the usuall chatter I would expect to see.

When repeating the process in standard cd ripper, the lookups are all present and correct, even for just AMG, or GD3. I suspect this is something to do with the username / password authectication code. When putting a username & password into the fields, I see that the authentication fails (not registered, random user / pass), so the lookup to your server is working, but nothing when the fields are blank (understandably).

Please clarify something for me to make sure I'm not missing the point. Does the batch ripper work with AMG / GD3 within the trial period of dbpoweramp, or does it only work if you have registered the product (and thus presumably received AMG login details)? If this is the case, it would explain why there is no comms without a valid login details, but I would like to trial the software first.

As an aside for anyone reading this: the login details are sent plain text, so don't use any security sensitive username & password combinations!

-Tim

[Spoon]

Re: Problem getting AMG to work in Batch Ripper

GD3 never works for the trial, only AMG. AMG will only work if Reference is registered (for Batch Ripper in trial).

[journeyman]

Re: Problem getting AMG to work in Batch Ripper

In case my previous comments were unclear, I AM using a registered version of dBpoweramp and batch ripper acts exactly as described by Tim:

When either AMG or GD3 are selected as the only source the lookup fails instantly and there is no data sent (and I mean, not a single byte on the wire!), however when other sources such as freedb are selected there is all the usuall chatter I would expect to see.

So this is not an issue that is unique to the trial mode of the software.