Exact Audio Copy Guide (old)

vbimport

#1

If this is not in the correct place in the forum will a mod please move it .
As far as I can tell it was not copyrighted.
I hope this helps some people.I spent some time working on copying it so it could be posted here.
This is an old guide that used to be available on the internet but no longer is as far as I can tell.
I don’t take any credit for writing this guide.
There will be links & probably some references that do not work.

First of all, you need to make sure that you have access to all the options needed for configuring EAC for exact
copying.
Hit F9 or click the EAC menu and choose “EAC options”. Click the “Tools” tab and make sure that “Activate
beginner mode, disable all advanced features” is not checked. If you had to uncheck it, click “OK” in order to
make the advanced settings take effect, then open “EAC Options” again.
Then it’s time to start configuring the EAC options:
Click the “Extraction” tab:

EAC01. Extraction (Attachment here)

Important settings:
Fill up missing offset samples with silence: Checked.
When using offset correction (see 5c. Offset/Speed), without the drive being able to overread into lead-in/lead-out, this setting fills missing
samples with silence in order to maintain the correct track length. If it were left unchecked, the ripped file would be missing some samples,
and thus not be that close to an exact copy as we want it to be.
No use of null samples for CRC calculations: Unchecked.
This setting does not affect the files as such, it “just” affects how the CRC values are calculated, and thus written to the log. One of the
ways in which to verify that a FLAC file is un-altered from the original rip is to decompress it to .wav and use EAC to compare that .wav
file’s CRC value with the one reported in the log. The two should match up.
There is a relatively easy way to check if the CRC values for files match those stated in the log: decompress the FLAC files to .wav, then
use the “Process WAV” tool to inspect the CRC values. “Process WAV” calculates CRC values including null samples by default, though. It
means that you can not use the tool in order to check files that were ripped with the “No use of null samples for CRC calculations” option
checked. Also, leaving it unchecked is a common recommendation, so there is a greater chance that the CRC values will match other rips
(such as those stored in the Accurate Rip database) if you leave this unchecked.
If you have files that were ripped with this option checked (or if the CRC values do not match when you use “Process WAV” and you want
to check if the files were perhaps ripped with this option checked), there is a more cumbersome procedure for checking them. Burn the
files to a CD-R (preferably using EAC with the correct write offset value, see EAC CD Burning Guide). Leave the CD-R in the drive when it is
finished. Check the “No use of null samples for CRC calculations” checkbox, then select all the tracks and choose “Test Selected Tracks” in
the Action menu. This will show you the CRC values for the files, calculated without null samples. If they match the CRC values in the log,
the files are indeed un-altered, but were ripped with this option checked. Remember to uncheck the checkbox after you are done
testing the files!
Synchronize between tracks: Checked.
EAC will synchronize a track with a preceding track if there is no silence at the track junction, so track transitions will be free from jitter
artefacts (pops and clicks, e.g. on live recordings)
Delete leading and trailing silent blocks: Unchecked.
Checking this would mean changing the CD structure, which means that the copy would not be “exact”.
Error recovery: High.
Change to Medium for the current disc only if EAC really gets stuck while ripping tracks and performing error correction. Do not change to
Medium if EAC rips tracks very slowly while performing error correction - that’s normal, it is what EAC should do when there is a lot of error
correction to be done. To be sure, there is a trade-off between the Medium and High settings. Consistent errors are less likely to slip trough
with Medium error correction than with High, but correction of detected errors is more efficient using the High setting.
The rest of the settings:
Skip track extraction on read or sync errors: Your decision.
I would say that it is a good idea to check this if you aim for perfect rips. The rip will not be perfect anyway if there are read or sync errors
for one or more tracks, so you will save time by just getting the error reported without having EAC spend time trying to slowly rip the track
anyway. If there are errors, clean and/or repair the CD and try again, see (for example) advice here and here about how to repair
scratched CDs.
Skip track extraction after duration longer than: Your decision.
Setting this to some appropriate value (you will have to experiment to find out what is “appropriate” for you!) will make EAC skip the track
if error correction takes so long that you might suspect it will not be successful anyway. I have this set to 4x realtime for the Plextor drive
used for most of the screenshots in the guide. That still allows the drive to go quite slow during error correction, but makes EAC skip tracks
that I know (from experimenting) it will not manage to rip with matching test-and-copy CRC values even when allowed to spend ages trying
to do so.
After each: XX mins of extraction, cool down the drive for YY mins: Use only if necessary.
Lock drive tray during extraction: Your decision. Check it if you are prone to accidentally open drives in use.
Extraction and compression priority: Normal for most situations; Idle for old and slow computers; High for
computers with multi-core processors or multiple CPUs.
3b. General
None of these settings have any influence on ripping quality, so they are completely up to you. I recommend
this one, though:
On unknown CDs: automatically access online freedb database. Checked.
If the CD you are about to rip is in the database, the information will be automatically added in EAC.
(Attach EAC02 here)
Checking “Show status dialog after extraction” will make the pop-up status report mentioned in EAC Ripping
Guide, step 7 show up. If you leave this unchecked, you will not get that pop-up.
If you do not uncheck “Beep after extraction finished”, you will have EAC beeping (using the computer’s
internal speaker) after each track is competed.
Also, note that this is where you choose the language for the EAC interface.
EAC03. Tools
Automatically write status report after extraction: Checked. This will automatically create and save a log file.
Do not open external compressor window: Unchecked - it is useful to see if the external compressor is still
running after EAC has finished ripping to .wav.
Activate beginner mode, disable all advanced features: Unchecked (as mentioned before).
The rest of the settings:
Important: nothing checked here! If you normalize the tracks, they are changed, and your rip will not be a
truly exact copy of the CD.
(EAC04 here)
File (and folder) naming will be a matter of personal choice, so I merely provide a couple of examples in order
to illustrate how it works.
(EAC05 here)

