AR CALCULATOR 0.9.4 Final !!!!!

[m0rtal]

BTW, is it possible to catch up some functions from Java XviD stats viewer (http://forum.doom9.org/showthread.php?s=&threadid=67639)?
I think it could be useful enough :)

[tiki4]

Originally posted by m0rtal
I don't know is this OK, but AR calculator changes XviD quantization settings for it's internal purposes when encoding a movie, but don't change them back to original state!
I mean, if, for example, I had quantization values I/P/B at 2-31/2-31/2-31, ARC changes them to 2-3/2-3/2-3, and after that I have to edit them manually to keep my favourite settings.
so, is it possible for ARC not to change quant values - or to change them back automatically?

You could export your favourite XviD settings into a .reg file with registry editor (just like GK does) and import them back by double-clicking in explorer.

tiki4

[nine]

First of all, I'd like to say nice tool :)

One thing I've noticed, after a quick look (v.9.2) is that there is a bug in the GUI when manually entering the CD size (I dont think I saw any references to it in the thread?)

Basically what happens is when I key in a CD size of 695 Mb (Not using the drop down!) (Call me paranoid ;) ) the CD size in the size box goes a bit insane: something like 288608256 kb. This in turn also breaks some other things when the calculate button is pressed.

[m0rtal]

Originally posted by tiki4
You could export your favourite XviD settings into a .reg file with registry editor (just like GK does) and import them back by double-clicking in explorer.
I know it, but it's a bit of manual work ;)
can't it just be automatic? encoders already have a lot of manual work to do...

[DarkDudae]

@m0rtal
ARCalculator is programmed for restoring everything it changes in registry entries. Since Api3 and Api4 share a lot of registry entries... I suggest you to try "load defaults" in XviD 1.0 Beta(s) before you use ARCalculator. In what cases are changed the quants? Can you describe what you do exactly to try reproduce the problem, and hopefully fix it?

@nine
Thanks... we really didn´t realize of that little problem.

Greetings

[m0rtal]

DarkDudae
currently I have Koepi's XviD 1.0 beta3, and of course I know about "Load default" peculiarity.
Quants are always changed when I'm loading a *.d2v in ARCalculator and saving it as avs. After that I'm starting VirtualDubMod, choosing XviD from "select video compression" menu - and voila! All qants are set @ 2-3...
surprised, I had changed them back to my favorite, try encoding the movie with new avs script, it was cool (thanks A LOT for your effort!!!), then I've tried AR calculator with another movie - goddamn, same situation! after "saving as avs", quants again set @ 2-3...

[m0rtal]

possible glitch found:
when loading ARCalculator 0.92 and directly after that clicking on "16:9" text, not on radio bullet, ARC fills "Real Aspect Ratio" field with strange value: -9,22337203685478E16
wtf?

:EDIT: btw, when next version, compatible with last xvid build, will be out? i can't wait to test it :)

[kadajawi]

The New AVS Optimizer combined with Beta 2 let XviD crash... is there any setting I've to set to avoid this? Using the normal AVS Optimizer works... :confused: And when will there be a Beta 3 compatible version? :D

[DarkDudae]

Before anything, we will release a new version in a few days.

@m0rtal
We have been trying to check why in your computer, quants values are changed automatically, because in our computers (and othere people who have tested the program, it works perfectly). Anyways, wait for the next versión, maybe that the internal changes we have done can help you.

@kadajawi
In what moment "crash" XviD? It creates de avs correctly or it fails during avs optimizer new pass? AVSOptimizer new needs that Avisynth 2.5.3 is installed in your computer.
AVSOptimizer new scripts, really need a good computer to work correctly... it needs a lot of Memory RAM (With only 128, it sometimes fails, and it is neccesary to down the SetMemoryMax to lower values, like 60). It uses a huge amount of trims. However, you should try the new version compatible with XviD Beta 3.

Greetings!

[kadajawi]

It crashes somewhere during the test encode. As I don't have that much CPU time left I couldn't verify, so it could be due to some other reason (although XviD's been quite stable... well, perfect stable ;) ). I hope I can try it with your new version.
I can use AR Calc to create an AVS for small videos (2 to 5 minutes), right?

[DarkDudae]

Originally posted by kadajawi
I can use AR Calc to create an AVS for small videos (2 to 5 minutes), right?

Yeah, of course... that is not the problem... Let´s see if new version works OK for you :)

