I seem to be having some problems with my drive reporting a C2 error where there is in fact no error present.
A CD can be ripped in burst mode and be verified as accurate by AccurateRip with high confidence. When I rip the same CD in secure mode, some tracks get an additional "Ultra Secure" pass because (I assume) the first pass had C2 errors reported by the drive.
The issue seems to be that the ripper does not compare the rip with AccurateRip if the track had C2 errors, is this true?
I know this is not a problem with dMC, but rather my hardware (though I was under the impression that Plextors had a rather good C2 implementation).
However, if the ripper strategy was to always compare with AccurateRip regardless of reported C2 errors some time and drive wear could be saved.
Maybe a suggestion for a future version?
Regards,
Peter
A CD can be ripped in burst mode and be verified as accurate by AccurateRip with high confidence. When I rip the same CD in secure mode, some tracks get an additional "Ultra Secure" pass because (I assume) the first pass had C2 errors reported by the drive.
The issue seems to be that the ripper does not compare the rip with AccurateRip if the track had C2 errors, is this true?
I know this is not a problem with dMC, but rather my hardware (though I was under the impression that Plextors had a rather good C2 implementation).
However, if the ripper strategy was to always compare with AccurateRip regardless of reported C2 errors some time and drive wear could be saved.
Maybe a suggestion for a future version?
Regards,
Peter
Comment