Naming scheme example 1: %D - %Y - %C%N - %T
This naming scheme will make EAC create a directory (the part before the backslash) and file names (the part
after the backslash) looking like this:

Retrieve UPC/ISRC codes in CUE sheet generation: Your decision - appreciated by some, but does not influence
ripping quality in any way. Note, however, that the presence of these codes in a cue sheet can cause problems
as you try to use the cue sheet for burning a CD-R, see EAC CD Burning Guide.
UPC = Universal Product Code, printed as a barcode on the CD artwork. ISRC = International Standard Recording Code, read about it here.
Use CD-Text information in CUE sheet generation: Your decision.
Create ‘.m3u’ playlist on extraction: Your decision. If you use it, you may want to also check the sub-option
“Write .m3u playlist with extended information”.
On extraction, start external compressors queued in the background: Checked unless it causes problems.
Use only one compressor thread unless your computer has a multi-core processor or multiple CPUs. You can use as many compressor
threads as your computer has processors; two threads for a dual core processor, etc.
Submit drive features after detection: Your decision.


#2

(EAC06 here)
If you like, you can also add the file format to the folder name. Remember to change the naming scheme if you
create different profiles for ripping and compressing to different formats, such as FLAC and mp3 V0.
Naming scheme example 2: %D - %Y - %C [FLAC]%N - %T

  • results in this folder being called "Queen - 1975 - A Night At The Opera [FLAC]"
    Naming scheme example 3: %D - %Y - %C (V0)%N - %T
  • results in this folder being called "Queen - 1975 - A Night At The Opera (V0)"
    Naming scheme example 4: %N - %T
    This naming scheme results in file names (track number - title) only, no directory will be created. You need to
    manually put the tracks into a properly named folder after you have finished ripping. The advantage is that you
    will not have to edit the cue sheet after ripping, since the path to the files will not be included in the cue sheet
    if you do not make EAC create a directory for the files.
    The various artists naming scheme is only used if you check “Various Artists” in the main EAC window before
    ripping a CD, see EAC Ripping Guide - 2. CD Information (scroll down a little).
    Various Artists example 1: %C (%Y)%N - %A - %T
    This naming scheme will make EAC create a directory and file names looking like this:
    (EAC07 here)
    Various Artists example 2: %D - %Y - %C%N - %A - %T
    This naming scheme will make EAC create a directory and file names looking like this
    (EAC08here)
    If you prefer “Various artists” to “Various”, use “Various artists” instead of “%D” in the naming scheme, like
    this:
    Various Artists example 3: Various Artists - %Y - %C%N - %A - %T
    The resulting folder name would be “Various Artists - 1995 - The Very Best Of Irish Folk”.
    You can of course choose to just name the files in this step, and manually put them into a properly named
    folder after you have finished ripping. That way you will not have to edit the cue sheet after ripping, since the
    path to the files will not be included in the cue sheet if you do not make EAC create a directory for the files.
    The naming scmeme would then be:
    Various Artists example 4: %N - %A - %T
    Oh, and please do not check “Replace spaces by underscores”. It_looks_so_very_ugly.
    3f. Catalog
    Irrelevant for ripping quality.
    3g. Directories
    Irrelevant for ripping quality, but for privacy reasons, I recommend that you do not use a save path that
    contains your computer user account name. The log will contain the path of the directory where you
    saved your rip. That means that you should not, for example, save your rips in “My documents”.
    If you have only one un-partitioned hard drive, you can (for example) create a directory for your EAC rips right
    under root (C: ), and make it your default directory. That has the added advantage of keeping the path to the
    files short. As is all too well known, Windows has problems with files if their names, including the path, exceed
    255 characters.
    (EAC09 here)





