write offset correction

2010-12-01 22:33:35

Hi to all,

A question to better clarify the "drive offset" and "drive offset correction". I'm interested about write offset.

For example:

for a Plextor drive,  it's reported a WRITE offset of -30.
Is it the "offset" or the "correct offset" ??

I think it should be simply  the offset.  Then if I use CUETools to correct the offset before burning with PlexTools,
I must type +30 in the offset window to balance the -30 ??

It's correct the procedure ?? 

Many posts generate a litlle bit confusion...

Thank you in advance

write offset correction

Reply #1 – 2010-12-02 05:46:01

Tell CUE Tools to apply -30, though I believe PlexTools already compensates.  Either that or burn with EAC and enter -30 for the write samples offset.

write offset correction

Reply #2 – 2010-12-02 06:55:17

Thanks


Ok, I must apply -30 in CUETools, but I don't understand if -30 is the "write offset" or " to correct the write offset".

How can I know if PlexTools has inside the correction of write offset, or what can I do to setup PlexTools for the write offset
instead of using CUETools ??

Thanks again   

write offset correction

Reply #3 – 2010-12-02 09:39:49

Don't worry about the verbage; -30 is the number you need to compensate for your burner's offset for either EAC as the burning application or for CUETools to be used in concert with a burning program that does not compensate.  IIRC, PlexTools just does it automatically based on internal data stored for the drive, in which case you don't need to offset the data prior to burning.

You can always burn a CD-RW and then perform a sample-wise comparison of any track except for the last one ripped from both the original and the copy to verify that there is no shift in offset.  The last track may differ because Plextor drives cannot overwrite.  In the case of Plextools, it will actually add an additional frame to the end of the last track if it turns out that the last 30 samples are non-null.