Ripping errors and AccurateRip

[Mark Scanlan]

Have tried ripping with EAC quite a number of what look to be CDs in excellent condition, only to get errors reported by AccurateRip. I am using the drive on my Dell laptop. Assuming I get access to a PC, is there a CD burner that is going to perform better than my laptop that I should be using instead?

Cheers
Mark

[Mark Lanctot]

Laptop drives are pretty bad, at least the one in my laptop is.

However, is it reporting errors on every track? If so, the drive may be improperly configured, or you might have a different (regional) pressing of the CD in the AccurateRip database.

If it's reporting accurate on some tracks and not on others then yes, it's the drive.

[haunyack]

Have tried ripping with EAC quite a number of what look to be CDs in excellent condition, only to get errors reported by AccurateRip. I am using the drive on my Dell laptop. Assuming I get access to a PC, is there a CD burner that is going to perform better than my laptop that I should be using instead?

Cheers
Mark

Perhaps the read sample offset correction has not been set for this drive?

.

[Mark Scanlan]

Perhaps the read sample offset correction has not been set for this drive?

.

Offset is OK - I have checked. It rips most tracks OK, but on average 1 per disc not. I gather there are CD drives that run over bad sections of CD many times and maximise your chance of getting a good rip, but don't know what they are ... can any anyone advise about this?

Cheers
Mark

[Mark Lanctot]

It rips most tracks OK, but on average 1 per disc not.

Yup, that's the drive.

Do you have access to a desktop? Most 3.5" drives in desktops perform better than the 2.5" drives in laptops.

As for which brand, you'll hear all sorts of recommendations, but I'm just using two randomly-chosen drives and they both work pretty well, better than the laptop drive definitely.

[Wombat]

If you have configured your drive using C2 error correction uncheck it and only use the accuratestream feature.
Just an idea. EAC unluckily detects C2 and uses it as default even if in most drives the implementation is buggy.
Would be nice to compare the results "if" this is like i think.