Well the routine at the beginning was purposed for Packshot, ... but I did implementate it in a standalone appl. as there has been asked for ;-)

8O
No Kwag, it isn't hard.
I think Inc took the comment as it was intended to be.
Every comment I make is to be helpful.
If it doesn't help, the programmer just forget it.
That's all.
:roll:

The only little problem is ... coding needs time and if every little "cosmetic" is respected now, the things will take more and more time to develope, and the main intention of this calc routine was purposed as a developement for Packshot. This result as Standalone App. was just a little bonbon for Commandline Programmers .
:)

So I put my focus yesterday on a BitrateCalculation routine (see my "Developement status"-Posting in the "Packshot suggestions" Thread.

Great, great, great :D .
You have extrasensorial powers, man 8O :o .
Yesterday, while I was loading a big d2v in new calcumatic, with 2 films to be PackShot-Menc-KDVDed, and trying to put in audio 0 kbps, or 0 audio tracks (as I already have my ac3 tracks, wanted calcumatic not to consider audio), I thought: It would be great to have a new PackShotBitrateCalc... and here you are :!: .
First suggestion for your still not delivered tool ( :roll: :lol: ): it would be nice you could input manually the filesize of your ac3 tracks.

This one will be the part of Packshots window where AVGbitrate will be calculated.
http://home.arcor.de/packshot/bitratecalculator.exe
The liitle avg Output field will be the one which already exists in packshot.
No matter what you or where you do enter values, the calculation result bases on the the sum of everything which you do input in the fields.

You can set Audio kbs! And when entering the right length of the movie the exact correct size in MBs of audio internally will be calculated, as anyway you have to know and enter the movie source length! So manual MB size input is not needed, and would cause MORE inputfileds where user will get confused.

Downloaded and "tasted",
- What does overheat stand for?.
- Is automatically calculated the mux overhead for each film? (sorry, maybe this is the answer to my previous question :oops: )
- Did you include a minimum amount of MB for authoring later? (don't know exactly what's needed. I think that with DVDlab I used about 180 MB).

I selected 2 films, 120 min each, with audio track nº1 384 kbps and audio track nº2 192 kbps... and I got avg 1400... maybe too low.
Does it any difference if audio tracks are 5.1 ch or 2 ch? (in file size I mean).

I'll do more tests and post results (maybe better I'll open a new thread, if you think it worth).

Great, another toy to play with... :wink:

Uops, I thought I already fixed that mistyping 8) Done!

Well the overhead should include these needed MBs for authoring, as I did a test when using an other claculator and the final avg matches! Also I did comparisons with CQmatic and almost the same comes out, ... ok Kwag applied a little more "safe" space if I do see it right. But internally this routine above uses the same calculation sheme like used in MencodeME... as Vmesquita gave me the formula.
As said, I did a compraison with cqmatic and even there less bits in avg came out.

And, what counts is Bitrate and not if its an 5.1 or 2.0 Encoding! ;-)

Heres the importand part of the code and below you can see the formula:

Regarding overhead, I've noticed that you can assume that a DVD is 4350 MB in size. I've used it for 2-3 movies per disc and also with TV series, 6-8 episodes per disc and it's always been on the spot, leaving only a tiny bit unused.

Hi Inc,

Check your calculations, because the resulting average is way higher than what's supposed to be.
For example, for one 120 minute movie with audio at 112Kbps on one DVD-5, the average bitrate is 4897.9 (without any overhead).
But Mencalc gives me 5109, which is too high.

-kwag

Inc,
I've revised your post slightly, so I may be wrong. But I used your calculator, and made calculations "by hand", and get different values. I think one error may be in audio calculation:
I don't think it's the same:
as
I do get different results. I think the first one is the correct.
But this just gives an error if using 2 or 3 films. I don't know where may be the error Kwag is getting with 1 film.

I dont know Kwag, but If using Fit2disk, enabling everything like VOb muxing, DVD authoring and all we do need to be included in the claculation...

... at 1movie at 120mins incl. 112kbit audio... in Fit2disk 5006 do come out!

... "Bitratecalculator", means my engine outputs 5005 (incl 90mb overhhead)

:?:

Also ... that routine is exactly the same as in mencodeMe , as its the claculation of VMesquita.
Therefore a DVD5 Size of 4482 is used in the claculation .... or is that wrong

And to your point Digi Doc .... thats a thought wich could be true!
Kwag what do you think about it??

I think that the "way" the formula is is correct, as I do get in Calcumatic the same relation if 2 or three movies are selected and then 2 or 3 audios!

Well "his" avg is smaller seen as a whole (and thats why quoted my DVD Media MBs above so he can see if its correct) but in relation the output if more than one movie is choosen is the same

Perhaps kwag using CalcuMatic for his bitrate an he set DVD-5 to 4300 MB and you to 4482? :?:

All with DVD mux overhead included tested:

- movie 1= 120
- audio 1 =112 kbit

CQ Matic = 4869.4
mine = 5005



- movie 1= 120
- movie 2= 120
- audio 1 =112 kbit
- audio 2 =112 kbit

CQ Matic = 2252.5
mine = 2334



- movie 1= 120
- movie 2= 120
- movie 3= 120
- audio 1 =112 kbit
- audio 2 =112 kbit
- audio 3 =112 kbit


CQ Matic = 1305.5
mine = 1369




:?:

You see digiDoc. at least the relation of multiple movies/audio seem to be correct .... now Kwag should tell me which Mediasize/overhead he uses as I think there we're different.

Kwag: To me it seems you use a DVD media size of 4400 minus Overhead??

He's using 4300 MBs! :wink:

Nope!
Not in his version 1.09a!

Sorry, I haven't seen. :oops: :D

BTW: This calculator is NOT "MenCalc " :lol:
"MenCalc" is just the resizing engine.

That Bitratecalculator got no name as it wasnt purposed as Standalone Appl., Its just the Part which will be used in Packshot :wink:
As already many BitrateClaculators as Standalone appl. are out ;-)

@Encoder Master & incredible
Off-topic
I was just wondering if you're brothers? I compared your avatars, and damn you look alike! :lol:

I hope for you that avatars aren't always the photography of the user :-)

@Dialhot
:lol: :lol: :lol: