title
Products            Buy            Support Forum            Professional            About            Codec Central
 

AccurateRip Verified Using Pressing Offset +6? (+possible bug)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • exec
    dBpoweramp Enthusiast

    • Dec 2007
    • 53

    AccurateRip Verified Using Pressing Offset +6? (+possible bug)

    Hi!

    I'm using dBpoweramp Release 14 and my ripping process looks something like this: When a CD can't be verified as accurate, I rip the same CD again using another drive and EAC (only test, no copy). Then I compare the CRCs and if these are the same, I assume that the rip is "pretty accurate".

    Now I've stumbled upon a case where I don't understand what dbp is trying to say me...
    CD is the bonus disc of Black Label Society's "Alcohol Fueled Brewtality". The first 4 tracks can't be verified as accurate, but so does the last track.

    Let's take a look at the logs (I'll skip the first 4 tracks as the logs say the same here):

    dbp:
    Code:
    dBpoweramp Release 14 Digital Audio Extraction Log from Dienstag, 22. März 2011 11:25 
    
    Drive & Settings
    ----------------
    Ripping with drive 'U:   [PLEXTOR  - DVDR   PX-708A  ]',  Drive offset: 30, Overread Lead-in/out: Yes
    AccurateRip: Active,  Using C2: Yes,  Cache: None,  FUA Cache Invalidate: Yes
    Pass 1 Drive Speed: Max,  Pass 2 Drive Speed: Max
    Ultra::  Vary Drive Speed: Yes,  Min Passes: 1,  Max Passes: 2,  Finish After Clean Passes: 1
    Bad Sector Re-rip::  Drive Speed: Max,  Maximum Re-reads: 60 
    
    Encoder: CLI Encoder -cli_encoder="C:\Program Files (x86)\FLAC\bin\flac.exe"
    -cli_cmd="-8 -V -f [infile] -o [outfile] -T {qt}ARTIST=[artist]{qt} -T
    {qt}ALBUM=[album]{qt} -T {qt}TITLE=[title]{qt} -T
    {qt}TRACKNUMBER=[track]{qt} -T {qt}GENRE=[genre]{qt} -T {qt}DATE=[year]{qt}
    " -nodbtag -hi_quality
    
    DSP Effects / Actions: -dspeffect1="HDCD=" 
    
    Extraction Log
    --------------
    
    Track 5:  Ripped LBA 88362 to 108583 (4:29) in 0:10. Filename: D:\Ripping\Black Label Society\Alcohol Fueled Brewtality\Disc 2\05. The Beginning... At Last.flac
      AccurateRip: Accurate (confidence 2)     [Pass 1]
      CRC32: 4BB83D74     AccurateRip CRC: 0FB355E7     [DiscID: 005-0004f4bf-00175550-4105a705-5]
      AccurateRip Verified Using Pressing Offset +6, Confidence 2 [old crc fb355e7] 
    
    -------------- 
    
    5 Tracks Ripped: 1 Accurate, 4 Secure
    And EAC:
    Code:
    EAC: Exact Audio Copy V1.0 beta 1 from 15. November 2010
    EAC extraction logfile from 22. March 2011, 23:36
    Black Label Society / Alcohol Fueled Brewtality
    Used drive  : PLEXTOR DVDR   PX-716A   Adapter: 1  ID: 1
    Read mode : Burst 
    
    Read offset correction                      : 30
    Overread into Lead-In and Lead-Out          : Yes
    Fill up missing offset samples with silence : Yes
    Delete leading and trailing silent blocks   : No
    Null samples used in CRC calculations       : Yes
    Used interface                              : Native Win32 interface for WinNT & 2000
    Gap handling                                : Not detected, thus appended to previous track 
    
    Performing a test extraction only  
    
    TOC of the extracted CD 
    
         Track |   Start  |  Length  | Start sector | End sector 
        ---------------------------------------------------------
            1  |  0:00.00 |  3:15.52 |         0    |    14676   
            2  |  3:15.52 |  7:00.26 |     14677    |    46202   
            3  | 10:16.03 |  4:36.71 |     46203    |    66973   
            4  | 14:52.74 |  4:45.13 |     66974    |    88361   
            5  | 19:38.12 |  4:29.46 |     88362    |   108582   
     
    Track  5 
    
         Filename D:\Ripping\Black Label Society\Alcohol Fueled Brewtality\Disc2\05. The Beginning... At Last.wav
         Peak level 80.3 %
         Extraction speed 26.6 X
         Test CRC 4BB83D74
         Cannot be verified as accurate (confidence 2)  [66D4340F], AccurateRip returned [0FB355E7]
         Copy OK 
    
    1 Track(s) nicht als akkurat verifiziert
    4 Track(s) nicht in der AccurateRip Datenbank vorhanden
    No tracks could be verified as accurate
    You may have a different pressing from the one(s) in the database
    No errors occurred
    End of status report
    Obviously, EAC calculates an "old" AR CRC whereas dbp uses a new AR CRC, which can the verified by AR. But what does ths "AccurateRip Verified Using Pressing Offset +6, Confidence 2 [old crc fb355e7]" mean?

    And the possible bug:
    Look at the "[old crc fb355e7]", which I assume is the old AR CRC. Compared to the CRC whcih was calculated by EAC, the leading zero is missing, isn't it?
  • Spoon
    Administrator
    • Apr 2002
    • 44582

    #2
    Re: AccurateRip Verified Using Pressing Offset +6? (+possible bug)

    It means another pressing of the CD was used to verify the rip, this other pressing has a +6 offset (regardless to your drive offset). EAC cannot check across pressings.
    Spoon
    www.dbpoweramp.com

    Comment

    • EliC
      dBpoweramp Guru

      • May 2004
      • 1175

      #3
      Re: AccurateRip Verified Using Pressing Offset +6? (+possible bug)

      Spoon, currently if there is only 1 entry for a certain pressing and other pressings has multiple entries, then the 1 entry does not show up. However, if the single pressing is cross-verified, will it show up?

      Comment

      • Spoon
        Administrator
        • Apr 2002
        • 44582

        #4
        Re: AccurateRip Verified Using Pressing Offset +6? (+possible bug)

        In R14.1 yes 4 results are listed from the best pressings
        Spoon
        www.dbpoweramp.com

        Comment

        • EliC
          dBpoweramp Guru

          • May 2004
          • 1175

          #5
          Re: AccurateRip Verified Using Pressing Offset +6? (+possible bug)

          My question had more to do with dropping single entries from the AR database. I was wondering if that has changed if that single entry is cross verified.

          As in the above example, the rip is accurate, as confirmed by cross pressing verification. However, since its only a single entry it would not currently show up as a match for another individual with the same pressing.

          Comment

          Working...

          ]]>