|
|
Welcome to the Exploding Garrmondo Weiner Interactive Swiss Army Penis. |
GFF is a community of gaming and music enthusiasts. We have a team of dedicated moderators, constant member-organized activities, and plenty of custom features, including our unique journal system. If this is your first visit, be sure to check out the FAQ or our GFWiki. You will have to register before you can post. Membership is completely free (and gets rid of the pesky advertisement unit underneath this message).
|
|
Thread Tools |
Encoding mp3s: min. bitrate advisable for VBR?
So recently I've taken to specifying an extremely low minimum bitrate in my VBR encoding, along the lines of 32kbps or less. While setting the max bitrate to 320, and even with a quality of 0 or 1, the filesizes are still relatively pretty small.
Is there a drawback to this? Despite the drastically reduced filesize, I can't imagine there'd be any significant quality loss, right? I mean, the 320 is still applied when necessary, but in places of quiet/low dynamics, it can go all the way down to 32 if need be. I was pretty surprised when I encoded a four-disc recording of one of Wagner's operas and the total size of the collection was less than 200MB. Anyone see a problem with this? Jam it back in, in the dark. |
All in the ears. If you don't hear anything wrong, hey, you just won at life. Or at least file encoding...
Personally, I lower bitrates of songs all the time for ones that don't matter. Podcasts, and the skit stuff can all go down. Songs, too, when there isn't anything happening, your ears won't be able to differentiate the low noises that are usually just "filler." There's nowhere I can't reach.
It turns out that today is opposite day, so all of what you have said is true, so you should probably just go.
|
Well, if there's a lot of silence in something, I could definitely see that helping out with the filesize. Sceptre's right though--if it sounds the same to you, who gives a crap?
This thing is sticky, and I don't like it. I don't appreciate it. |
What tool are you using to encode your MP3s? I would just totally ignore minimum & maximum bitrate settings. After all, some frames will legitimately need 320Kbps to sound good (limiting the maximum is never a good idea), and the encoder will go as low as 32Kbps where the audio is completely silent. Use the latest recommended LAME (3.97 final) and the setting -V 2 --vbr-new as detailed in my ripping and encoding guide.
There's usually no problem with VBR resulting in lower-bitrate files, assuming you're using a good encoder & setting. The MP3 encoder merely determined those were the bitrates needed to reach the level of quality you specified. I've had -- using -V 2 --vbr-new -- some piano CDs where many of the resulting MP3s' average bitrates dipped slightly below 128Kbps, just because the tonal complexity was that low. Classical recordings can tend to have lowish bitrates as well. Conversely, metal and electronica stereotypically push the bitrates up due to heavy use of distortion and percussion, both of which make the audio more 'noisy' than purely tonal. (Although that's really a simplification.) And there are always exceptions, too, so you shouldn't really worry about the bitrates you end up with in a VBR file. Most amazing jew boots Good morning, post-apocalyptia!
Last edited by Moguta; Dec 3, 2006 at 01:22 PM.
|
I'm using a program called Switch. It's handy and a front-end interface. Honestly I don't know if it uses LAME or not since nowhere in the program is it specified what mp3 encoder it uses. I used to use RazorLame, which I enjoyed, but I got a lot of errors with it and pissed me off.
Most of the stuff I encode is orchestral. Otherwise I wouldn't worry about it, but since this includes a lot of very quiet music, it was worth bringing up. I was speaking idiomatically. |
What kind of toxic man-thing is happening now?
It turns out that today is opposite day, so all of what you have said is true, so you should probably just go.
|
I honestly can't see whether Switch uses LAME having looked throughout the webpage, either. Seeing it's a shareware (or at least upgrade-to-PRO-ware) program, I'd kinda doubt it. That's not what you call a front-end either. Instead, it's a term for applications that merely provide a graphical interface for a program that you must already have, like how RazorLAME requires you to have a version of the LAME encoder.
I love Multi Frontend because it simply acts as a "dock" between your different encoders & decoders. How these formats are transcoded is dependent entirely on the specific encoders/decoders and settings you plug into it. I like having that power, rather than relying blindly on a program that just says "convert to MP3" using whatever unspecified methods and settings were coded into it. There have been some horrible encoders in the past, and who's to say lazy developers might not pick something random as long as it encodes to that magic three-letter MP3 format, not giving much thought to quality. FELIPE NO Good morning, post-apocalyptia!
Last edited by Moguta; Dec 4, 2006 at 11:17 PM.
|
Wark! |
I dunno why you are trying. Your mp3 setting WILL be worse quality than the presets (-V0 to -V9).
The presets are created by people who actually know how mp3 works internally (that is not you or me) and tested numerous times by people with good hearing and ability to recognize of mp3 artifacts. Mp3 encoding is all about trade-offs. You can't have both perfect quality AND a low average bitrate. You have to find some compromise between quality and bitrate (+ the many other settings). The lame developers already did that for each bitrate range with the presets. If you want low bitrate than you should just use -V4 or whatever. Btw. All vbr presets already use 32kbps for pure silence. What, you don't want my bikini-clad body? |
If you didn't mean anything to the contrary of what I said, then I at least want to clarify for others. ^^ And I agree with everything else you had to say. Jam it back in, in the dark. Good morning, post-apocalyptia!
Last edited by Moguta; Dec 5, 2006 at 09:10 PM.
|