Regards

[kadajawi]

Not sure if its clear :) The video I encoded was a live concert, but usually I only encode video clips (well only... they are quite troublesome). But I've deleted the source as I'm fine with the result.

[m0rtal]

what settings ARC uses to run 1st xvid pass? especially the b-frame ones - i.e., I want to have 30 consecutive b-frames and sensivity set to 3... is it possible?

[DarkDudae]

Originally posted by m0rtal
what settings ARC uses to run 1st xvid pass? especially the b-frame ones - i.e., I want to have 30 consecutive b-frames and sensivity set to 3... is it possible?

ARcalculator allows the user to configure the codec with the settings that you want. The only thing that ARCalculator configures automatically, is the old AVSOptimizer additional pass (because the new one, will allow configuration).

[m0rtal]

Originally posted by DarkDudae
ARcalculator allows the user to configure the codec with the settings that you want.
really? I can't find where I can change codec settings...
maybe I'm just blind and stupid...

[DarkDudae]

Originally posted by m0rtal
really? I can't find where I can change codec settings...
maybe I'm just blind and stupid...

Well, as you can see, you can choose internal encoder (Avs2avi) or an external encoder (like VirtualDub). If you use avs2avi, when you create the avs, you can choose Encode or Save & Encode. And well, a windows will be open in your computer, and you will be able to choose the codec you want to use, and of course, configure first, and second pass.

Greetings

[m0rtal]

DarkDudae
goddamn, fella, you rocks! ;)
thanks a lot!
now I love ARC even more :D

[DarkDudae]

ARCALCULATOR 0.9.3

CHANGELOG

-Full Support for XviD 1.0 (its betas, and, hopefully, all the next releases)

-Added a New AVSOptimizer, witch can be used from only a 10% of additional pass, and besides, it is addaptative (addaptative to bitrate, resolution and complexity of video used). IMPORTANT: It only works with XviD 1.0 (betas) and later.

-New profiles system for the new AvsOptimizer, witch allows to create, load, save and edit profiles with complexity cases that will use the script generated by

AvsOptimizer. It comes with 4 profiles:

* Default - (default one): Great for all sort of movies.
* Anime - For anime movies.
* Alternative - Alternative profile to default one.
* Debug - Profile that will show on screen the complexity case that AVSOptimizer is using in that moment (only for testing)

-Added new option of 1/2 CD, or 1/3 of CD in number of CDs list box. (For 2 or 3 chapters of a serie in a CD)

-Added a little window to configure credits settings (quantizer, greyscale, weight...) inside ARCalculator, however, it still DOES NOT WORK.

-Now, Compressibility check allows us to change the size of video final, and the number of CDs, burning mode... and see how changes de compressibility calculated without to repeat again the test with different values.

-Now, you can edit the AVSOptimizer avs script, or to use a compressibility check with it.

-Now, crop line is not added in avs script if you doesn´t configure any crop.

-Now, you can choose the resolution you want, without limits.

-Now, you can edit any script, and use it for AVSOptimizer pass.

-Aspect Ratio error, is now shown in negative and possitive values (in 0.9.2 was shown in absolute values). Besides, it has 2 colours: Green, for error lower than 3, and Red, for others.

-Fixed a bug in advanced Aspect Ratio options when the height were changed, now, it changes correctly, and with the mod you want.

-Some minor bugs fixed.

-New language: German (Still incompleted - Thanks to Nobody, Hybrid, LigH & falkDeluxe)

-French, German, and Croatian languages are still not finished in this new version, so it is possible, that some lines aren´t translated on these languages).

