|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 |
![]() Join Date: Mar 2010
Posts: 3
|
Batch Ripper and CD Ripper data different
Can anyone tell me why the metadata pulled down for an album from the same source is different in the batch ripper mode to the Cd ripper mode?
|
|
|
|
|
|
#2 |
|
Da Man
Join Date: Apr 2002
Posts: 19,396
|
Re: Batch Ripper and CD Ripper data different
You have AMG & GD3 enabled in both? in Batch Ripper GD3 is per lookup (like AMG) but comes with no free lookups.
|
|
|
|
|
|
#3 |
![]() Join Date: Mar 2010
Posts: 3
|
Re: Batch Ripper and CD Ripper data different
The weird thing was that using the same CD GD3 returned different metadata in the Batch Ripper to CD Ripper. In CD ripper, despite the fact that it shows as having 122 days of AMG lookups remaining, there was no AMG data found -but it found metadata for that disc in Batch Ripper. This is using the same PC & batch ripper taking settings from the CD ripper.
Hope you can help here. |
|
|
|
|
|
#4 |
|
Da Man
Join Date: Apr 2002
Posts: 19,396
|
Re: Batch Ripper and CD Ripper data different
If it is a classical disc this is right as CD Ripper subscribes to sonatadb, batch ripper does not.
|
|
|
|
|
|
#5 |
![]() Join Date: Mar 2010
Posts: 3
|
Re: Batch Ripper and CD Ripper data different
Yes it was a classical CD ... so is sonatadb part of the GD3 data?
|
|
|
|
|
|
#6 |
|
Da Man
Join Date: Apr 2002
Posts: 19,396
|
Re: Batch Ripper and CD Ripper data different
It is delivered through GD3 but is not part of it.
|
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
![]()