Here is the methodology I used in testing the MJ Ripper:
I used two versions of the same CD (One brand new and one older and badly scratched) and tested it two times by both MJ(secure mode) and EAC (secure mode). This is a total of 2 x 2 x 2 = 8 tests. The first four tests done while the rest of the computer was idle. The next four were done while I tried to “stress” the computer as much as possible – moving windows, playing music, opening applications etc. Here is a summary:
1. MJ, computer idle, new CD
2. EAC, computer idle, new CD
3. MJ, computer idle, old CD
4. EAC, computer idle, old CD
5. MJ, computer stressed, new CD
6. EAC, computer stressed, new CD
7. MJ, computer stressed, old CD
8. EAC, computer stressed, old CD
I used the .wav’s created from 2. above as the no error reference. MJ was always faster in execution of the ripping process than EAC.
What I found was this:
When the computer was idle, there was not a significant difference in performance between EAC and MJ
a. With the new CD, both rips were clean as tested against the EAC, idle, new CD reference.
b. The old CD produced similar errors in both EAC and MJ. On some tracks EAC produced more errors and on others MJ produced more errors.
When the computer was being stressed, the results from EAC were more or less the same as when the computer was idle. BUT… MJ created random errors in the .WAV when the computer was being stressed.
The last line is the spoiler for me. Is there anything the Media Jukebox developers can do to make the ripper output absolutely consistent regardless of what is going on in the rest of the computer? I STRONGLY prefer to use Media Jukebox from a convenience point of view – auto database update, auto cover art download, integrated interface etc.