AR CALCULATOR 0.9.4 Final !!!!!

[Enigmax]

Mashabak has created an excellent tool to obtain greater quality in compressions of 1 CD with XviD. One is at the moment in version 0.9.4 Available here:
http://canalxvid.urbenalia.com/pafiledb/pafiledb.php?action=file&id=28
Link Repared
In that page you have to click in DESCARGAR (download in spanish) button.

A great work :).
Thanks Mashabak and DarkDudae.

NEWS:

ARCALCULATOR 0.9.4

CHANGELOG


- Credits configuration window is working now. All credits XviD 1.0 zones can be created in ARCalculator. (You only have to configure start, and ending frames for credits and then, configure credits windows with your chosen settings.

- Shutdown Computer automatically option added.

- Fixed bug when AVSOptimizer script + subtitles were used together.

- Now the audio size in manual mode is set to 0 by default.

- Fixed litle bug that caused error with old AVSOptimizer the first time it was executed. (Only in some computers)

- Now, final video size will be automatically configured by ARCalculator (so you don´t have to put it manually in codec configuration)

- Added new versions of fluxsmooth and mipsmooth filters. (Thanks to all avisynth developers)

- New internal functions for optimal work.

- Fixed problem when XviD codec had not been used by first time and its registry entries were not initialized.

- Fixed wrong deinterlacing filter bob configuration.

- Fixed bug when you push 4:3 or 16:9 aspect ratio without any d2v opened.

- New Avs2Avi version (1.35) included. It works better with time estimations, and now it works with XviD 1.0 Status window.(Thanks to developers of this great CLI encoder).

- Added shortcut to Avs2Avi encoder in File menu. (Just if you want to encode directly from an avs file previously created)

- Added full ARCalculator's manual (in spanish
if you are interested in translating to other languages, please, contact with us). Thanks seth and affar for this wonderful work

- Added 1/4 of CD in CDs number.

- Hopefully fixed "Text exceeds memo capacity" error in Comp.Check and AVSOptimizer options for users with W9x/ME OS.

- Changed Default NewAVSOptimizer profile with a new one that offers better quality. The old one now is the Alternative profile.(Thanks daviduco for this work).

- Added croatian language (thanks to ffroms).


Remember you need at least Avisynth 2.5.4 and XviD 1.0 RC3 for full compatibility with advanced options. It is HIGHLY recommended you uninstall any previous ARCalculator versions and you reboot your computer after you install the program.



ARCALCULATOR 0.9.3 FAQ
By DarkDudae:

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

[Teegedeck]

Could you explain in more detail how this tool resizes better than/different from GKnot?

[Enigmax]

It incorporates a new called tool AVS Optimizer, that making one first pass analyzes the video and creates optimal script AVS, applying to different filters (resized, blur...)from the video. Example: Blur in accion scenes, Simple in quiet scenes, Bilinear in credits, UnFilter, Undot... Created differents trims in the AVS script.

Later makes the two last normal passes with the optimized AVS. Their results are very good, increasing the compressibility until 30/40%. Recommended for rips in one CD.

Greetings

[sysKin]

IMHO the idea is very interesting, and the proggy needs to be checked :)

Does it support both dev-api-3 and dev-api-4? That's more or less what I figured out from our irc talks ;) but correct me if I'm wrong :)

Radek

[DarkDudae]

ARCalculator is a useful tool programmed by Mashabak for www.canalxvid.com that can help with XviD Encodings. You can open a .d2v, avi or avs file and then, the program works like others AR Calculators, however, it has a lot of features. Whith this tool, you only need a .d2v proyect and your audio file for all XviD Encoding process. It calculates AR, crop, Video Size, resolution, compressibility tests for all XviD versions, avs etc. Besides, as Enigmax has said, it has an utility called "AVSOptimizer", witch makes an additional XviD pass to create an optimized avs script. It studies the sort of video, its changes between high and low motion scenes, what it needs, etc, and then, it uses different filters for each sort of scene...(it is able to detect almost 20 different cases of video complex)so, this tool is ideal for long and complex movies you want to fit in a single 700MB CD with good quality. This feature remember filters like the great QMF avs filter, however they work in different ways. QMF studies the changes of scenes, and it can detect 3 different cases (Low,Medium and High Motion) but it doesn´t count what XviD Codec needs. Let´s say that AVSOptimizer tries to help XviD Codec, adjusting filters, but allways keeping a good quality (as PSNR tests show).

About what advantages or disadvantages has over other tools... just to say that all of them are different, and great programs, and that the user can decide by himself.

[TNM]

Ummm I'm sorry if this is ridiculous but after installing I couldn't find avsoptimizer anywhere... and I dunno Spanish so I couldn't read the manual to find where it is:(
Thanks for creating another good tool for xvid encoding anyway :)

[jonny]

Wow! I was dreaming to program something similar in the future!
This save my a lot of time - going to check ^^

[Mashabak]

Hi, first of all, thanks all for your comments.

TMN, Avs Optimizer is one funtion inside AR Calculator.
To acceed, you must to calculate values on program first screen and then go to "File/Save as avs" and in the next screen you can find a button called "Avs Optimizer". Clicking on this, you acceed to the utility.

Regards, Mashabak.

[precjednik]

Originally posted by Mashabak
TMN, Avs Optimizer is one funtion inside AR Calculator.
To acceed, you must to calculate values on program first screen and then go to "File/Save as avs" and in the next screen you can find a button called "Avs Optimizer". Clicking on this, you acceed to the utility.


I can't get this function work.
Is this function for d2v project only or we can use it with avi files also?
In manual mode it's allways grey out.

[Mashabak]

Avs Optimizer works analizing video properties, based on macroblocks predicted by Xvid on 1 pass, and then, it makes an optimized avs file witch will be used in final encoding.

Then, if you use manual mode, you can´t analise any video, because there isn´t any video to be analysed.
The method only can be used on .d2v files at this moment, but I´m working on a version that can support avi files.

And finally, you only can enable "Save as avs" option if you use a .d2v file, because in manual mode is not logical to save any avs file.

I hope I resolved your doubts. ;)

Regards, Mashabak.

[precjednik]

Originally posted by Mashabak
I´m working on a version that can support avi files.


It will be absolutely great!
I know that I'm not the only one who is waiting for such kind of tool.
Keep up the GREAT work!

thx
Cheers!

[Koepi]

I wanted to give this promising tool a go and... it gives me some floating point error when trying to open a .d2v created with Neuron2's dvd2avidg version :(

Can you extend the software to be able to use 1.77.3-d2v versions as well?

Best regards
Koepi

[Mashabak]

@ precjednik

Thanks :D

@ Koepi

I test with version 1.76 and version 1.85 by gloval and with these versions works fine, but I know this bug, and I´m searching information to fix it.
I hope that can be fix soon.


Regards.

EDIT: Can you tell me where can I find this version of DVD2AVI to test with?

[jjseth]

