@Inc: That 2 pass aproach doesn't worth as cq given in HC Encoder log file is not the correct when used in cqmaxbitrate mode as in this mode the encoder do "cut" bits that doesn't brings back to the stream.
If you use cq mode, you have a high probability that your streams can't be load in any dvd author program, neither play in any SAP.

Yep thats what I called "the issue Ive heard/read of".

So maybe that will be fixed sometime in the near future as its possible to do mpegencoding by keeping the compilancy in CQmode without "cutting" peaks afterwards .... but I do keep my head low as I dont have any clue about that complex programming of an mpegencoding engine from almost scratch.

The used avg Quant CAN be parsed afterwards by HC encoder and putted/changed in the log. Thats stored in the flow of the mpegstream somewhere I dont know exatly ... as Bitrateviewer is also able to parse the FINAL existing Q values out of a ready encoded mpeg stream. So a final last step mpeg parsing could switch that value in the log text.

You can see a tool as I was talking here:

http://www.kvcd.net/forum/viewtopic.php?t=15979

I don't understand why all about calcumatic/cqmatic is here in this thread. It seems that we don't open more threads in this subforum and I don't know why. 8O
But anyway:
@Kwag: Could you explain me this:

http://www.digitalfaq.com/archives/i.../2005/07/1.png

You can see that calculated avg bitrate = 5511.9 kbps

103' 49'' = 103,8206667 min

103,8206667 * 60 * 5511.9 / 8 = 4291868 KB

And calcumatic shows 4191088.

Similar about audio:

103,8206667 * 60 * 384 / 8 = 299003 KB

Why calcumatic does it in this way?

Because you're missing a small detail :)

( 103,820.6667 * 60 * 5511.9 / 8 ) / 1.024 = 4191277 KB

And ( 103,8206667 * 60 * 384 / 8 ) / 1.024 = 291995 KB

(Results are rounded)

That's why CalcuMatic will give you EXACT results, and you can confirm that if you do an average bitrate encode (2-pass), and then compare the file size on disk (with Windows file manager) against the size CalcuMatic gave you. The result will be almost identical ;)

-kwag

:douh:

Also I misstyped , (commas) by . (point) as in north american way.

I know :lol:
Took me a second to figure it out :mrgreen:

-kwag

Then if:

(103.8206667 * 60 * 5511.9 / 8 ) / 1.024 = 4191277 KB results are KB

what units are

(103.8206667 * 60 * 5511.9 / 8 ) = 4291868

:imstupid:

Kilobytes. Based on 1000 bytes, instead of 1024 bytes.

-kwag

Hmm...
Since you're dividing by 1024 to get to Kilobytes, it means the previous figure should be bytes based in 1000.
Am I right?

Not.
He is dividing by 1.024 (decimal number).

No he is not.
He's grouping digits :lol:.
1 Kilobyte is not == 1,024 bytes.
1 kilobyte is == 1024 bytes.
That's what Karl is doing.
He is dividing by 1024 to reach Kilobytes.
Cheers

Yes he is :-)

Karl is is dividing by 1dot024. Not 1024 (that is 1comma024).
And he does so because "5511.9" is already in 'kilo' (kbps = kilo bit per second)

The problem is : is 5511.9 in base 1000 or 1024 ? That is perhaps the question you asked Rui.

Phil,

let me answer for Rui:

in portuguese, the decimal separator is "," (comma) while the thousands separator is "." (dot) - that's why the confusion.

so one and twenty four thousenths is 1,024 ("in portuguese") and 1.024 ("in english") ;
One thousand and twenty four is 1.024 ("in portuguese") and 1,024 ("in english").

I know. That's the same in all Europe.

Ok.
I got it all wrong :lol:
Karl was really talking about 1 dot 024.
I did get confused because usually in my calcs I use bytes and not kilobytes where I divide by 1024 to reach kilobytes in the end.
Sorry guys.
BTW I don't see why doing the calcs using movie time in minutes and seconds while we can do it in frames which is a much more accurate measure.
Cheers

To avoid confusion between 23.976 and 23,976 :D

BTW Did you test and compare ProCalc, based on Boulder spreadsheet?

You joker :twisted: :lol:

Not yet.
My PC won't let me.
I mean I have downloaded ProCalc and all but it won't start even with the VB6 runtimes...
Too many DLL's all screwed up or something.
It's a miracle that I can still browse the web on FireFox.
It's slow as hell and I was blaming my ISP :lol:.
All started happening from the moment I installed avast for testing and they uninstalled it to go back to avg free :roll:.
avast uninstaller presented me with tons of errors and froze my pc.
I had to hard reset it and then I got presented with a lot of errors on boot.
I shall reinstall XP and I'll let you know then.
When will I learn that I must do some XP images for times like this when things get difficult :?
Cheers

ProCalc info minutes and seconds so in that way ASPA (Available Space Proportional Allocation) is compatible in a straight way with CQmatic, as it require min and sec as input plus avg btr and TMPGEnc project. But, "in fact" ProCalc do all calculations based on frames and fps.
You know, same than Boulder spreadsheet.