Quote:
Originally Posted by majkel /img/forum/go_quote.gif
3) try to extract "unnecessary" bits from the 320kb/s mp3 file, I forgot the name of the executable which does that trick. In 320kb/s, especially FhG it finds no spare bits.
|
Not unused, no, but useful? Depends on the listener. If you can't hear them, it's pointless to keep them. -V0 gives the encoder a chance to discard more where it believes it can, but whether it works out depends on the accuracy of that decision.
The way CBR works (roughly), the encoder iteratively picks frequency bands to make less accurate, then checks with the psy model to see if it's done any audible damage to the sound yet. It stops when it finds an acceptable result at the bitrate you asked for (or picks the best it can do if it can't get it perfect -- no miracles at 128kbps!). If you ask for 320bkps, it will use every bit of it, without even considering the possibility it could have used less.
Quote:
Originally Posted by majkel /img/forum/go_quote.gif
-V0 doesn't even reach the 256kb/s quality level - just because of the fact of lower bitrate. Don't believe in miracles that less bits will sound better.
|
It's around 700kbps. If I had to pick doing that or using 128kbps mp3 for my music, I'd pick the mp3. Efficiency, and not just raw bitrate, matters.
Yes, thanks to the bit reservoir, 256kbps mp3 can effectively reach 320kbps... for a very short time, until the reservoir is depleted. It has a very small fixed maximum size. -V0 is free to encode every frame at 320kbps if it feels the need. I've seen it average well above 256kbps.
Then again, if you don't trust the VBR mode, 320kbps CBR should never sound worse. The worst risk is a potential waste of space.