:lol:

Most Wanted - Reward

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

I never saw any of these guys.

who :?: ....where :?:
:roll:

I wont show a photography of mine, but one of the girl at the cash desk of the supermarket where I buy my stuff.

http://www.digitalfaq.com/archives/i.../2004/05/7.jpg

:mrgreen:
So what tells us that?! :arrow: She still lives near Cologne!! (Bergisch Gladbach) ... and has to earn a little "extra" money in that supermarket as Flavio B. doesnt want to pay alimony! (IMHO) :lol: :lol:

Well, Inc, now running a test with the value I got manually, that is higher than that I got with your calculator. I'll post the result.
When I said that maybe the audio bytes formula was wrong, I said it:
1. from a mathematical point of view: it's not the same (a x c) + (b x d) as(a+b) x (c+d). It's not exactly what happens with your formula, but an approximation. In your formula you sum audio length and video length, and then apply the formula. When you really better applu the formula for each film, and then sum them.
2. I did by hand calculations, and got different results.

... but I may be (almost sure) wrong. I just say that in case you revise it.
Saludos.

Too much porn DVD ripped for developing pack-shot Inc... tsss...

This is not real life :-)

@Inc,

You'll know what to do with this ;)




And then:



-kwag

Where's 80kbps (for mono audio) ?

Nowhere :!:
Because many players can't reproduce that audio bitrate. Just like 40Kbps ( One of my players included :) )

-kwag

Hey, you learn something new every day 8O

But still, here's your gift :cool:
Might be useful for some special cases :)

CalcuMatic 1.0.13
http://www.kvcd.net/downloads/CalcuMatic.exe

Added Custom audio size ;)

-kwag

thanks Kwag!
:wink:

removing doubts: loading ifos i get negative numbers:
minutes -4800
seconds -79
and all in the "results"

how the preview work? if i click using ifos,vobs or avs scripts i got:
"error,can't load the movie..." :?

Thanks for the code Karl!

Im just in optimizing the MenCalc Resizer so that all Sources like captured non 1:1 PAR ones will be also supported :)

After that Ill do optimize the bitratecalculator. :wink:

Hi Jorel,
The preview feature is only available for mpeg or avi sources.
It won't work with ifo/vob/avs :( ... yet, I hope :)
The problem with the negative figures is also happening with my DVDs and I've told Kwag about it and told me to wait a bit longer as he is under heavy development on the parsing mechanisms used by calcumatic for those new sources.
C ya

ok,thanks Correia.

the worse is that i "double post" the same doubts in CQMatic/CalcuMatic forum!
:oops:
now i have to "stryke" myself! :lol:

:rotf: :rotf: :rotf: :rotf: :rotf: :rotf:

New version of "MenCalc" is out .... see change log in first post of this thread for details.

http://home.arcor.de/packshot/mencalc1.01.0.exe

thank you ink !
:D

This question might sound off the wall..but where do I put the values that MenCalc gives me?..




David

Do you know mencoders syntax?

Thanks inc, love the new version.

@ DigiDoc

Related to calculate the bitrates in that bitratecalculator...

You where right!!! ;-) I have to calculate the audios separately!

I left everything as it was except a modified audiocalculation (as you pointed me to) and the mediasize and overhead values suggested by Kwag .... now its correct.

If you want to test, use the old link to that bitratecalculator in this thread.

Also for shure thanks to Kwag! ;-)

You'll have to forgive me , I havent had much sleep in the past few days. Do you mean the temp.conf or setting.ini ? I havent had to use MenCalc yet because I have been great results so far.



David

Well lets see it on an example by using aready made .fil file in the filters folder of mencodeme:
use Mencalcs output:
i.E: "-vf scale=480:576::0:9,crop=448:544:16:16,expand=480:5 76:16:16"
(A 720x576 DVD to 480x576 overscanned kSVCD ...both PAL)

and change the filter file like this:

I still left the filters between Crop and expand.
After this safe that fil file using a diff name and it will be seen next time you open MencodeMe ... and the new values will be forced, even if you set other resizing values in mencoder IF this fil file is choosen in the filter combo box of mencodeMe! ;-) ... so you could do several resizing templates, safe them as fil files in the filters folder and these you can simply use as often as you deal with same source/target size :)

Ok, now I got it, thanks inc..can this be used with packshot too?





David

Well that programm is a result of developing a resizing routine FOR PACKSHOT :lol: !
So the next version of packshot will got it integrated! ;-)
Then you only have to choose your target resolution and the overscan factor, no more -- everything else will be automatically.

The next days Ill be in re-coding packshot.

Cool, thanks inc can't wait to see this :D



David

very understable explanation of how Mencalcs can be used !!!

many thanks Inc

@Inc,

Could you add a "Real Film Area" (Film Pixels) fields to MenCalc :?: ;)

-kwag

I see your point as its figured out in the "noise" thread that Mencoder isnt that "black border" smart as assumed before.

Yep! That will be on my todo list!
Till that time use avisynth/Makeavis OR do replace the vaules with the ones gotten from a MS calculation --- as the next Packshot supports "commandline only" where you simply can tweak these needings, and after that run the bat file manually. (as you shurely know all that so this is written here as an response directed to others ;-) )

After vacations the new version is released.

Please do report bugs also in here.

Thanks

Thanks for updating this great calculator Inc. :D

Thanks Inc. :D

-kwag

Gee, thanks Inc. :D
Great! Now we have crop/scale/expand :)
Many thanks buddy ;-)
Cheers

Nice to "read" you rds.
Why now first crop?
Why last values change to -1 -1? I know what it means but why previous Mencalc did use another values?

First crop .... because in that version of mencalc you can determine the active Px movie area (remember the min-bitrate noise trick?). So this one has to be cropped first.
And as I want to avoid a double-cropping command, the crop-scale routine does compensate that.

Also you now can see how the image proportion will do change when performing the image resize process and also how the AspectRatio Error will be finally (like in FitCD, I took that nice idea from shh).

Also a safe-routine is implementated, means the calculator will look which type of cropping/scaling will keep most pixels as by keeping the AR normally it can happen that many pixels have to be cropped for instance in the width ... I only do say 352 1/2DVD resolution! ;-)

In the previous version I did let calculate Mencalc how the image will be placed centered or Macroblock aligned, that will also be possible in the next final release as also you will be able to enter individual Xpositions and Ypositions of the active movie area.
And so in this release state I did let calculate mencoder internally the center position using -1,-1

@Incredible: I'm trying to emulate MenCalc in cmd scripting language, and I don't understand something.

I can apply calculation based in http://www.uwasa.fi/~f76998/video/co...nversion_table
to standard PAL/NTSC resolutions.
But how to calculate resizes, etc. with avi sources.

e.g. 576*256. It can't be found in the table and I don't know how to do calculations.

Other question,why (is needed) and how (formula) calculates crop values?

http://www.arachnotron.nl/videocap/d..._cap_v1_en.pdf

All you need is in there (at the end of the PDF where size calculations are explained: There also 768x576 is PAR 1:1 like mpeg4 avis)

576x256 is NOT mentioned in Jukka Ahos site as its NO valid Video output device resolution. Its just an individual PAR 1:1 mpeg4 resolution based on the DISPLAY AR (like 1.33:1 , 1.78:1 or 2.35:1 etc).

If I have time, on my to do list is the creation of an executable binary of mencalc, easy to call from a batch file. And also a .dll version so VMesquita can use it in DIKO.