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: Doing drive offset correction by hand (Read 8685 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Doing drive offset correction by hand

For sometimes ago, I have some EAC ripa that are not offest corrected, such as my drive has +99 correction, Is it possible for me to move the samples in the wav file 99 samples (which way should I move as well?) to be offset corrected?

Doing drive offset correction by hand

Reply #1 –
I experimented with that only a few days ago. Here is screenshot of two files in Wavelab. The file on the bottom is ripped without an offset correction and the file on the top is ripped using a +102 correction in EAC (which is right for the used drive).



102 samples is about 2.32 ms, which I was able to verify with Wavelab.

So if your correction should have been +99 and you ripped without any correction you would need to remove 99 samples from the beginning of the file and add 99 samples to the end.

I tried find a sample accurate tool for making the fix in Wavelab or Audition, but I found only tools for changing the file durations and clip positions on the timeline in time units. Possibly I could have done that by cutting and pasting but that would have been a tedius trial and error task.

My solution was to mount the wave file & cue with Alcohol 120% and rip the mounted disc image using a +102 correction. I verified the resulting wave & cue image by burning it to a CD-RW with EAC (using the right write sample offset value) and ripping it again with a physical drive (using the right read sample offset correction). This rip passed the Accurate Rip test with a good confidence.

Doing drive offset correction by hand

Reply #2 –
Very good answer
My correction is same as yours!!
What I 'm looking for is a small tool that can help me to be lazy, just type in +102 or +99, even more, automatically lookup the drive offset from google and to the samples add/remove

Can someone compile a tool like this? Sounds easy but useful.

Doing drive offset correction by hand

Reply #3 –
If you have a cuesheet or can make one, you can use CUE Tools to do it (write offset is configurable in Advanced Settings).

Doing drive offset correction by hand

Reply #5 –
Moitah is great  , but is it possible to embeed a small table file of drives offset (.ini, .txt)or Google it out within the cuetool?

Doing drive offset correction by hand

Reply #6 –
Quote from: martin2048 on
Moitah is great  , but is it possible to embeed a small table file of drives offset (.ini, .txt)or Google it out within the cuetool?
Google's not necessary anymore for that. Use AccurateRip's drive database: http://www.accuraterip.com/driveoffsets.htm

PS: Just use the the values as is, for example you don't have to switch the algebraic prefix.

Also note that you can check the result with ARCue.pl in case it's a single WAV. Alternatively you can mount the WAV+CUE with something like DaemonTools and use a AccurateRip capable ripper of your choice. The disc still has to be in their database tho, and be the same pressing, so even if the offset conversion was correct you still need some luck to verify it with AR.

Doing drive offset correction by hand

Reply #7 –
Cue Tools seems to be a very nice application. Its "write offset" option works fine. I had downloaded a couple of versions, but I never had time to actually try it before now.

Quote from: Fandango on
Alternatively you can mount the WAV+CUE with something like DaemonTools and use a AccurateRip capable ripper of your choice. The disc still has to be in their database tho, and be the same pressing, so even if the offset conversion was correct you still need some luck to verify it with AR.

That may not work without burning a CD because also the drive (and its offset value) has to be in the database before AR can be used.

Doing drive offset correction by hand

Reply #8 –
Quote from: Alex B on
the drive (and its offset value) has to be in the database before AR can be used

This is not true

Doing drive offset correction by hand

Reply #9 –
Quote from: greynol on
Quote from: Alex B on
the drive (and its offset value) has to be in the database before AR can be used

This is not true

I had the impression that AccurateRip stores the drive specs to the DB after three key discs are succesfully scanned and the drive offset is verified.

A virtual drive has an offset correction value of 0. I don't know if this causes the problem, but I have not been able to configure AR with my mounted disc images (which are accurately ripped from physical CDs).

At first EAC 0.99b3's AR window reports that the mounted disc is a key disc that can be used, but when I try to proceed it seems to always return this warning:
Code: [Select]
This Key Disc cannot be used for offset detection (it does not match the one stored in AccurateRip's database), please try a different Key Disc.


The AR option stays greyed out until the drive (the virtual drive in this case) is properly configured.

Perhaps I just should try other disc images until I finally find the correct ones. It is quite tedious because first I need to decompress my lossless files and then mount and test them one by one.

Doing drive offset correction by hand

Reply #10 –
Quote from: Alex B on
I had the impression that AccurateRip stores the drive specs to the DB after three key discs are succesfully scanned and the drive offset is verified.
This is more or less correct, but doesn't mean that a drive must be in the database before it can be used.

Quote from: Alex B on
A virtual drive has an offset correction value of 0. I don't know if this causes the problem, but I have not been able to configure AR with my mounted disc images (which are accurately ripped from physical CDs).  At first EAC 0.99b3's AR window reports that the mounted disc is a key disc that can be used, but when I try to proceed it seems to always return this warning:
Code: [Select]
This Key Disc cannot be used for offset detection (it does not match the one stored in AccurateRip's database), please try a different Key Disc.
The offset correction value of 0 has nothing to do with it.  In fact, there quite a few drives in the database with a read offset correction of 0.  Instead, this is probably because more than one pressing of your key disc exists in the database combined with your virtual drive probably not legitimately existing in the database.
 

Doing drive offset correction by hand

Reply #11 –
Quote from: Moitah on
If you have a cuesheet or can make one, you can use CUE Tools to do it (write offset is configurable in Advanced Settings).


My CDs have been ripped so, that each FLAC file contains one song. I would like to use CUE Tools just to fix the offset. Is there a way I could generate the CUE sheets so that the offset correction could be accomplished?