TMPGEnc: VCALC v0.0.5 (beta), a PRO bitrate calculator
 

----- ----- Welcome to VHELP's 3rd installment tool ----- ----
-- = -- = -- = -- = -- VCALC.EXE -- = -- = -- = -- = -- = --

- --- --- --- --- --- a PRO bitrate calculator --- --- --- --- ---

Lets try this again !! :) !!


http://www.digitalfaq.com/archives/error.gif

* DOWNLOAD: vcalc.v0.0.5 (beta)
* DOWNLOAD: borland.files.rar

You may need to D/L the Borland files if you can't run the app :!:

WHAT IS IT:
-----------
A tool to calculate bitrates, movie lengths, video size, ave bitrate and
NEW formula for calculating "Ave MIN bitrate" for CQMatic and TMPGEnc - posible
future versions to include other enhancements etc.
Also, equipted with a scaling factor % using a slider to obtain a close
approximation to MS final readout.

NOTES:
* using an experimental mathematical precision proximeter. Default is 0.73%
...when enabled. This is to be used when comparing/debugging w/ MS readout.
Sorry, but I'm alone on this, and I'm doing the best I can, w/ my limited
math skills :roll:


LATEST CHANGES - vcalc.exe
------------------------------------------

07.27.03 - v0.0.5 (beta) .. (prev. was v0.0.4)
MAIN INTERFACE
[x] - BUGfix: bitrate off, thanks to Kwag for finding this one.
[x] - Adjust: CDsize (or number of disks) list is expaned..
[x] - Add: precision slider for MS scale factor.. experimental.. (def 0.73)
.......also, slider is Disabled by default.
[ ] - Debug: note, not all error-trapings have ben caught/implemented.

07.26.03 - v0.0.4 (beta) first release..
MAIN INTERFACE
[x] - Add: precision controls for finer settings
[x] - Adjust: all controls have respective HINTS for "what is"
[x] - Adjust: all hints applicable, include "formulas" associated
[x] - Adjust: not exactly placement coordinated, but workable.
[x] - Add: option for "always on top"
[x] - Add: option for change 1024k calc to 1000k calc
[x] - Add: option for modifying (0.57 * AveBitrate) calc precision

PLANNED FEATURES..
[ ] - DVD calcs and things
[ ] - cdSize for DVD ie, 4.3gig
[ ] - Save last project on shutdown.
[ ] - Ouput generator (text formt) (well, you may want one)
[ ] - Save certain NEW values (future discoveries) - maybe


BASIC USE:
-------------------
If you've ever used a bitrate calc before, you should feel at home with
VCALC. If not, just move your mouse pointer over the controls, and read the
hint baloons that pop up. You can also use the crsr up/down, rt/left keys
to adjust the precision sliders and dropdowns.
Anything in cyan (light blue) will be the only fields that needs user inputing.
No other field should be edited in any way! No typing anything in any fields.
And, no decimals either!!


TO USE:
------------------------
1 - First, begin with selecting your CD size. This is your required size (goal)
2 - Next, select your preferd audio bitrate ie, 112k, or 192k for others that
....considers themselves sound gurus.
3 - Then, input your Movie Minutes ie, 128 minutes or 68 minutes etc. For
....finer precisions, drag the "slider bar" left/right to increment minutes.
3a - You can adjust the precidion of decimal (Dec [2]) places. Note that 2 is
.....the default value. Mostly for debuggin purposes.
4 - Finally, watch your bitrates jump out at ya.. well, watch them display.
5 - Special treat.. all controls are WYSIWYG updateable.
.
Update.. 07.27.03
6 - There is now a scale factor for MS equivalence. After enabeling the
......field, MS prec[x], the slider to the right should now begin to activate
......and reflect the new "scaled" bitrate, approximating MS's. It's not
......perfect, but better than nothing, if you're an MS gauger.


