Tweet
I could not get a secure rip after enabling "C2 Error Pointers for Error Detection"; yes, my drive passed the "detect C2 support". When visiting www.daefeatures.co.uk to verify my CD drive supports C2 errors, this web site also confirms "yes".
On several almost perfectly mint condtion CDs, while ripping, 100's of frames per track would have errors and 3-4 min tracks would take over 15 minute/track to try to re-rip the erroneous frame; obviously this will make ripping prohibitive due to the enormous time required.
I have now unchecked "C2 Error Pointers for Error Detection" and these same CD's rip fine in 6-8 minutes and claim Accurate (65), Accurate (64), etc. per track under Rip Status.
Looking @ the extraction log, this states Accurate (Confidence 65), etc.
How confident can I be that what I'm ripping is 100% secure with C2 Error Pointers unchecked but it appears to pass the AccurateRip standard (or so I think, is 65 or 66 good enough?). What does Confidence 65 <Accurate (65)> mean?
On several almost perfectly mint condtion CDs, while ripping, 100's of frames per track would have errors and 3-4 min tracks would take over 15 minute/track to try to re-rip the erroneous frame; obviously this will make ripping prohibitive due to the enormous time required.
I have now unchecked "C2 Error Pointers for Error Detection" and these same CD's rip fine in 6-8 minutes and claim Accurate (65), Accurate (64), etc. per track under Rip Status.
Looking @ the extraction log, this states Accurate (Confidence 65), etc.
How confident can I be that what I'm ripping is 100% secure with C2 Error Pointers unchecked but it appears to pass the AccurateRip standard (or so I think, is 65 or 66 good enough?). What does Confidence 65 <Accurate (65)> mean?
Comment