Gknot not using the bitrate entered?

[theReal]

Through the new tool VDubConf, I saw that when I manually enter a bitrate of 800 in the bitrate calculator, the codec will actually be set to 819 for encoding.

This is without any re-calculation for audio or credits, but it's exactly (800/1000)*1024 = 819,2
Am I right with this calculation?

I thought Gknot made this conversion visible (because the bitrate changes immediately when you switch to Divx 3), so you could use it as a bitrate calculator for avi to divx conversions (I used it like that quite often, but I never realized Gknot would set the bitrate a little higher in the end if I was actually encoding through Gknot).

So, to make this a question: Do I have to multiply the shown bitrate by 1.024 in any case when I'm using Gknot as a calculator only (for manual encoding)?

[hakko504]

It's like this: MPEG defines 1kb as 1000bytes! Therefor fully MPEG compliant codes like DivX5.0x, DivX4.x XviD, MPEG-2 and MPEG-1 uses this value. DivX3.11 though is NOT fully MPEG compliant and uses the standard computer 1kb=1024 bytes. Therefor GKnot will use those values when setting bitrate for encoding.

In answer to you question: If you have the correct codec set on the bitrate tab of Gknot you do not need to change the value calculated by GKnot.

[theReal]

Not really: I enter 800 in Gknot (which is set to Divx5 and stays there, no change to Divx3), then I set up an encoding job and Gknot starts Divx 5 with a bitrate of 819 (which you don't notice, usually)
But, when I can't set up an encoding job in Gknot because I encode an avi file, then I have to set up the Divx codec configuration manually. I usually would have entered 800 because that is the value I entered in Gknot to calculate the filesize that I will get for a DIVX 5 BITRATE of 800.

Only through the use of VdubConf I saw that Gknot enters another bitrate in the codec configuration.

I'll check if the same happens when I don't enter a bitrate in Gknot, but a filesize.
F.e. I enter 700MB and Gknot calculates "843", does it encode with 843 then, or with 863??

[TheWEF]

this is a bug.

to avoid this do not encode divx5 in "Calculate Avi Filesize" mode.

[hakko504]

My mistake. :( Disregard the last paragraph of my previous post.

[theReal]

Thanks, that was what I wanted to know.

hakko, I explained it a little clumsy. I guess it was hard to understand what I meant unless you knew this already, like theWEF did.

[calinb]

Ahhaa! I thought this might be a bug! I use calculate avi filesize mode because I'm always using weird file sizes to fit on various over-burned CDs. (715MB, 727MB, 735MB...whatever I happened to buy cheap.)

Anyway, the mode seems to work out pretty well if I encode for my desired filesize divided by 1.024.

[theReal]

As far as I understood TheWEF, the bug doesn't appear in "Calculate Average Bitrate" mode. That is the mode you use when you enter a filesize, so you don't need to divide anything here.

[TheWEF]

Originally posted by theReal
As far as I understood TheWEF, the bug doesn't appear in "Calculate Average Bitrate" mode.

correct. just enter the bitrate you want, switch back to "Calculate Average Bitrate" and everything is fine.

don't forget to uncheck "recalculate bitrate if needed" in the encoder dialog to enforce the bitrate.

wef.