#3

(EAC10 here)
Note: If you set a default directory, this is where the cue sheet for your rip will automatically be saved. If you
check “Ask every time” instead, a dialogue box for choosing where to save it will pop up as you create the cue
sheet.
3h. Write
Irrelevant for ripping quality.
i. Interface
Try with the native interface first (if you have one):
(EAC11 here)
However, if your drive(s) will not show up in the main EAC window, like this:
(EAC12 here)
…or if EAC has problems detecting features when you get to the drive configuration, you need to add an ASPI
layer to the EAC folder (as mentioned in Programs and Files That You Need To Install).
You can try the one from Nero (just copy it from Nero if you have it installed, or get it from here).
After downloading it, right-click the file wnaspi32.dll and copy it, then browse to the EAC directory and paste it
in that very folder.
(EAC13 here)
Another option is to use ForceASPI (download from here: http://radified.com/ASPI/forceaspi.htm).
If you use an external ASPI layer (that you paste in the EAC folder as detailed above), choose “Installed
external ASPI interface” instead:
(EAC14 here)






#4

Configuration - Compression Options
Most of the settings here have to do with setting up EAC to use flac.exe as an “external compressor” after the
files have been ripped to .wav. There is important do not do this-or-that advice here, too.
If you want to set up EAC for making mp3 or Ogg Vorbis files, follow the instructions for “Compression Options” in the Lossy Setup Guide.
Hit F11 or click “Compression Options” in the EAC menu.
a. Waveform
Ignore this tab, it is irrelevant for FLAC rips.
b. External Compression
(EACCO01 here)
Settings:
 Use external program for compression: Checked.
You need to check this in order to make EAC look for the flac.exe file that you specify below.
 Parameter passing scheme: Select “User Defined Encoder” in the dropdown menu.
 Use file extension: .flac - remember the dot before “flac”, and do not type “Flac”, or “flc”, or “FLAC”. The
program will copy what you type here exactly the way you typed it!
 Program, including path, used for compression: Browse to where you have saved flac.exe.
For EAC 0.95: If you installed the FLAC frontend, you will find it in C:\Program Files (or Programs )
\FLAC\flac.exe (unless you changed the default install directory while installing):
(EACCO02 here)
If you chose to just get the flac.exe file (perhaps placing it in the EAC folder) instead of the FLAC frontend, you
still need to browse to it and select it (probably C:\Program Files (or Programs)\Exact Audio Copy\flac.exe) at
this step of the configuration:
(EACCO03 here)





#5

For EAC 0.99: FLAC was included with the EAC 0.99 installation. You will find the flac.exe file in a subfolder in
the Exact Audio Copy folder, see the path in the picture below:
(EACCO04 here)
For both EAC 0.95 and 0.99:
Additional Command Line Options: Select, then copy this line, and paste into the box in EAC:
-V -8 -T “artist=%a” -T “title=%t” -T “album=%g” -T “date=%y” -T “tracknumber=%n” -T
"genre=%m" %s
This is what the command line options mean:
-V makes flac.exe verify the files after compression.
-8 is the level of compression. There are 8 compression levels, and level 8 is the highest of them all. Level 8 produces the smallest possible
file size for the FLAC files. Using the highest compression level makes the process take only slightly more time than the other levels on new
computers. However, if you have an old computer, say with a CPU speed of less than 1 GHz, level 8 may take too much time. In that case,
it is OK to change the compression level to 5. The resulting files will be somewhat larger than those compressed at level 8, though.
All the -T options are for adding proper FLAC tags (Vorbis comments) for the files. The tags will be what you see in the main EAC window:
( EACCO05 here)
%s will be replaced by EAC with the full path to the source wave file.
Many (older) EAC guides will recommend the command line “-8 -A tukey(0.25) -A gauss(0.1875) -b 4096 -V -T “artist=%a” -T “title=%t” -T
"album=%g” -T “date=%y” -T “tracknumber=%n” -T “genre=%m” %s". This probably became a “standard” due to a bug in FLAC version
1.1.3, for which the -A tukey switch is a workaround, see this Hydrogenaudio forums thread. You can use that command line with later
versions of FLAC, too, it will do no harm, but it is doubtful if there is much point in it: see this this Hydrogenaudio forums thread and make
sure that you read the FLAC developer Josh Coalson’s reply.
Bitrate: Will be ignored, so it does not matter what it says. It happens to say “320” and “128”, respectively, in
the screenshots; but you can just as well leave it at 128 kBit/s.
Delete WAV after compression: Checked (unless, for some reason, you want to keep the wave files).
Use CRC check: Unchecked.
This setting will be ignored when a “user defined encoder” is used. In some other cases, it makes the encoder store the CRC value in the
file’s header, which is seldom of any practical use. This setting has nothing to do with the Test and Copy (= Read) CRC values that show in
the main window and the log file.
Add ID3 tag: Unchecked.
It is very important that you do not check this option. The tags will be added by the use of a command line (which is different for FLAC,
mp3 and Ogg Vorbis, see EAC Lossy Setup Guide for the latter). Adding anything but Vorbis comments (FLAC Tags) to FLAC and Ogg Vorbis
files will make them unplayable by some players. (To be sure, the files may be OK even if you have checked this option, provided that you
have not checked some options under 4d. ID3 Tag as well. Still, you need to open the files in a hex editor in order to check if they are
really free from ID3 headers. It is much better to simply keep this checkbox unchecked.)
Check for external programs return code: Checked.
This option makes EAC check for and report errors reported by the external compressor (flac.exe), including incorrectly used parameters in
the command line. Enable it as an extra precaution against encoding errors (that may happen after the actual rip is finished).
High/Low quality: Leave this at “High” - it will have no influence on the rip anyway.
c. Offset
Ignore this tab, do not change any settings here. This means that the “Use Offset Correction” option should be
left unchecked. Enabling this setting, even with “0” as the sample offset value, would permanently alter the
ripped files, so that you would not create an exact copy of the CD.
The option is included in EAC for the very special cases when you use one (mp3) codec that introduces a certain offset for encoding, and
you know that you will use another (mp3) codec with a different offset for decoding. As mentioned above, even a zero offset will affect the
files, and it has been shown that encoding LAME mp3s with a zero offset causes problems with gapless playback.
(EACCO06 here)
d. ID3 Tag
(EACCO07 here)
Important: nothing checked here! Tags get added by using the command line in the "Compression Options"
tab. It is especially important to keep this unchecked for FLAC (and Ogg Vorbis) since mp3 headers would
make the files unplayable on some systems.
The command line is different for FLAC, mp3 and Ogg Vorbis - see the Lossy Setup Guide for mp3 and Ogg Vorbis command lines.






#6

Configuration - Drive Options
Hit F10 or click “Drive Options” in the EAC menu.
Note: If you want to configure more than one drive for ripping, you will need to save the settings for the first
drive, then re-do the drive settings for the next drive, and save those settings under a different name. See
Saving Profiles. Choose the drive you want to configure by selecting it in the drop-down menu in the main
window.
Also, if you upgrade the firmware on your drive (flash the firmware) you will need to set up the drive options
for EAC again, as well as the CacheX and Feurio tests if EAC still reports that your drive does not cache audio
data.
You need to insert a CD in the drive in order to run some of the drive tests. For 5c below (“Detect read sample
offset correction”) it needs to be a CD that can be found in the database, so bring a pile of reasonably wellknown
CDs with you to the computer.
As mentioned in the introduction, EAC 0.99 supports AccurateRip. If you insert a CD that is in the AccurateRip
key disc database as you configure your drive, there will be a popup offering you to take advantage of the
opportunity to have some of your drive features automatically set by AccurateRip:
(EACDO01 here)
Click “Configure”. You will be greeted with a success message after a few seconds:
(EACDO02 here)
If AccurateRip does not start automatically, and you do have a CD that is in the AccurateRip key disc database
in the drive you are about to configure, make sure that the “Use AccurateRip with this drive” option in the
Offset/Speed tab is checked (see 5c. Offset/Speed). If the option is greyed out, so that AccurateRip is not
available to you, see 5f. Appendix: If “Use AccurateRip with this drive” is greyed out, but note that it will be
greyed out unless/until you have a CD that is in the database in the drive.
a. Extraction Method: Secure
Secure Mode: Checked.
Since this is a “radio button” choice, it follows that “Paranoid Mode”, “Synchronized Modes” and "Burst Modes"
should all be left unchecked. (But see Alternative Extraction Method: Burst for using burst mode instead of
secure mode after all.)
Next, click “Detect Read Features” in order to let EAC check if your drive caches audio data, and if it has
Accurate Stream (in which case EAC has no need to perform additional synchronization). It will also check for
C2 error info, but we will leave this option unchecked no matter what EAC says about it.
We will trust what EAC says about the Accurate Stream feature. We will also trust EAC if it says that the drive
caches audio data, like this:
(EACDO03 here)
After the detection is done, click “Apply” to have the detected features automatically applied as settings.
However, uncheck “Drive is capable of retrieving C2 error information” - if the feature is left enabled, some
errors may in fact go undetected.
Quote from EAC’s FAQ page:
"What is C2?
On all CD-ROM media are at least two levels of error correction, called C1 and C2. If both fail, the output is probably not correct anymore.
Most drives are not able to report if audio reads failed or not, so each block had to be read twice and be compared to make sure that
everything is fine. But some newer drives are able to report if C1/C2 failed on specific samples on a read, making it possible to read only
once and see if a read error occured. But there is still a problem, as some drives do not report these errors correctly, so you should test it
thoroughly before trusting the results. (…) It seems that C2 is not correctly implemented in some drives. To be on the safe side, you should
turn off the C2 error correction."
In other words: C2 could be utilised for speeding up the extraction process if you dared trust it with EAC. It would make (a lot of) the rereads
that EAC performs unnecessary. However, testing your drive is a bit… involved. See this page about DAE Quality (scroll down a bit).
So the recommendation is to simply not use C2 with EAC rips, even if it would be OK in some cases. If you use it with EAC and it does not
perform as expected, errors may go undetected and thus uncorrected.
This is how the settings should be:
(EACDO04 here)
It is very important that “Drive caches audio data” is checked if your drive does cache the data. EAC needs to
read from the disc, not from a cache, each and every time. This is the basis for error detection and correction,
and thus for establishing that the rip is a (near) perfect copy of the disc: it is almost impossible that the data
would read the same more than once if the drive did not read it correctly from the disc. However, if the data is
cached it is no surprise that it reads the same the next time it is accessed.
So, a drive that caches audio data defeats the purpose of making secure rips, unless you tell EAC that the drive
caches audio data. If EAC “knows” that a drive caches audio data, it will flush the drive’s cache in order to be
able to read from the disc again.
There are doubts about whether EAC really detects drive caching properly. This is why many guides
recommend (or even demand) that you always disable/defeat cache (that is, check “Drive caches audio data”).
As far as rip quality is concerned, it is never wrong to have “Drive caches audio data” checked.






#7

EAC may show that your drive does not cache audio data, like this:
(EACDO05 here)
You can still choose to have “Drive caches audio data” checked as shown above. It will do no harm to the rip
quality, but the rip may take a bit longer.
On the other hand, it seems pointless to defeat an audio cache that does not take place in the first place (and
some sources indicate that it puts unnecessary strain on the drive, shortening its lifetime). There are other
tools for testing whether the drive caches audio data or not, such as Spath’s Cache Explorer and Feurio!. If EAC
reports that your drive does not cache audio data, you have to test with one or both of them in order to
determine if your drive really does not cache audio data. If you do not perform further tests on your
drive, or if any of the tests show that your drive does in fact cache audio data, you have to check
"Drive caches audio data" as shown above.
N. B. EAC reads data in 64 kB chunks, so a cache smaller than 64 kB will actually not affect the ripping result. See this Hydrogenaudio Wiki
article.
Spath’s Cache Explorer (shortened to CacheX from now on) is a small command line tool that can actually
be used to investigate some other drive features, too, but here we will only look at the drive cache detection
features. Test with this tool first!
Download CacheX from here. It is a .zip file that needs to be extracted before you can use the program. Extract
it to a location of your choice; if you extract it to C:\ it will be easier for you to access the program in the
command prompt, as described below. I recommend you to do so if you are not used to working with
command line tools.
(Since I like to have my files logically structured, I created a CacheX folder in “Program Files” for it. This is why the screenshots show a
slight difference compared to the instructions in the text. Just ignore it. Do as the text says.)
Insert an audio CD in the drive you want to test, then click Start - Run and type “cmd” (without the quotes),
hit Enter or click “OK”. This will open the command prompt.
Here is how to perform the test, assuming that you extracted CacheEx to C:\ as recommended above:
In the command prompt, go to C: by typing “cd” (without the quotes), hit Enter.
If you are curious about what the program can do, you can get a list of the command line options by typing “cachex --help” (without the
quotes).
For a “standard” test for audio caching, type “cachex -i -c -n 10 [drive letter]:” (without the quotes), then
hit Enter. Of course you have to substitute [drive letter] with the actual drive letter for your drive.
In the examples below, I have tested the drives on M and D, respectively. The -i command makes CacheX
show information about the drive. Note that the drive may report a buffer (that can be used to cache data), but
still not cache audio data. The -c command makes CacheX test if the drive actually caches audio data. The -n
command tells CacheX how many times it should test if the drive caches audio data. Let it test at least 10 times
in order to make sure that the result is reliable. The cache will not be detected in each and every test, so
running it just a few times may give you a misleading result.
(The user name has been edited out from the home directory C:\Documents and Settings*USERNAME*, creating an abnormal empty space
in that line in the screenshots. Just ignore it.)
This drive caches audio data according to CacheX - with a result like this, you have to check “Drive caches
audio data” in the drive settings for EAC:
(EACDO06 here)
This drive does not cache audio data according to CacheX:
(EACDO07 here)
If CacheX shows that your drive does not cache audio data, you may run yet another test. Feurio! is an
"ordinary" Windows application with installer and graphical user interface. Download it from here and install the
trial version. It is pretty straight-forward to use it for testing your drive cache. Insert an audio CD into the
drive. Click the “Program” menu and choose “Program Parameters”, select the drive you want to test in the
drop-down menu, click the “Test Device” button (bottom right), check only “Cache test” for “Do the following
tests”, then click “Start test”. When it is done, save the results. Here is an example of a report for a drive that
does not cache audio data:
Informations from INQUIRY command:
Manufacturer: PLEXTOR, Product: DVDR PX-800A, Version: 1.00
Synchronous data transfer: Not supported
Reading device capabilities: OK
Maximum speed: 7056 kByte / second (40.0 times)
Cache size: 2048 kByte
Read CD-RW: Yes
Read Bar code: No
Read UPC code: Yes
Read ISRC code: Yes
Return C2 error pointers: Yes
Read R-W subcodes: Yes
R-W subcode de-interleaved: No
Read CD-DA: Yes
Read CD-DA correctly: Yes

+++++++++++++++++++++++++
++ Cache test
+++++++++++++++++++++++++
Number of sectors: 1 (=2 kByte) -> 1.438 MBytes / second
Number of sectors: 2 (=4 kByte) -> 0.125 MBytes / second
Number of sectors: 3 (=7 kByte) -> 0.217 MBytes / second
Number of sectors: 4 (=9 kByte) -> 0.290 MBytes / second
Number of sectors: 5 (=11 kByte) -> 0.363 MBytes / second
Number of sectors: 6 (=14 kByte) -> 0.435 MBytes / second
Number of sectors: 7 (=16 kByte) -> 0.508 MBytes / second
Number of sectors: 8 (=18 kByte) -> 0.578 MBytes / second
Number of sectors: 9 (=21 kByte) -> 0.569 MBytes / second
Number of sectors: 10 (=23 kByte) -> 0.544 MBytes / second
Number of sectors: 15 (=35 kByte) -> 0.817 MBytes / second
Number of sectors: 22 (=51 kByte) -> 0.802 MBytes / second
Number of sectors: 15 (=35 kByte) -> 0.816 MBytes / second
Number of sectors: 16 (=37 kByte) -> 0.871 MBytes / second
Number of sectors: 17 (=39 kByte) -> 0.739 MBytes / second
Number of sectors: 18 (=42 kByte) -> 0.784 MBytes / second
Number of sectors: 19 (=44 kByte) -> 0.826 MBytes / second
Number of sectors: 20 (=47 kByte) -> 0.866 MBytes / second
Number of sectors: 21 (=49 kByte) -> 0.808 MBytes / second
Number of sectors: 31 (=72 kByte) -> 0.966 MBytes / second
Number of sectors: 46 (=108 kByte) -> 1.114 MBytes / second
Number of sectors: 69 (=162 kByte) -> 1.363 MBytes / second
Number of sectors: 103 (=242 kByte) -> 1.496 MBytes / second
Number of sectors: 154 (=362 kByte) -> 1.598 MBytes / second
Number of sectors: 231 (=543 kByte) -> 1.623 MBytes / second
Number of sectors: 346 (=813 kByte) -> 1.692 MBytes / second
Number of sectors: 519 (=1220 kByte) -> 1.729 MBytes / second
Number of sectors: 778 (=1829 kByte) -> 1.741 MBytes / second
Number of sectors: 1167 (=2744 kByte) -> 2.631 MBytes / second
Number of sectors: 1750 (=4116 kByte) -> 2.669 MBytes / second
Number of sectors: 2625 (=6174 kByte) -> 2.669 MBytes / second
Number of sectors: 3937 (=9259 kByte) -> 2.718 MBytes / second
Number of sectors: 5905 (=13888 kByte) -> 2.751 MBytes / second
Number of sectors: 8857 (=20831 kByte) -> 2.806 MBytes / second
Number of sectors: 13285 (=31246 kByte) -> 2.856 MBytes / second
Number of sectors: 19927 (=46868 kByte) -> 2.926 MBytes / second

Result:
Maximum transfer rate: 2926 kBytes/Second
Cache size for audio data: 0 kByte
It seems that your device isn’t able to cache audio data!
############################################

FINISHED

############################################
If you have tested your drive with CacheX and Feurio!, and if neither EAC nor CacheX nor Feurio! say that your
drive caches audio data, then you may apply the following settings:
(EACDO08 here)






#8

a. Alternative Extraction Method: Burst
Here is a controversial alternative: using burst mode for ripping. If you want to be on the safe side (not
least in discussions over proper rips), always follow the above instructions for configuring EAC for ripping in
secure mode and skip this alternative section.
However, it can be argued that all the re-reads that EAC performs in secure mode are not really necessary for
CDs that are in good condition. In burst mode, EAC just reads the track once, which makes burst rips go faster
than secure rips. Now, just one read is of course not reliable, but if you combine it with the option to “test and
copy” the tracks, and use AccurateRip to boot, I believe that you can trust that your rip is as perfect a copy as
it is possible to get.
“Test and copy” is explained here and here and AccurateRip results here.
(EACDO09 here)
If you rip a CD in burst mode it is extra important, indeed necessary, to check the log afterwards. If all the
other EAC settings are correct and if there are…
No errors
Matching test and copy CRC values
AccurateRip confidence at or above 2
…then you may be quite confident that your burst rip is fine.
If there are errors, mismatching CRC values, or no/low Accurate rip verification, re-rip the CD in secure mode.
Note that there is no actual error detection in burst mode; the “timing errors” that may show up may or may not indicate actual problems
with the rip.
In other words, do not interpret this section as saying that you do not need to configure your drive for secure
ripping as detailed above. On the contrary: I recommend that you set your drive up for secure ripping, and
save your settings in the profile for FLAC rips (see 6. Saving Profiles). If and when you want to test if a CD can
be properly ripped in burst mode, all you need to do is to check “Burst mode” (and click “OK”) before you start
ripping. You can revert to secure ripping at any time by loading the profile you have saved with all the correct
settings for secure ripping.
b. Drive
Click “Autodetect read command now” in order to have EAC select the correct setting for your drive.
(EACDO10 here)
“Big Endian” byte order (Motorola): Unchecked, unless extracted tracks consist of noise. (If they do, try
checking it.)
Swap channels: Unchecked, unless your drive has the stereo channels backwards. If it does, you are likely to
notice that fact when you listen to a rip from it.
Spin up drive before extraction: Unchecked, unless your drive has difficulty reading data on spin-up.
c. Offset/Speed
If you allowed AccurateRip to configure your drive with EAC 0.99, the top half of this window will be greyed
out:
(EACD011 here)
You should still configure the settings from Speed Selection and downwards, see below.
For EAC 0.95 only (or for EAC 0.99 as well, if for some reason used without AccurateRip):
Use read sample offset correction: Checked.
Do not trust what EAC says when reporting the result of the “Detect read sample offset correction” test; it may
or may not detect your drive’s offset correctly.
Check for the correct offset correction value for your drive in the AccurateRip database. (You know the name of
your drive from the drop-down menu top left in EAC’s main window.) You can also look for offset correction
values in the DAE Drive Features Database, but it is considered somewhat less reliable than AccurateRip.
A small number of drives are not present in the AccurateRip database, or are marked as “purged” because there are different read offset
values for different drives with the same name. If you have one of those drives, you do need to check your drive’s read sample offset by
using AccurateRip with one or more of the key discs in the database. (That means that, if you use EAC 0.95, you still need to install EAC
0.99 in order to test the drive. You can install it in a different folder than the default one, and thus keep EAC 0.95 untouched. Also, if you
for whatever reason intend to stick to EAC 0.95, there’s no need to do the rest of the setup for EAC 0.99. Just use it to test the drive.) Take
a screenshot of the AccurateRip results for your drive’s offset so that you have a record of it: use the “Print Scrn” button in order to copy
what you see on the screen to the clipboard, then open any image editing program (“Paint” will do), paste the screenshot there and save it.
Overread Lead-In and Lead-Out: Unchecked in most cases.
Press the button that says “Detect read sample offset correction”. Enable this setting if it says your drive can overread from both the Lead-
In and Lead-Out or if it says Lead-Out and your offset correction is positive or if it says Lead-In and your offset correction is negative.
Otherwise disable (uncheck) it.
(EACD012 here)
The resulting settings:
(EACDO13 here)
For both EAC 0.95 and EAC 0.99:
Speed Selection: Actual.







#9

For both EAC 0.95 and EAC 0.99:
Speed Selection: Actual.
Allow speed reduction during extraction: Checked.
EAC needs to be allowed to slow down during error correction.
CD-Text Read capable drive: Checked for most drives, unless quite old.
If you want to check if your drive can read CD-Text, check this option, then (with a not-too-old CD in the drive) click the Database menu
and choose “Clear Actual CD information…”. (Click OK when you are warned that the information will indeed be erased.) Click the Database
menu again, choose “Get CD information from… CD-Text”. If no information appears, your drive can not read CD Text. You can get the
information from freedb back by clicking the Database menu once again, then choose “Get CD informations from… Remote freedb”.
d. Gap Detection
(EACDO14 here)
Gap/Index retrieval method: Try method A, change to B or C if detection is slow, or is not working at all.
Sometimes the retrieval method will have to be changed depending on the CD you rip: with the Plextor drive used in most of the examples
here, I can usually use any of the methods, but with some CDs only method A will work, while B and C both freeze at a certain track. This
setting does not influence the ripping quality as such: A, B and C are merely different methods for retrieving indices (such as gaps). If they
all work on your drive, A will usually be faster than B, which is usually faster than C.
A few drives will show slightly different gap lengths depending on which retrieval method you use. (See discussion in this Hydrogenaudio
Forum thread.) Note that the gap length does not affect the audio. Properly ripped tracks will have the same CRC values even if the gap
lengths differ depending of the retrieval method. But, if you want to be able to re-create and burn a perfect copy of the audio CD (or, as
perfect as is possible), take the time to check if your drive detects the same gap lengths for all the methods. If it does not, use the same
CD and test with another drive (if you have one). Presumably the gap lengths that match across methods and drives are the correct ones.
Detection accuracy: Secure.
Change it (try “Accurate” before “Inaccurate”) if the gap detection does not work at all. “Secure” and “Accurate” both retrieve the position
of the gaps several times, “Inaccurate” only once.
e. Writer
Irrelevant for ripping, but very important for burning exact copies. See EAC CD Burning Guide.
Continue to 6. Saving Profiles
f. Appendix: If “Use AccurateRip with this drive” is greyed out
Note: these instructions are only for the problem with the greyed out option in EAC 0.99 - if
AccurateRip works, you don’t have to perform this step! Also, note that they option will be greyed out
until/unless you have a CD that is in the AccurateRip key disc database in the drive.
If you have installed EAC 0.99, but AccurateRip does not start even though you have a CD that is in the
AccurateRip database
(EACDO15 here)
… you need to edit the registry. N.B. be cautious, do NOT make any other changes than the one
described here. There is no “undo” option as you edit the registry, and improper changes can have
severe consequences.
Click “Start” - “Run”, type “regedit” (without the quotes) and hit Enter (or click “OK”).
In the Registry Editor that thus opens, navigate to
"HKEY_CURRENT_USER\Software\Illustrate\dBpowerAMP\CD-NoAccurateRip". If you click the dBpowerAMP
folder in the left pane, you will see the “CD-NoAccurateRip” key in the right pane:
(EACDO16 here )
If “CD-NoAccurateRip” has any other value than 0 (zero), the option to use AccurateRip with EAC will be
disabled, so you will have to edit it back to 0 (zero).
Right-click “CD-NoAccurateRip”, choose “Modify”:
(EACDO17 here)
A box for editing the value pops up. Leave it at hexadecimal and type “0” without the quotes, then click “OK”:
(EACDO18 here)
This is what the value for “CD-NoAccurateRip” should look like when you are done:
(EACDO19 here )
Then just exit the Registry Editor. You may need to restart EAC in order to have the new setting recognized so
that AccurateRip becomes available to you.
Fix originally found in a thread at the EAC support forums.








#10

I made an error in one image above .this should have been EAC11 in post #3
Maybe a mod could change it for me.