QUOTE(sTisTi @ Nov 2 2005, 04:37 PM)
Did you check "use C2 information"? This should be safe for Plextor drives (after all, also Plextools Pro relies on C2 info and is considered safe). This should speed up the extraction considerably.
You seems to be really right, sTisTi. I made some more tests and here are the extraction speed results with different switches activated:
CODE
Drive Caches, No FUA, No C2: 7.8
No Drive Caches, FUA, No C2: 6.5
Drive Caches, No FUA, C2: 11.1
No Drive Caches, FUA, C2: 25.6
All the tests were done ripping Joini Mitchel's "Chalk Mark in a Rain Storm", Geffen 924 172-2, witch lasts for 46' 24''. The CD is in fair conditions with a total of about 32000 C1 and a burst of about 1500 C2 errors.
It seems that using Plextor's C2 error information gives a HUGE advantage in terms of speed, particullary when used toghether with the -usefua command line options, that on the other hand makes extraction slower when no C2 information is used.
I'm not competent enough on the internals of the Plextor drives/firmware and EAC to comment my own results. Any comment from a knowledageble person (Pio2001, are you listening??

) will be really apreciated.
I must add that I'm not yet totally convinced, in terms of "ripping security" about using the "Drive is capable of retrieving C2 error information" EAC option, even with my Plextors, but I may be badly wrong and at this point I will be really happy to be proved such.
Sergio
Edit: Spelling
P.S.: "No Drive Caches, FUA, C2" is on a par with burst mode, for speed.