When there is only a single AR entry and it doesn't match?

2019-06-30 16:13:40

Since there was only one other entry in the AR database anyone know what to make of this? Track 18 is the one showing as inaccurately ripped and track 19 is the one that differs in samples in CTDB. The CD is visually pristine.

These rips were made on two different computers, one using EAC test and copy secure (drive offset is correct), the other with dbpoweramp secure. They were made within an hour of each other and neither have submitted results to AR yet, I just leave that as the default every 30 days.

I'm just wondering if I should just leave this rip alone since the checksums from dbpoweramp and EAC match? Or any other suggestions?

EAC:

Code: [Select]

Track 18

     Filename C:\dnmd\18 - Etudes - Etude 3.wav

     Peak level 21.7 %
     Extraction speed 1.7 X
     Track quality 100.0 %
     Test CRC 1F4A735F
     Copy CRC 1F4A735F
     Cannot be verified as accurate (confidence 1)  [96AD6A76], AccurateRip returned [84E64F44]  (AR v2)
     Copy OK

Track 19

     Filename C:\dnmd\19 - Etudes - Etude 4 (Variation III).wav

     Peak level 47.9 %
     Extraction speed 1.0 X
     Track quality 99.8 %
     Test CRC B6174D46
     Copy CRC B6174D46
     Accurately ripped (confidence 1)  [A1D8FEE7]  (AR v2)
     Copy OK

31 track(s) accurately ripped
 1 track(s) could not be verified as accurate

Some tracks could not be verified as accurate

No errors occurred

End of status report

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: NxlCb.6DguEYWcLN3LCVKSInWpA-] found
Submit result: NxlCb.6DguEYWcLN3LCVKSInWpA- has been uploaded
Track | CTDB Status
  1   | (1/1) Accurately ripped
  2   | (1/1) Accurately ripped
  3   | (1/1) Accurately ripped
  4   | (1/1) Accurately ripped
  5   | (1/1) Accurately ripped
  6   | (1/1) Accurately ripped
  7   | (1/1) Accurately ripped
  8   | (1/1) Accurately ripped
  9   | (1/1) Accurately ripped
 10   | (1/1) Accurately ripped
 11   | (1/1) Accurately ripped
 12   | (1/1) Accurately ripped
 13   | (1/1) Accurately ripped
 14   | (1/1) Accurately ripped
 15   | (1/1) Accurately ripped
 16   | (1/1) Accurately ripped
 17   | (1/1) Accurately ripped
 18   | (1/1) Accurately ripped
 19   | (1/1) Differs in 24 samples @00:25:57-00:25:58,00:28:11
 20   | (1/1) Accurately ripped
 21   | (1/1) Accurately ripped
 22   | (1/1) Accurately ripped
 23   | (1/1) Accurately ripped
 24   | (1/1) Accurately ripped
 25   | (1/1) Accurately ripped
 26   | (1/1) Accurately ripped
 27   | (1/1) Accurately ripped
 28   | (1/1) Accurately ripped
 29   | (1/1) Accurately ripped
 30   | (1/1) Accurately ripped
 31   | (1/1) Accurately ripped
 32   | (1/1) Accurately ripped
If you are sure that your rip contains errors, you can use CUETools to repair it.

dbpoweramp:

Code: [Select]

Track 18:  Ripped LBA 174483 to 180553 (1:20) in 0:17. Filename: C:\dnmdrip\Etudes symphoniques, Kinderszenen, Blumenstück\18 - Etudes - Etude 3._
  AccurateRip: Inaccurate (confidence 1)   Secure  [Pass 1 & 2, Ultra 1 to 2]
  CRC32: 1F4A735F     AccurateRip CRC: 96AD6A76 (CRCv2)     [DiscID: 032-0048f659-0696e05a-e610c820-18]

Track 19:  Ripped LBA 180553 to 184610 (0:54) in 0:02. Filename: C:\dnmdrip\Etudes symphoniques, Kinderszenen, Blumenstück\19 - Etudes - Etude 4 (Variation III)._
  AccurateRip: Accurate (confidence 1)     [Pass 1]
  CRC32: B6174D46     AccurateRip CRC: A1D8FEE7 (CRCv2)     [DiscID: 032-0048f659-0696e05a-e610c820-19]
  AccurateRip Verified Confidence 1 [CRCv2 a1d8fee7]

Re: When there is only a single AR entry and it doesn't match?

Reply #1 – 2019-06-30 23:48:49

If you didn't notice any problems while listening, you should keep what have and perhaps check the databases later for confirmation from additional submissions (that aren't your own).
It may take some time. That existing entry in CTDB was from December 2015.

Edit: removed edit