Help - Search - Members - Calendar
Full Version: --preset standard aka -V2 --vbr-new
Hydrogenaudio Forums > Lossy Audio Compression > MP3 > MP3 - Tech
Squeller
Hey,

I encode some stuff with the 3.97a10, which works quite well. I use -V2 --vbr-new.

What I see is, theres often many samples (>80%) encoded in 192k, 10% in 160 and 10% 224.

I know it depends on the source material, but this is pretty obvious. In other versions (or was it in vbr old) there was a wider spreading of the bitrates, which, I may be wrong, to me feels like being more realistic, adaptive and better.

Someone else recognized this?
beto
This thread might help.
VCSkier
i remember hearing this mentioned briefly in another thread a while ago. it might have been the official 3.97a10 release thread, or maybe one of the other many threads asking about it. but i believe gabriel may even have mentioned it, or at least been present in the general discussion, but no specific reason was given for the less spread distribution of frame bitrates. i too am curious about this apparent contradiction, but i guess as long as the quality turns out as good, it doesn't matter how they do it. the things those dev's can do never ceases to amaze me.

edit: iirc, all --vbr-new files had this tendency, to be less distributed
Madrigal
In this thread, timcupery appears to have experienced a narrower bitrate spread with --vbr-new as well.

Regards,
Madrigal
timcupery
Thanks Madrigal, I was just wondering if I'd have to build a link to that previous thread. Not that the issue ever got resolved. I still have semi-distrust of --vbr-new because it seems that effective VBR would be spreading the frame sizes around more depending on complexity of each frame being encoded. However, I can't argue with testing showing that --vbr-new (in 3.97a10) is outperforming the old vbr algorithm...
ChiGung
QUOTE(timcupery @ Jun 28 2005, 02:19 AM)
Thanks Madrigal, I was just wondering if I'd have to build a link to that previous thread. Not that the issue ever got resolved. I still have semi-distrust of --vbr-new because it seems that effective VBR would be spreading the frame sizes around more depending on complexity of each frame being encoded. However, I can't argue with testing showing that --vbr-new (in 3.97a10) is outperforming the old vbr algorithm...
*


I think the bitrate spread may be related to a difference in how vbr-new uses the bitreservior compaired to vbr-old rather than the actual bits its giving each frame.
Its just a possibility, just noting that indicated framesize includes bitreservoir allocation so if eg vbrnew was using the reservoir more than old, it would allow the apparent framesize to be more restricted. 'So many variables - thats why the tests are the ultimate indicator.
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.