Don't take this wrong, but you'll have to do better than that (just giving a link to the instructions you followed) if you really want constructive help.
Please mention the actual EAC settings, your ripping drive, the ripping mode you choosed, your comp specs... the more details the better.

EAC Options:

Extraction Tab
[X] Fill up missing offset samples with silence *Optional. For drives that overread lead in/out this is not needed.*
[ ] No use of null samples for CRC calculations *Doesnt change audio*
[X] Synchronize between tracks
[ ] Delete leading and trailing silent blocks
[X] Skip track extraction on read or sync errors (wont affect rip, but I check yes for next 3)
[X] Skip track extraction after duration longer than X times realtime
[X] After each 30 minutes of extraction, cool down the drive for 5 mins
[X] Lock drive tray during extraction
Extraction and compression priority: Normal
Error recovery quality: Medium **this is a change from my previous recommendation. This will decrease the number of error bars from 5 to 3. I have never had a rip go past 3 bars (really usually only 2 at most) and have an error free rip. Save the time. Plus its easier on your drive.

General Tab
doesnt matter for ripping.

Tools Tab
[X] Retrieve UPC/ISRC codes in CUE sheet generation
[X] Use CD-Text information in CUE sheet generation
[ ] Create '.m3u' playlist on extraction - **user option
[X] Automatically write status report on extraction
[X] On extraction, start external compressors queued in the background [1] - **user option.
[X] Do not open external compressor window - **user option
[X] Submit drive features after detection
[ ] Activate beginner mode, disable all advanced features

Normalization Tab
NOT CHECKED!!!