SPECIAL NOTES:
----------------------------------
* You'll note a field for [calc 2] this is just another field for "kbits" calculations.
....Just another debuggin aid.
* The field for [Using: [1024k]].. I decided to implement this option to switch
....between 1024k and 1000k because I saw this used in other bitrate calcs and felt
....must serve some purpose. Changing this field (default is 1024k) will reflect
....in changes in calc'ed bitrates etc.
* Speical note, I've incorporated an option to revise the (0.57 * AveBitrate) 's 0.57
....to be variable adjusted, by moving the precision slider. This was a last minute
....decision, in case a change was to be made in the formula.. and last item worked on.
.
Update.. 07.27.03
* incorporated a scaling factor, though experimental. I'm also thinking
....about incorporting a "pivot" pointer. That may narrow the result even
....further, to MS's. I'm thinking about it :roll:


THANKS:
---------------------------
* to RazorBlade2000, for his assistance w/ the forumulas, and putting things
....into perspective I could understand, in versions prior to v0.0.4

Enjoy,
-vhelp

Looks really nice vhelp :D
But check your math against Moviestacker. I just compared a 120 minute movie, which gives me an average bitrate of 800Kbps in MS, but only 782.79 in vcalc :!:

Great job :cool:
-kwag

:D
a new gift vhelp?

thank you, seems great.

:wink:

hi Kwag.. and all :)

Becuase I'm only using the formulas as is - straight.

If you'll notice in vcalc, you'll see I have the formulas inside the HINT
baloons, so that you too, can following how vcalc is calculating/arriving at
the bitrate.. so that if you have issues w/ its calc's, you can correct me,
and I'll be happy to fix - but it's their mainly for those who want to know
how vcalc arrives at the final bitrate. That's all :)

Below is the formula uesd at arriving at the bitrate (from hint box)

* Value is: (movieSec * audioSize kbits) / 8 / 1024) = final size in MB.

hmmm... LOL ..I just realized.. "where is the above formula in vcalc source code?"
I can't find it !! I wonder what happended to it ??

Oh well, now to find out where to PUT IT!! hehe..

Thanks Kwag, for find the FIRST BUG !! hehe..

-vhelp


EDIT: -- ahh, and here's the bad formula:
.
and w/ no (movieSec * audioSize kbits) / 8 / 1024) to be found.
The above code-snip is incorrect anyways though.

I'll fix it shortly.
-vhelp

This looks really nice :!: Could you add a number of cds setting? It seems that when I change the cd size to 1600, 2400.. I get the same result as if I were to change the # cds though :idea:

great job on this vhelp

ren

great idea friendal,
:wink:

vhelp, maybe a "custom size"... can you add?
:D

Hi rendalunit.. pal,

I'd love to implement your ideas, but at the moments, I'm pulling my hair
out, cause of an error in a calculation - thought it was easy, but it's proving
to be a pain in the neck. Cause, the formula I revies (see above) is still
in error. ..the part her: ) / 8 / 1024 is not working. I think I made
a mistake in my understanding, and confused the issue w/ Razor.. that
we were factoring in a calc based on MANUAL "videoSize" and that's causing
me problem w/ the accuracy of the final bitrate, otherwise, it's off by a few
10ths (well, you know what I mean)

Thanks for your interest. I'll get back to ya on this :)
-vhelp

@ all..

I think I fixed it. Maybe, a yeah!! But, we'll see :wink:

Could someone Please run a few tests for me, using MovieStacker (I don't
have it installed) ??

Using below params, and give me what the Ave Bitrate is:

LN 01 - CDSize: 640 / Aud: 128k / Movie: 104 min. =
LN 02 - CDSize: 700 / Aud: 128k / Movie: 104 min. =
LN 03 - CDSize: 800 / Aud: 128k / Movie: 104 min. =

LN 04 - CDSize: 640 / Aud: 112k / Movie: 104 min. =
LN 05 - CDSize: 640 / Aud: 112k / Movie: 120 min. =
LN 06 - CDSize: 800 / Aud: 224k / Movie: 58 min. =

LN 07 - CDSize: 640 / Aud: 128k / Movie: 104 min. =
LN 08 - CDSize: 640 / Aud: 112k / Movie: 104 min. =
LN 09 - CDSize: 640 / Aud: 96k / Movie: 104 min. =

What I'm doing is test a "widerange" of values.

Please, I would really appreciate it MUCH !!

If all works correctly (or close) I'll release the next version.
I mean, does it really have to be 100% accurate ??
Otherwise, I'll release the next version with more smiles :)

Thanks again,
-vhelp

