Help - Search - Members - Calendar
Full Version: Rubyripper MP3 MD5Sums dont match lame/grip's
Hydrogenaudio Forums > CD-R and Audio Hardware > CD Hardware/Software
Zaskar
Been doing more tests with Rubyripper, between it and grip.
Both programs wav files match up when comparing md5sum's. But their encoded mp3's dont. The file size matches up exactly to the byte though.

Now when I encode either of those wave files using lame in command line with the same switches, the file's md5sum matches the one from Grip.

So, whats Rubyripper doing differently? I notice it doesnt say that Lame is a dependency on its readme, is it using a slightly older version of lame thats compiled right into the program, and maybe thats whats causing the difference? (the fact that the file sizes are the same is just weird though)

Anyone able to enlighten me as to what it is doing different?

Thanks
Heliologue
RubyRipper uses encoder binaries in your PATH for its presets. Dunno what you've got Grip set up to use. Or what you're using on the command line.

Can you post your settings for each program?
Zaskar
QUOTE(Heliologue @ Aug 31 2007, 13:37) *

RubyRipper uses encoder binaries in your PATH for its presets. Dunno what you've got Grip set up to use. Or what you're using on the command line.

Can you post your settings for each program?

Rubyripper:
"-q 0 -b 320" next to "Lame Mp3"

Grip:
/usr/bin/lame
-q 0 -b %b %w %m
bitrate set to 320
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.