Filename Tab
Naming Scheme: %A - %C - %N - %T (or as you prefer, check EAC's FAQ.txt)
Various Artists: %C - %N - %A - %T (see above)

Catalog Tab
Not important

Directories Tab
**user option.

Write Tab
Nothing to do with extraction here

Interface Tab
Not so important, you can use the Native one



Drive Options

Extraction Method Tab
Secure Mode (after "detect read features" option is used, with appropriate settings)
**It is also reasonable to use Burst Mode if you always use Shift-F6 (Test & Copy). It has been argued that this is more secure then secure mode and its tends to be faster. Burst mode alone (without Test & Copy) is not secure!
[X] Drive caches audio data (clears the drive cache)
[ ] Drive is capable of C2

Drive Tab
Autodetect for drive read command
[ ] Big endian
[ ] Swap channels
[X] Spin up before extraction

Offset / Speed Tab
Offset locked by AccurateRip
Overread into lead-in and lead-out data (You will need to test this one on a disc, if you get a read sync error on the first or last track of a new CD your drive cant overread and the option should be unchecked - this will mean that you loose the number of samples equal to your drive offeset on either the first or last song, the only solution is a different drive)
[X] Allow speed reduction during extraction
[X] CD-Text Read capable drive

Gap Detection Tab
Gap/Index retreval method: per drive setting (start with method A or B)
Detection Accuracy: Secure (some prefer to use accurate)


Compression Options

External Compression Tab
[X] Use external compression
User defined encoder
Use file extension: .flac
Program including path: -browse and select flac.exe-
Additional Command Line Options:
[b]-6 -V -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" -T comment="%e" -T "comment=EAC (Secure Mode)" %s[/b]
Bitrate: Doesn't matter
[X] Delete WAV after compression
[ ] Use CRC check
[ X] Add ID3 tag
[X] Check for external compression return code

Offset Tab
[ ] Use offset detection for encoding and decoding Do NOT check this as it will add gaps to gapless music

Both Drives have Caching.

I am a little mixed up on this, on one hand I read to check the feature to use Cache when ripping to Flac but on the other hand I read that the information coming from Cache can lead to errors.  One of my drives supports cache, the other doesnt.  i am using EAC.

One-size fits all solutions for EAC suck.  I suggest you follow this guide instead:
http://wiki.hydrogenaudio.org/index.php?ti...Lossless_Backup

...and again, Burst with T&C is perfectly fine, so don't feel compelled to follow it to the letter.

Also, rips based on C2 error information without T&C are only as secure as your drive's ability to provide reliable C2 pointers.  Without thorough testing you should assume your drive can't provide reliable C2 pointers.  Like with Burst mode, until you use T&C you should assume your rips are not secure when enabling the use of C2 pointers.  In the case of Francksoy-Wizzu's NEC drive, a brand notorious for giving unreliable results in EAC when C2 information enabled, an extra 3 seconds per track is a minor price to pay in order to insure true security.  This fast ripping speed is largely attributed to the fact that it does not cache audio data, BTW.

If you are interested in learning about the drive features read this:
http://wiki.hydrogenaudio.org/index.php?ti...C_Drive_Options

Moving on...

Quote from: JHFerry on 2008-01-07 02:08:01

Both Drives have Caching.

...but four days ago you said:

Quote from: JHFerry on 2008-01-03 04:12:53

I am a little mixed up on this, on one hand I read to check the feature to use Cache when ripping to Flac but on the other hand I read that the information coming from Cache can lead to errors.  One of my drives supports cache, the other doesnt.  i am using EAC.

Which is the case?

Lastly, adding an ID3 tag to FLAC files is not a good idea!!!

How fast does your drive actually read the CD? My LG drive hard locked read speed at 4x (or maybe 3x even) when reading Audio CDs.

I remember that thread, I think I was getting mixed up because one of the drives does C2 checking and the other does not.  I might have confused that with Caching.

Quote from: lexor on 2008-01-07 05:14:32

How fast does your drive actually read the CD? My LG drive hard locked read speed at 4x (or maybe 3x even) when reading Audio CDs.

Thats a good question, I dont remember having any locks in any other app like winamp.  I dont remember seeing any options for drive speed in EAC.

Quote from: JHFerry on 2008-01-07 15:53:19

I remember that thread, I think I was getting mixed up because one of the drives does C2 checking and the other does not.  I might have confused that with Caching.

So EAC's test for audio caching came back and said both drives cache audio data, correct?

Quote from: JHFerry on 2008-01-07 15:53:19

Quote from: lexor on 2008-01-07 05:14:32

How fast does your drive actually read the CD? My LG drive hard locked read speed at 4x (or maybe 3x even) when reading Audio CDs.

Thats a good question, I dont remember having any locks in any other app like winamp.  I dont remember seeing any options for drive speed in EAC.

EAC has throttling options, but I believe lexor might be talking about drives that automatically lock the speed of discs they detect as problematic.  This is determined by the drive and is something you cannot control.

Can EAC output a log after testing a drive or is there something else out there I can use to test so I can post results?

I also checked the EAC lossless guide you posted and my settings are pretty much the same aside from the burst settings which I will change.

[X] After each 30 minutes of extraction, cool down the drive for 5 mins
[X] Spin up before extraction

have you tried a new firmware on your pioneer, it may speed up ripping.

http://forum.rpc1.org/dl_firmware.php?download_id=2331

(make sure you fully read the instructions before doing it or you may brick your drive)

Just to push home the point about Accuraterip. If you get a positive accuraterip result you don't need to test and copy. This will greatly help speed up the ripping process too.

I followed the FAQ above for setting up EAC to rip to FLAC.  The only issue I have is the time its taking.  Its averaging 30 minutes each CD and I have hundreds to rip.  I am not using burst or anything like that, I followed the FAQ to the letter. 

Is there anyway to speed this up?

I believe in theory, that the image from most image reading programs will be bit-for-bit accurate with the results of EAC reading from the DVD/CD-ROM.

The benefit in my opinion would be that the audio CD would be treated as a data disc, and no firmware limitations would impede the ripping speed.

Error handling can be controlled by the ripping/image extracting application (such as MagicISO or ISOBuster, etc.) to keep DVD/CD drive speeds at error-free working levels.

In the case of Francksoy-Wizzu's NEC drive, a brand notorious for giving unreliable results in EAC when C2 information enabled, an extra 3 seconds per track is a minor price to pay in order to insure true security.

This fast ripping speed is largely attributed to the fact that it does not cache audio data, BTW.

Just for the heck of it I installed Foobar and set it to Standard error checking and my rip took about 1 minute less.  So it ripped around 5:30.  The drive speed was much better, in the mid 20's although I dont know why it doesnt rip full speed, error checking I guess.

Quote from: JHFerry on 2008-01-10 19:46:58

Just for the heck of it I installed Foobar and set it to Standard error checking and my rip took about 1 minute less.  So it ripped around 5:30.  The drive speed was much better, in the mid 20's although I dont know why it doesnt rip full speed, error checking I guess.

Be careful with foobar2000 and ripping, especially in standard mode.  When it comes to security going from EAC to foobar2000 is a step backwards (less immunity to consistent errors, no AR support).  With your drive that provides C2 pointers, going to dBpoweramp will be a step forwards.

Do you still have the "Spin up drive before extraction" option enabled in EAC?
You will experience a decrease in ripping time if you disable it.