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.