Skip to main content

Topic: Getting two different MD5 values (Read 2231 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • darin
  • [*][*][*]
Getting two different MD5 values
I ripped a CD useing EAC to the hard drive with no errors reported. Afterwards, I used digestIT 2004 to take the MD5 value from the wav file I just ripped and I took the MD5 value from the same track on the Audio CD itself. I got two different values so does that mean that my CD Rom drive isn't ripping my music file 100% identical to the originial one? Even though EAC says 100% qaulity after ripping?

Thanks,
-Dman
Cowon Iaudio X5 30 gig. It rocks!

  • teleguise
  • [*][*][*]
Getting two different MD5 values
Reply #1
Without more information .. (like if EAC is configured correctly as per the recommended settings)

If so then.. No, it just simply means the method EAC reads a CDDA
track and digestIT 2004 does are different.

Offset correction, null sample settings etc.. can effect what is also contained in your
file. Which if all your after are good clean rips means poo and shouldn't confuse
you.

You could either use the Test & Copy function to compare the CRC's, rip it 2x manually
or if you don't trust the CRC, rip it 2x manually and compare the md5 hash values.

  • Jud
  • [*][*]
  • Members (Donating)
Getting two different MD5 values
Reply #2
Quote
I took the MD5 value from the same track on the Audio CD itself.
[a href="index.php?act=findpost&pid=319966"][{POST_SNAPBACK}][/a]

How did you do this?

edit: if you just did "Hash File" on the .cda file it only calculated the hash of the 44 byte header.
  • Last Edit: 14 August, 2005, 02:43:10 AM by Jud

  • darin
  • [*][*][*]
Getting two different MD5 values
Reply #3
I just right clicked on the Wav file and chose calculate MD5 value. Then I went to the drive letter of the CD rom, open the directory of the audio CD, and did the same MD5 calculation for that audio track on the audio CD itself.
Cowon Iaudio X5 30 gig. It rocks!

  • Jud
  • [*][*]
  • Members (Donating)
Getting two different MD5 values
Reply #4
Yeah, I don't think digestIT is DAE aware.  It's only calculating the MD5 of the 44 byte file that's shown to the file system.

If everything sounds good to you, I think you're doin' fine.