Help - Search - Members - Calendar
Full Version: Offset questions with EAC
Hydrogenaudio Forums > CD-R and Audio Hardware > CD Hardware/Software
audiomunky
Hello there. I have two questions, but first I'll give you my background. I'm using a Plextor 708A with EAC and AccurateRip installed and configured. AR calculated my offset to be +30 samples, and Plextools reports both my read and write offsets to be -120 bytes. I've ripped 20 or so CDs without error from either EAC or AR.

1.) I noticed in EAC that the drive options for my Plextor 708A were set to "Use combined read/write sample offset correction": 0. I looked through my logs of all my rips and noticed that it was set to this as well. I thought that EAC / AccurateRip set this value (by default) to "Use read sample offset correction." Could it be that when I ticked "Overread into Lead-In and Lead-Out," EAC automatically switched over to the combined setting? In any event, with the combined read/write offset correction set to 0 and overread on, are my rips still okay, or should I go back and re-rip with the read sample offset set to +30 and overread turned on?

2.) I'm trying to burn a copy of a CD that I ripped. I'm somewhat confused, though, with this "Use combined read/write sample offset correction" business. Should I put -30 under the Writer tab, or should I just put down 0 and use this "combined read/write sample offset correction?"

I hope this is somewhat clear. Please ask me if you need anymore clarification. Thank you for any and all help!

millennium2000
Hi audiomunky,
As you described you got AR installed and configured (my interpretation: you get an AR-report after ripping in EAC) which means you're ripping is done with a read-offset correction (of in your case +30), no matter what the log or the EAC screens tell you... This is a known flaw in older versions of EAC (don't know if it's really resolved in the new version) but it can easily be fixed... You should close EAC and temporarily remove/rename the accuraterip-dll in the EAC directory... Start EAC up, fill the correct settings manually (read offset correction: +30), close EAC, put the accurate rip dll back in the EAC directory and you're "problem" will be solved-> read-offset correction of +30 and greyed out (your logs of future rips will also show this value)...


And for the write offset-value; as you're rips were done with the correct read offset correction of +30 it's best to fill the write offset correction with -30...

If you can live with the fact that the logs of your rips sofar give "incorrect" information there is no need to redo your rips...

greetz,
Mill
greynol
QUOTE(millennium2000 @ Jul 19 2007, 15:26) *
(don't know if it's really resolved in the new version)

This has been fixed in V0.99pb1.
audiomunky
Thanks Mill and greynol, appreciate the help. I am using EAC 0.95b4 for reference. If it doesn't affect the rips, then why bother! biggrin.gif Just to make sure I got it: I'm not going to bother with the drive settings then if AR has them locked in correctly, but I will fill in -30 for the write samples offset correction under the Writer tab. Correct?

Also, should I consider upgrading to EAC 0.99pb1?

Much thanks again.
JensRex
QUOTE(audiomunky @ Jul 20 2007, 02:57) *
I will fill in -30 for the write samples offset correction under the Writer tab.
Not really. My old writer had a read offset of +700-something and a write offset of 6, so they aren't necessarily identical.
greynol
He's got a PX-708A, PlexTools reports a write offset as -120 bytes. The correct write samples offset as entered in EAC for this drive is -30. This is consistent with every report on a PX-708A I've ever seen (dozens), no question about it.

Come to think of it, every true Plextor writer I've ever seen has had a write samples offset of -30.
millennium2000
QUOTE(audiomunky @ Jul 20 2007, 02:57) *

Thanks Mill and greynol, appreciate the help. I am using EAC 0.95b4 for reference. If it doesn't affect the rips, then why bother! biggrin.gif Just to make sure I got it: I'm not going to bother with the drive settings then if AR has them locked in correctly, but I will fill in -30 for the write samples offset correction under the Writer tab. Correct?

Also, should I consider upgrading to EAC 0.99pb1?

Much thanks again.


As Greynol stated above, -30 is the correct write offset correction for your drive...

And about upgrading to EAC 0.99pb1 ? The new version has some neat features like AR-results indluded in the EAC-log, build-in Flac support the ability of T&C for Image ripping... The "ripping" engine hasn't changed though... If ripping seperate trachs is what you tend to do, as you already have your version of EAC setup to work with AR and manually flac support isn't that hard a task, I would stick to the old version for now..As can be read on this forum among other places, the new version has some "minor" flaws, which I trust will be fixed shortly. But till then maybe it's wisest to stick to the old version. FWIW; I have to instances of EAC installed, 0.99pb1 and 0.95b2 (in which you still can select the native TOC), but most of my ripping now is done with the new version...
audiomunky
Thanks to everyone for their advice!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.