Ar Calculator v 1.0.0

[Mashabak]

After more than one year of life, ARCalculator finally arrives to 1.0.0 version.

Changelog:
-----------
-All program code rewritten.
-New visual aspect, everything has been changed for a more friendly and usable one.
-Overhead Calculation for Avi, Ogm and Mkv containers and a lot of different audio types.
-Added support for 4 audio tracks for calcs.
-Added support for adding extra files (like subtitles, launchers, codecs...) witch will be considered in calculations.
-Now, you can choose "Size Unit" for calc. (KB or MB)
-Preview of video is now integrated in two modes: Resized and Real Size
-Now you can go to a determined frame, or second of the video in the preview. (You also can go to credits start/end frames directly)
-Added new info data like Overhead A/V size... etc
-Now you can modify resolution manually, changing weight and heigh simultaneously or individually (with module defined by user)
-Now, you can set avisynth filters position (Default, before resize, or after resize)
-Added IVTC (Inverse Telecine), witch will allow you fps of vide (i.e: NTSC 29,97 to 23,975fps)
-Now you can hide preview window in advanced filters settings.
-New improvements in AVS Optimizer. Now you can define aggresivity levels for filtering, or you can give priority to motion estimation over other settings (Old AVS Optimizer Method).
-Deleted old AVS Optimizer, since it has been integrated in the New Avs Optimizer.
-Modified QMF default values. (Current ones should give best results)
-Mipsmooth is used now in QMF instead of Convultion 3D.
-Added Queue Job, witch will allow you to add encodings of any video codec, and launch them when you want. You even can add avs optimizer pass followed by two normal passes. (Queue Job is for avs2avi only)
-Now, you can configure, XviD, DivX, or any installed codec inside the program.
-New Stats Reader for XviD 1.x , witch will allow us to analyze this type of files or even compare it with another one. Perfect for comparing bitrate curves between different codec settings or avisynth filters. It allows to save a screenshot of the graph, or define range of frames showed.
-Added a new configuration menu, where you can define usual settings you prefer, like container, encoder, avisynth filters...etc. These values will be used as default ones.
-You can select alternative mpeg2dec decoders, like Donald Graft ones.
-Added Warnings messages in case you haven´t installer XviD 1.x in your computer, or if it has not been initialized.
-Added decimal separator symbol control. No more error in conversions to floats numbers.
-Added status window for AVS2AVI with useful encoding info. It allows you to change priority of the proccess in exec time, or abort it. You can minimize it to system tray, and operate it from there with a popup menu.
-Now you can use VirtualdubMod for compressibility check or for AVSOptimizer pass. (Tested with VDMod 1.5.10.1)
-Added help file with a full manual of the program. (Only in spanish, if you are interesed in transtating it into english, you are more than welcome)
- New Avs2Avi version (1.38)
-Due to interface change... old language files are not usable anymore, so, only english and spanish languages has been added in this release. (if someone wants to translate to other languages, please, contact with us ).

As you can see, there are a lot of changes and new features. In first versions of the program, ARCalculator was only a simple bitrate calculator helpful for choose a proper resolution. The program has changed a lot... in each release have been added a lot of feaures, and now, ARCalculator allows yo to encode a video easily and with a great quality. It has all tools you need for it: Compressibility check, creation/edition of avisynth scripts, optimizer scripts personalized for each video, stats reader for xvid, overhead calcs, queue job ...
Everything we had on mind when we began to develop this proyect, has become a reality with this version. And we will improve it even more in the future.