You can download it HERE (http://canalxvid.urbenalia.com/pafiledb/pafiledb.php?action=file&id=28)


ARCALCULATOR 0.9.3 FAQ

What do I need for using ARCalculator?

A- Your need Avisynth 2.53 or later installed, an OS: Windows 9x, Me, 2k, NT or XP , or Linux with Wine. For using all features of the program (like AVSOptimizer new, it is neccesary to use XviD 1.0 beta or later.

Can I use ARCalculator with other codec?

A- Yes, you can use the codec you want, but special features like Compressibility Check, or AVSOptimizer will only work with XviD codec.

How do I use New AVSOptimizer?
A-For using new optimizer, it is recommended not to use any de-noisy filter (like fluxsmooth, Convultion3D ...) to do the additional optimizer pass . (Only is recommended to use that sort of filters when it is a noisy source or a very low quality one). Filters like undot, or lumafilter, YES are recommended for additional pass. Like this, we allow that avsoptimizer has more accuracy choosing complexity cases. About the profiles, the default one works OK for almost every video. Anyways, you can choose Anime Profile for that sort of movies, or create, edit, or save a new one. It also is recommended that you use same settings for AVSOptimizer new pass, and the 2 normal passes. You can choose a % of avsoptimizer pass, from 10% to 100% . High values are more accuracy trims that low ones. Anyways, an additional pass of 10% works fine. We recommend 30% for quality/speed. However, if the time is not problem for you, go for 100%.

Why the avs script generated by AVSOptimizer new sometimes crash the encoding?

A-That scripts need a good computer to work perfectly, because avsoptimizer generates a big amount of trims. If your system has low RAM and you have problems, try to edit the scriptm, and change the firs line (SetmemoryMax(100)) for a lower value, like SetMemoryMax(60).

Does ARCalculator configure credits settings of XviD codec automatically?

A- No. ARCalculator allow to the user to configure the codec manually(credits included), but it doesn´t gives you the possibility of configuring credits inside the program (The credits menu configuration is not implemented yet)

What rules must I follow to create/edit profiles for the new AVSOptimizer?

A-Just configure the 10 complexity cases (from C0-low complexity, to C9-high complexity), and use, at least a resize filter in each one. Use XRES,YRES. If you want to use some additional avisynth filter, you will have to edit manually (Edit AVS buttom) the script generated, adding neccesary "LoadPlugin" lines. If you want to use less complexity cases, you only have to configure some cases with the same settings.

What values for Compressibility. check are the optimal ones?

A- That is up the user, but as recommendation, if you are using old XviD versions (before XviD 1.0 betas), a value of 70,75% with the choosen resolution use to be OK... if you are using XviD 1.0, it would be 60,65%. If you are going to use AVSOptimizer, 50,55% is OK for good quality. Of course, the highest compressibility values, the more quality obtained.

Sorry for my english... I now it is really bad.

Greetings

[m0rtal]

Originally posted by DarkDudae
Why the avs script generated by AVSOptimizer new sometimes crash the encoding?

A-That scripts need a good computer to work perfectly, because avsoptimizer generates a big amount of trims. If your system has low RAM and you have problems, try to edit the scriptm, and change the first line (SetmemoryMax(100)) for a lower value, like SetMemoryMax(60).[/B]
well, how much memory is necessary actually? or how much memory is recommended to have?

[DarkDudae]

Originally posted by m0rtal
well, how much memory is necessary actually? or how much memory is recommended to have?

We recommend 256, but with 128 Works OK(just that if it gives problems, maybe you need to low the SetMemoryMax value to 60.

Regards

[vaxis]

First of all, thanks for this brilliant program.

Now on to my problem. I have tested to run avs optimizer on two different dvds (rock in rio and one episode of fawlty towers). On both of them, the result is the same. Here's the procedure I perform: I first choose "New AVS Optimizer", go with the default profile and then "start calculates" with 100% analysis. Then I go with 1 pass encode in the xvid settings dialog that pops up. It's after that when the problem appears. The analysis only runs 240 frames of 45530 for fawlty towers and 240 frames of 186252 for rock in rio. That's not even close 100%...

So it appears that regardless of which movie I run an avs optimizer on, it only runs 240 frames.

Another thing that seems to be a bug is that no matter what encoder you choose it runs avs2avi anyway.

Looking forward to get a solution of my problem!

[DarkDudae]

@vaxis
Those 240 frames, are an avisynth script error. Try to open that avs file with a player,(like if it would be an avi file) and you will see an error instead of the video. Please, post it. By the way, do you have avisynth 2.5.3 installed?

About the external encoder, have you choosen correctly the path to the encoder you want to use? Think that avs2avi will allways be used for Comp. Check, and for AVSOptimizer pass.

Regards

[Gazza]

My first test with the new version resulted in error messages "not a valid d2v...". I then tried re-installing avisynth (version 2.5.4) and now everything works well.

ARCalculator is a fine program, especially now it works with the latest xvid betas.

Gazza

[vaxis]

Ok. I have found the reason for the 240 frames problem. I come from Sweden (perhaps a problem itself =)) and one of the folder in my path to the d2v file has a letter that's not in the english alphabet. So in the mpeg2source function in the produced avs file the unknown letter was ignored. So it's not so strange that the avs file didn't work!

About the encoder thing, I didn't know that avs2avi always was used for avsoptimizer. Obviously I haven't explored the program enough. I didn't know that this program was similar to gordian knot in that case that it makes the whole encoding process easier. I have only focused on the awesome avs creating stuff...

So both of my problems are solved. Thanks!

[Gazza]

At the end of the compressability test, arcalculator crashed with the following message "8 8 is not a valid integer value". Got any ideas what could cause this? I think I had a similar message at the end of the first pass when using the latest xvid beta 3 with an old version of arcalculator.

Gazza

[DarkDudae]

@Gazza
Maybe that problem is because you have chosen Dev-api-3 instead of XviD 1.0 betas/Dev-Api-4

Greetings

[DarkDudae]

Just to say, that ARCalculator works perfectly with new XviD 1.0 RC1.

Greetings

[Gazza]

@DarkDudae,
Thanks. I will give it another test.

Gazza

[kadajawi]

When using the new avs optimizer with beta 3 and rc1 it only encodes the first 240 frames of the video. This occurs when using filters (having set to UnDot and Convulsion3D). Using only UnDot works. The filename is 100% without non english characters, I have AVIsynth 2.5.3 installed. And usually I use C3D without problems.

[DarkDudae]

@Kadajawi

Try to open that avs with your media player (the 240 frames video is an avisynth error screen).

And then, you will see a screen error... can you, please, post it?.. and if you can... it would be helpfull you post the avs itself here too :)

Thanks in advance

[kadajawi]

hmm, if I manually set in my filters it works. Using the same filters I checked in AR Calc. But I convert to YV12 first before applying filters. Source is a huffyuv file. Will try to reproduce the error later.

[loni_blues]

@DarkDudae

Hi,

Is the compressibility test for Xvid 1.0 betas in AR calculator 0.9.3 100% accurate with b-frames enabled? In case not, how much does the value it gives differ from the real one?

Thanks a lot,

loni_blues

[DarkDudae]

Comp. check works with B, and without B-frames correctly. Api3 and Api4 are different. Usually, you will get lower comp. values with api4. It is a difference of about 12,5%. Anyways, api4, with comp. values of 65% will produce better results that api3 with comp. of 75%.

Let´s say that the references are different.

In the next days we will release ARCalculator 0.9.4.

Greetings

[loni_blues]

Thanks, DarkDudae.

Let´s say that the references are different.

Does the difference between Api3 and Api4 comp check values lie in a different 100% quality reference, since I believe that Api3 uses as reference for 100% quality a fixed quant 2, while Api4 uses a fixed quant 1? Or is the difference in the comp check values between them due to something else?

Thans again,
loni_blues

[iradic]

I'm using xvid 1.00 rc1

When loaded avs in ARcalc avs is this line - avisource("*.avs",false)... is this correct?
Also I get error "Text exceeds memory..." (can't remember exactly) after New AVS Optimizer - avi Trailer ... (winMe 640MB ram)

[DarkDudae]

@iradic

Recently some users of W9x/Me are reporting us that problem. Under W2k, XP... works perfectly.

However, in other W9x/Me computers, it works OK too... so we really don´t know where is the problem right now, and why only in some computers. We are trying to find what is wrong.

Thanks and sorry for that.

Greetings

[Nozomi]

I am new to this program and I want to give it a try but the FAQ can't answer my questions... Please advice if the following sequence of steps are correct:

Data Menu
Video properties
1) Open a .d2v

Audio properties
2) Open the required audio track

