I have a CD in my collection that when I rip in Secure mode with C2 Error Pointers enabled results in an Inaccurate/Secure rip (multiple re-rips confirm the same CRC set). Which led me to believe it was probably different pressing.
I was messing around with settings because I wanted to see if I got the same CRC set when slowing down the drive. Turns out I cant do this for the 1st pass. I have to disable C2 Error Pointers and slow down the second pass. So I did.
To my surprise the rip (previously Inaccurate/Secure) started coming out Accurate!
I guess my question is, with C2 Error Pointers enabled, how is it possible that can DBPA report that an entire CD has ripped securely, with the same CRC set again and again, when they're obviously bad rips (they don't match the AccurateRip CRC despite being the same pressing - evidence is I can get an AccurateRip CRC match if I re-rip at low speed)?
I wish I could slow down the 1st pass while leaving C2 Error pointers enabled.
Drive is an Asus DRW-1814BLT, DBPA reports C2 support after testing.
I was messing around with settings because I wanted to see if I got the same CRC set when slowing down the drive. Turns out I cant do this for the 1st pass. I have to disable C2 Error Pointers and slow down the second pass. So I did.
To my surprise the rip (previously Inaccurate/Secure) started coming out Accurate!
I guess my question is, with C2 Error Pointers enabled, how is it possible that can DBPA report that an entire CD has ripped securely, with the same CRC set again and again, when they're obviously bad rips (they don't match the AccurateRip CRC despite being the same pressing - evidence is I can get an AccurateRip CRC match if I re-rip at low speed)?
I wish I could slow down the 1st pass while leaving C2 Error pointers enabled.
Drive is an Asus DRW-1814BLT, DBPA reports C2 support after testing.
Comment