Help - Search - Members - Calendar
Full Version: Plextor Premium 2 and usefua with EAC/REACT
Hydrogenaudio Forums > CD-R and Audio Hardware > CD Hardware/Software
RBI Champ
Jun 28 2008, 12:33
Hi, I've been using EAC and REACT together for several months with my Plextor Premium 2 drive. I've been averaging around 8X extraction speed.

Just today I've come across the "usefua" switch. I would like to use it to speed the up the extraction process. (I still have about 2/3 of my collection left). I can deal with the slowness of my previous settings, but if I can become assured of "usefua" and unchecking "drive caches audio data" that would be ideal.

I'm hoping for step by step help in confirming that the updated settings are proper for insuring accurate/secure rips at the faster speed.

I've run spath's cache explorer, but I'm not entirely sure what I've proved with it. smile.gif I've included the results of some tests below. Please tell me if running those once is sufficient.

I've also added the following line to my react.ini, and as noted, unchecked "drive caches audio data."

CODE
EAC=C:\Program Files\Exact Audio Copy\EAC.exe -usefua


I've put in two different cd's with these new settings and extracted from them in the 20X range (with no delay between tracks!)

I've also put in a disc that has a known problem track. There is a very small "hole" in it that can be seen if you hold it up to the light. I think I've read that seeing "read error" and "sync errors" on a known bad disc, after implementing the "usefua" switch, confirms that it is reading directly and not from the cache (please see image at bottom of this post).

Thanks in advance for any help or suggestions.

CODE

cachex>cachex.exe -p -r 0xd8 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is  PLEXTOR  CD-R   PREMIUM2  1.03

[+] Plextor flush command: accepted
[+] Plextor flush tests: 5/5


cachex>cachex -i -c -n 3 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is  PLEXTOR  CD-R   PREMIUM2  1.03

[+] Buffer size: 8192 kB, read cache is enabled
[+] Supported read commands: BEh A8h(FUA) 28h(FUA) D4h(FUA) D5h(FUA) D8h(FUA)
[+] Testing cache line size:
397 kB / 173 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors

cachex -i -p -d e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is  PLEXTOR  CD-R   PREMIUM2  1.03

[+] Buffer size: 8192 kB, read cache is enabled
[+] Supported read commands: BEh A8h(FUA) 28h(FUA) D4h(FUA) D5h(FUA) D8h(FUA)
[+] Plextor flush command: accepted (status = 0)
[+] Plextor flush tests:
info: using command BEh
info: 5 test(s), c/nc ratio: 4, burst: 1, max: 1000
59.42 ms / 0.73 ms -> 50.97 ms / 17.93 ms
49.97 ms / 0.78 ms -> 50.46 ms / 17.87 ms
51.11 ms / 0.67 ms -> 44.83 ms / 17.47 ms
51.32 ms / 0.70 ms -> 57.77 ms / 18.15 ms
51.25 ms / 0.68 ms -> 51.23 ms / 18.16 ms
result: 5/5



IPB Image
greynol
Jun 28 2008, 13:05
Generally speaking when using cache explorer, you want to do more than 5 passes (I recommend 16); but because you are getting Read Errors the FUA command is indeed working properly.

Although you didn't mention it, EAC's test for caching is also inconclusive and should not be used to test the -usefua switch.

This is OT, but I notice you've got the Error recovery quality level set to high. While this may help in getting an accurate rip in some instances, it also increases your chances of getting consistent errors without EAC reporting suspicious positions.
RBI Champ
Jun 28 2008, 19:14
greynol, thanks for the assistance.

Per your recommendation, I've set "error recovery quality" to medium. In what circumstances should I change it back to the "high" setting?

I've also ran the cachex tests with 16 passes. The results are below. Do they look ok? Anything I should be concerned about?

CODE

cachex.exe -p -r 0xd8 -n 16 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is PLEXTOR CD-R PREMIUM2 1.03

[+] Plextor flush command: accepted
[+] Plextor flush tests: 16/16

------------------------------

cachex -i -c -n 16 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is PLEXTOR CD-R PREMIUM2 1.03

[+] Buffer size: 8192 kB, read cache is enabled
[+] Supported read commands: BEh A8h(FUA) 28h(FUA) D4h(FUA) D5h(FUA) D8h(FUA)
[+] Testing cache line size:
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
571 kB / 249 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
1171 kB / 510 sectors
266 kB / 116 sectors
1171 kB / 510 sectors

----------------------

cachex -i -p -d -n 16 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is PLEXTOR CD-R PREMIUM2 1.03