hey vhelp,

There's no setting for cd size = 640 in MovieStacker. It's 74, 80, 90 and 99

ren

some problems :

when i run the prog show a warning:
'1217.42' is not a valid floating point value
than i click ok
another warning:
'1201.49' is not a valid floating point value
than i click ok again.

the program open but in the botton(brown window)
don't have anything(no numbers).
in every adjust that i try,i got another warning...
and can' t get any result!

i download and unrar the borland files in the same folder.
please vhelp, what is miss in my system?
:?

@ all.. :(

Unfortunately, I'm taking VCALC down permanentaly, due to the faulty
calculation in final AveBitrate. It's off by 2.19%, but even trying to add
compensate for the 2.19%, it's still not working. Percentage was never my
strong point. And, I can't seem to get it to flow into the formula:

* (strTofloat(txt_calc2.text) / strTofloat(txt_movieSec.text))

which by the way seems to be the correct formula anyways. (see below)

I've exhausted myself on this one field, and it is not matching no matter
what I do to it. I'm using Kwag's first attempts:

* CD size: 800 / Audio: 112k / Movie min: 120

The above is adding up to an aveBitrate of 782.79 based on the
formulas.

I honestly thing that MS is padding the bitrate someone by 2.2% because if
the formulas are the same, MS should be resulting with: 782.79

I can't see having a faulty app here. There's too much going on, and we need
better accuracies w/ these apps. I just feel like not polluting it w/ mine.
So, I'm sorry for disapointing you all.

For the record, below is the formulas and scenario for the movie "Dogma".

Those of you who have D/L'ed the VCALC (good luck) have fun with
the scenario below. Those who didn't D/L, sorry.. isn't worth it, if
it's off by a few numbers. I'm going by MS to be the true giver here :)

-------------------------------------------

Move Title: "Dogma"

cd Size: 800
audio Size: 112k
video Size: 688 ------ Result base on:(cdSize-audioSize)

Movie Min: 120

Wanted VS: 704,512 -- Result base on:( videoSize * 1024 )
Calc2: 5,636,096 ---- Result base on:( wantedVS * 8 ) (is kbits)
Movie Sec: 7,200 ---- Result base on:( movineMin * 60 )

AVE BITRATE: 782.79

hi vhelp,

The problem just might be a bug in the formula like not converting kb->mb or something. I've been studying this page to try and figure out where the problem lies- but am getting a headache now :roll:

ren

hi rendalunit..

Actually, I just came back from my headache nap. But, i"m pretty finished
with this app. That's why I took it off. I didn't think it was worth having
it around if my formula was buggy at the last stage (w/ no answers)
The link, yes, I've ben their. Believe me. The formula is correct. Also,
Razor.. helped me, on these formulas too. But, I did continue doing other
searches on bitrates math, and in the end, my formula stays!!
And, he hasn't (Razor) hasn't said anything either. So, something's def.
ammiss here. :roll:
So, I don't know. Only way to know for sure, is to find Mauddib, and
ask for his source code (you do the honors) and/or ask him is he's using
some padding hehe..
Maybe it's a MS thing that needs it for internal calcs or something. I don't
know, but damn that 782.79 seems correct to me.

All in all, if my calcs are correct, then, I wonder how many peoples are
using MS's bitrate as a final answer ? And, what if Kwag incorporates
this same padding into his future bitrate he going to implement into CQMatic ?
Makes me wonder about all those countless issues we've all had with all
the various apps and steps and new ideas that's ben coming along since
MS's release. :roll:

Even if MS IS padding, w/ the 2.2% I calculated, using:
-> =$D$1*(D5/D6)-$D$2 - - (from excel)

-> ( 100 * 800/782.79 ) - 100 = 2.19

This is our 2.2% padding I need to add into the formula below:

