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
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)
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
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.
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.
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.
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.
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.