I wonder whether there is a CD/DVD-ROM drive database including overread capabilities that's big enough to have my drive included. It's a NEC 3500.

Fandango - You can test it yourself. -Start EAC and place any original cd into your drive. Then do the offset test and only pay attention to the overreading part of the test. It dosent matter if the cd is a reference disc or not, because we are only going to check for the overreading capabilities of your drive and not the offset correction value. Just make sure to use an original cd and not an cdr. -Martin.

Are you talking about the "Detect read sample offset correction..." button? Mine's greyed out. Is that due to accuraterip?

Thanks!

Answered my own question, moving/renaming AccurateRip.dll let's you change this.

And when I do so how do I see whether my drives are able to read into lead-in or/and lead-out? EAC doesn't tell you that. You have to do some more to be sure...

I have seen a tutorial that describe a long and painful method with comaparing ripped wavs and so on "all by hand", seriously I don't got the nerves to do that. I always get very impatient when reading, writing, ripping and pushing around ~400-500MB big files takes longer than 10 seconds. So I was asking whether anyone knows if a drive database with lead-in and lead-out capabilities exist.

I already did some testing based on CRC values, but I need a CD that has data at the beginning and at the end instead of null samples. Finding such a CD among my collection would take some time, too.

The actual reason why I want to know my drives capabilities is that I have found out that ripping some CD creates an identical copy on both my drives (Toshiba SD-M1612 and NEC ND-3500A) and other CDs always come out as not identical no matter what EAC options I change. So I experimented a bit with the read into lead-in/out option of EAC a bit, without much success. Either it made no difference with some CDs, or the in case of my Toshiba drive other CDs gave me read sync errors towards the end of the rip. The Toshiba has a positive offset and the NEC a negative one, so I assume that's the cause. Actually I was a bit surprised, because I thought with corrected offsets CD copies are identical with every drive (except for some rare CDs that have data in the lead-in/out). Well, some CDs (e.g. Matching Mole/self-titled) are OK, both drives produced the same wavs (needed to switch off C2 with the Toshiba tho), but most CD rips won't work out as being identical.

Again, the fact that most CDs won't be identical when ripped with both my drives really surprised me. I thought this is what the offset correction was all about! I use Accurate Rip and before that my offset correction values where correct, too. I never thought that it wasn't so important anyway. Well, either I messed up some settings, or I use a rip method (img+cue) that is being widely mistaken for producing 1:1 copies or most likely, identical copies from different drives aren't possible anyway, never were and won't ever be.

What wonders me in the latter case is, why all this fuzz about offset correction when it is useless? The only 1:1 copies I can do are those I rip and burn with the same drive, my NEC writer. Well, I thought the possiblity to make a 1:1 copy when ripping and burning with different drives is why offset correction was impleted? Why doesn't it work with a SD-M1612 and a ND-3500A? Is one of them bugged? So whats the point in using offset correction anyway, when 1:1 copies only work when you rip and burn a CD with the same drive, but won't work when you use different drives for both things? I think I should do some Accurate Rips with some Key CDs... maybe this will give me some clues... but I bet that both my drives will pass the test just fine...

Seems I'm loosing my faith in EAC... that project is dead anyway. And the source code is closed. Pretty bad. And a pitty, it's such a useful tool, but it needs a rework. Not saying this because of my probs with it but because I think it's time for a new version. I hate it when such a good program abandoned by its developer is locked away, because it isn't open source...

Fandango - The method i have told you does indeed tell you wether or not your drive can overread into the pregap/lead-out! -And the EAC project is not dead. Andre is working on a new version. -Martin.

I must have missed that... maybe because my drives aren't capable of overreading and any overreading capability reports are omitted in that case? Hmm, got to remove the accurate rip dll... I'll be back

EDIT: Ok, now I see it. The first field... actually I never used the auto-detect, because I don't have a single CD that is in this database. That's why I switched to Accurate Rip, at least I have some of their Key CDs. Before that I entered the offset corrections manually, took them from an online database.

So is this detection really accurate? It says NONE, but I mean it only takes a second, and I seriously doubt that EAC tries to overread the last and first track within that time. This detection is of no use for me, I think I need a CD that is in EAC's database for the detection to actually start, right? Sorry, I don't have such a CD. What now?



Is he alone btw? No wonder it takes over a year for the next version...

The test is accurate. It will only take about a second and you can use any original cd. It has been confirmed by Andre. And he is alone...