3) Select CD Size / No. of CD

4) Press "Calculate"
Anything I need to change in the "Encoding Optimal Values" or "Other Dates (Advanced Users)"? Do I need to Crop here? Do I need to change the resoultion here?

5)File -> Save as avs

6)Select the correct encoder program (e.g. Vritualdub MOD) location, then what should I do next? "New AVS Optiomizer" or "Compresibility Test".

[DarkDudae]

@Nozomi

Before you press button "Calculate", you should do autocrop. For that, go to Crop-Change-AutoCrop, and then, press Calculate.

If you want, you can change resolution. The next is ups to you. You can do a comp. check if you want to adjust the resolution, or, if you want, you can to try AVSOptimizer to create an avs script automatically.

Greetings

[Nozomi]

AR 0.9.3 w/XviD v1.0 RC2

I found the above error message pop up when enter:

1) New AVS Optimizer -> click "Ok" to AVS Optimizer Profiles, I can continue with the calculation but after calculation finish and return, the same error message pop up.

2) Compresibility Test -> Start -> "OK" to What XviD version are you using, no matter I select "Dev-Api3" or "XviD 1.0 beta" and return to the original "Compresibility Test" screen. Cannot start the Comp Test at all.

[Nozomi]

@DarkDudae

I've done the Auto-Crop as adviced but the same error message pop up as mentioned above and I cannot proceed with the Comp Test. I am using English version of Windows XP Home Edition and a Dell I8600 notebook.

