Mark Lanctot;207308 Wrote: > I'm going with what Rubyripper reports in its logs. It lists an MD5 > checksum for each track in the log. They didn't match rip-to-rip.
I'm not sure how rubyripper generates this md5 checksum, but depending on header information, this has the potential to give misleading info. A similar trap means that WAVs encoding identical sound information can have completely different checksums. In other words, I'm not sure that your test is actually comparing the important information (ie the sound) between the different rips. I'd be very interested to know whether the resultant FLAC files from the 2 drives have the same md5 checksum as generated by "metaflac --show-md5sum filename.flac" - as far as I understand, this command just compares the sound rather than the entire files. I'm not trying to be critical btw - I'm keenly interested in this topic, because I'm quite anal about ripping correctly and I've been using rubyripper in an attempt to get a "perfect" rip... :) -- bukharin ------------------------------------------------------------------------ bukharin's Profile: http://forums.slimdevices.com/member.php?userid=10859 View this thread: http://forums.slimdevices.com/showthread.php?t=35895 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