There´s a version of ARCalculator0.81 for Devapi4 by Mashabak (but the compresibility test it isn't included) here (http://www.canalxvid.com/uploader/ArCalc-DevApi4.zip) .
In this case compresibility test may be done with a tool by DarkDudae. Download here (http://miarroba.com/foros/ver.php?temaid=1057692&foroid=66725)

No problem with .d2v created by Dvd2avi1.85 by Gloval in ARCalculator 0.9 for Devapi3 and ARCalculator0.81 for Devapi4.

[TNM]

Originally posted by Mashabak

TNM, Avs Optimizer is one funtion inside AR Calculator.
To acceed, you must to calculate values on program first screen and then go to "File/Save as avs" and in the next screen you can find a button called "Avs Optimizer". Clicking on this, you acceed to the utility.

Regards, Mashabak.

Hi, thanks for yr answer.

I just run a test with a 640x448 m2v clip. ARCalc suggested the res to be 704x384 which made my clip distorted, and I couldn't change the res back to normal for compressibility test and avsoptimizer (the error is always > 0%)
:confused:
One more thing... this is actually a feature request :D Looks like AVSOptimizer only suggests value for blurring in motion scenes so I'd really love if it can also suggest value for deinterlace and decimate... and yeah, support for .avi is also great ;) Again, thanks a lot for this awesome tool :)

[Koepi]

Mashabak:

There is a interesting thread here (http://forum.doom9.org/showthread.php?s=&threadid=44150) which fixes some bugs of dvd2avi like dropping some frames etc.

Donald Graft's website (http://neuron2.net/fixd2v/decodefix.html) has the binaries and sources available.

I hope this helps.

Regards
Koepi

[Balm]

I tested the tool a little and I am positively surprised. :)
Will there be a "stand alone"-version of the Avs Optimzer in the future?

Cu Balm

[Mashabak]

@Koepi

Thanks for info, I didn´t know drop frames bug on dvd2avi, but it is interesting prevent this. I will work on this to fix all possible bugs :p

@Balm

Until the moment I had not thought that possibility, but can that I makes it.

@TNM

Well, I will explain the real function of the program.
It, in the origin, was born as an utility to show best resolution for a video keeping in mind that bits per pixels was 0.25 (Development gruop think this is the best value), with the real aspect ratio, fps, duration, etc... Then, the program gets original video resolution and, after crop proccess, calculates real aspect ratio; and with this value, video duration and fps, calculates the best resolution to have 0.25 bpp, but after this, the program rouds this resolution to show a resolution compatible whit overlay (Width/32=0 and height/16=0).
Because it, the showed Optimal resolution hasn´t aspect error 0, but you can change the values in "Other data (Expert users)" and in crop section to use your favorite resolution with an aspect error 0.

Talking about avsoptimizer, We (development group) decided to apply a blur filter to complicated scenes (different values for each case of dcomplexity), but this was only the first idea, and we are working to tune the filters´ values (and filters type) with PSNR tests to get the best optimization that the filters could do.

Regards, Mashabak.

[neuron2]

Originally posted by Koepi
I wanted to give this promising tool a go and... it gives me some floating point error when trying to open a .d2v created with Neuron2's dvd2avidg version :(

Can you extend the software to be able to use 1.77.3-d2v versions as well?
Koepi! Hail.

Just FYI...dvd2avidg can save 1.76 style D2Vs. Of course, I agree with you that the tool should be able to read both styles. I believe Nic pioneered that finesse; I just copied him.

[DarkDudae]

Well, the support for .d2v files made with DVD2AVI 1.77 is fixed yet, so, next ARCalculator version, will support them perfectly. It will support devapi4, and it will come with some other features.

Greetings

[Koepi]

Heya Donald,

I know that there is the option to save "1.76 d2v", but i was in a hurry (needed to go to bed to have at least 4 hours sleep before having a usual 10hrs work day) so I decided not to "waste" another 10 minutes by creating another d2v project file but hope for the drive of a fresh, new application and it's coders ;)

And - you wrote something in that loooooong thread about buggyness of that older d2v project file format so I thought it would be best to go with your version origin(? my english sucks a whole lot more than it used to these days) files.

I'll try with 1.76 export tomorrow (~3 am here now) as I really have great expectations of this tool.

Best regards
Koepi

[Ruppl]

Here is an example for an AVS-Optimized script...

->AVS (http://mitglied.lycos.de/ruppl19/stuff/optimized_script.htm)

[precjednik]

Originally posted by Ruppl
Here is an example for an AVS-Optimized script...

->AVS (http://www.ruppl.de.tk/stuff/optimized_script.htm)

Hey!
Suprising, just can't wait, this looks VEERY promising!
So tweaked, so good (and so pure, and simple also).
I will not hurry devels, but instead, trust me, many people (me included) would not have enough words to thank you.

Cheers!!!

[Selur]

there isn't that much 'variation/optimisation' in the script, mainly it's just a variation in the blur settings,..

"it is able to detect almost 20 different cases of video complex"
Will these 20 different cases also dealt with differently ?

Cu Selur

[Ruppl]

@ Mashabak

When i´m using the AVS Optimizer it makes one pass and then it generates the optimized script. After that I start a two pass encoding!
This means: Normal two pass with avs optimzer = 3 Passes!!?

Is it possible, to make a two pass encoding and the optimzation is included in the first pass?!
And the compCheck should be started after optimizing!!?

[Mashabak]

@Selur

At the moment, optimizer only uses blur filter with different settings depending of complexity. But it´s only the first pass on the development, because we will do some PSNR test to know what filter and with what value are the best to apply in each situation.
For wath I see in that script, this movie have "medium complexity", because blur values are 0.1 and 0.2 almost always. I think that Optimizer works more fine when situation is extrem (you have a little bitrate to encode, for example), because in simply movies, you can get a good quality without external methods as optimizer.
And yes, optimizer can detect almost 20 cases of video complex, but depending the movie, this will be 10, 15, 5, etc.
Now, it is only a "previous version" to see if it works fine and detect correctly complexity cases (works fine, but not "perfectly"), and in the future we will change filters, values, and complexity cases.

@Ruppl

Yes, Optimizer needs 1 adittonal pass to analize video characteristics from the point of view of XviD codec. Then, makes an optimized avs and save it. Because it (it changes avs values), you must do then a normal 2 pass compression with optimized avs.
Because of optimizer works from the point of view of XviD codec, it is necessary to do the adittional pass, but if you know how to do the same work with only 2 passes, you will convert me on the most happy man on the world :D.

Regards, Mashabak.

[jonny]

Yes, Optimizer needs 1 adittonal pass to analize video characteristics from the point of view of XviD codec.

Why don't you try to use a sort of sampling (with SelectRangeEvery)?
The only big problem to solve with this approch is that you don't have an exact figure of the keyframes allocation...

[Selur]

...we will do some PSNR test ...
http://forum.doom9.org/showthread.php?s=&threadid=61128 might also be interesting,.. ;)

Cu Selur

Ps.: Keep up the nice work :)

[DarkDudae]

@jonny
As you have said, avsoptimizer analyzes datas between 2 keyframes to calculate the complexity. So it is not possible to do a SelectRangeEvery at the moment. (Maybe making some changes in the code, but it would be less effective)

@Ruppl
Compressibility test is recommended to be done before avsoptimizer pass(to adjust the resolution).

@Everybody
Note that this tool is in an early state of develop. So, there are many things to do. There are great ideas on it.

[crOOk]

@Mashabak
Great idea, this avs-optimizer thing. Best news regarding compressibility issues for a long time.
Using blur filters in different variations for every scenario does not sound very promising though...
Maybe you should let the user configure which filter to use for each kind of material... This way we could all experiment with different settings (Just think of how many different denoisers there are, lots of space for additional search processes). The results could be reported here and possibly be implemented into a later version of your (hopefully soon stand-alone tool) avs-optimizer.
I hope you'll keep up the great work, I think many users would really appreciate your tool! BTW I'll try it out right now and if it benefits the encode I'm doing right now (Dirty Deeds, script could be improved for 1 cd, 1stpass size@roughly 1200Megs), I might just as well never let go of it again, too bad it's so far from completion.

[Mashabak]

@Crook

Yes, It´s really the idea that we have ;). When finish to implement avi support (and other minor funtions), I will do a special version with configurable filters on avs optimizer to test this in different video situations, to get the best optimization in each situation.

Regards, Mashabak.

[crOOk]

Great news. I can't wait to see it!

[Heathcliff]

i try this sofware on the dvd "caligula" (150 mins) and the quality is outstanding !!! it outperforms my old rip...
i must say the supplemetary pass is very very long to do, but this tool is really good ! thanks :D

[Mashabak]

Hi, here it is a new version, AR Calculator 0.9.1

Changes:

-Added compatibility with d2v projects generated by DVD2AVI 1.77.x

-Added support for avi and avs files

-Added support for XviD Dev-Api-4 versions (compressibility test included).

-Added custom errors messages when you try to use CALCULATE button, this will help to know what is going wrong.

-Fixed a little problem when you changed from AR 4:3 to 16:9

-Fixed a problem when you regret from preview avs files after a compressibility test.

-Fixed a problem of avs files preview when dimensions where out of the screen.

-Fixed problem of wrong resolutions after do croping using custom resolutions.

-Added advanced options for resolution and Aspect Error in Crop Screen.

-Added support for subtitles in VobSub format (idx).

-Fixed a problem showing advanced data after a compressibility test.

-Added an option that allows to see how changes compressibility automatically in changes of resolution.

-Fixed a problem with negative values in predicted size video calculates.

-Fixed a problem making compressibility avs script.

-Added more possibilities to change resolutions, from advanced and simple tab.

-Fixed other minor bugs and added minor characteristics.

-Added languages portuguese(thanks to Obcecado), Catalan (Thanks to Enigmax and _Dardo_), Euskera (Thanks to Kalisto), Gallego (thanks to Mele and Affar), and french(thanks to CoCo). If you are interested in translate ARCalculator into other languages, you are welcome :)

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

That is all.

Regards.

[precjednik]

First of all, thank You for this great tool!

Manage to make some tests...
And run into some problems.

I captured 30 sec from local TV station to test this clip with your tool.After loading avi I got this error

ERROR1 (http://web.vip.hr/horvat_stanko.vip/1.jpg)

Same when I put desired size

ERROR2 (http://web.vip.hr/horvat_stanko.vip/2.jpg)

But OK, everything went fine... here is the pic (http://web.vip.hr/horvat_stanko.vip/3.jpg)

But then I got this (http://web.vip.hr/horvat_stanko.vip/4.jpg) error.

Trying to open temporal.stats... but proggi create temporal.avi file instead... :(

So I am unable to take advantage of AVS Optimizer tool, yet :)
Is it something related with my system or just a minor bug you could easy remove :)

Thx for your time, cheers!

[Mashabak]

Hi all.

Some people have commented me this error, although it has been a surprise to me since in my system and in others in those that have been carried out tests everything works correctly.

I think that it is caused because I load avi files with an avisynth script.

Now you wondered reason I make it this way: I make it this way to can charge xvid files compressed whit Dev-Api-3 versions having installed Dev-Api-4 version.

I will try to fix it using avisnth to charge avis (to conserve Dev-Api-4 compatibility in this case), but if it isn´t possible, I will charge avis directly.

Regards.

[CruNcher]

@precjednik

do you have also problems loading avs files into Gknot or any other Delphi application ? and do you have this unofficial WindowsXp Kernel Build installed thats floating arround lately if you useing Xp ?

[precjednik]

@Mashabak

About first two errors... they are gone. After rainy night, I was sleeping like a baby, and errors are gone :D
Maybe computer have to sleep too :)

But problem with false opening temporal.stats (instead temporal.avi created by prog) still exist.
I made my way to overcome this problem. Just waiting for command prompt window called by AVS Optimizer to be gone, in this moment just before loading temporal.stats, using automation tool temporal.avi is converted to temporal.stats.

Tricky, but works for me.

@CruNcher

Unfortunately, I don't use GKnot just because I never do any DVD rip. DVDs aren't cheap in our country, even when boroved from video store (it's illegal too :) heheh) so my movie collection is mainly made from captured analog material.
WindowsXP is official, but without any service packs (and any Microsoft software lately including IE and other stuff.... thanks to XPLite)... maybe there could be the reason.

Thanks all for your replying, the problems are gone (or can be easily overcome).

Cheers!

[DarkDudae]

@precjednik

That is a very strange error. Maybe it is something about registry lines. What XviD version are you using? and, what OS?

We know some avi opening strange issues, but that is new :D

Regards

[precjednik]

@DarkDudae

I have installed latest unstable Koepi's binary (XviD-24062003-1).
OS is WinXP without Service Pack, trimed down to cca 350 MB :D total (without installed programs)... for video editing purposes.
I suppose that's why this strange error appear. It's strange though, because I don't get any other errors in all installed apps.

Something is missing probably... I'll try to find out what (File Dependencies, try to search registry etc...) after work.

I'm using a bypass as I describe, rename temporal.avi to temporal.stat just before the AVS Optimizer try to open it.

Cheers!

[Ruppl]

I have done a mini Test with new Version AR Calculator 0.9.1!
My Source is the Trailer from "Lord of the Rings - Fellowship" DVD, it´s a very good source....

Here are two images for comparing

Not Optimizied (http://mitglied.lycos.de/ruppl19/stuff/no_ar_calc.png)

Optimized (http://mitglied.lycos.de/ruppl19/stuff/ar_calc_0.91.png)

For me AR Calculator is going to be a very nice alternative for Gknot. It works fine on my WinXP System!

[Enigmax]

Good comparison :) .
AR Calculator has become for my a essential tool to obtain the very best possible quality.
Better alternative for rips of a one CD cannot exist.
Thanks Mashabak for your great work.

Greetings

[precjednik]

Originally posted by Ruppl
I have done a mini Test with new Version AR Calculator 0.9.1!
My Source is the Trailer from "Lord of the Rings - Fellowship" DVD, it´s a very good source....

Here are two images for comparing

Not Optimizied (http://www.ruppl.de.tk/stuff/no_ar_calc.png)

Optimized (http://www.ruppl.de.tk/stuff/ar_calc_0.91.png)


I'm going to test it too, huh, when I got time... (this weekend probably)...

So, please give us Xvid encoding options, bitrate and maybe a bit of Optimized script generated.
It's interesting to compare someones encoding options, and you have some nice results :) :)

Cheers!

[ffroms]

I still have a problem opening AVI and AVS (haven't tested with D2V) like precjednik did have. With AVI reports that it is 10 sec. long and with resolution 40x0 and when I try to change resolution it give me "Floating point division by zero" (AVI opens fine in Virtual Dub Mod). When I creat AVS with same AVI (but put false for audio) I have error like precjednik. Anything I click (like resolution or Calculate) I have same error (again avs opens fine in Virtual Dub Mod). Anyway I've manage to start copm. check and when it finished it say analysing stat 100% and it doesn't move.
I have WinXP with latest version of avisynth 2.5.1 (CVS).

@precjednik - did you find what was wrong at your PC?

FFS

[precjednik]

Originally posted by ffroms

@precjednik - did you find what was wrong at your PC?

FFS

@ffroms

Well... nothing is worng with my PC :)
I realized that when trying to run ARCalc on friend's comp, and having same "errors".

The best part is, I'm unable to reconstruct the ERROR situation, the errors are simply gone. Try restarting...

... but, ARC is still trying to open temporal.stat instead created temporal.avi (after AVS Optimizer is finished), but this is probably registry assotiation/problem/IDontKnowWhat. I'll try to find out.
Going to test some clips.

Cheers!

[DarkDudae]

We know the problem opening avi/avs in some computers, and now, we know why it occurs. So when it be fixed (Mashabak is working on it), there will be a new version :) (thanks for posting the problems, and sorry for that issue). Anyways, after installing avsoptimizer, try to reboot the computer, as precjednik did. That would be helpfull.

@precjednik
About that temporal.stats issue, we don´t know why, and you are first one reporting it. Can you give us more info about it?

Thanks again :)

[precjednik]

Originally posted by DarkDudae

@precjednik
About that temporal.stats issue, we don´t know why, and you are first one reporting it. Can you give us more info about it?

Thanks again :)

Don't worry, my fault... false alarm... but probably worth to mention that:

In Xvid encoding options I never have specified where *.stats file should be generated, so ARC couldn't find *stats file. Till now, never have that problem because when encoding in VDub (2 pass), stats files were located in the root drive (suppose default location if no other is chosen) and everything were fine.

Now, I have selected "d:\multimedia\capture\video.stats" (via Regedit to be perfectly safe ;)).

Sorry about alarm... but maybe there is someone with this problem around so...

Wow, hm hm, what to say... PERFECT
THX very much.

EDIT:
Well, about that Temporal.avi/temporal.stats confusion:
There is no day when I don't learn something.
Temporal.avi isn't *.stats file but file which is always generated when encoding to Xvid isn't it?
And somehow related with "Discard first pass" option in Xvid encoding options (not sure about that... but never mind).

[DarkDudae]

ARCalculator 0.9.2

New version of this tool. This time, it is only a "fix bugs" version.

-Fixed problem when loading avi/avs in some computers.

-Fixen problem with preview of avs in some computers.

-Added option of not using any resize filter.

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

IMPORTANT NOTE:

-The use of noise filters before Avsoptimizer pass, makes this less effective in detecting complexity cases. (What it is normal)

-In case you have problem opening avi/avs files after installing ARCalculator, please, reboot and try again.


All ideas, bugs or wathever you want about this tool, will be welcome.

Regards

[ffroms]

Hi!
Thanks for this new version. I've tested right away. I've open same avi as before and this time had no problems in opening :p . I was trying to recompress it to very low resolution (original at 472x276) but can not lower resolution under 480x288 (I was going for something like 192x112 with low bitrate). I don't know if it is problem with me or maybe bug or something else.
Keep up with your great work.

FFS

[Mashabak]

Hi ffroms. It is not your problem. This happends because I programmed it to don´t use low resolutions (originally it is used to encode dvd sources, and I think that encode a dvd source with a lower resolution than 480x*** isn´t ytil).
In next version I will allow to use lower resolutions.

In other thread, Cruncher tell me one problem with last version. If you use Avs optimizer with devapi4 it creates a file called "optimo.stats" but search to analise "temporal.stats". It is a forgetfulness for my part and I have fixed it, but canalxvid server are down at the moment. When it is on-line again I will upload corrected version and a zip file that will contain only executable program (for not having to download the installer again).

Regards.

[ffroms]

Request: I'm sure that you don't have to much time for requests but it would be nice to have something to look for right resolution (like Bits/(Pixel*Frame) in GKnot what I allways use to set resolution for best picture) and maybe some kind of job list for avs optimizer so that I can start jobs over night.
For some time I was looking for good tool to replace GKnot (I'm using it only for setting resolution, calculation of size and comp. check) 'couse I allways open avs in VDubMod and start compression manually and ARCalculator could be that new tool. Alse it could be great to have option to configure filter a little more (like values for unfilter or lumafilter) and still be able to preforme avs optimizer.
Thanks again and looking forward for next release.

FFS

[Mashabak]

About bits/(pixel*frame), it is implented. The program, when you click on "Calculate" calculates best resolution to get 0.25 bits per pixel in this movie, and then rounds this resolution to respect overlay rules (whidth/32 and height/16). Then, you can use this resolution or chage for other one.
About job list, it is one of the things on my TODO list, and I hope to implement it shortly.
And about configure filters to use in script that will be used on avs optimizer, it is also something that I want to make for some time and will include this on next releases.

Regards.

[Ruppl]

(like Bits/(Pixel*Frame) in GKnot what I allways use to set resolution for best picture) and maybe some kind of job list for avs optimizer so that I can start jobs over night.


Those things would be very usefull.....:)

[ffroms]

GREAT !!
Can't wait for next release. I have much more ideas to make this tool flexible and useable by newbie and experts but I'll wait for next release. And thanks for info about bits/(pixel*frame) but I think it would be more usefull to see actual value.

FFS

[Seppe]

I would like to download this program, to experiment with it. But the link has been giving me 404's from the beginning.
Is it possible to set up a mirror for the file ?

thx in advance

[sillKotscha]

Originally posted by Mashabak
...canalxvid server are down at the moment. When it is on-line again I will upload corrected version and a zip file that will contain only executable program (for not having to download the installer again).

[Enigmax]

Here available download alternative for AR Calculator0.92:
http://enigmax.en.eresmas.com/download/arcalculator.zip

Greetings

[Mashabak]

Well, I upload fixed versions of Ar Calculator 0.9.2

Only avs optimizer + devapi4 use error fixed.

HERE (http://www.divxhouse.com/calcul/arcalculator_092.zip) is full version (with installer).

And HERE (http://www.divxhouse.com/calcul/ARCalc092-onlyexe.zip) is lite version (only executable).

To use lite version, simply unpack zip file and replace "ar_calculator.exe" file on AR Calculator´s install directory with .exe inside zip file (to use it, obviouslly, non-fixed 0.9.2 full version must be installed on system before).

Thanks to affar to upload these files to his server (http://www.divxhouse.com) while canalxvid server was ready, and sorry to all for the problems.

Regards, Mashabak.

[ChristianHJW]

... cool idea to change the resizing filter depending on the content. Now please allow me to add that theoretically this could be extended to even select different resolutions during the encoding - again, in theory ! - if we implement the 'codec state' element in MKV video tracks, that would allow to reinitialize the codec in the middle of the stream.

Needless to say, there is absolutely NO WAY to play such a video stream on DirectShow, so we had to say Good-Bye to some of our preferred players and go for win32 versions of mplayer or VLC ....

[Koepi]

Please stop spamming on non-related topics chris.

Koepi

[cjaar]

@Mashabak

any support for divx??? or can i use the optimized avs file for divx.

thx
cjaar

[DarkDudae]

Originally posted by cjaar
any support for divx??? or can i use the optimized avs file for divx.

AVSOptimizer doesn´t support DivX codec. Codec DivX is different that XviD one, so they dond´t need filters at same scenes, so maybe an AVSOptimizer script can help DivX Codec, but not too much. It is a full additional pass that for DivX hasn´t sense.

Greetings

[Mashabak]

@cjaar:

AR Calculator works with Divx codec, but two features are implemented especially for XviD: Avs Optimizer and compresibility test.
Then, you can save an avs file and encode with Divx in avs2avi or VDub, but you only can use optimizer and compressibility test with XviD codec.

And to use optimized avs file with Divx... I have never test this case and I can´t answer if it can be useful, but I think it isn´t, because optimized file is created from the point of view of the XviD codec and Divx analyzes in a different way video frames.

Regards, Mashabak.

[ffroms]

Just one little question. Do I have to set Xvid like for encoding or I can set it to minimum (like no Qpel,Bframe, Chroma Motion etc) 'couse I have very slow PC (Celeron 800). As I understand ARCalculator analyze stat file from xvid and where bitrate distribution goes up program set more blur or change resize filter and where is low bitrate it sets sharper resize and no blur. Activating extra features (bframe,Qpel etc.) will not effect avs optimizer too much or maybe I'm wrong?
BTW I think avs optimizer could help divx5 but you have to encode it manualy.

FFS

[Mashabak]

I internally configure XviD codec to do first pass with (I think) best values to analyse video complexity. Then, you don´t need configure the codec before first pass.

Regards.

[ffroms]

I have to report a possible bug. I'm trying to encode some video that I have in avi. Everything was OK but then I selected start credits but it's not at begining of video (credits start at 3921 frame). Created AVS looks like this
#########################################################
# Script Generado por AR Calculator #
# #
# http://www.canalxvid.com #
#########################################################

LoadPlugin("C:\PROGRA~1\ARCALC~1\mpeg2dec3.dll")
LoadPlugin("C:\PROGRA~1\ARCALC~1\unfilter.dll")
LoadPlugin("C:\PROGRA~1\ARCALC~1\undot.dll")

Avisource("C:\1\VIDEO.AVI",false)

LumaFilter()
Crop(0,0,-0,-0)
UnFilter(-5,-5)
Undot()
a=trim(3921,5754).BilinearResize(480,224)
b=trim(5755,77367).LanczosResize(480,224)
c=trim(77368,79272).blur(0.5,0.5).BilinearResize(480,224)
a+b+c

As you can see I'm missing first 3920 frames of video. I guess it's nothing serious but I hope you'll fix it in next realese.

FFS

[jjseth]

The avs script created count the video frames from the first inicial credits frame to the last final credits frame.
In this case i dont'n mark any credits and i add to the final avs ...=trim(xxx,xxx).BilinearResize(xxx,xxx) taking care to keep the trims/frame order.

Sorry my poor english.

[Mashabak]

Thanks for info. I had not thought on this case. I will fix it in next release.

Regards.

[ffroms]

@jjseth - Thanks for explaining but I understand why that happens. I only wanted to point out the bug.

@Mashabak - Great. I'm waiting for next version to test it. BTW same thing happens for end credits (at end of video). Maybe it would be good to remove crop if all crop values are 0 (like in my example) couse I've read in Avisynth forum that crop function slow down everything a little (frameserving). This program could be use for DVD 2 DVD conversion too.

FFS

[Manao]

For the AVSOptimizer's developpers :

Take a look there (http://forum.doom9.org/showthread.php?s=&threadid=63442&highlight=trim+memory) and there (http://forum.doom9.org/showthread.php?s=&threadid=46570&highlight=trim+memory).

I tried your tool, it looks great, but it takes a lot of time ( around 1 minute ) to load the script in vdub. Modifying the script using the ideas in these two post made the loading almost instanteanously.

[MoonWalker]

Hi,

I think I have found a bug at the ARCalculator..When you press "Save AVS" it saves the avs but when you make a 1-pass with AVS optimizers or any other function it uses it's own avs not the one you have changed..Also it doesn't save setting like the path of VdubMOD..

Regards,
MoonWalker

[ffroms]

I've noticed that to but I'm waiting for new version to see if that is changed and to look for more bugs. I'd like to be able to change AVS (add some diffrent filters) and then run AVS optimizer with changed AVS.

FFS

[DarkDudae]

Thanks everybody for your reports and suggestions, of course these litle bugs will be solved in future versions.

@Manao
Thanks for that scripts, maybe we optimize memory use with some changes like that.

Thanks to the work of ffroms, you can download a new language for ARCalculator: Croatian (http://canalxvid.urbenalia.com/uploader/Croatian.zip)
Just unzip this into languages folder in ARCalc Working Dir.

We need someone translate it into german :(

Regards

[Ruppl]

We need someone translate it into german :(

I will look for someone who could do this! I don´t have any time for this,.........i hate school....;)

[Mashabak]

Hi all and thank you for interest :)

@Moonwalker

At the moment, different forms to work with avs filters works independently; then, for example, if you change something in form "Edit Avs" these changes aren´t saved to work with avs optimizer. Now, only filters you choose in form "Save avs" are implemented to be remembered in the rest of forms, but I´m working to integrate this in such a way that all the forms interact among them.

Regards.

[ffroms]

GREAT! That will make AR Calculator more flexable. When will new version come up (I'll do tutorial on new version in Croatian)?

FFS

[Affar]

why isn't this program announced in doom9's news if it's the same or better than Gordian Knot?:confused: :confused:

Regards
Affar

[ffroms]

AR Calculator is not "all in one" tool nor it is better or worse than GKnot ('couse they work differently). This tool that will help you get your encoding better. There is still some bugs to be kill and then (maybe) it will be in news sections. We will see what is in new version.

FFS

[HellSpawn]

I used the latest version to make a pass for the movie "Matrix Reloaded".After a couple of hours the .avs that was produced had loaded the filters I wanted (undot,fluxsmooth etc) but at the various trim points it only used Lanczos resize and blur.Is that a bug or did I do something wrong?Thanks in advance.

[ffroms]

No it's not bug. That is the way it works. All your filters are used for global picture but AVS Optimizer uses Xvid STATS to analyze movie and sets blur where are moving parts (to set lower bitrate), and clear sharp picture for static parts.
In next version it should use diffrent resize filter for diffrent part of movie.

FFS

[HellSpawn]

So you are saying that the filters will actually be used and that I should use that .avs as always?

[ffroms]

Yes. Use filters when ever you need so. If you dont need them uncheck them in program or manualy delete them from avs script.

FFS

[HellSpawn]

What I want is use lets say convolution at low motion scenes and fluxsmooth at high motion scenes.How can I do that?

[ffroms]

As far as I know , for now there is no option to do that. Only manualy.
When you use Convolution for whole video, and blur on high action parts that is something like using fluxsmooth on high action parts.
Maybe in next version it will be more flexible so that you can use diffrent filters on difrent parts of video. We'll se when it comes (hope soon).

FFS

[tiki4]

@DarkDudae: Hi,

I just wanted to say that current ARCalculator doesn't work with current CVS dev-api-4. As your tool already supports the upcoming XviD 1.0 maybe is is important to know that for the developers. I think GomGom changed the layout of the .stats file so all tools using it have to be adopted. If you already know that fact, just ignore my post.

tiki4

[DarkDudae]

@HellSpawn

You can use an option called "Avisynth optimization", instead of AVSoptimizer. It uses QMF conditional filter, and you can configure, low, mid, and high motion scenes filters, resizers... etc.
Anyways, future avsoptimizer will allow you to configure all differente complexity cases.

@tiki4

Thanks for the info. As you have said, the stats file has changed a little, so it is easy to fix it. Next version will support latest CVS version in that moment.

Greetings

[Alxemi]

Hi Spanish people around the XviD scene... i hope we´ll meet in the IRC soon. We are not so many and we need to be togheter!! :)
Just here to notice that another thread (http://forum.doom9.org/showthread.php?s=&threadid=65009) about avsoptimizer has been started in the avisynth forum, maybe you want to take a look.

Best Regards and seeya!!

[tiki4]

@DarkDudae:

Thanks for the info. Your work is really very much appreciated. Great tool.

tiki4

[koszopal]

here my error :
after optimalization
ive got script .avs:

LoadPlugin("D:\movie\ARCALC~1\mpeg2dec3.dll")
LoadPlugin("D:\movie\ARCALC~1\undot.dll")
LoadPlugin("D:\movie\ARCALC~1\Fluxsmooth.dll")

Mpeg2Source("C:\eliza\ELIZAB~1.D2V")

LumaFilter()
Crop(4,76,-8,-88)
Undot()
Fluxsmooth(7,7)
ai=trim(0,5118).LanczosResize(608,320)
aj=trim(5119,5157).blur(0.1,0.1).LanczosResize(608,320)
ak=trim(5158,5449).LanczosResize(608,320)
al=trim(5450,5614).blur(0.1,0.1).LanczosResize(608,320)
am=trim(5615,5935).LanczosResize(608,320)
an=trim(5936,6001).blur(0.1,0.1).LanczosResize(608,320)
ao=trim(6002,6057).blur(0.6,0.6).LanczosResize(608,320)
ap=trim(6058,6095).blur(0.2,0.2).LanczosResize(608,320)
aq=trim(6096,6185).blur(0.3,0.3).LanczosResize(608,320)
ar=trim(6186,6237).blur(0.4,0.4).LanczosResize(608,320)
as=trim(6238,6949).LanczosResize(608,320)
at=trim(6950,6990).blur(0.1,0.1).LanczosResize(608,320)
au=trim(6991,12325).LanczosResize(608,320)
av=trim(12326,12388).blur(0.1,0.1).LanczosResize(608,320)
aw=trim(12389,13915).LanczosResize(608,320)
ax=trim(13916,13968).blur(0.1,0.1).LanczosResize(608,320)
ay=trim(13969,18113).LanczosResize(608,320)
az=trim(18114,18143).blur(0.1,0.1).LanczosResize(608,320)
ba=trim(18144,19086).LanczosResize(608,320)
bb=trim(19087,19136).blur(0.1,0.1).LanczosResize(608,320)
bc=trim(19137,23078).LanczosResize(608,320)
bd=trim(23079,23143).blur(0.1,0.1).LanczosResize(608,320)
be=trim(23144,46318).LanczosResize(608,320)
bf=trim(46319,46359).blur(0.1,0.1).LanczosResize(608,320)
bg=trim(46360,47282).LanczosResize(608,320)
bh=trim(47283,47330).blur(0.1,0.1).LanczosResize(608,320)
bi=trim(47331,49116).LanczosResize(608,320)
bj=trim(49117,49148).blur(0.2,0.2).LanczosResize(608,320)
bk=trim(49149,53536).LanczosResize(608,320)
bl=trim(53537,53583).blur(0.1,0.1).LanczosResize(608,320)
bm=trim(53584,53931).LanczosResize(608,320)
bn=trim(53932,53959).blur(0.1,0.1).LanczosResize(608,320)
bo=trim(53960,64015).LanczosResize(608,320)
bp=trim(64016,64265).blur(0.1,0.1).LanczosResize(608,320)
bq=trim(64266,67708).LanczosResize(608,320)
br=trim(67709,67755).blur(0.1,0.1).LanczosResize(608,320)
bs=trim(67756,68406).LanczosResize(608,320)
bt=trim(68407,68528).blur(0.1,0.1).LanczosResize(608,320)
bu=trim(68529,71437).LanczosResize(608,320)
bv=trim(71438,71519).blur(0.1,0.1).LanczosResize(608,320)
bw=trim(71520,86272).LanczosResize(608,320)
bx=trim(86273,86407).blur(0.1,0.1).LanczosResize(608,320)
by=trim(86408,86438).LanczosResize(608,320)
bz=trim(86439,86510).blur(0.2,0.2).LanczosResize(608,320)
ca=trim(86511,94589).LanczosResize(608,320)
cb=trim(94590,94642).blur(0.1,0.1).LanczosResize(608,320)
cc=trim(94643,94678).LanczosResize(608,320)
cd=trim(94679,94851).blur(0.1,0.1).LanczosResize(608,320)
ce=trim(94852,94949).LanczosResize(608,320)
cf=trim(94950,94976).blur(0.1,0.1).LanczosResize(608,320)
cg=trim(94977,104876).LanczosResize(608,320)
ch=trim(104877,104966).blur(0.1,0.1).LanczosResize(608,320)
ci=trim(104967,105632).LanczosResize(608,320)
cj=trim(105633,105795).blur(0.1,0.1).LanczosResize(608,320)
ck=trim(105796,106244).LanczosResize(608,320)
cl=trim(106245,106298).blur(0.2,0.2).LanczosResize(608,320)
cm=trim(106299,106332).LanczosResize(608,320)
cn=trim(106333,106372).blur(0.3,0.3).LanczosResize(608,320)
co=trim(106373,106819).LanczosResize(608,320)
cp=trim(106820,106861).blur(0.1,0.1).LanczosResize(608,320)
cq=trim(106862,115438).LanczosResize(608,320)
cr=trim(115439,115600).blur(0.1,0.1).LanczosResize(608,320)
cs=trim(115601,121704).LanczosResize(608,320)
ct=trim(121705,121768).blur(0.2,0.2).LanczosResize(608,320)
cu=trim(121769,129991).LanczosResize(608,320)
cv=trim(129992,130035).blur(0.2,0.2).LanczosResize(608,320)
cw=trim(130036,130232).LanczosResize(608,320)
cx=trim(130233,130284).blur(0.1,0.1).LanczosResize(608,320)
cy=trim(130285,166027).LanczosResize(608,320)
cz=trim(166028,166095).blur(0.1,0.1).LanczosResize(608,320)
da=trim(166096,166248).LanczosResize(608,320)
db=trim(166249,166386).blur(0.2,0.2).LanczosResize(608,320)
dc=trim(166387,167219).LanczosResize(608,320)
dd=trim(167220,167267).blur(0.1,0.1).LanczosResize(608,320)
de=trim(167268,170773).LanczosResize(608,320)
df=trim(170774,177663).blur(0.5,0.5).BilinearResize(608,320)
a+b+c+d+e+f+g+h+i+j+k+l+m+n+o+p+q+r+s+t+u+v+w+x+y+z+ai+aj+ak+al+am+an+ao+ap+aq+ar+as+at+au+av+aw+ax+ay+az+ba+bb+bc+bd+be+bf+bg+bh+bi+bj+bk+bl+bm+bn+bo+bp+bq+br+bs+bt+bu+bv+bw+bx+by+bz+ca+cb+cc+cd+ce+cf+cg+ch+ci+cj+ck+cl+cm+cn+co+cp+cq+cr+cs+ct+cu+cv+cw+cx+cy+cz+da+db+dc+dd+de+df

u see this line a+b+c...etc
I think it should be ai+aj+..etc.
koszopal

[trbarry]

If I understand all this right this script is driven off the quants in the Xvid log file. If so it could be made extremely powerful and versatile by just referring to a separate function for each quant, where we could define these with our own filter preferences. For instance:

function QuantFunc1(clip v1){
return v1} # just return for quant=1

function QuantFunc2(clip v1){
return UnDot(v1)} # filter tiny bit for q2

function QuantFunc3(clip v1){
return UnDot(v1).UnFilter(-8,-8)} # a bit more, etc.

...
ai=trim(0,5118).QuantFunc1
aj=trim(5119,5157).QuantFunc2
ak=trim(5158,5449).QuantFunc1
al=trim(5450,5614).QuantFunc3
...
ai+aj+ak+al + ... . .LanczosResize(608,320)

Eventually we could all converge on our favorite filters and QuantFunc's for each quant.

- Tom

[DarkDudae]

koszopal@

It is very strange. Can you tell me what XviD version, source and OS you have used?

trbarry@
No, AVSOptimizer doesn´t work in that way, it doesn´t use quants, it is more complex. It reads quants, mblocks, kblocks... from stats file to detect complexity cases.

Greetings

[trbarry]

trbarry@
No, AVSOptimizer doesn´t work in that way, it doesn´t use quants, it is more complex. It reads quants, mblocks, kblocks... from stats file to detect complexity cases.


Okay, sorry, I should have read more carefully. I was only directed to AVSOptimizer today in a respone to another post of mine asking for a similar function. And it looks like I could get the results I wanted (bunch of personal blur functions) with a global edit macro anyway if I needed. But it is too early to know for sure.

Still have not tried it but it sounds very impressive. Nice work! :)

- Tom

[koszopal]

@DarkDudae
hi
OS - W2k + SP4 + latest hotfixes.
XVID koepi 24-06-2003
source was DVD Elizabeth (i ve just made rip using GK but i wanna compare with AR Calculator)
koszopal

[tiki4]

Any news about this tool? I'd like to try it with current XviD 1.0 betas.

tiki4

[Mashabak]

We have published 2 new program betas compatible with xvid 1.0 beta1 and beta2 (not with beta3 because changes in stats file), but not any official version (and because it, there are some lines that aren`t translated into english). If you want test this, go to canalxvid forums (http://canalxvid.urbenalia.com/phpBB2/viewtopic.php?t=254&start=0) or download the executable (http://canalxvid.urbenalia.com/uploader/ARCalculator093B.zip) (only executable without installer). In this version, also xvid 1.0 beta compatibility, we have added a new experimental avs optimizer, which can do only a % of necessary additional pass (minimum 10%) and can configure the filters you will use in each complexity case (with profiles if you want).

Regards.

[ffroms]

Sorry it doesn't support beta 3. Hope that will be soon.

FFS

[tiki4]

Thanks for info, I guess I will give it a try. I appreciate your work very much.

tiki4

[Gazza]

Mashabak,
I appreciate your work and have found your tool very useful. Any progress with a version that can handle beta 3 of xvid 1.0?

Cheers

Gazza

[DarkDudae]

@Gazza

We are working on it... compatibility with latest beta, is not a hard thing (just change some code lines). Maybe we have a "final" version in a few days ;)

Regards

[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?

[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)

:)

[Nozomi]

@DarkDudae

Am I correct that I need to use the XviD "Two-Pass first pass" setting when AVSOptimizer pop up the codec configuration screen? I need to keep the same codec configuration for the later normal 2 pass encoding with the AVSOptimizer generated .avs?

[DarkDudae]

@Nozomi
AVSOptimizer will use allways XviD 1st pass, so, if you choose single pass, or 2nd pass, it will use 1st pass for avsoptimizer pass, so don´t worry about that.

It is recommended you use same configuration for avsoptimizer pass and 2 normal passes because the complexities of scenes will be detected with the settings of the codec used in additional pass.

For more info, read ARCalculator FAQ witch is in this same thread.

Greetings

[flloyd]

Originally posted by DarkDudae
In the next days we will release ARCalculator 0.9.4.

Any news on this. I just found this yesterday and it seems to be doing great but new and improved features are always appreciated.

[DarkDudae]

Originally posted by flloyd
Any news on this. I just found this yesterday and it seems to be doing great but new and improved features are always appreciated.

Thanks !

Well, 0.9.4 is mainly a bugfixes version, but it comes with some utilities, like configure XviD zones credits from inside ARCalculator easily, and some new internal functions.

Right now, we are working in ARCalculator 1.0... and well, it will come with a lot of news ...

Greetings

[m0rtal]

DarkDudae
have you ever seen what FuPP is working on?
take a look: http://forum.doom9.org/showthread.php?s=&threadid=70734

[V|E|G]

Hi there,

Just wondering how ARCalculator 1.0 is coming along-its a great alternative to GKnot, especially when combined with the AVS optimiser.
Any news?

[DarkDudae]

ARCALCULATOR 0.9.4

CHANGELOG


Credits configuration window is working now. All credits XviD 1.0 zones can be created in ARCalculator. (You only have to configure start, and ending frames for credits and then, configure credits windows with your chosen settings.
Shutdown Computer automatically option added.
Fixed bug when AVSOptimizer script + subtitles were used together.
Now the audio size in manual mode is set to 0 by default.
Fixed litle bug that caused error with old AVSOptimizer the first time it was executed. (Only in some computers)
Now, final video size will be automatically configured by ARCalculator (so you don´t have to put it manually in codec configuration)
Added new versions of fluxsmooth and mipsmooth filters. (Thanks to all avisynth developers)
New internal functions for optimal work.
Fixed problem when XviD codec had not been used by first time and its registry entries were not initialized.
Fixed wrong deinterlacing filter bob configuration.
Fixed bug when you push 4:3 or 16:9 aspect ratio without any d2v opened.
New Avs2Avi version (1.35) included. It works better with time estimations, and now it works with XviD 1.0 Status window.(Thanks to developers of this great CLI encoder).
Added shortcut to Avs2Avi encoder in File menu. (Just if you want to encode directly from an avs file previously created)
Added full ARCalculator's manual (in spanish if you are interested in translating to other languages, please, contact with us). Thanks seth and affar for this wonderful work :)
Added 1/4 of CD in CDs number.
Hopefully fixed "Text exceeds memo capacity" error in Comp.Check and AVSOptimizer options for users with W9x/ME OS.
Changed Default NewAVSOptimizer profile with a new one that offers better quality. The old one now is the Alternative profile.(Thanks daviduco for this work).
Added croatian language (thanks to ffroms).


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

Remember you need at least Avisynth 2.5.4 and XviD 1.0 RC3 for full compatibility with advanced options. It is HIGHLY recommended you uninstall any previous ARCalculator versions and you reboot your computer after you install the program.

[jimmy basushi]

@ darkdudae - gave your new AR Calculator version a try on my Win98 system that used to get the other "text exceeds memo" error and it works perfectly now. great work again!

[DarkDudae]

Originally posted by jimmy basushi
@ darkdudae - gave your new AR Calculator version a try on my Win98 system that used to get the other "text exceeds memo" error and it works perfectly now. great work again!

Nice to hear that jimmy, it has been hard to find that bug since almost everybody uses Windows 2k/XP :)

[jimmy basushi]

yea darkdudae, thats why i just used my other winxp box for ArCalc.. problem is in xp sp1a the sun java is slower and screwy when you use it heavily like i do so i had to go back to win98 with virtual machine :(

was the bug something to do with win98's problem of reading bigger then a 64k text file using notepad? that was my theory..

[DarkDudae]

@jimmy

Yeah, it was something about that. Stats XviD files were loaded into a delphi component, and if that stats was higher than 64k, that error was produced under W9x/Me. We changed that component and it seems it works. :)

[grua]

Hi,

I wrote a profile for New AVSOptimizer especially for analog TV-captures. The filers result approximately in the same compressibility like the filters in ARCalculator's default-profile, but they remove noise of analog captures more effective.

For C0, C1 and C2 (low motion?) I only use temporal filtering, for C7, C8, C9 (high motion?) only spatial. From C3 to C6 the temporal part ist decreased and the spatial part is increased.

I use PeachSmoother and VagueDenoiser because of Wilbert's recommendations for analog TV-captures (see http://forum.doom9.org/showthread.php?s=&threadid=71485).

I'm loading the captured AVI in ARCalcualtor via an AVS-script in which I use UnDot(). Then I use the NewAVSOptimizer with the following profile:

C0=clip.PeachSmoother(NoiseReduction=20, Stability=30, Spatial=0, Noiselevel=nl, Baseline=bl).LanczosResize(XRES,YRES)
C1=clip.PeachSmoother(NoiseReduction=20, Stability=30, Spatial=0, Noiselevel=nl, Baseline=bl).BicubicResize(XRES,YRES,0,0.75)
C2=clip.PeachSmoother(NoiseReduction=30, Stability=20, Spatial=0, Noiselevel=nl, Baseline=bl).BicubicResize(XRES,YRES,0,0.5)
C3=clip.PeachSmoother(NoiseReduction=50, Stability=30, Spatial=30, Noiselevel=nl, Baseline=bl).BicubicResize(XRES,YRES,0,0.5)
C4=clip.PeachSmoother(NoiseReduction=60, Stability=30, Spatial=80, Noiselevel=nl, Baseline=bl).BicubicResize(XRES,YRES,0,0.5)
C5=clip.PeachSmoother(NoiseReduction=60, Stability=30, Spatial=130, Noiselevel=nl, Baseline=bl).BicubicResize(XRES,YRES,0,0.5)
C6=clip.PeachSmoother(NoiseReduction=60, Stability=30, Spatial=180, Noiselevel=nl, Baseline=bl).BicubicResize(XRES,YRES,0,0.5)
C7=clip.VagueDenoiser(threshold=4, method=1, nsteps=6, chroma=true).BilinearResize(XRES,YRES)
C8=clip.VagueDenoiser(threshold=4, method=1, nsteps=6, chroma=true).BicubicResize(XRES,YRES,0.8,0)
C9=clip.VagueDenoiser(threshold=5, method=1, nsteps=6, chroma=true).BicubicResize(XRES,YRES,1.2,0)

Peach's vaules of Noiselevel and Baseline are determined in VDub in a low motion scene with PeachSmoother(Readout=true,Dot=true).

cu, grua

[DarkDudae]

Thanks for your work grua, this profile will help a lot of people.

C0,C1...(low complexity) and ...C7,C8,C9(high complexity).

It is not a simple low motion and high motion detection... new AvsOptimizer studies not only motion, but complexity of scene, and besides, it is adaptative, (adaptative to motion, compressibility, bitrate you have for that movie...) so, a script for 1CD movie will be very different with a script for the same movie but 2 CDs.

Regards

[jimmy basushi]

one question for you darkdudae also, how come your version of the avisynth dlls are *so* much smaller then the released versions from the authors? they seem to work the same tho?

[TorgoGuy]

Originally posted by jimmy basushi
one question for you darkdudae also, how come your version of the avisynth dlls are *so* much smaller then the released versions from the authors?
Haven't looked at them, but perhaps he uses UPX: http://upx.sourceforge.net/

[Mashabak]

Yes, as toroguy says, we use upx to repack dll and exe files to do it smaller (the files works exactly as original but has smaller size).

Regards.

[DarkWave]

hi,

wow, what a great tool ;)

i just tried your tool and what do i have to say: the result is outstanding! not only that i went back to xvid after using divx for a (maybe too) long period, no - encoding is reduced to a third of the time i used to spend with divx (standard-standard-slowest)...

two suggestions:
what about a possibility for running in batch mode (i´m encoding stargate sg-1 atm - four episodes a time)?
is it possible to implement an option to let your tool mux an existing ac3-file?

thx for your affords and sorry for my typical german school-english ;)

DarkWave

[DarkDudae]

@DarkWave

About "bath mode", next version will come with a lot of new features, and one of then, will be a full queue job control (like VirtualDubMod one).

Muxing audio/video is something we also are planning for future versions.

About your english, don´t worry, I am not native english speaker... (like most of us) :D

Regards

[DarkWave]

Hi,

me again ;)

after testing settings within arcalculator, there´s just one question left (and i tried to get through the avisynth manual for this as well - but maybe i didn´t get it or my english isn´t enough...)

when you have somehing like this in your .avs

clip=Mpeg2Source("E:\epicap14.d2v")
clip=LumaFilter(clip)
clip=Crop(clip,2,6,-2,-2,align=true)
clip=Undot(clip)

C0 = clip.LanczosResize(640,352)
C1 = clip.LanczosResize(640,352,0,0.75)
C2 = clip.Unfilter(-5,-5).LanczosResize(640,352,0,0.75)
...

Does it mean, that first all filters are used, before the clip is resized?
Or does it first resize and then apply filter?

After working with divx for a long time i archieved better results when first resizing, then applying filters...
so, if it´s answer 1, can i do something like this:

C0 = LanczosResize(clip,640,352)
C1 = LanczosResize(clip,640,352,0,0.75)
C2 = LanczosResize(Unfilter(clip,-5,-5),640,352,0,0.75)
...

thx in advance for help ;)

DarkWave

[Ark]

[QUOTE]Originally posted by DarkWave
clip=Mpeg2Source("E:\epicap14.d2v")
clip=LumaFilter(clip)
clip=Crop(clip,2,6,-2,-2,align=true)
clip=Undot(clip)

C0 = clip.LanczosResize(640,352)
C1 = clip.LanczosResize(640,352,0,0.75)
C2 = clip.Unfilter(-5,-5).LanczosResize(640,352,0,0.75)
...

Does it mean, that first all filters are used, before the clip is resized?
Or does it first resize and then apply filter?
[QUOTE]

This has not much sense for me, because you're saying:

clip is Mpeg2Source("E:\epicap14.d2v") (OK)
clip is LumaFilter(clip) (but now "clip" is Mpeg2Source("E:\epicap14.d2v") or LumaFilter??)
the same goes for the others.

You can more simply do so:

clip = Mpeg2Source("E:\epicap14.d2v")
clip.LumaFilter().Crop(2,6,-2,-2,align=true).Undot()

or

Mpeg2Source("E:\epicap14.d2v")
LumaFilter()
Crop(2,6,-2,-2,align=true)
Undot()

..without specifying any argument.

[DarkDudae]

@DarkWave


clip=Mpeg2Source("E:\epicap14.d2v")
clip=LumaFilter(clip)
clip=Crop(clip,2,6,-2,-2,align=true)
clip=Undot(clip)


This means, that these filters are used in all the movie (like general filters) These filters are the ones you check in avs creation window of arcalculator. About if it is better to put them after resizing, I have to say that it is better for speed, but not for quality (at least for us). Anyways, you can edit ARCalculator Profiles manually and save them, so, if you want to use Lumafilter and Undot during all the movie, just edit the profile like this:


...
C0 = clip.LanczosResize(640,352).Lumafilter().Undot()
C1 = clip.LanczosResize(640,352,0,0.75).Lumafilter().Undot()
...


Anyways, maybe we give the option of filters before, and after resizing in future versions.

@Ark

This:

clip=Mpeg2Source("E:\epicap14.d2v")
clip=LumaFilter(clip)
clip=Crop(clip,2,6,-2,-2,align=true)
clip=Undot(clip)


Is the same that:

clip = Mpeg2Source("E:\epicap14.d2v")
clip.LumaFilter().Crop(2,6,-2,-2,align=true).Undot()


We are using allways the clip argument because it is easier in programming terms for us, and it is the same.

Greetings

[DarkWave]

@DarkDudae

thx for your fast reply and help ;)
i would appreciate an option for changing the sequence filter <-> resizing

happy easter ;)

DarkWave

[DarkDudae]

Someone reported us that the link to the program is not working properly... the correct one will be allways updated in the first post link (Enigmax one).

It is this:

http://canalxvid.urbenalia.com/pafiledb/pafiledb.php?action=file&id=28

(in that page you have to click in DESCARGAR (download in spanish) button.

Greetings

[davegould]

I just made a full rip of Kill Bill 1, at 652x340, that is 630792kb (not added subs) and yet looks pixel perfect, even frame-by-frame.

I changed a few things from normal XviD encoding: VHQ 4 instead of 1, Jawor's 1-CD quant matrix and, of course, ARCalculator and its filters.

I almost gave up on ARCalculator because of the lack of English instructions. If you want a hand with some translation, let me know. (I can't translate, but I could probably clean up an automatic conversion).

[DarkDudae]

Well, the english manual is in our TODO list, but we have not time. Besides, our english is not far good enough and we don´t like Babelfish translations hehe. If someone want to help us to translate the manual into english or other languages, or translate the program to another language (rusian and italian would be great) he will be welcome.

If someone is interested, please, contact with Mashabak or myself with a PM.

Regards

[pelle412]

First off I'd like to thank the AR Calculator developers for a fine piece of software.

Would it be possible to make the AVS Optimizer use the encoding application that I select as opposed to always use avs2avi at normal CPU priority? (Selecting VirtualDubMod has no effect on AVS optimizer...) Alternatively, allow configuration of CPU priority (-p flag). I'd like to be able to use my computer during the AVS optimizer pass without everything going in slow motion.

Thanks!

[DarkWave]

Originally posted by pelle412
First off I'd like to thank the AR Calculator developers for a fine piece of software.

Would it be possible to make the AVS Optimizer use the encoding application that I select as opposed to always use avs2avi at normal CPU priority? (Selecting VirtualDubMod has no effect on AVS optimizer...) Alternatively, allow configuration of CPU priority (-p flag). I'd like to be able to use my computer during the AVS optimizer pass without everything going in slow motion.

Thanks!

Hi,

you can use your taskmanager to set priority of the encoding process...

greetz
DarkWave

[DarkDudae]

davegould has fixed english.ini translation of ARCalculator 0.9.4.

Old translation was not very good (sorry, I was the one who translated it from spanish to english, and as you can see at these lines, my english is really bad)

You can find the language file HERE (http://enigmax.eresmas.com/English.zip)

Thanks for your work davegould :)

Just unzip the file and overwrite the existing one in ARCalculator\languages folder.

About the priority process, next version will fix that and it will allow to change it in runtime.

Greetings

[pelle412]

@DarkWave: Yes but that is less convenient.

[davegould]

Originally posted by DarkDudae
davegould has fixed english.ini translation of ARCalculator 0.9.4.

Old translation was not very good (sorry, I was the one who translated it from spanish to english, and as you can see at these lines, my english is really bad)

Nah, wasn't as bad as I thought - you used the word "edition" a few times which really threw me!?!

Besides, you should see my Spanish. ;)

Hopefully, it will help a new English-speaking user to use this great program. Any feedback, please PM me.

I also tried to add short descriptions of the general filters, but what does "clip=LumaFilter(clip)" actually do to the luminosity?

[nemoxnine]

First I'd like to say a big "thank you!!" for producing this quality program. :)

Secondly, I just installed Windows Server 2003, and I had a problem using ARCalculator. There was an error when I tried to use either optimizer. I solved this by downloading the latest build of avs2avi from http://daveel.leffe.dnsalias.com/ and replacing the version you packed in your install program.

I'd suggest updating this, assuming it still works with your software, which it appears to now. :)

Best of luck,

nemo

[DarkDudae]

@nemoxnine

We don´t include avisynth in the installer of ARCalculator. We only include some avisynth filters neccesary for the correct working of program. In this same thread, you can read that Avisynth 2.5.4 or higher is neccesary for using ARCalculator because we use some new instructions in the avs files.

By the way, thanks for your words, we are happy the program is helpfull for all of you :)

@davegould
clip=LumaFilter(clip) sentence is only used in avsoptimizer scripts. In normal scripts we use Lumafilter() that it is really the same thing.
Lumafilter, basically, makes dark zones darker, and the sime for bright ones. It is some sort of contrast filter. You can find more info about it in avisynth.org, but it works in this way:

LumaFilter(clip, integer "lumoff", float "lumgain")
the transfomation is : yy = (y*lumgain)+lumoff

lumoff :
Luminosity offset.
default = -2

lumgain :
Luminosity gain.
default = 1

Greetings!

[gnr]

Thanks DarkDudae for this great tool. found a prob while using it. whenever i use "new avs optimizer" with 10% of video to analysis, it does the full 1st pass and takes sametime as "avs optimizer" takes. And my crop setting was "0,12,-2,-12" but i found in avs "0,12,-0,-12". i checked these several times. am i making any mistake?

[DarkDudae]

Originally posted by gnr
found a prob while using it. whenever i use "new avs optimizer" with 10% of video to analysis, it does the full 1st pass and takes sametime as "avs optimizer" takes.

When you do the New Avs Optimizer 10% pass , during that pass a file named: temporal.avs will be created in you ARCalculator folder. Open it with notepad, and post that file here to check where is the problem. Anyways, the last line of that script, should be this:

SelectRangeEvery(140,14)

And my crop setting was "0,12,-2,-12" but i found in avs "0,12,-0,-12". i checked these several times. am i making any mistake?

Yeah, some of the new avsoptimizer profiles, are using filters like mipsmooth witch needs width resolutions MOD 4 for working correctly, so the program, automatically change softly the crop to make resolution MOD 4. If the source+crop is MOD 4, the program will not alter the crop.

Greetings!

[gnr]

heres the temporal.avs
==========================
LoadPlugin("F:\PROGRA~1\ARCALC~1\mpeg2dec3.dll")

Mpeg2Source("C:\ICE_AGE\ice.d2v")

Crop(0,12,-0,-12,align=true)
b=trim(0,108524).LanczosResize(576,320)
c=trim(108525,116878).blur(0.5,0.5).BilinearResize(576,320)
b+c
=========================

i kept all the avs. temporal.avs, one after "new avs optimizer" and one after "avs optimizer". if u want to analyse i can upload.

thanks

[DarkDudae]

heres the temporal.avs
==========================
LoadPlugin("F:\PROGRA~1\ARCALC~1\mpeg2dec3.dll")

Mpeg2Source("C:\ICE_AGE\ice.d2v")

Crop(0,12,-0,-12,align=true)
b=trim(0,108524).LanczosResize(576,320)
c=trim(108525,116878).blur(0.5,0.5).BilinearResize(576,320)
b+c
=========================


That is an avs optimizer normal script, not a new avsoptimizer script.

Delete it from the ARCalculator, and make sure you post the one created during NEW Avs Optimizer pass (open the avs during the additional pass and copy again)

It has not sense it creates a avsoptimizer script instead of an newavsoptimizer script :confused:

Regards!

[nemoxnine]

Sorry for my ignorance above :) I found avs2avi in the ARCalculator folder and assumed I guess.

Keep up the good work.

<edit>

Wait no! I take that back. The running avs2avi problem had nothing to do with using an Avisynth script. If I tried to run it from the command prompt with no arguments it would still give the same error. So you are tricky, but not tricky enough to fool me ;)

[DarkDudae]

@nemoxnine
Ups :rolleyes:, sorry, I readed in your post "avisynth" instead of "avs2avi" .Maybe I was sleepy :o . I will check it right now, but it is strange since noone has reported that bug with avs2avi version we included in 0.9.4 :confused:

Anyways, we allways include latest avs2avi version when we publish a new version of the tool, so there is not problem. Your post maybe it will help people if they experience that problem.

Thanks