[Nozomi]

@DarkDudae

I completely exit AR and done everything again with your Auot-Crop suggestion before calculation... Now no more error message and I can continue with the Comp Test, thanks!

[Nozomi]

When I select 700M 1xCD:
Calculated Result
Bitrate 441Kbits/s
480x272
Error with Current Configuration 41.93%

When I select 700M 2xCD:
Calculated Result
Bitrate 1266Kbits/s
608x336
Error with Current Configuration 40.421%

What is this error with Current Configuration % means?

I use the above (700M 2xCD) Crop value and proceed with the Comp Test. Compresibility Test result video with selected setting = 7540.08%. What is this % value means? What is the suitable % value for a correct resolution setting?

When I attempt to change/reduce the resolution and press "Calculation" again it reset to the original Autocrop resolution value, is this normal? How can I change the resolution value and re-calculate?

[DarkDudae]

@Nozomi
That "Error with current configuration" is Aspect Ratio Error, and it should be between 0 and 5%. Maybe that you have not selected Original Aspect Ratio correctly (4:3-16:9) or that you are changing that value after of pressing the "Calculate" button. Anyways, of course you can change resolution manually to adjust Aspect Ratio Error (In Other dates -Advanced Users- you can change Width or Heigh manually. Or, you can change it in "Encoding Optimal Values - Resolution.

What you say about change resolution and re-calculate, has not mean since what is calculated is the resolution. If you want to change resolution, and use that resolution for comp.check, avsoptimizer etc... just select it and then: File-Save Avs.

Greetings

[Nozomi]

Thanks, Aspect Ratio Error being corrected to less than 2% then File-Save Avs. Compresibility Test result video with selected setting = 10727.86%, what does this funny value incidate? I would expect Comp Test result should always be less than 100%.

[Nozomi]

I am glad to report that problems with Auto-Crop wrong Aspect Ratio being identified due to a wrong .d2v source being used :-( Compressibility Test result video with selected setting now get down to 128% looks more reasonable but how come still over 100?

[pitiwat]

I have some questions.
In Gknot, I have options to set IVTC before encoding ,but in AR CALCULATOR 0.9.3. How can I do this? Besides, I don't want to force film in DVD2AVI, because some movies have progressive and interlace. So I can not force film.
:confused:

[Siku]

There's 'Use Deinterlacing filters' under the Misc Filters section. There you can choose the deinterlace method that you prefer.

[pitiwat]

There's 'Use Deinterlacing filters' under the Misc Filters section. There you can choose the deinterlace method that you prefer.

I understand, but I need to convert 29.976 fps to 23.976,too.
So, IVTC in AVISYNTH is the only method. Maybe the developers add this option to AR CALCULATOR:(

[DarkDudae]

@Nozomi

That value of 128% in compressibility, is normal. Excesive, but normal if you are using a high bitrate or lower resolutions. Do the comp. check, and then, you can increase resolution, or use 1 CD instead of 2 CD. When you change resolution, or final filesize, you will see how the compressibility values change. The optimal values for compressibility are between 60 and 75% for XviD 1.0.

@pitiwat

IVCT is not implemented in ARCalculator... you are the first one who asked for that. Anyways, maybe in future versions we add it.
You can edit avs script manually ...

Greetings

[pitiwat]

Thank DarkDudae for implementing this feature.
I think IVTC is essential for newbie like me.
Could you please explain how to edit avs manually?
(Showing example of this script, please)

:)