EAC is ripping songs at what seems like random bitrates- like I'll rip an album, and the bitrates of the songs will be all messed up. Most will be 320, some will be 192 or 256, and there was one that was at 224 (?) even though I have the command line parameters set to rip at VBR around 192 (according to the wiki).
I had it working before but I messed around with the command line and now I can't get it to work again. Does anyone know what I might be doing wrong?
Full Version: Random bitrate problem
QUOTE (dazedd @ Sep 21 2008, 23:22) 
EAC is ripping songs at what seems like random bitrates- like I'll rip an album, and the bitrates of the songs will be all messed up. Most will be 320, some will be 192 or 256, and there was one that was at 224 (?) even though I have the command line parameters set to rip at VBR around 192 (according to the wiki).
I had it working before but I messed around with the command line and now I can't get it to work again. Does anyone know what I might be doing wrong?
I had it working before but I messed around with the command line and now I can't get it to work again. Does anyone know what I might be doing wrong?
It sounds like you might be relying on Windows to tell you the bitrate. It is wildly inaccurate. I'm not sure what it's doing exactly, but from general appearances it seems to be only telling you the bitrate of the first frame or first few frames.
Post your command line you have put in EAC for lame.
Post the rest of the settings you have configured on the External Compression tab as well.
What do you have configured for the Parameter passing scheme?
What do you have configured for the Parameter passing scheme?
QUOTE (benski @ Sep 21 2008, 21:44)
QUOTE (dazedd @ Sep 21 2008, 23:22)
EAC is ripping songs at what seems like random bitrates- like I'll rip an album, and the bitrates of the songs will be all messed up. Most will be 320, some will be 192 or 256, and there was one that was at 224 (?) even though I have the command line parameters set to rip at VBR around 192 (according to the wiki).
I had it working before but I messed around with the command line and now I can't get it to work again. Does anyone know what I might be doing wrong?
It sounds like you might be relying on Windows to tell you the bitrate. It is wildly inaccurate. I'm not sure what it's doing exactly, but from general appearances it seems to be only telling you the bitrate of the first frame or first few frames.
Yeah, that might be it- I'm just hovering over the files in windows explorer to see the bitrates...
My command line options:
-V 2 --vbr-new --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" %s %d
And here's a screenshot of my external compression options:
Thanks for putting up the information. Benski was right, the problem is with Windows not being able to display VBR bitrates correctly.
Your command line looks fine, but you should either use Lame to tag or check "Add ID3 tag" but not both.
If you're using Lame 3.98, I'd just use -V2 %s %d (--vbr-new is no longer necessary), and let EAC tag your files.
If you're using Lame 3.97, I'd just use -V2 --vbr-new %s %d, and definitely let EAC tag your files.
Your command line looks fine, but you should either use Lame to tag or check "Add ID3 tag" but not both.
If you're using Lame 3.98, I'd just use -V2 %s %d (--vbr-new is no longer necessary), and let EAC tag your files.
If you're using Lame 3.97, I'd just use -V2 --vbr-new %s %d, and definitely let EAC tag your files.
QUOTE (greynol @ Sep 21 2008, 23:57)
Thanks for putting up the information. Benski was right, the problem is with Windows not being able to display VBR bitrates correctly.
Your command line looks fine, but you should either use Lame to tag or check "Add ID3 tag" but not both.
If you're using Lame 3.98, I'd just use -V2 %s %d (--vbr-new is no longer necessary), and let EAC tag your files.
If you're using Lame 3.97, I'd just use -V2 --vbr-new %s %d, and definitely let EAC tag your files.
Your command line looks fine, but you should either use Lame to tag or check "Add ID3 tag" but not both.
If you're using Lame 3.98, I'd just use -V2 %s %d (--vbr-new is no longer necessary), and let EAC tag your files.
If you're using Lame 3.97, I'd just use -V2 --vbr-new %s %d, and definitely let EAC tag your files.
I opened up the files in Mp3tag and the bitrates looked normal.
I'll switch the command line, then- Thanks for your help!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.