Which CD DAE software is the most accurate for Mac OS X?, Is XLD the most accurate with feature set? Options

[macman4hire]

I notice an incorrect entry on your ripper comparison chart: xACT does NOT have a "verify suspicious sectors" option, nor does it verify them.

Also, xACT does query Freedb (you can see it on the log), although it will not actually title the tracks on output. One problem with xACT is that the developer made it a "run only" application, so you cannot edit the app. I believe this may be a violation of the cdparanoia GPL, but what do I know?

CODE

cdda2wav: There is no sound support configured!
Type: ROM, Vendor 'SONY ' Model 'DVD RW DW-D150A ' Revision '1.MD' MMC+CDDA
176128 bytes buffer memory requested, transfer size 32768 bytes, 4 buffers, 13 sectors
#Cdda2wav version 2.01.01a28_darwin_8.10.1_i386_i386, libparanoia support
AUDIOtrack pre-emphasis copy-permitted tracktype channels
1-13 no no audio 2
Table of Contents: total tracks:13, (total time 66:23.13)
1.( 5:22.50), 2.( 5:48.73), 3.( 5:04.00), 4.( 7:40.50), 5.( 2:35.60),
6.( 8:20.62), 7.( 7:53.05), 8.( 2:32.05), 9.( 5:42.05), 10.( 1:59.70),
11.( 6:45.18), 12.( 1:18.17), 13.( 5:19.48)