-> (strTofloat(txt_calc2.text) / strTofloat(txt_movieSec.text)) or,
-> (5,636,096 kbits / 7,200) = 782.79 bitrate (<-- add 2.2% here, to make
......final bitrate 800, as in Kwag's test w/ MS)

I haven't ben able to incorporate it into my aveBitrate formula !!
Any math guru's here ? Theoretically, the 2.2% should work in the final
stage, but it's not. I'm doing something wrong. But, here is what I have
case someone is math guru, and can figure it out (see above)

-vhelp


----------------------------------------------------------

FROM VCDHELP's page:

Just for those that were curious, and want to tackle the issue w/ their
math wizidry (see above post) ...

MS says 800, but vcalc says 782.79 (2.2% difference)

http://www.digitalfaq.com/archives/error.gif

Hi Jorel..

Sorry for not responding to this post (below) I missed it.

Since you and Rendalunit are the only ones who D/L'ed it anyways..
I'll see what I can do ta help w/ what you have now. Bare in mind, that
its the last version !! If I make any further enhancements (ie, fix the bug)
I'll keep it to myself. I didn't think that others here would be interested in
another calc. (I knew that) but I wanted to give it a try FWIW.. Anyways..

Ok, the FIX:
Basically, you don't need to reload the Borland files. Especialy if you got
it working w/ my other apps ie, SLIM-G :wink:

If you reopen VCALC, don't bother entering in number manually. These
are the error-trappings I was refereing to, that I haven't yet caught all of
them on. Instead, leave these boxes filled in, and only use the dropdown
boxes. Since CDSize is already selected (highlighted) you only need to press
the crsrDN/UP keys (and watch the bitrate values change instantly) same
w/ AudioSize, and MovieMin (click the sliderbar, and crsrRt/Lft for some more fun)

As long as you don't type anything into these boxes, all will work no mater
what. That's why I made the TAB key only browse to the pulldown boxes.
though the MovieMin did escape me (was suppose to be the sliderbar)

Also, if you want to test the (0.57*aveBitrate) w/other values ie, 0.75 you
would check the box ie, min prec.[x] and it will enable the slidebar
for it to change. Just click on th slider (right of [x] box) and using your
crsrRt/Lft keys) see the NEW precision calc before your eyes.

I'm sorry about that nasty calc bug for aveBitrate. It wuold have ben a
great app. I had other feature plans for it, and actually stated to emplement
some of them ie, rens' CD issue etc. but.. - too bad :( Anyways..

If you can, please enjoy what's left of it, and thanks again for your great
support !!
-vhelp

vhelp,
i adjust the values like your picture posted.

i don't have the 446.19 (yellow numbers) in the brown(little window).
:arrow: nothing is there,no one number!
and for each moviment in the prog,
i have the warning with the same advice posted.

my position about your project:
don't need to wrote that we don't want to loose your develop here.
i'm sorry that i can't help you to build it,i don't have knowledge.
but if i could build something like you did,i never will stop.
here we have many many inteligents members like you.
they are wise,friendly and helpful.
maybe one or more of them can help you to
encrease the precision of Vcalc!

:wink:

hi jorel..

http://www.digitalfaq.com/archives/error.gif

That's very strange. I just tried it on my other pc, and everything is all
working well. That pc (2nd pc) does not have Delphi 6 installed on it. It's
my test machine (from a newbie point of view) Sometimes, though I forget
to test on it first, before releasing. In any case, it past the test. So, it must
be something you're giving it (value'wise)

Make sure you are NOT using any decimals in your number ie, don't use 1217.42
Just use 1217 (if you must type it in manually, and out of curiosity of what
vcalc would calculate for the bitrate of that CDSize)

CDSize is based on the actual size of the CDR ie, 640, 700, 800 and 900.
I ended up adding in those that ren wanted (before I became stumped w/
the calculation isssue)

I'm not sure why you would need any "." in your numbers though. But,
the reason why you got that error message (and you got stuck with it) was
becuase the format w/in the control does not allow for decimals, and thats
why you got that error, and thats also why it stays, and never dies (like
energizer battery) untill you Ctrl+Alt+Del and close it hard.

Note, if you have any params that you feel or comes out to, w/ decimals,
ie, 128.5 minus, please just use 128 or 129. Don't use any diminals for
CD Size / Audio Size/ and Movie Min :wink:

So, just close down VCALC and rerun it.
If I remember correctly, the Borland files go into the \system directory or
in the current foldre of the app ie, VCALC. But you're best to put it into
\system though.

I wish I could just figure out how to incorporate that 2.2% into the formula
(see above) - - RaTtS

Have a great evening all.
-vhelp

