different mp3 files from same command line
2002-03-13 06:45:50
I've been using lame recently to convert some favorite cds to mp3 for use over the summer... I was given a discman-type portable cd player that can handle mp3 discs, and it'll be nice to only bring 10 cd's to the Yosemite high country and still have 100+ albums worth of my favorite music. I'm encoding at --alt-preset cbr 128, this isn't for archival purposes or anything. I'm looking forward to the day when ogg or mpc receives good portable support, and then I'll think more about archiving. Anyway, I can rip wav files and send them to lamedrop, or set up EAC to run lame.exe as an external encoder, or use john33's cdex with the lame dll and --alt-preset support. However, each of these methods creates a different file. I test this by decoding the mp3 files back to wav (always using the same decoding method), and then using the "compare files" option on eac. It doesn't surprise me that CDex, using the lame dll, puts out a slightly different mp3 file for --alt-preset cbr 128 than does lame.exe. However, it seems strange that lame.exe will put out differing wav files depending on whether I call it up using EAC or Lamedrop. I've got all my options configured in EAC so that it should be just sending the same commandline that lamedrop does. for the record, this issue isn't one of burning importance. I can't hear a difference between the files from CDex lame dll, EAC-called lame.exe, or Lamedrop-called lame.exe. But it would still be cool to know what's up here.