wrong read offset using EAC, how bad is this? |
![]() ![]() |
wrong read offset using EAC, how bad is this? |
May 18 2005, 22:55
Post
#1
|
|
|
Group: Members Posts: 9 Joined: 18-May 05 Member No.: 22136 |
I just ripped a whole bunch of cd's using eac and have now discovered that the read offset I was using is wrong (long story) How does this affect if at all the quality of the rips and or wav files themselves? I tried searching on this topic and didn't find what I was looking for. Thanks in advance.
|
|
|
|
May 18 2005, 23:07
Post
#2
|
|
|
Moderator Group: Super Moderator Posts: 3934 Joined: 29-September 01 Member No.: 73 |
In themselves, the wavs are not affected at all in quality. It's a very small time shift of the data.
It affects their comparison with other wavs, or the comparison of their CRC (checksum given by EAC as an extra control of secureness). It will affect the comparison with the original if you want to burn an offset corrected copy. The data will be exactly the same, but shifted. Details in the FAQ of the forum, link at the top of this page. |
|
|
|
May 18 2005, 23:18
Post
#3
|
|
|
Group: Members Posts: 9 Joined: 18-May 05 Member No.: 22136 |
Thanks for the reply. I did read through those links in the faq but I didn't see anything that mentioned the consequences of using an incorrect offset. Thanks again.
QUOTE (Pio2001 @ May 18 2005, 10:07 PM) In themselves, the wavs are not affected at all in quality. It's a very small time shift of the data.
It affects their comparison with other wavs, or the comparison of their CRC (checksum given by EAC as an extra control of secureness). It will affect the comparison with the original if you want to burn an offset corrected copy. The data will be exactly the same, but shifted. Details in the FAQ of the forum, link at the top of this page. |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 24th May 2013 - 03:05 |