AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

[HeyItsTodd]

Drive: HL-DT-ST DVDRAM GH24NSC0
In Database: Yes


This drive was removed from a computer after the motherboard died. It had been used for YEARS with dbPowerAmp / CD Ripper. It was placed into a newly built computer. It is detected as the same model it was previously, and is in the database (see attached image).

Now, after over 50 CD's, I have a ton which generate the message

"This Key Disc cannot be used for offset detection it does not match the AccurateRip stored disc, or your drive does not exist in AccurateRip and this disc has multiple pressings stored. Please try a different Key Disc."

I have exactly one which generates the message

"AccurateRip needs to verify the offset generated , for this it needs 3 Key Discs that give the same offset, please insert another 'Key Disc'. [Calculated offset value: +16 samples, +64 bytes. ]"

I guess that means I need two more sacred discs to finish verification?


I am running Windows 11 Pro, updated to today.
I am using CDGRAB.EXE v 16.6.0.2 with elevated administrator privileges (the Windows account is a user account). The application successfully pulls down Artist/Track info, so it is not blocked by the Windows firewall.


This is the same physical drive using CD's which it has successfully ripped before, using Secure Mode and AccurateRip. What on earth is going on? I have gotten great value out of this program over the years, but this is taking all of the joy out of the process. What can I do to get the damn thing to run the way it did previously?

[Dat Ei]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

Keep feeding CDs! The drive has to be verified and recognized on your new computer. Therefore dBpa needs to read three key discs.

Dat Ei

[HeyItsTodd]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

I'm probably screwed - I went digital around 2003 and have very few discs from later than that. I did NOT have to go through this in previous installations.

[HeyItsTodd]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

This is asinine. I have tried 250 CD's. The best I can do is get three discs to get to the configuration stage



I repeat that this drive was used with this version of CD Ripper with these CD's. What the hell is going on?

[Spoon]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

Your sample offset +16 does not match the +6 of the 800 or so people who have this drive, your drive perhaps has a problem.

[HeyItsTodd]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

I find this coincidental failure odd - the drive was removed from one case and placed in the other, with no down time to collect dust, get dropped, etc. It is now in a much faster machine (from 13-year old AMD chip to an AMD Ryzen 7 7700x chip). The cabling is new and from a quality company. I've spent more than enough time fighting it, and will now go ahead and buy a replacement after scanning the compatibility database.

Thanks for taking the time to reply.

[GBrown]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

I find this coincidental failure odd - the drive was removed from one case and placed in the other, with no down time to collect dust, get dropped, etc. It is now in a much faster machine (from 13-year old AMD chip to an AMD Ryzen 7 7700x chip). The cabling is new and from a quality company. I've spent more than enough time fighting it, and will now go ahead and buy a replacement after scanning the compatibility database.

A 13 year old optical drive that has been used to rip a lot of CDs is likely past it's prime. They definitely have a limited lifespan. If you had some troublesome discs that dBPoweramp or other software had to do a deep dive to try and rip the data, it can shorten this further. I have a couple of drives and find I have to replace them every 4-5 years max.

[Spoon]

Re: AccurateRip - AYFKM? 50+ discs and still no "Key Disc"?

EAC uses the same DLLs as dBpoweramp, even manually setting the offset would not use AccurateRip on Windows, it has to key.