Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: EAC Drive Offset, resolving miss-match (Read 1391 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

EAC Drive Offset, resolving miss-match

Hi guys, longtime lurker, new community member here; I'm hoping to get some help in setting up my EAC correctly with a newly purchased drive that's giving me some grief.

I have used EAC in the past to good effect in making lossless backups (I'm happy to provide a copy of the guide I followed). However, I have a few discs in my collection that have given me grief with read and sync errors.

Due to their limited pressings, makes tracking down alternate copies rather hard. In researching this issue, I came across the following two blog posts:

https://john-millikin.com/%F0%9F%A4%94/why-i-ripped-the-same-cd-300-times
https://john-millikin.com/%F0%9F%A4%94/error-beneath-the-wavs

Therein, the author described using a "Two Sheep" to resolve his issue, with a list of drives found here:

https://web.archive.org/web/20050825194656/http://www.makeabackup.com/burners.html

In making a list of possible Two Sheep Burners I came across a factory sealed, brand new in box, ASUS CRW-5232AS with 1.0 firmware on eBay and purchased it for hopes of getting it to run.

Due to the older IDE connections the drive has, I purchased an IDE <-> SATA converter to allow the drive to work on my Windows 10 PC. However, in trying to setup the drive on that PC, I found the offset of it didn't match what was listed in the AccurateRip Drive Offset Database.

I figured that the offset may have been caused from the introduction of the converter, and as of this weekend, setup a Windows XP PC in order to eliminate that as a cause. In trying to setup EAC and AccurateRip in turn, I received the same error message, specifically as follows:

"AccurateRip will not key to this offset as it miss-matches the drive database offset.
 [Calculated offset value: -582 samples, -2328 bytes. ]"

In looking at AccurateRip Drive Database Offset, I found an interesting quirk, in that the CRW-5232AS is listed twice.

It is listed first, as "CRW-5232AS" (with a drive offset that matches my own), and secondly as "ASUS - CRW-5232AS", with a drive offset of +6 (which is what it's currently being seen as).

My question is, is it possible to setup my drive in a way that internally references / treats it as "CRW-5232AS" in order to for it to match this drive offset in the database, and thus key it to Accurate Rip?

Thanks so much, looking forward to figuring this problem out and getting it working with you guys, cheers!