AR CALCULATOR 0.9.4 Final !!!!!

[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