TMPGEnc misses target bitrate

[WarpEnterprises]

I'm using TMPG 2.53 plus and normally when using 2pass the average bitrate it gives is quite close to the setting made.
Recently I made some MPEG2, SVCD-standart with strange results:
1600kbit gives exactly 1600, 1550 gives 1500, 1500 gives 1400, and so on.
Is there anybody else who sees this effect?
(It seems below a certain reolution/.../dependend-threshold the bitrate calculation goes wrong)
How exact are your kbit-results??

[Arky]

ever since TMPGEnc was BORN, it's been notorious for not adhering to the specified bitrates you set it at - after a while, you just get used to it and make allowances! Other than that, ad the time it takes, it's a flippin' fantastic encoder :D


Arky ;o)

[WarpEnterprises]

I made some deeper tests myself and discovered that for 2pass new type there is some bitrate lower threshold , which depends solely on the output resolution. Below that the resulting bitrate gets completely wrong (not just some % around the specified):
576x480: 1500
576x352: 1100
288x352: 600
Besides: yes - TMPG is the one and only.

[mc510]

Are the newer versions of TMPGenc any better at hitting their bitrate? I'm using 2.53, and it's kind of ridiculous how bad it is!

[WarpEnterprises]

I'm using 2.54 since there were no real changes that affected me.
This version hits the target bitrate exactly in 2pass, with the exception I wrote above.

This behaviour has not changed in 2.58
You can't encode 480x576 below 1500kbit with 2pass.