Offset correction without liability to install AccurateRip would be nice. This to receive absolutely bit-identical rips, also for blank space at the begin and the end of a track.
Greez
Paesc
Last edited by paesc on 18-08-2007 at 23:39
Sorry, I don't understand that... To disable AccurateRip, either disable "Use AccurateRip with this drive" or just delete the AccurateRip DLL from the EAC folder...
Of course you can extract "blank" space (silence) at the begin and the end of tracks!?
cu, Andre
I don't use AccurateRip actually and I did never use it. What I like to say is, that it would be nice if EAC in future can detect the Offset correction its self (without AccurateRip), for example still by installing EAC and the drive properties.
This, because some drives have a great difference in positioning the laser. I had this problems sometimes with my old drive Pioneer DVR-109. For good calibrated drives, Offset correction is not a must, but nice to have absolutely bit-identical copies, so that the empty space at the end and the begin is equal to zero (no difference, even not 1/44100).
Do you understand now what I mean?
Greez
Paesc
EAC has auto-detection of the offset built-in. But the reference CDs are far less than those that can be used by the AccurateRip.dll.
You can either look up your drive's offset from the AR database using your web browser (http://www.accuraterip.com/driveoffsets.htm) or use AccurateRip.dll just for auto-detection and write down the offset (it will vanish once your've removed the dll) and then use that correction value in EAC's settings.
I don't really see what the problem is. It's not like EAC doesn't support offset correction without AR...
...not to mention this person seems to think offsets create unwanted silence between tracks. This isn't true, of course.
@Lund: thank you for your notes. So offset correction can easily done on myself. Do you mean in EAC the point "EAC - Drive Options... - Offset / Speed"? I didn't know about that... Sorry! Since a short time I'm discovering, what "tuning" or improving ist possible with EAC - so of course EAC can more than just rip like every other programm. Until yet, I only heard about AccurateRip for detect the offset correction.
So are both methods, AccurateRip and offset with EAC, equal precise? If yes, so I prefer the EAC way and will not use AccurateRip for auto-detection.
No, of course "this person" don't thinks offsets create unwanted silence between tracks! How did you came to this, is it written anywhere? He - this person - just wanted to have bit-identical copies - precisely to 1/44100, if possible. THEN we can speak of an exact 1:1-copy, like the name of the programm, exactaudiocopy, sais. Didn't you read that this person had problems with his Pioneer DVR-109? When you are saying something about other persons, so first read exactly what they had written...
Greez
Paesc
"...seems to think..."
I'm happy I was wrong. Perhaps you might see how I got this impression...
For copies that are not offset from the original, it is the combined offset of the reader and the write that matters. Depending on your drive you may not even need to configure any offset corrections for this to happen. If you're so concerned about "empty space" maybe you should find a reader that is able to overread as well as a writer that is able to overwrite.
Ok, thanks. Let's forget the misunderstanding. I know that normally the offset isn't great, but it may happen. The less offset differences appear, the better results you got... My old Pioneer DVR-109 had sometimes problems... Actually, I am happy with my both drives Plextor PlexWriter Premium2 and Plextor PX-716SA. But to test them would be nice.
Greez
Paesc
Can I fairly trust to the values in the database of AccurateRip and the EAC offset correction? I think about fluctuations in production of the drives. Or can I be shure the variations of the drives are less than the correction of the offset causes?
Have both database, the one in EAC and the one of AccurateRip, the same quality for the offset correction?
Greez
Paesc
AFAIK there's no such thing as a fluctuation on a drive to drive basis. The offsets will always be correct for the same models, and most often for several generations of models, too, as you can easily see in the list of drive models.
I don't know the exact technological reason for this tho. I guess the same controller chip and laser pickup system is all that it takes to get consistent offsets for the drives.
This thread is quickly going off-topic.
Wishlist Item:
Please restore the Constant Bit Rate options for WMA Encoding that were present in the 0.95 versions. It was very convenient to have them show up in the drop down menu once you chose the Microsoft WMA9 Encoder. I don't see a reason why they were removed, even if VBR is a better way to encode. I own two devices that will not play VBR files, so I still need the CBR option. Thanks.
Last edited by X-ray Doc on 22-08-2007 at 20:10 Reason: Left out word.
I ripped 40 CDs and saved them as wav files in a dir tree like this:
c:\rips
--|artist a
----|album 1
----|album2
--|artist b
--|artist c
----|album 1
I would like to have an option to mass encode all wav files in c:\rips and all subdirectories.
I think this function should have:
-- options to save the compressed file to the same directory as the wav file or to automatically create a subdirectory under the wav directory, such as:
c:\rips
--|artist a
----|album 1 <-- wav files here
------|MP3 <-- optionally auto-created subdirectory
-- and option to look for an existing compressed file of the same type and skip re-compression if it exists. [this is so that only newly added wav files are compressed.]
If such a power already exists in EAC, my wish is that i knew how to do it![]()
Last edited by bugMagnet on 23-08-2007 at 11:21
Lesezeichen