QUOTE (odyssey @ Jun 15 2007, 12:26)

That said, my experience with dBpowerAMP is that it sometimes are slower to rip a secure track than a CRC matched track in EAC.
Depending on your drive and how you configure and use both programs, speed differences might not be all that profound, but as Sebastian already said, dBpowerAMP has an automated process to deliver a secure rip as quickly as possible regardless of your drive's features.
Just as an example, if you have a chaching drive that won't accept the FUA command and can't provide good C2 pointer information, there's no question that dBpowerAMP is the faster solution for secure results.
With my Plextor, however, I can get burst speeds and the ability to perform error correction in the very first pass. With a track that requires re-reads to be ripped correctly and can be verified by AccurateRip,
this can go twice as fast as (EDIT: sorry!

)
the speed is comprable to dBpowerAMP.
But then there are cases where the use of C2 pointers during re-reads can make a difference in getting a good rip in which case EAC won't be able to get the job done. I think the configuration of dBpowerAMP secure settings still has much to be desired, but Spoon hasn't expressed any interest in my suggestions.
Anyway, there are still lots of other things dBpowerAMP has implemented to improve the ripping process over EAC such as cross-checking and attpemting to detect if interpolation has resulted in a consistent error, though I have never personally expienced a benefit with these.
Odyssey, can you tell me the circumstances (drive features and relative settings in both programs) where you've seen EAC rip more quickly than dBpowerAMP?