[+] Buffer size: 8192 kB, read cache is enabled
[+] Supported read commands: BEh A8h(FUA) 28h(FUA) D4h(FUA) D5h(FUA) D8h(FUA)
[+] Plextor flush command: accepted (status = 0)
[+] Plextor flush tests:
info: using command BEh
info: 16 test(s), c/nc ratio: 4, burst: 1, max: 1000
45.00 ms / 0.74 ms -> 43.40 ms / 18.47 ms
48.35 ms / 0.70 ms -> 47.93 ms / 24.13 ms
48.39 ms / 0.69 ms -> 49.01 ms / 19.53 ms
49.07 ms / 0.74 ms -> 49.04 ms / 18.16 ms
48.96 ms / 0.70 ms -> 48.98 ms / 24.67 ms
48.96 ms / 0.67 ms -> 48.96 ms / 24.69 ms
49.09 ms / 0.67 ms -> 49.02 ms / 24.70 ms
49.00 ms / 0.61 ms -> 49.10 ms / 22.55 ms
49.00 ms / 1.51 ms -> 42.55 ms / 18.16 ms
49.01 ms / 0.70 ms -> 48.92 ms / 18.16 ms
49.02 ms / 0.73 ms -> 48.97 ms / 18.13 ms
48.99 ms / 0.57 ms -> 42.41 ms / 24.63 ms
49.08 ms / 2.49 ms -> 48.96 ms / 18.17 ms
48.99 ms / 0.75 ms -> 49.08 ms / 17.46 ms
42.46 ms / 0.58 ms -> 49.02 ms / 18.12 ms
42.48 ms / 0.69 ms -> 48.99 ms / 18.13 ms
result: 16/16

Moderation: Changed code to codebox and removed unnecessary quotation.
greynol
Jun 29 2008, 17:29
I would change the error recovery setting it to high when ripping discs that give suspicious positions, though I'd probably try throttling the speed down to 8x or 4x first. When EAC requires 3 or more sets of re-reads, I start to become skeptical about the results. In these situations I would turn to AR results if possible or settle for matching results from a different (non-Plextor) drive; matching CRCs from the same drive don't give me much confidence. This is especially true when you see EAC repeat more than one CRC.

With cachex saying 16/16 you aren't going to have any problems, but because you're able to see a Read Error running cachex wasn't necessary.

That screenshot you provided was perfect. Next time someone asks about sync errors and read errors and where they can be found we can point to your post. Thank you! smile.gif
RBI Champ
Jun 29 2008, 20:32
greynol, thanks for the confirmation. This just seems to good to be true. After being stuck in the 8X (maybe 9X range on a good day), its hard to believe this is for real! smile.gif

I've run through 20 or so cd's and I've even seen the speed hit 30X (20X range still the average). I'd have to say this overpriced drive is now paying off.
greynol
Jun 29 2008, 22:39
Are you using C2 pointers as well? With my PX-716, -usefua doesn't buy me much just by itself.
RBI Champ
Jun 30 2008, 05:02
I have "Drive is capable of retrieving C2 error information" checked in EAC's drive options (under the extraction method tab). Is that what you mean?

Here is a recent EAC log:

CODE

Exact Audio Copy V0.99 prebeta 4 from 23. January 2008

EAC extraction logfile from 29. June 2008, 22:20

Pearl Jam / Who You Are (Single)

Used drive : PLEXTOR CD-R PREMIUM2 Adapter: 1 ID: 0

Read mode : Secure
Utilize accurate stream : Yes
Defeat audio cache : No
Make use of C2 pointers : Yes

Read offset correction : 30
Overread into Lead-In and Lead-Out : Yes
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks : No
Null samples used in CRC calculations : Yes
Used interface : Native Win32 interface for Win NT & 2000
Gap handling : Not detected, thus appended to previous track

Used output format : User Defined Encoder
Selected bitrate : 1024 kBit/s
Quality : High
Add ID3 tag : No
Command line compressor : C:\Program Files\FLAC\REACT.exe
Additional command line options : REACT %o %s %d "%a" "%g" "%t" "%n" "%x" "%y" "%m" "%e" "%f" "%b" %r


TOC of the extracted CD

Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.00 | 3:55.17 | 0 | 17641
2 | 3:55.17 | 3:36.15 | 17642 | 33856


Track 1

Filename "Who You Are.flac"

Peak level 99.4 %
Track quality 99.9 %
Copy CRC 1B3A8201
Accurately ripped (confidence 5) [B0CF313F]
Copy OK

Track 2

Filename "Habit.flac"

Peak level 98.0 %
Track quality 100.0 %
Copy CRC D40E4505
Accurately ripped (confidence 5) [E0CA1022]
Copy OK


All tracks accurately ripped

No errors occurred

End of status report


QUOTE(greynol @ Jun 30 2008, 00:39) *

Are you using C2 pointers as well? With my PX-716, -usefua doesn't buy me much just by itself.

greynol
Jun 30 2008, 09:00
QUOTE(RBI Champ @ Jun 30 2008, 04:02) *
I have "Drive is capable of retrieving C2 error information" checked in EAC's drive options (under the extraction method tab). Is that what you mean?
Yep.

I would also recommend performing a test pass (F8) when AR can't verify. Your Plextor probably provides accurate C2 error information, but you can't be too careful. Considering that you're now getting speeds comparable to burst mode, it's a small price to pay. If you can instead generate a matching test CRC with a different drive, that's even better.
RBI Champ
Jun 30 2008, 11:29
So if I extract a disc that "Cannot be verified as accurate" according to AccurateRip, I should leave the disc in and hit F8 for a "second opinion." Or optionally put it in my secondary drive and see how it does (CRC wise from my "new" EAC log from this secondary drive)?

