illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

c2 corner cases

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • inphobia

    • Apr 2025
    • 32

    #1

    c2 corner cases

    after testing error detection on 30 drives or so i have 2 corner cases i'd like some advise on.

    i have a cd with actual bitrot that i use for the "detect c2 support" option. after the detection is done i will also rip the cd (if no c2 support is detected i enable it manually for this one rip). i will then check the detailed rip log to see if and on which frames it detected the c2 errors. the results of the "detect" function are correct except for 2 drives:

    HL-DT-ST DVD-ROM DH10N firmware 0F05:
    the detect function said c2 was not supported, however when ripping the bitrotted cd it did detecf c2 errors on the frames that are corrupted

    PLDS DVD+-RW DH-16ABS firmware PD11:
    detect feature instantly (under 5 seconds) returns c2 supported. the manual states "noting if a c2 pointer error is signaled right at the start then the cd drive might not be compatible". ripping the bitrotted disc does give c2 errors on the problematic frames.

    i realize not everyone has actual bitrotted discs and a bunch of drives to test on making this a non issue for most users.

    however, for clarity, which result is most trustworthy? since an actual rip detected c2 errors on the expected frames i would trust that over the detect feature's result. or does the detect feature has a different way to check for c2 support compared to actual ripping?

    secure rip settings used:
    Code:
    Pass 1 Drive Speed: Max, Pass 2 Drive Speed: Max
    Ultra:: Vary Drive Speed: No, Min Passes: 1, Max Passes: 2, Finish After Clean Passes: 1
    Bad Sector Re-rip:: Drive Speed: Max, Maximum Re-reads: 3​
  • Spoon
    Administrator
    • Apr 2002
    • 45363

    #2
    The detection routine rips the same as ripping with c2 enabled, so it relies on the drive returning c2 data.
    Spoon
    www.dbpoweramp.com

    Comment

    • inphobia

      • Apr 2025
      • 32

      #3
      i suspected as much.

      still, this drive did not detect c2 features with this disc, while it did detect the errors when ripping:

      Code:
      Drive & Settings
      ----------------
      
      Ripping with drive 'F: [HL-DT-ST - DVD-ROM DH10N ]', Drive offset: 102, Overread Lead-in/out: No
      AccurateRip: Active, Using C2: Yes, Cache: 256 KB, FUA Cache Invalidate: No
      Pass 1 Drive Speed: Max, Pass 2 Drive Speed: Max
      Ultra:: Vary Drive Speed: No, Min Passes: 1, Max Passes: 2, Finish After Clean Passes: 1
      Bad Sector Re-rip:: Drive Speed: Max, Maximum Re-reads: 3
      
      Track 12:  Ripped LBA 200227 to 221882 (4:48) in 0:25. Filename: C:\temp\rip\x-calibrate\Sol_Invictus\Let_Us_Prey\12_-_The_Killing_Tide.flac
        AccurateRip: Inaccurate (confidence 5)   Insecure  [Pass 1, Ultra 1 to 1, Re-Rip 29 Frames]
        CRC32: A948FDD3     AccurateRip CRC: 07FAB8DC (CRCv2)     [DiscID: 012-0016205b-00cdb894-950b8e0c-12]
        ** Reached Maximum 2 Unrecoverable Frames For This Track
          Re-rip Frame: 203044 (00:00:37,560) matched 10 / 11
          Re-rip Frame: 212409 (00:02:42,426). Insecure  (c2 dropped 10)
          Re-rip Frame: 212410 (00:02:42,440)


      the disc itself has plenty of errors as you can see from this drive:

      Code:
      Ripping with drive 'D: [ATAPI - DVD A DH16ABSH ]', Drive offset: 6, Overread Lead-in/out: No
      AccurateRip: Active, Using C2: Yes, Cache: 1536 KB, FUA Cache Invalidate: No
      Pass 1 Drive Speed: Max, Pass 2 Drive Speed: Max
      Ultra:: Vary Drive Speed: No, Min Passes: 1, Max Passes: 2, Finish After Clean Passes: 1
      Bad Sector Re-rip:: Drive Speed: Max, Maximum Re-reads: 3​
      
      Track 12: Ripped LBA 200227 to 221882 (4:48) in 0:51. Filename: C:\temp\rip\x-calibrate\Sol_Invictus\Let_Us_Prey\12_-_The_Killing_Tide.flac
      AccurateRip: Inaccurate (confidence 5) Insecure [Pass 1, Ultra 1 to 1, Re-Rip 17 Frames]
      CRC32: 2A05BBB1 AccurateRip CRC: E11F26DA (CRCv2) [DiscID: 012-0016205b-00cdb894-950b8e0c-12]
      ** Reached Maximum 2 Unrecoverable Frames For This Track
      Re-rip Frame: 207964 (00:01:43,160) matched 10 / 11
      Re-rip Frame: 212409 (00:02:42,426). Insecure (c2 dropped 4) [c2 best match]
      Re-rip Frame: 212410 (00:02:42,440). Insecure (c2 dropped 2) [c2 best match]
      Re-rip Frame: 212426 (00:02:42,653). Insecure (c2 dropped 2) [c2 best match]
      Re-rip Frame: 212461 (00:02:43,120). Insecure (c2 dropped 2) [c2 best match]
      Re-rip Frame: 212548 (00:02:44,280). Insecure (c2 dropped 6) [c2 best match]
      Re-rip Frame: 212549 (00:02:44,293). Insecure (c2 dropped 3) [c2 best match]
      Re-rip Frame: 212600 (00:02:44,973) matched 10 / 11
      Re-rip Frame: 212617 (00:02:45,200). Insecure (c2 dropped 9) [c2 best match]
      Re-rip Frame: 212618 (00:02:45,213). Insecure (c2 dropped 10)
      Re-rip Frame: 212635 (00:02:45,440)​
      (for cache size i use whatever cdripper says when clicking the "technical" link in settings)

      must have been a fluke....

      Comment

      Working...