Results about different scalings

I did I test over the Matrix and here are the results : Target : 1046532 Kb Internal : 1046624 Kb Koepi's : 1046528 Kb Nitrogen's : 1046614 Kb The average quantizer was excactly the same 2.503, the things tha changed were the number of I/P-Frames and the distribution of the quantizers.. MoonWalker

You have encoded the whole movie 3 times, just to test the scaling method? Bravo!!!! Well, the results speak for themselves. Internal linear scaling works just fine. I don't think the extra 100 kb at a desired size of 1046532 (0.01%) is a problem. Koepi, our programs are now officially useless. ;)

The result must be compared to the rate we entered, nitrogen, that's the point! Dunno what you want to achieve with the "reported scaled size", I just have that as debug info in there, it's a sum up of the scaled sizes + some corrections, and I can correct them in a way I like so it can be a copy of the value we entered - the value is just _for me_ as debug info. Dunno what you want to achieve now, but that's a VERY bad attitude that I don't see the first time now! Alarming behaviour... I think you want do some "competition" where I stated a "just kidding" above and meant it that way. *scratching my head* Koepi

I did the same test, and found Koepi's StatsReader to yield the lowest average quantizer, with the fewest outliers. Not by much, though.

A test in the new scaling of Nitrogen's Target : 1046532 Kb Result : 1046665 Kb MoonWalker

Hmmm, that's very strange. If you check the created ext. stats file, you'll see that the total frame size is exactly the desired one. So, why are more than 100kb there? Any ideas?