vhelp,
i was not clear.

i don't put this values there.
when i run the prog,the window with advice show this values
than i click ok twice.then the program came.
if i don't click ok,the prog don't came and the warning
wait for the ok(wait to the click)
(don't know from where it came)

all moviments that i try in the prog i got the same warning
with another number in the advice.
like this:
'xxx.xx' is not a valid floating point value.
then i have to click ok again.
if i try to change the cd size or the audio size,
the warning came again and wait for another ok.
:arrow:
all moviments in the prog give the same advice warning posted.
and no one yellow numbers like your picture posted
show in the brown (little window)
conclusion:
i can't put any number,this warnings show the numbers
"xxx.xx" with the same advice.
:?

hi jorel..

you know.. in all the futzing around, I just bet that you might have run
out of STACK space. When that happens, your sys resources are very
low. It happended to me today, and my system rebooted 8O on me.

But I'm stumped w/ your xxx.xx error cause I have VCALC running all
afternoon (in right corner w/ [x] stay on top checkeck) cause I'm still
LOL bebbuging this app, and I'm at 35% sys resource remaining under
Windows 98.

But, once you get out of the error message (ctrl+alt+del) and close down
that app, double check your sys resources to make sure you aren't running
low, and then restart VCALC. Again, you should see the same pic at the top
of this page. I keep here (there) for debuggin purposes for you.

The first thing you do when it opens, is just click the [800 [:] box and
make your selection their. You can use the crsrDn/Up if you like. Don't
type anything into the boxes (only crsr bold) to the left of:
[800 ] ... [800 [:]
[112 ] ... [112 [:]

If you're still getting errors message, then your system must have gotten
corrupted due to STACK errors. You may have to reboot :(

And, remember.. no more decimals ie, "." ok ?
-vhelp

again i wrote to you my friend vhelp.
:arrow: i don't put the decimals :!:

:arrow: the program show the decimals caming from nowhere :!:
8O

i can't put anything in the prog cos i got the warning advice
in all situations.....before and after i run the prog.
i reboot the system,put the borland files in the program folder
and in the windows system folder....just the same!
the 'xxx.xx' and the warning came after any moviment in the prog.
i don't have any numbers in the bottom of the prog,
only the brown banner.
when the program came all numbers and adjusts are the same like in
your picture posted without the yellow 446.19 number(nothing is there),
but all that i try to change in Vcalc,
the warning back and i have to click " ok" again and again!

:?

Vhelp:
I sent a pm to you, regarding this topic, a couple of hours ago, but am not sure if it went out. Did you receive it?

Totonho03

hi tots..

A couple of headaches ago, did you say .. nah, didn't get :)

I'm not giving up just yet. Still working on the fomrmulas. I found some
thing interesting w/ Razor's formula, and comparing w/ vcdhelps. They
are both accurate, but one of them is missing something. And, I think it
may be ME 8O hehe.. I'm getting their, but I'm not sure I'll ever reach it
if that 782.79 doesn't change to 800 !!

Oh, did I say I have a swelling headache ??

Thanks for your assist tots, however my PM is empty (no new junk mail, hehe)

ooh, dinner time for me.. rice and beans - peeuuu!
-vhelp

Vhelp:
I am glad to hear that you are not giving up. I do not know why you did not receive the pm, ...."only the shadow knows...........", but knowing that you are still working on it is very re-assurant. Nevertheless, I will send you a small one this tme.

Totonho03 (aka tots :lol: )

@ all (or Kwag) ...


With respect to this post, please see the latest PIC at top of this page
(assuming page 2) for the latest debugging values (note the grayed
readouts) The latest app is v0.0.5 (beta) - - - thanks !!

I'm back. Looks like I may be on to something. Also, that I may have blown
all this nonsense w/ the actual aveBitrate calc after all.

Here's what I did...
* I D/L'ed latest version of MS, and installed it.
* I imediately opend my VFAPI converted .d2v to a psuedo .avi in MS
* There is where I started to notice a few things. Member my "padding" claim ???

Anyways, it looks like MS is doing other things behind the seems and the final
result is whatever MS is doing, "calculation" wise, it's causing or throwing off
the ave bitrate. Maybe it not "throwing off" to say, but that, w/ all the
features it's incorporating, who knows what it's spiting out 100% 'ly speaking.

Anyways, here is what I noticed already. Using my movie, "Dogma" I looked to
the audio bitrate and set it to 112k as in my VCALC, matching everything I could.

Then, I had a look at the audio MB in MS.
* MS is reporting 103.93mb
* VCALC is reporting 105mb.

A difference of 1.9%

Also, my bitrate was for this movie was (see above pic, top of page 2,
v0.0.5 (beta) ) and note the difference!! Not as much as before, I think :roll:

So, what is MS doing to my audio - calculationlly speaking ??
It would seem that MS is throwing something into the Audio calculation.

Otherwise, maybe I should be setting up MS accordinly. I might have missed
something in MS. This is my first time using it (even if it just for testing
debuggin purposes)

Does anyone have any good suggestions to setting up MS, if all I'm doing is
opening up an VFAPI source file and ONLY verifity:
* audio bitrate (MB)
* average bitrate

Thanks in advance!
-vhelp

Hi all again..

Addtional notes to 5th paragrah of previous post...

Also, it would seem that not all or not every source brought into MS would
result in the same readouts ie, ave bitrate and audio MB size. Perhaps
it would depend upon the user making any settings. There doesn't seem
to be any default, as one user makes a change ro anythikng (even if by
mistake, it could result in future misreading :( and that could cause issues
as in my case for instance.
So, when a user uses VCALC, he/she will only get the true actaul readout
of what a ave bitrate truely is, because it's not being tainted by ANY factors
as in MS. Not saying that MS is in error, but rather sort of missleadng to
some degree. VCALC is not tainting values. ie, the audio MB size is not
being tainted or mulested in any way. So, the audio calculation is prestine.
As to other variables, I can't say what next, w/ respect to throwing off the
ave bitrate values in MS, but as far as VCALC is concirned (myself) the
functions are acting properly (as far as I can tell)

Sorry, my head is spinning - :roll:
-vhelp

EDIT: - - sorry, ben a change already.. read prev post. I made
change to 105mb vs. 98mb was suppose to be 105mb for VCALC!!
and 103.93mb for MS.

vhelp:
One question, and perhaps this is showing mi lack of experience regarding these programs, but have you compare the the size of your head3ac output file to MS's? When setting MS, shouldn't we use the same bit rate used at heac3ac? In other word, if I use say 160 with head3ac, shoud I manually change this number in moviestacker? This may be comparing apples and oranges, but couldn't help my curiosity....

Thanks

Totonho03

hi totonho03..

sorry for not getting back to ya. I was fluxing mulitple posts, and correcting
them as I fluxed them hehe - did make my head spin for a bit..

All is fixed now w/ posts. So, please re-read my last few above :)

Na, I don't think so.

MS has the option for users to change their audio bitrate ie, 112 or 128 etc.
Same for Movie length in minutes. And, as you change them, you also
change the "ave bitrate". I played around with this one a bit.

There are some thing going on w/ MS, and probably for the better.. if you
think about it - I think :roll:

MS was showing 104mb (103.93mb) and VCALC was showing 105mb. Even
though final ave bitrate for both were minmally different, its enough to
throw off things.. like, predictuion 8O we all know how sensitive it can be,
as well as hair-pulling. BUT, as long as we know what other apps are doing
w/ our calculations ie, MS vs. VCALC then we can syncrunise or factor them
into the final results obtained ie, ave bitrate from MS vs. VCALC.

I know that the above sounds a little bit crazy, but after spending the whole
day on this, I feel like a pro. I just coudn't give it up.. those that know me
for my stubberness.

So, now that we know that MS taints (w/ respect to benefiting) we can still
use the bitrate given in VCALC ??
I think so !!

But, to be safe, we should really have a look at what MS is really doing w/
your source, and examine how it is arriving at a final ave bitrate :idea:

Never the less !! I'm feeling much better now.. and can maybe realease
an long awaited updated version ?? Maybe not hehe..

-vhelp

Hmmm.....

There is one other thing to considere also, when dealing w/ results obtain
by MS vs. VCALC vs. any other "ave bitrate" onbtainer ..

Assuming that MS is THE final guaging tool of choice..
If a user uses any app, including VCALC to check for ave bitrate, and then
goes to check MS's results, do bare in mind that MS is going to be the one
the shows what might actually come out, assuming that your source is
musassged in MS, and MS changes or guggles some things around, like
numbers and stuff.

But, what makes me wonder, is who's telling the true. Is MS, after messaging
the source, does the final result (encoding) truely reflect of of MS's messagings ??
OR, after performing a ave bitrate for BOTH apps (or any other for that
matter) result in a final result (encoding) that will refelct based off of the
calc that does NOT do anything to the final ave bitrate result :!: :!:
.
.
This is something we have to think about. I think I've only discoverd it,
cause I started my own calculator and stubmled accross obtsticles.

I don't know.. maybe there is a default in MS, where NOTHING is changed,
and the final results would match any other bitrate calculator.

:idea: Ok, besides vcdhelper's, is their any other bitrate calculator that does the
same thing - not 100mb in size to D/L ??
I'd like to try a few to see how they compare :roll:

-vhelp

Update.. v0.0.5

@ all..
After taring through countless documents on bitrate and things, I've come
up w/ an alternative or bandaid to the MS readout delima.

I've managed to incorporate a scaling factor algorithem for obtaining as
close a match to MS's final readout of ave bitrate. Unfortunately, the Lower
you go, the further (though small) the values turn on each other. Likewise,
the Higher as well. I only done short tests of this. So, you may experience
differences, pending upon your source.

So, weather you go by MS as a guage or not, the choice is yours, in VCALC.

There are bound to be errors or other bugs surfacing. I'll deal w/ them as
they come :)

Enjoy,
- vhelp

hi vhelp,

glad you didn't give up on it. I downloaded ver. 5 beta and it seems that the bitrate is still too low. MovieStacker will pad the bitrate if you have the SVCD scan offsets and seq. header aligning boxes checked so make sure they're unchecked. Also did you make sure that you convert the cd size (mb) to KB { i.e.- cd 800mb = 819,200 KB } in your formula?

example:

cd size = 800 mb ; audio kbits = 128 kbps ; length seconds = 7200 (2 hrs)

(cd size KB - (audio KB * length seconds ) ) / length seconds = avg bitrate

(819,200 KB - (16 KB * 7200 seconds) ) / 7200 seconds = avg bitrate

(819,200 KB - 115,200 KB) / 7200 seconds = avg bitrate

704,000 KB / 7200 seconds = avg bitrate

97.78 KB = 782.24 kbps avg bitrate

vhelp..............
 

What is kb for 700mb?

Also, vhelp, don't forget us maverick KDVD to CDVD folks. I really need a CQ prediction for sizing output, both for CD's and DVD's! Your efforts are very appreciated.

Thanks guys, for the support :lol:

@ Ren....
I'll have a re-look at your suggestion to be sure. But, I'm pretty sure that
I am converting properly. However, 8O that CD example cought me off
guarg 8O

--> (800 * 1024) = 819,200mb

But, I think I have it correct anyways.. I'll look again.

@ nicksteel..
Thanks too.. for da support.

>> What is kb for 700mb ?

Ans: given the formula above, (700 * 1024) = 716,800mb

Sorry pal.. no comprenday 8O

>> KDVD to CDVD faults ??
.
.
. . and >> CQ prediction for sizing output, both for CD's and DVD's!

I'm not sure what you mean 8O Please enlighten me, thanks.

Also, don't forget, that CQMatic will be comming w/ a calc built-in soon. :!:

What I'm offering w/ VCALC, is an alternative to other calcs and things, and
also for other external reasons - if that made any sense :wink:
Yes, also, becuase there may be features in my calc app, that others do
not have. ..another good reason for an external calc app :wink:

@ Jorel..
I hope you got VCALC working now !!

Thanks all, and have a great evening,
-vhelp

hay Ren..

you're right !!

[ ] seq. header aligning and [ ] SVCD scan offsets

left unchecked made MS's ave bitrate go from 744, down to 729.
That is much closer to VCALC's 733.87 !!

But, that was for a MUX setting for bbMPEG VCD MPEG-1

Anyways..
-vhelp

vhelp my friend....help me.

i got the same with the new 005.
i know that is something miss in my system but don't
know "what" is wrong.
don't know what to do.
:(

@ Jorel.. my friend .. :)

I'm stumped !! :(

I've change "most" of the control fields to Reals (delphi talk) that now
accepts decimals (though I still prefer you NOT to use them [once you get
vcalc working] for anything)

Now, I'm busy working on another update version. In my confusion and
frustration of MS vs. VCALC final "ave bitrate" I lost some coding I was
working on, in version v0.0.4, ..deleted it somehow - - too many cut/paste
things were going on :( I had to re-invent the wheel (via coding) to get it
all back. Funny how I didn't notice it gone in v0.0.4 though 8O

Note 1 - I have it working on my 2nd pc. And, all it function positive (no negatives)

Note 2 - I also brought a copy w/ me to work, NT stations. And, it too, is
working flowlessly. No function negatives going on their either.

So, currently, the OS that I am aware of, that VCALC works under are:

* Windows 98 (Gold/Orginal)
* Window NT
* Rendalunit's Windows XP
* Kwag's ???

The only thing I can think of thats causing you issues, is the Borland files.
* Where did you copy ALL the files to ??
* Did you copy all, to your VCALC folder
* Did you copy all, to your \system folder (or \system32)
* Note, if my other app, SLIM-G stopped working, then it's a sure bet that
...something gone amis w/ the Borland files. BUT, if SLIM-G IS working,
...then you got something going on, that I cannot figure out from my POV.

:banghead: Come on.. surely you can get it to work !!

:idea: 1 - Maybe, if you have another pc, you could try it on that one.
:idea: 2 - Also, please visit a friends pc, to see if it works.

I sure DO hope you get it working !!
-vhelp

Windows XP - it runs fine :wink:

Thanks Ren..

Glad to hear it!!
-vhelp

my dear vhelp (and friendal too)
you wrote:
"(though I still prefer you NOT to use them [once you get
vcalc working] for anything"

for the 4th time i repeat,
:arrow: i don't enter any decimals in the prog(don't put anything),
they shows from nowhere. :?

when i double click to run i got the advice and after i click "ok" twice
the program run without any number in the brown window..
(don't know the right name of this place where are the yellow numbers)
i download the borland files again and put in the windows system
folder and in the Vcalc folder too(i unrar the files,of course).
every moviment that i try in the prog the advice back again!
i know that something is wrong or miss in my system,not in Vcalc.
:arrow: i have the same borland files in
the SLIM-G folder and it's working.

than again i write,don't know what´s wrong and
everything that i post here is the same that i posted before!
don't work and is not Vcalc,is something in my system 98 se
and it's the only prog that don't work....don't know what's wrong.
:? :? :? :?

your really lost friend :!:
:lol:

....
if you want i can send some pictures to your mail.

Hi Jorel,

Sorry, I forgot to mention/ask.. :?: :idea:

I recall you mentioning that you have 50 MB web space...
..but that you didn't know how to setup to post your issues (ie, pics/files)

First, if you can post some screen shots of your issue, that would be most
helpful :!:

But, if you cannot, because you don't know how to, PM me, and I'll see if
I can "guide" you to a setup.

Then, the only TWO apps you'll need are:
* an FTPs (I would prefer you to use what I use "exactly", WS_FTP95 LE
* Paintshopt pro - - for the pic

HOW TO...
* to copy your "current" app, you Alt_PrintScreen (will copy to your clipboard)
* then, in painshop pro, you Paste
* then, you save as .jpg for smallest** files.

** note, I prefer .jpg vs. .png (why, because .png files don't always behave,
and will load another graphics app or browser or something, and just take
up too much resources and things)

I do hope you know how to U/L files though, cause it would be a bugger, if
I have to train "guide" you hehe 8O :roll: 8O

-vhelp

wow thanks for that too vhelp.
i install everything later(doing tests now with CQMatic)
and i pm to you.
your help will be fantastic my friend.
i need this 50mb space but nothing is there cos i'm stup.
when i was in school,my teachers ever say:
you can do hard things, :bruce:
but turn the simple things too complicated. :screwy:

it means.....i'm mad?
:teeth: :hammer: :i: :expert: :hammer: :bigooh: :eyes10:


:lol:

thanks vhelp!
:wink: