EAC audio extration seems slow!

[CorCentral]

Eac/Lame (recent editions)

I've used this in the past & have recently upgraded my cdrw to a Lite-On 52x24x52.
All options are set to default & I've done all the Drive tests, etc. It just seems slow on Extracting (3.8x) Does this seem right?

Help

 

[waylman]

you probably have EAC set to secure mode. Set it to burst mode and it will FLY.

 

[waylman]

forgot to mention..just hit F10 in EAC to bring up this option

 

[DaveSimmons]

What condition are the CDs in? EAC will slow way down if it's having to retry to fix correctable errors.

 

[CorCentral]

Yes, it's in secure mode. My cd's are in decent condition (some have small scratches) but want the best outcome

 

[PrincessGuard]

I get around 3x so that seems about right. Secure extraction slows down a lot if your drive does caching.

 

[VirtualLarry]

I think that this might be a combination of the "secure mode" in EAC, interacting with the "Smart-X" variable-speed extraction feature. You see, when in "secure" mode, it re-reads overlapping groups of sectors, and thus, isn't actually reading data when it's doing the re-seeks. So the "Smart-X" feature likely averages how fast the data-buffer is being read, and slows the spindle-speed down to match, roughly.

Although, honestly, even on my "56X max" IDE CD-ROM, "secure" mode seemingly only topped out at something like 6-8x effective read speeds anyways. If you have a good drive with "accurate stream", then use the mode that doesn't re-read overlapping sectors. (I think that "Burst" ignores all hardware read errors too, not sure if you want that. I could be wrong, it might be "Burst", haven't used EAC in a while.) To be safe, I usually rip at 8x anyways.

 

[CorCentral]

So, if I set it to Burst mode & it finds an error, will the track be screwed?
I think it may be better to go with Burst & when it's finished, check the results. If a track is bad, go over that track in secure mode?

 

[BespinReactorShaft]

Originally posted by: CorCentral
So, if I set it to Burst mode & it finds an error, will the track be screwed?
I think it may be better to go with Burst & when it's finished, check the results. If a track is bad, go over that track in secure mode?

Not a bad idea, if you mean to compare between the two CRC check results and don't mind putting up with more than one ripping pass. Personally, I'd still go for secure mode.