Tweet
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:
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
Comment