I just ran some more discs through and saw a new record speed of 36.6X. This was around the 7th track of Frank Zappa "Joe's Garage" (Disc 2).

The next disc I did peaked out around 34X and I took a screen shot to be sure I wasn't seeing things. smile.gif I've included the EAC log beneath the screen shot. When I see something like this I should be excited and not concerned. This is really going to take some getting used to.

IPB Image

CODE

Exact Audio Copy V0.99 prebeta 4 from 23. January 2008

EAC extraction logfile from 30. June 2008, 13:19

The Black Crowes / Amorica (Banned Cover Version)

Used drive : PLEXTOR CD-R PREMIUM2 Adapter: 1 ID: 0

Read mode : Secure
Utilize accurate stream : Yes
Defeat audio cache : No
Make use of C2 pointers : Yes

Read offset correction : 30
Overread into Lead-In and Lead-Out : Yes
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks : No
Null samples used in CRC calculations : Yes
Used interface : Native Win32 interface for Win NT & 2000
Gap handling : Not detected, thus appended to previous track

Used output format : User Defined Encoder
Selected bitrate : 1024 kBit/s
Quality : High
Add ID3 tag : No
Command line compressor : C:\Program Files\FLAC\REACT.exe
Additional command line options : REACT %o %s %d "%a" "%g" "%t" "%n" "%x" "%y" "%m" "%e" "%f" "%b" %r


TOC of the extracted CD

Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.32 | 5:08.30 | 32 | 23161
2 | 5:08.62 | 4:46.68 | 23162 | 44679
3 | 9:55.55 | 4:01.57 | 44680 | 62811
4 | 13:57.37 | 5:56.70 | 62812 | 89581
5 | 19:54.32 | 4:16.20 | 89582 | 108801
6 | 24:10.52 | 5:48.55 | 108802 | 134956
7 | 29:59.32 | 3:39.10 | 134957 | 151391
8 | 33:38.42 | 5:39.25 | 151392 | 176841
9 | 39:17.67 | 5:32.73 | 176842 | 201814
10 | 44:50.65 | 3:41.17 | 201815 | 218406
11 | 48:32.07 | 5:39.65 | 218407 | 243896


Track 1

Filename "Gone.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC 179377D2
Accurately ripped (confidence 43) [834733F8]
Copy OK

Track 2

Filename "A Conspiracy.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC FB073805
Accurately ripped (confidence 43) [EFAE143C]
Copy OK

Track 3

Filename "High Head Blues.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC E0FF194B
Accurately ripped (confidence 43) [4DD7E774]
Copy OK

Track 4

Filename "Cursed Diamond.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC 8BFAF435
Accurately ripped (confidence 43) [E1A1BBA9]
Copy OK

Track 5

Filename "Nonfiction.flac"

Peak level 100.0 %
Track quality 99.9 %
Copy CRC 13437719
Accurately ripped (confidence 43) [9D1EE01B]
Copy OK

Track 6

Filename "She Gave Good Sunflower.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC 08145823
Accurately ripped (confidence 42) [ADF3C871]
Copy OK

Track 7

Filename "P. 25 London.flac"

Peak level 99.9 %
Track quality 100.0 %
Copy CRC B6FBC1A9
Accurately ripped (confidence 42) [B4592F91]
Copy OK

Track 8

Filename "Ballad In Urgency.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC D3AFD0A6
Accurately ripped (confidence 42) [29AA3092]
Copy OK

Track 9

Filename "Wiser Time.flac"

Peak level 100.0 %
Track quality 100.0 %
Copy CRC 20793F81
Accurately ripped (confidence 42) [C5231891]
Copy OK

Track 10

Filename "Downtown Money Waster.flac"

Peak level 100.0 %
Track quality 99.9 %
Copy CRC B7588D1A
Accurately ripped (confidence 42) [7D6E3A76]
Copy OK

Track 11

Filename "Descending.flac"

Peak level 99.9 %
Track quality 100.0 %
Copy CRC 15335E74
Accurately ripped (confidence 42) [05E2372E]
Copy OK


All tracks accurately ripped

No errors occurred

End of status report




QUOTE(greynol @ Jun 30 2008, 11:00) *

I would also recommend performing a test pass (F8) when AR can't verify. Your Plextor probably provides accurate C2 error information, but you can't be too careful. Considering that you're now getting speeds comparable to burst mode, it's a small price to pay. If you can instead generate a matching test CRC with a different drive, that's even better.
greynol
Jun 30 2008, 13:14
QUOTE(RBI Champ @ Jun 30 2008, 10:29) *
So if I extract a disc that "Cannot be verified as accurate" according to AccurateRip, I should leave the disc in and hit F8 for a "second opinion." Or optionally put it in my secondary drive and see how it does (CRC wise from my "new" EAC log from this secondary drive)?

I think so, yes. The reason being is that with the exception of synchronization, EAC will only read the disc once and solely rely on your drive's ability to fully and correctly report any and all errors when ripping with C2 pointers.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.