Table of Contents: starting sectors
1.( 32), 2.( 24232), 3.( 50405), 4.( 73205), 5.( 107755),
6.( 119440), 7.( 157002), 8.( 192482), 9.( 203887), 10.( 229542),
11.( 238537), 12.( 268930), 13.( 274797), lead-out( 298770)
CDINDEX discid: R2nrzEhgxe9Io70AQkUL_6wpHNs-
CDDB discid: 0xcc0f8f0d CDDBP titles: resolved
CD-Text: not detected
CD-Extra: not detected
Album title: 'Kiss My Axe' [from Al Di Meola]
Track 1: 'South Bound Traveler'
Track 2: 'The Embrace'
Track 3: 'Kiss My Axe'
Track 4: 'Morocco'
Track 5: 'Gigi's Playtime Rhyme (Interlude #1)'
Track 6: 'One Night Last June'
Track 7: 'Phantom'
Track 8: 'Erotic Interlude (Interlude #2)'
Track 9: 'Global Safari'
Track 10: 'Interlude #3'
Track 11: 'Purple Orchids'
Track 12: 'The Prophet (Interlude #4)'
Track 13: 'Oriana (September 24, 1988)'
samplefile size will be 13799228 bytes.
recording 78.2266 seconds stereo with 16 bits @ 44100.0 Hz ->'audio'...
using lib paranoia for reading.
percent_done:
0%
0%
1%
2%
3%
4%
5%
6%
7%
8%
9%
10%
11%
12%
13%
14%
15%
16%
17%
18%
19%
20%
21%
22%
23%
24%
25%
26%
27%
28%
29%
30%
31%
32%
33%
34%
35%
36%
37%
38%
39%
40%
41%
42%
43%
44%
45%
46%
47%
48%
49%
50%
51%
52%
53%
54%
55%
56%
57%
58%
59%
60%
61%
62%
63%
64%
65%
66%
67%
68%
69%
70%
71%
72%
73%
74%
75%
76%
77%
78%
79%
80%
81%
82%
83%
84%
85%
86%
87%
88%
89%
90%
91%
92%
93%
94%
95%
96%
97%
98%
99%
100% track 12 'The Prophet (Interlude #4)' recorded with minor problems (1.2% problem sectors)

100% 0 rderr, 0 skip, 72 atom, 0 edge, 0 drop, 0 dup, 0 drift

100% 81 overlap(0.5 .. 0.5)

Pepzhez I will change Mac CD Ripper Comparison Chart to reflect the fact xACT does query Freedb placing the info in the log only after the rip is completed and currently does does write tags to outputted files. I will clarify that xACT does not verify suspicious sector but does report problem sector % in the log, I did not make this clear getting lazy! Thanks for the correction.

This post has been edited by macman4hire: Sep 7 2008, 12:36

[macman4hire]

I have created a comparison for three CD rippers that use CDParanoia on the Mac. This comparison is in know way a definitive comparison as the feature sets of these applications constantly change. Please contact me if any information appears inaccurate or you feel a crucial feature has been omitted.

From the other thread on this subject, I think it's not yet entirely clear that XLD actually disables the drives cache.

Click here to learn more about the status of XLD and CDParanoia capability to disable the drives cache from this thread posted September 12,2008.

[jhart71]

I'm new to XLD - just downloaded and started learning about it today.

I noticed that there has been some discussion/debate about the new version of CDParanoia and also of drive cache disabling. There are a few posts on this very thread that show before/after rip logs that have different results.

My question: if an XLD rip matches the AccurateRip database, and all the log results are "0" (with an accurate rip confidence factor of 200) is that not an accurate rip? I see how turning cache on/off might affect the results, but wouldn't that result in a questionable rip log?

For the record (and for any further advice) here are my settings:

Version: 20080913 (89.0)
Drive offset: 48 (Pioneer DVD-RW DRV-106D)
Disable cache: OFF
Test before copy: only when track does not exist in AccurateRip DB

Any help is appreciated.

[Pepzhez]

My question: if an XLD rip matches the AccurateRip database, and all the log results are "0" (with an accurate rip confidence factor of 200) is that not an accurate rip? I see how turning cache on/off might affect the results, but wouldn't that result in a questionable rip log?

If a confidence level of 200 isn't an accurate rip, I don't know what is.

Would turning cache on or off result in a questionable log? Experience tells me "not necessarily." You can try ripping it both ways and comparing logs for differences (if there are any).

[jhart71]

I just ripped the same track twice - once with the "Disable cache" checked, and one with it unchecked.

I compared the result logs side-by-side, and they are identical (both are confidence 200 rips with "0" in all the line-item fields). Would that be indicative of what I can expect across the board in regards to cache performance/effectiveness?

And, having said that - which setting (disable or not) do most people use?

[tim.lance]

I just ripped the same track twice - once with the "Disable cache" checked, and one with it unchecked.

I compared the result logs side-by-side, and they are identical (both are confidence 200 rips with "0" in all the line-item fields). Would that be indicative of what I can expect across the board in regards to cache performance/effectiveness?

And, having said that - which setting (disable or not) do most people use?

Was that track a previously "troublesome" track? Doesn't sound like it.

[jhart71]

I just ripped the same track twice - once with the "Disable cache" checked, and one with it unchecked.

I compared the result logs side-by-side, and they are identical (both are confidence 200 rips with "0" in all the line-item fields). Would that be indicative of what I can expect across the board in regards to cache performance/effectiveness?

And, having said that - which setting (disable or not) do most people use?

Was that track a previously "troublesome" track? Doesn't sound like it.

You're right, but I don't have many troublesome CDs or tracks. I've never used Accurate Rip or a log until today. Right now I'm doing a little research to get the right settings before I start ripping en masse.

[tim.lance]

You're right, but I don't have many troublesome CDs or tracks. I've never used Accurate Rip or a log until today. Right now I'm doing a little research to get the right settings before I start ripping en masse.

Yeah, I had to go get some from the library. I did have some with rot but the rest are well kept. Keep us informed.

[gloog]

I have created a comparison for three CD rippers that use CDParanoia on the Mac.

I'd like contribute to this summary with a little research on very important subject, completely omitted in any XLD-related topic. It is a question of Pre-Emphasis.

I've found the only solution how to correctly detect PRE flag, and it is provided by xAct, only as a result log that is not even saved with rip.

Log looks like this (check the last two lines):

CODE

cdda2wav: There is no sound support configured!
Type: ROM, Vendor 'TSSTcorp' Model 'CDDVDW SH-S202N ' Revision 'SB01' MMC+CDDA
176128 bytes buffer memory requested, transfer size 32768 bytes, 4 buffers, 13 sectors
cdda2wav: Read TOC CD Text failed (probably not supported).
#Cdda2wav version 2.01.01a28_darwin_8.10.1_i386_i386, libparanoia support
cdda2wav: Host is down. Cddb connect failed.
AUDIOtrack pre-emphasis  copy-permitted tracktype channels
      1-10          yes              no     audio    2

How to handle such CD is another question, probably best solution is to burn on CD-R using reliable sw with PRE flag set ON. Toast supports this, but does not read this setting from CUE. It has to be set manually.

For those who want to play files from computer, there are some options: iTunes 7 during ripping performs frequency equalization similar to the one provided by stand-alone CD player, when encounters a PRE flag. The resulting Wav file is of course not a bit-perfect copy of a CD track. Any other ripping sw ignores this. Only some rippers can write correct PRE flag on the CUE sheet [like EAC], bot none on Mac OS-X. Playback with equalization on-the-fly is only possible in Foobar2000 / Win.

So for this reason, line containing Pre-Emphasis should be added to the table, with important benefit of xAct allowing to detect it, at least, and there's also a recommendation to XLD developer to consider implementing of proper PRE flag reading and logging.