Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: XLD vs EAC (Read 11449 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

XLD vs EAC

I tried to search through the forums, but I must not be using the proper search strings. So please excuse me if this has been brought up before. I've been using EAC for years (by no means a power use, but I get good rips) and I've recently been looking into XLD since I use my MacBook more often than my PC desktop.

I'm trying to figure out the proper settings so that I can get identical rips from both EAC and XLD. I tried to do this earlier but with no success. I ripped a CD with EAC and generated an MD5 for the wav files. I then ripped the same CD with XLD, but they didn't pass the MD5 verification and when I generated a new MD5 on my Mac to compare, the values were completely different.

Is this not a valid test? Is there a better way to go about doing this? If so, what do my settings need to be for XLD to ensure that tracks ripped with that program will be the same as if they were done in EAC?

Many thanks
LBX

XLD vs EAC

Reply #1
Have you made sure that you have the correct offset configured for each of your drives?

Although md5 verification should work, I would make sure that the 32-bit CRCs for the raw PCM data between the two programs match and that null samples are being used in the calculations.

XLD vs EAC

Reply #2
I noticed that I needed to upgrade my version of EAC, which I did, and I also noticed that I needed to set the offset correction. Unfortunately, my cd drive isn't listed on the AccurateRip list (ASUS - CD-S520/A5) and I keep getting different offset values for Key discs I put in the drive.

Is there a sticky somewhere that I'm missing that helps troubleshoot or explains how to deal with these issues? I have a feeling this isn't the first time these questions have been asked, and the veterans here probably get tired of them....

Thanks for any help

EDIT:
I went back and configured the CD/DVD drive on my PC (I never use it because it pretty much sucks) and was able to get, what I believe is the proper set up rather easily. I did a test rip and the results are as follows:

From EAC:
Code: [Select]
Exact Audio Copy V0.99 prebeta 4 from 23. January 2008

EAC extraction logfile from 17. February 2009, 11:52

Creedence Clearwater Revival / Chronicle

Used drive  : TSSTcorpCD/DVDW TS-H552U  Adapter: 2  ID: 0

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

Read offset correction                      : 12
Overread into Lead-In and Lead-Out          : No
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 : Internal WAV Routines
Sample format      : 44.100 Hz; 16 Bit; Stereo


TOC of the extracted CD

    Track |  Start  |  Length  | Start sector | End sector
    ---------------------------------------------------------
        1  |  0:00.32 |  4:35.48 |        32    |    20704 
        2  |  4:36.05 |  4:32.02 |    20705    |    41106 
        3  |  9:08.07 |  3:08.73 |    41107    |    55279 
        4  | 12:17.05 |  2:20.05 |    55280    |    65784 
        5  | 14:37.10 |  3:11.27 |    65785    |    80136 
        6  | 17:48.37 |  2:34.08 |    80137    |    91694 
        7  | 20:22.45 |  2:42.65 |    91695    |  103909 
        8  | 23:05.35 |  2:44.57 |    103910    |  116266 
        9  | 25:50.17 |  2:20.18 |    116267    |  126784 
      10  | 28:10.35 |  2:09.22 |    126785    |  136481 
      11  | 30:19.57 |  2:29.15 |    136482    |  147671 
      12  | 32:48.72 |  2:42.43 |    147672    |  159864 
      13  | 35:31.40 |  3:06.07 |    159865    |  173821 
      14  | 38:37.47 |  2:32.48 |    173822    |  185269 
      15  | 41:10.20 |  3:34.22 |    185270    |  201341 
      16  | 44:44.42 | 11:06.35 |    201342    |  251326 
      17  | 55:51.02 |  2:39.73 |    251327    |  263324 
      18  | 58:31.00 |  2:42.57 |    263325    |  275531 
      19  | 61:13.57 |  2:55.53 |    275532    |  288709 
      20  | 64:09.35 |  4:01.45 |    288710    |  306829 


Track  9

    Filename C:\Documents and Settings\Owner\My Documents\My Music\09 Creedence Clearwater Revival - Fortunate Son.wav

    Peak level 82.4 %
    Track quality 99.8 %
    Copy CRC 3DF00B6D
    Accurately ripped (confidence 40)  [C294A07F]
    Copy OK


All tracks accurately ripped

No errors occurred

End of status report

From XLD:
Code: [Select]
X Lossless Decoder version 20090217 (101.1)

XLD extraction logfile from 2009-02-17 11:56:42 -0600

Creedence Clearwater Revival / Chronicle

Used drive : HL-DT-ST DVDRW  GSA-S10N (revision BP10)

Use cdparanoia mode    : YES (CDParanoia III 10.2 engine)
Disable audio cache    : OK for the drive with cache less than 2750KB
Make use of C2 pointers : NO
Read offset correction  : 667
Max retry count        : 100

TOC of the extracted CD
    Track |  Start  |  Length  | Start sector | End sector
    ---------------------------------------------------------
        1  | 00:00:32 | 04:35:48 |        32    |    20704 
        2  | 04:36:05 | 04:32:02 |    20705    |    41106 
        3  | 09:08:07 | 03:08:73 |    41107    |    55279 
        4  | 12:17:05 | 02:20:05 |    55280    |    65784 
        5  | 14:37:10 | 03:11:27 |    65785    |    80136 
        6  | 17:48:37 | 02:34:08 |    80137    |    91694 
        7  | 20:22:45 | 02:42:65 |    91695    |  103909 
        8  | 23:05:35 | 02:44:57 |    103910    |  116266 
        9  | 25:50:17 | 02:20:18 |    116267    |  126784 
      10  | 28:10:35 | 02:09:22 |    126785    |  136481 
      11  | 30:19:57 | 02:29:15 |    136482    |  147671 
      12  | 32:48:72 | 02:42:43 |    147672    |  159864 
      13  | 35:31:40 | 03:06:07 |    159865    |  173821 
      14  | 38:37:47 | 02:32:48 |    173822    |  185269 
      15  | 41:10:20 | 03:34:22 |    185270    |  201341 
      16  | 44:44:42 | 11:06:35 |    201342    |  251326 
      17  | 55:51:02 | 02:39:73 |    251327    |  263324 
      18  | 58:31:00 | 02:42:57 |    263325    |  275531 
      19  | 61:13:57 | 02:55:53 |    275532    |  288709 
      20  | 64:09:35 | 04:01:45 |    288710    |  306829 

List of alternate offset correction values
        #  | Absolute | Relative | Confidence
    ------------------------------------------
        1  |    474  |  -193  |    18   
        2  |  -874  |  -1541  |      3   
        3  |  -871  |  -1538  |      2   

Track 09
    Filename : /Users/Lunchbox/Desktop/09 Creedence Clearwater Revival - Fortunate Son.wav

    CRC32 hash            : 3DF00B6D
    CRC32 hash (skip zero) : 5CCE75D6
    AccurateRip signature  : C294A07F
        ->Accurately ripped! (confidence 40)
    Statistics
        Read error                          : 0
        Skipped (treated as error)          : 0
        Edge jitter error (maybe fixed)      : 0
        Atom jitter error (maybe fixed)      : 0
        Drift error (maybe fixed)            : 0
        Dropped bytes error (maybe fixed)    : 0
        Duplicated bytes error (maybe fixed) : 0
        Inconsistency in error sectors      : 0

No errors occurred

End of status report

Now it looks to me that the CRC hashes are the same and legit, I just want to make sure I'm reading this properly. Am I on my way, or is there more work to be done? Any help is appreciated.

Cheers,
LBX

XLD vs EAC

Reply #3
Are you using EAC's built-in test for determining offsets, or the automatic AccurateRip configuration?  Either way you can find your answer here:
http://wiki.hydrogenaudio.org/index.php?ti...p#Drive_Options

Unfortunately, getting inconsistent results is perfectly normal.  Different pressings of the same disc will have different offsets.

As for your drive, I have an ASUS 40X and an ASUS 50X.  Both require a read samples offset correction of +1858, but your 52X can easily be different.

XLD vs EAC

Reply #4
Safest (but slow) settings:
CDParanoia mode
No C2
No Old CDParanoia
Offset (drive specific)
Query AccurateRip
Verify suspicious sectors
Test before copy (when not in AccurateRip)

XLD is an excellent application. I like it very much. Finally the new version supports batch conversion.

The troubles you had were probably as suggested solely caused by different offsets.

 

XLD vs EAC

Reply #5
Safest (but slow) settings:
CDParanoia mode
No C2
No Old CDParanoia
Offset (drive specific)
Query AccurateRip
Verify suspicious sectors
Test before copy (when not in AccurateRip)

XLD is an excellent application. I like it very much. Finally the new version supports batch conversion.

The troubles you had were probably as suggested solely caused by different offsets.


What about the "Scan ReplayGain" option? Any special reason to ignore it?

Thanks in advance