You can find more information about this tool in the older developmnet thread HERE (http://forum.doom9.org/showthread.php?s=&threadid=62286&highlight=Calculator).

You can find all information about this version in canalxvid forums (in spanish) HERE (http://canalxvid.urbenalia.com/phpBB2/viewtopic.php?t=827).

And, finally, you can download last version HERE (http://canalxvid.urbenalia.com/pafiledb/pafiledb.php?action=file&id=28).

Regards.

[Enigmax]

When AR Calculator in the News of Doom9?
Great program. Simply, the best.

Greetings

[Sharro@Home]

Muchas Gracias por la nueva version!!

Thanks for the nEw VeRsIoN!

All the best

Sharro

[DarkDudae]

A little tip:

If you want to open a d2v proyect created by DGIndex, don´t forget to configure first an alternative mpeg2dec3.dll (like DGIndex.dll) in options/general menu.

Greetings

[drjimmy526]

Anyone else have problems with flash movies after installing AR Calculator? I installed this program, decided to uninstall it a few hours later, during which I opted not to delete flash.ocx or something similar from the system directory. Out of curiosity I tried playing some local flash files to see if they still worked, and most of them were just a white screen. I tried reinstalling Macromedia flash and Swiff player, but no go. I finally had to revert my hard drive a few hours to before I installed AR Calc, and now flash movies work fine (out of curiosity I first reverted to merely before I had uninstalled the program, but the files didn't work - apparently the prog must have done something when it was installed).

[jjseth]

Flash files are played fine for me after ARC installation.:confused:

Thanks for this great tool. The best for XviD works, now with DivX and other codecs and AVSoptimizer+every codec support....yeah!

SethNet.tk (http://www.sethnet.tk)

Sorry my poor english:o

[Mashabak]

drjimmy: I suppose that the problem is that we install swflash.ocx on winsysdir/macromedia/flash folder. It´s possible (I can´t verify this now) this file was only-read property. Try to find this file and remove this property. Anyway, we prepare the installer to ask when another swflash.ocx was installed on system; because it´s possible that the installer ask and you press "yes" to overwrite.

Regards.

[Lobuz]

What about HD resolutions? It looks like they are not supported. Are there any plans to support .ts(HDTV)-> XviD(HDTV) conversions? I mean resolutions like 1920x1088 or 1280x720.

Regards
Lobuz

[Mashabak]

In the next version is probably that HDTV resolutions be supported.
Anyway, if you want use these resolution now only must change the resolution in manually avs edit.

Regards.

[buzzqw]

would be possible to implement a "basic besweet gui" into Ar Calculator ?

BHH

[Enigmax]

DHAudio Encoder, from Affar:
http://www.divxhouse.com/

Good idea for future implementation .;)

Greetings

[jjseth]

:D
DHAenc would be a great implementation for extend ARC support to audio encoding.

[Byonod]

-Due to interface change... old language files are not usable anymore, so, only english and spanish languages has been added in this release. (if someone wants to translate to other languages, please, contact with us ).

Actually I'm in big trouble, but I'll try to start a german translation for the new version as fast as possible, too.

It would be really funny to see a Babelfish translation on the german.doom9 Forum from DarkDudae again or just a post like this one:D :

(darkdudae)Hi again, just to say, that Nobody is translating it into german right now. Thanks to everybody for your interest

(Hybrid) Do you mean #"Nobody" the member# on this board or do you simply mean nobody?? :confused:

cya

Nobody

[DarkDudae]

If someone has problems downloading from canalxvid server, there is a mirror HERE (http://www.divxhouse.com/encoding/ARCalculator-100.zip)

@Byonod
It was funny :D... of course, I was talking about "nobody" the member.

[DarkWave]

Hi,

thx for this new version. will there be an english manual?
'cause i don't know any spanish word, i'm not sure if i understood everything in the spanish manual.
am i supposed to use wether avs-optimizer or qmf or can/must i use both together?

sorry for my crappy english and maybe stupid question(s)...

DarkWave

[jjseth]

Hi DarkWave
You must choose one optimization method: AVSoptimizer or QMF, but i recommend to use AVSoptimizer cause it gives best optimized .avs scripts.
About English manual CanalXviD team tried to find a spanish-english translator but nobody seems to have enough time :( . Maybe in a future version....

[DarkDudae]

Originally posted by DarkWave
will there be an english manual?
'cause i don't know any spanish word, i'm not sure if i understood everything in the spanish manual.
am i supposed to use wether avs-optimizer or qmf or can/must i use both together?


Yeah, there will be an english manual in the future... as soon as we find a volunteer able to translate it from spanish to english. Our english level is not good enough to do it. (None of us is native english speaker).

About AvsOptimizer and QMF , you only have to use one of them. QMF doesn´t need an additional/partial pass, but it requires a powerful PC, and AVSOptimizer gets better results than QMF.

Mini-Guide for optimal results:

In AVS filters, check lanczosresize as resizer, and only Lumafilter and undot. (This example is for clean sources). Make a compressibility check and adjust resolution to get compressibility values from 50 to 60%. If you have more than 60%, you can use higher resolutions. If you are using a DVD as source, and at 704x2xx you get a compressibility values higher than 60%, IMHO you don´t need any type of optimization.

If you have 60% or lower values and you don´t want to use lower resolutions, you can use AVSOptim. with default settings. With a compressibility of 50%+AvsOptimizer you will get a great quality output video. With lower comp. values, it will get good results too, but it will add more filtering.

You can even add AVSOptmizer pass to queue job, and then normal two passes automatically. Anyways, all program buttons and controls have a little help. If you leave mouse cursor on them for 1 second, you will see a hint message with some info about it.

For any doubt, you allways can ask here.

Greetings

[Gambler's Ruin]

hey haven't had a chance to use the new version yet but it looks great. just a note, in the Tools/Tools Menu/Configure Options/Avisynth Settings window, the "Filters Position" is still showing up in Spanish although the language is in English mode. Also, I wouldn't mind translating the "Ayuda y Manual" to English. It doesn't look too difficult or lengthy. My AP Spanish is 5-years rusty but with a dictionary it shouldn't be too bad. It's a great tool, so I wouldn't mind helping out. Even with school/work I could pump out a coupla help sections a day or something. I know how frustrating it was to figure out 0.9.x without a legible manual of some sort. Had to pore over these forums backwards and forwards. Anyways, lemme know if you need some translation done and I'll try and help.

[DarkDudae]

Originally posted by Gambler's Ruin
Also, I wouldn't mind translating the "Ayuda y Manual" to English. It doesn't look too difficult or lengthy. My AP Spanish is 5-years rusty but with a dictionary it shouldn't be too bad. It's a great tool, so I wouldn't mind helping out. Even with school/work I could pump out a coupla help sections a day or something. I know how frustrating it was to figure out 0.9.x without a legible manual of some sort. Had to pore over these forums backwards and forwards. Anyways, lemme know if you need some translation done and I'll try and help.

It would be great if you can help us with translation of help/manual into english. Noone is working on it, so, you can translate what you want. Of course, if you need help with it, or if you don´t understand something, just ask :)

Thanks a lot!

I will send you a PM right now with contact data.

PD: You have reason about filters position translation...I didn´t realize. We will fix it for next version... it is only neccesary some lines in english.ini.

[kadajawi]

I like the tool, but I have a problem with it. The speed:
I want to make the first pass to create the optimized AVS. After having set everything, click on AVS Optimizer, Optimize AVS. Speed is around 10 fps, no matter if I let avs2avi or VirtualDubMod do the job. When I take the temporal.avs created, load it into VirtualDubMod by hand, full processing, same settings in XviD, essentially everything should be the same, and start the encoding, I get 30 to 40 fps. Seems to be wrong to me.
I had the same problem with the old AR Calculator version, but for that I had a work around, something like doing it by hand and then take the resulting stats file, name it like the file AR Calculator awaits, set it to write protection, and start the encode again with AR Calculator. Cancel it and it would take the stats file and process it. That worked fine. But that doesn't work with v.1.0.0 :(

Any idea?

Another thing... when doing it by hand, encoding might take 100 megs of RAM, when using AR Calculator its 300+ megs (and I only have 512, that results in 860 meg RAM usage).

[DarkDudae]

@kadajawi

That speed issue has nothing to do with the program. Internally, we define one only xvid zone at Quant 2.00 in avsoptimizer and comp.check passes. This is the same that using 1st pass full quality checked, witch is slower than normal xvid first pass because VHQ, Qpel and other advanced xvid features are not ignored when creating stats file. We need that type of pass to optimize avs correctly, because a video compressed with VHQ4 will need less filtering that one with VHQ 1. If you check "Give priority to motion estimation" in avsoptimizer settings, it will be used a xvid normal pass, so it will be as fast as allways, but this avsoptimizer is not as good as normal one.

Greetings

[kadajawi]

Oh, ok, then that is a reason of course. Thx :)

[Sharro@Home]

Ola,

In previous version, when resizing, if I selected mod 16 I could go up to 720 x XXX width, how can I do it in new version ?


All the best,

Sharro

[Mashabak]

Originally posted by Sharro@Home
In previous version, when resizing, if I selected mod 16 I could go up to 720 x XXX width, how can I do it in new version ?

In this version you can´t go up 720 x 576 resolution. In next version we will add HDTV compatibility with higer resolutions.
In this version, the only way to do that is editing manually the avs script and changing width and heigth values.

Regards.

[gnr]

Its a great software but i think its less known/popular because it has no english guide. do u like to focus on that too strictly in next version? I am sure that this would be the ultimate tool for 1cd rip.

[DarkDudae]

Originally posted by gnr
Its a great software but i think its less known/popular because it has no english guide. do u like to focus on that too strictly in next version? I am sure that this would be the ultimate tool for 1cd rip.

Gambler´s Ruin offered his help to translate the manual, so, hopefully, next version will have an english manual. In the worst case, we will translate the manual by ourselves, and maybe a native english speaker can correct it.

About low popularity of the program... I don´t think it is because it needs an english manual. There are not english language webs witch announce our tool and it seems they are not interested in the program at all.

Regards

[gnr]

Originally posted by DarkDudae
Gambler´s Ruin offered his help to translate the manual, so, hopefully, next version will have an english manual. In the worst case, we will translate the manual by ourselves, and maybe a native english speaker can correct it.

About low popularity of the program... I don´t think it is because it needs an english manual. There are not english language webs witch announce our tool and it seems they are not interested in the program at all.

Regards

dont be dissapointed. if u keep updating it, it will become popular for sure...u might like to consider renaming it to "AVS Oprimizer" or something like that because Ar calculator sounds a little confusing. u also can submit this to some sites to make mirror and to make this known to ppl. best of luck and thanks again for the hard work.

[grua]

Hi,

when I do a compressibility check with XviD and same settings (resolution, bitrate, filter, ...) in Gordian Knot and in AR Calculator, I get different results. I tested it some days ago with the former version of AR Calculator and I remember that GKnot reported higher compressibility than AR Calculator.

How can it be and how can the values be compared? :confused:

cu, grua

[DarkDudae]

@grua

I don´t know how is compressibility check of gordian knot, or how can be compared with ARCalculator´s one.

I suppose they use different ways to calculate compressibility.

Greetings

[grua]

Why isnt't it possible to open AVS-Files as video files anymore? In version 0.9.4 I could open AVS, but in 1.0.0 it only recognizes D2V and AVI. As I always do some prefiltering (Trim, FadeIn, Deinterlace, ...) in my manualy written AVS-File, I need the possibility to open this file in ARCalculator to do the AVSOptimizer - but without this possibility I need to use version 0.9.4
cu, grua :confused:

[DarkDudae]

Originally posted by grua
Why isnt't it possible to open AVS-Files as video files anymore? In version 0.9.4 I could open AVS, but in 1.0.0 it only recognizes D2V and AVI.

One AVS script as AVI (Video) source of an AVS Script is not very usable since you only get a green screen as output. If you want to use additional filters, you only need to add them manually.

Greetings

[kadajawi]

Uh... sure? I recall having opened AVS scripts with AR Calculator 1.0. In the open dialog, enter * and then [return]. Then you should be able to select and use the AVS script. I needed to do that to load d2v's created with the DG version of DVD2AVI.

[Gambler's Ruin]

Hey sorry it's taking so long, I've been busy and translation is harder work than I figured. I've been trying to go more for meaning than for verbatim translation, and it's a little hard to understand the nuances of words that don't seem to have a direct dictionary translation. Anyway, enough complaining.

I do have some questions about AR Calculator and XviD though. Basically I just need a confirmation of the way it does things, as I run the process through my brain. The AVS Optimizer (was new, now default) uses XviD's first pass to determine the complexity of the video, I think. Now, from what I gather from Crusty's XviD FAQ, XviD uses temporal motion detection and spatial redudancy as compression techniques. Here's where I'm sketchy: the first pass determines what the extent to which it can apply these compression techniques to each frame is, or "compressibility", so that it can apply more bits to the less compressible frames. Now here comes AR Calculator. From what I understand, ARC uses the first-pass stats file in its own way to determine many different magnitudes and types of complexity so that it can apply certain filters in the right places. Now, what I really want to know is, what kind of complexity does AR Calculator determine? Since I also use this on TV captures, it may be helpful to apply certain cleaning filters at certain places, to minimize these filters' weaknesses. In fact, at what point in the encoding process would be the best to apply denoisers? Before we even throw AR Calculator at it, so that ARC (and XviD) know what it's working with? Or incorporate it into the script that AVS Optimizer generated with the noise still in? I've never thought about it before, but common sense says, denoise first. I suppose you can reencode the source with filters and a lossless-codec, then AR-Calc it. I know most of these topics may already have been covered in the earlier thread but it's all sinking in now.

[edit]Originally posted by DarkDudae
One AVS script as AVI (Video) source of an AVS Script is not very usable since you only get a green screen as output. If you want to use additional filters, you only need to add them manually.

It just occurred to me that ARC does take .avs input, does that mean it would take my denoising script and AR-Calc it, or are you saying it doesn't work like that, and would only get a green screen?

[endedit]

Lastly, the original purpose of AR Calculator: to compute the best resolution so that we can a bit/pixel ratio of .25, which is supposedly the best. Yet doing this at the standard size of 2 1-hour (more like 40min w/o commercials) episodes per CD (700MB) gives really low resolutions, around 416x312. Most encodes I've seen are around 512x4xx. And AR Calculator always spits out optimum ARs of ~.21 bpp, so I guess it depends on personal preference as to what looks better, but I still don't quite understand it. Also, ARC seems to smoosh the video into not-quite original ARs, does that have to do with being of a certain multiple?

Finally, what happened to all the initial interest? I was reviewing the old thread, and the XviD gurus Koepi and Syskin seemed to be really interested in what this tool could accomplish.

Sorry for all these questions, I guess all of my encoding thought processes exploded out at one time. I'll get to work on those translations.

[grua]

One AVS script as AVI (Video) source of an AVS Script is not very usable since you only get a green screen as output.
I tried the way kadajawi told: In the open dialog, enter * and then [return]. Then you should be able to select and use the AVS script. It seems to work. In the preview-window I see the right picture, no green screen!?

If you want to use additional filters, you only need to add them manually.
That's not always a good idea. I also use for example a script like this:
clip1 = avisource("test1.avi)
clip1=clip1.Trim(10,5656)+clip1.Trim(6052,0)
clip2 = avisource("test2.avi)
clip2=clip2.Trim(0,2563)+clip2.Trim(2658,475865)
clip1+clip2
Now I want to open this AVS-File with ARCalculator to do the AVSOptimizer...

cu, grua

[DarkDudae]

Originally posted by kadajawi
Uh... sure? I recall having opened AVS scripts with AR Calculator 1.0. In the open dialog, enter * and then [return]. Then you should be able to select and use the AVS script. I needed to do that to load d2v's created with the DG version of DVD2AVI.

Yeah, sure, you can open an avs file and preview it with old ARCalculator versions, but if you try a script like this:

LoadPlugin("C:\ARCALC~1\mpeg2dec3.dll")
LoadPlugin("C:\ARCALC~1\unfilter.dll")
LoadPlugin("C:\ARCALC~1\undot.dll")
Avisource("C:\LOTR_R~1\VIDEO_TS\RETORN~1.AVS",false)
UnFilter(-5,-5)
Undot()
LanczosResize(672,272)

You will get a green screen as output. So, it has not sense to use an avs as source of other avs file. That is the reason we disabled support for avs files. If you want to encode an avs file directly, you can do it in File Menu.

About d2v created with DG DVD2AVI, you can do it with ARCalculator 1.0 without any problems, you only need to configure an alternative mpeg2dec3.dll in Tools - Tools Menu - Configure Options - Use alternative mpeg2dec3.dll file. For example, DGDecode.dll. Then, you will be able to open d2v files created with DG DVD2AVI versions.

Originally posted by Gambler´s Ruin
Now, what I really want to know is, what kind of complexity does AR Calculator determine?


XviD Stats file has a lot of useful info. Frame type, kblocks, mblocks, ublocks, framesize.... looking kblocks, mblocks, ublocks, you can imagine how motion is there in that scene, and looking into their framesize, you know the size of those frames. So we can determine the motion of each scene, and its compressibility with video size the user has selected. With these data, we get the complexity level of the scene, and we assign one case or other. If you check: Give priority to motion estimation... we will determine motion level of the scenes, but not their complessibility. The advantages of this is that we use normal XviD first pass, witch is faster than 1st XviD Full Pass, but it is not addaptative.

The level of the Filtering Curve will assing higher or lower cases. For example, if you choose Level -1 of Filtering Curve, instead of a C6, you will get a C5. About denoising filters, it is recommended not to use them together with AVSOptimizer if you have a clean source like a DVD without "Film Effect" (Like all Steven Spielberg Films). For noisy sources like captures or low quality videos, it is recommended you use a general denoising filter together with AVSOptimizer, or desing a new profile specific fot that type of video. (There is a capture profile in old program thread).

For example, if you have a clean source like Matrix Revolutions DVD, and you use for example Fluxsmooth together with AVSOptimizer, the program automatically will assing lower cases, because of the effect of the general fluxsmooth filter in the whole film.


Originally posted by Gambler´s RuinIt just occurred to me that ARC does take .avs input, does that mean it would take my denoising script and AR-Calc it, or are you saying it doesn't work like that, and would only get a green screen?


Answered to kadajawi right now ;) .

Originally posted by Gambler´s Ruin
Lastly, the original purpose of AR Calculator: to compute the best resolution so that we can a bit/pixel ratio of .25, which is supposedly the best. Yet doing this at the standard size of 2 1-hour (more like 40min w/o commercials) episodes per CD (700MB) gives really low resolutions, around 416x312. Most encodes I've seen are around 512x4xx. And AR Calculator always spits out optimum ARs of ~.21 bpp, so I guess it depends on personal preference as to what looks better, but I still don't quite understand it. Also, ARC seems to smoosh the video into not-quite original ARs, does that have to do with being of a certain multiple?

Mashabak will answer better than myself that question since he is the one who programmed all Calculator part of the program.

Originally posted by Gambler´s Ruin
Finally, what happened to all the initial interest? I was reviewing the old thread, and the XviD gurus Koepi and Syskin seemed to be really interested in what this tool could accomplish.


They are the ones who should answer that.

By the way, I received the first part of your manual translation. I will reply you shortly. Thank you very much!! :D

[grua]

There is a capture profile in old program thread.
I think you meant my profile for analog captures:


C0=clip.PeachSmoother(NoiseReduction=20, Stability=30, Spatial=0).LanczosResize(XRES,YRES)
C1=clip.PeachSmoother(NoiseReduction=20, Stability=30, Spatial=0).BicubicResize(XRES,YRES,0,0.75)
C2=clip.PeachSmoother(NoiseReduction=30, Stability=30, Spatial=0).BicubicResize(XRES,YRES,0,0.5)
C3=clip.PeachSmoother(NoiseReduction=50, Stability=30, Spatial=30).BicubicResize(XRES,YRES,0,0.5)
C4=clip.PeachSmoother(NoiseReduction=60, Stability=30, Spatial=80).BicubicResize(XRES,YRES,0,0.5)
C5=clip.PeachSmoother(NoiseReduction=60, Stability=30, Spatial=130).BicubicResize(XRES,YRES,0,0.5)
C6=clip.PeachSmoother(NoiseReduction=60, Stability=30, Spatial=180).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)


You also can determine values for the Noiselevel and the Baseline parameters of PeachSmoother with PeachSmoother(readout=true, dot=true) before and use these parameters also.

cu, grua

[grua]

Yeah, sure, you can open an avs file and preview it with old ARCalculator versions, but if you try a script like this:

LoadPlugin("C:\ARCALC~1\mpeg2dec3.dll")
LoadPlugin("C:\ARCALC~1\unfilter.dll")
LoadPlugin("C:\ARCALC~1\undot.dll")
Avisource("C:\LOTR_R~1\VIDEO_TS\RETORN~1.AVS",false)
UnFilter(-5,-5)
Undot()
LanczosResize(672,272)

You will get a green screen as output. So, it has not sense to use an avs as source of other avs file. That is the reason we disabled support for avs files
I think that's just a question of the color-room the output of the AVS-script has. It seems that ArCalculator needs YUY2, but can't work with YV12. For example this script works fine if you open it in ArCalculator:
LoadPlugin("D:\Programme\ARCALC~1\AVS_Plugins\mpeg2dec3.dll")
LoadPlugin("D:\Programme\ARCALC~1\AVS_Plugins\unfilter.dll")
LoadPlugin("D:\Programme\ARCALC~1\AVS_Plugins\undot.dll")
Avisource("H:\Film-Capture\Working\Mundl\VHS\05 Der Besuch.avi",false)
UnFilter(-5,-5)
Undot()
LanczosResize(672,272)
ConvertToYUY2()
But this script will make a green picture:
LoadPlugin("D:\Programme\ARCALC~1\AVS_Plugins\mpeg2dec3.dll")
LoadPlugin("D:\Programme\ARCALC~1\AVS_Plugins\unfilter.dll")
LoadPlugin("D:\Programme\ARCALC~1\AVS_Plugins\undot.dll")
Avisource("H:\Film-Capture\Working\Mundl\VHS\05 Der Besuch.avi",false)
UnFilter(-5,-5)
Undot()
LanczosResize(672,272)
ConvertToYV12()
So you just would have to determine the color-room an change it to YUY2 if it ist YV12. Maybe this could be done automatically in ArCalculator, than you could activate the support for AVS files again?

cu, grua

[DarkDudae]

Originally posted by grua
So you just would have to determine the color-room an change it to YUY2 if it ist YV12. Maybe this could be done automatically in ArCalculator, than you could activate the support for AVS files again?

Thanks for the info! We didn´t know that. We will add support for avs files again in next version.
And yeah, I was talking about your profile in before post.

Greetings!

[Mashabak]

Originally posted by Gambler's Ruin
Lastly, the original purpose of AR Calculator: to compute the best resolution so that we can a bit/pixel ratio of .25, which is supposedly the best. Yet doing this at the standard size of 2 1-hour (more like 40min w/o commercials) episodes per CD (700MB) gives really low resolutions, around 416x312. Most encodes I've seen are around 512x4xx. And AR Calculator always spits out optimum ARs of ~.21 bpp, so I guess it depends on personal preference as to what looks better, but I still don't quite understand it. Also, ARC seems to smoosh the video into not-quite original ARs, does that have to do with being of a certain multiple?


About a year ago, when program born, we determine that 0.25 bpp was the best value to calculate optimal resolution. Because we can´t know really the best resolution for a movie without a compressibility test or another method to analyse the video, we decide to use this vale as "standar value" to show an aproximated value. Really, this isn´t the best value for all movies, and when you do a compressibility test (for example) the recommended resolution will change, but for give an orientative value without these methods we think it is a correct value.

Originally posted by grua
I think that's just a question of the color-room the output of the AVS-script has. It seems that ArCalculator needs YUY2, but can't work with YV12.


Yes, we know this. Ar Calculator shows preview screens using Bitmaps, and because that we need to read one source image that has a 8 based pixel color depth (16, 24 or 32 bits). Then, with YV12 (12 bits color depth) we can´t show any preview. Because that we charge avi files using avisynth, adding at the end of a temporal avs file the line "ConverttoRGB32" to show files correctly.
But this isn´t the reason for we remove avs support. We remove this feature because we think that use an avs file as source for another avs file was, simply, ilogic (I think). If you know any application of that, tell us and we add again avs source support.
In addition, as Darkdudae says, if you use an avs file as source for another avs file you will get as exit a green screen (not AVI files as source, AVS files as source).
Peraphs, to use calculator part of the program, use an avs source can be util, but for use the rest of the program (avs file creation) this was unuseless. If you want to encode an avs directly, you can do this using the option in menu "File" -> "Avs direct encoding" (or pressing F2).

Regards.

PD: Sorry for my poor and "child" english :o
PD2: Thanks for your help and work, Gambler´s Ruin.

[grua]

We remove this feature because we think that use an avs file as source for another avs file was, simply, ilogic (I think). If you know any application of that, tell us and we add again avs source support. There are two reasons why I want to use an AVS file as source for another AVS file:


1) Trimming:
I do analog captures from TV which contain advertisement-scenes (what's the right english word for this?) which I want to remove. So I load the AVI in VirtualDub and determine the frames which I have to trim. I'll create an AVS script which contains AviSource(...) and Trim(...), for example:avisource("test1.avi)
Trim(10,5656)+Trim(6052,100254)Now I want to load this AVS-Script in ArCalculator to do the bitrate-calculation and to run the AVSOptimizer.


2) Joining Clips:
clip1 = avisource("test1.avi)
clip1=clip1.Trim(10,5656)+clip1.Trim(6052,0)
clip2 = avisource("test2.avi)
clip2=clip2.Trim(0,2563)+clip2.Trim(2658,475865)
clip1+clip2Now I want to load this AVS-Script in ArCalculator to do the bitrate-calculation and to run the AVSOptimizer.


I think this wuold be done most simply by AVS-support in ARCalculator.

cu, grua

PD: Sorry for my poor english too ;)

[Mashabak]

I understand that you can use this avs file to do all calculations about bitrate, resolution, etc.
But I don´t understand how you want to use this avs file as source in another avs file to do AVS Optimizer. As I said, if you do this:

LoadPlugin("D:\....\mpeg2dec3.dll")
Avisource("D:\....\your trimmed avs file.avs")
Filter
Filter
Filter

you only get a green screen (in my test I get this) and then, you can´t work correctly with this avs file. The compressibility test (for example) will show you 10000% of compresibility, and AVs Optimizer, based on XviD first pass values, will do a non-trimmed avs file (because a green screen in all the movie have any complexity cases).
If you want to use your avs script in avs optimizer, the only way (at this moment) to do this is replacing all lines with yours in "Manual Edition" in AVS creation section, changing original video source whit your trims.
Anyway, in next version we will add avs support, but only in calculator section (because all things I was explained).

Regards.

[grua]

No, that's not the experience I made. Because I opend the following AVS-script in ArCalculator 1.0.0 as Video-File (not for direct encoding) and it worked fine with bitrate calculation, compressibility check and AVS-Optimizer:clip1=AviSource("H:\Film-Capture\Working\Mundl\VHS\Capture1.avi",true,"YUY2")
clip1=clip1.Trim(0,31384)+clip1.Trim(32882,0)
clip1=clip1.TomsMoComp(-1,5,0)
cl = 8
co = 2
cr = 12
cu = 6
clip1=clip1.Crop(cl,co,-cr,-cu)

clip2=AviSource("H:\Film-Capture\Working\Mundl\VHS\Capture2.avi",true,"YUY2")
clip2=clip2.Trim(0,67420)
clip2=clip2.TomsMoComp(-1,5,0)
cl = 8
co = 0
cr = 12
cu = 8
clip2=clip2.Crop(cl,co,-cr,-cu)

clip1+clip2

UnDot()

saturation_u=1.1
saturation_v=1.0
cu=-(1-saturation_u)*256
cv=-(1-saturation_v)*256
ColorYUV(off_y=0,gain_y=4,cont_u=cu,cont_v=cv)
Limiter()I think it is really just a question of YUY2 or YV12. The two AVI-files themselfs were captured in YUY2 and as you can see I opened the AVI-files as YUY2 with AviSource() and I think that's the key, dont't you?

cu, grua

[kadajawi]

And this is the AVS I used, no problem at all to crop etc. I'm mainly using the AVS-Optimizer, and then taking the resulting AVS to VirtualDubMod.

loadplugin("C:\Programme\AviSynth 2.5\plugins\DGDecode.dll")
mpeg2source("F:\DVR\Requiem for a Dream\Requiem for a Dream.d2v")

[DarkDudae]

@grua

In your scripts, you still are using avi files as video sources. We know that works perfectly, but try an avs file instead an avi file. You will get a beatiful green screen. I have been playing around with colour conversions without success. YUY2, YUV12, RGB.... all of them with the same result. Our friendly green screen.

Maybe opening avs files can be usefull for bitrate calcs... but not for using them as sources of other avs files.

@kadajawi
You should try to program AVSOptimizer and 2 XviD normal passes in ARCalculator Job Queue instead of VirtualDubMod. In this way, you can make automatically 3 passes.

Greetings!

[grua]

In your scripts, you still are using avi files as video sourcesYes, that's the only thing I want to do: I want to create an AVS-script manually which opens an AVI-file. And open this AVS-script as video-source in ArCalculator. but try an avs file instead an avi file. You will get a beatiful green screen. This really makes no sense at all (for me). but not for using them as sources of other avs filesbut for using them as sources of AVI files. Opening an AVI in an AVS and opening this AVS in ArCalculator makes sense! And it works already now in ArCalculator 1.0.0. We just have to use the trick we wrote above: In the open dialog, enter * and then [return]. Then you should be able to select and use the AVS script.It's OK for me to do it this way, but it would be more simple if we could open the AVS without that "trick". But as I said: it's OK if we have to use that trick as long as it works!

cu, grua

[Mashabak]

Really I don´t know how you can load this avs script in AR Calculator and get a good preview. I was doing tests using different avi files as source in an avs file (RGB 16, 24 and 32, YUV2 and YV12) and when I load this avs file as video source on AR Calculator I get always a green screen as preview.

Anyways, if you want to charge AVS files in the program, must locate "English.ini" file at installation directory and find the line "general.abrir_video.Filter=Video Files |*.d2v;*.avi|DVD2AVI files(*.d2v)|*.d2v|AVI Video Files(*.avi)|*.avi"
Then replace this line with: "general.abrir_video.Filter=Video Files |*.d2v;*.avi;*.avs|DVD2AVI files(*.d2v)|*.d2v|AVI Video Files(*.avi)|*.avi|Avisynth Files(*.avs)|*.avs" (without "").
Then, you can load avs files on Ar Calculator.

Regards.

[grua]

dont't know why it works on my PC but not on yours... :confused:
But thanks for the tip with the ini-file!
grua

[grua]

Maybe a bug in AR Calculator 1.0.0:

Video:
1h 27min 12s
RAR 1,33
25 fps

Audio/Container:
AVI
No Audio

Extra Files:
Nothing

Size:
Automatic
Mode 1
1 CD
700MB (80min)

Now in the Recommende Settings I see Output Video Size 717848KB, Overhead 2044KB and Final Size only 716800. That means the video size is larger than the final size???

cu, grua

[DarkDudae]

@grua

That is pretty normal grua. You can use xvid bitrate calculator, and you will see it also offers higher values than calculated. XviD needs that little-extra bytes to get desired output size.

Greetings

[grua]

calculations by different calculators:

1 h 27 min 12 s
25 fps (PAL)
Target size 716800 KB (CD 700 MB)
no audio

AR Calculator:
video size: 717848 KB
avr. bitrate: 1119 KB/s

XviD 1.0.1 built-in calc.:
calculator says 714757 kbytes, written into encoder is 717822

--> you are right, I didn't know this - sorry!

greetings, grua