Isn"t it easier to test how affect all these avisynth filters the source if we open our script with VirtuladubAVS?
Then open with notepad the script, modify it (change the values of filters or add more filters, etc..) save it and hit F5 in Vdubavs.Now we can see in the preview window how these filters work...

__________________
The aRt oF FaLLing ApaRt

hi VILLA21,

I do this all the time w/ notepad..

This is basically my process, and it works so well for me.

When I'm working on capture projects (which is quite often) I first open
my Interlace.avs and Telecine.avs scripts (each in notepad)
which are on my DESKTOP in an easy place to quickly click, drag and drop
into vdub.

Then, after my captures (which may be just quick caps of something that
just caught my eye on Satellite) AND, thank's to my unique filenaming
convension in my AVS scripts, I just edit AVI's sequence number at the top
line of my script (note the bold) as follow..

Then, I just drag that Interlace.avs or Telecine.avs script
into vdub and begin my analisys of the source, or I frameserve it into TMPG.
I am forever in vdub w/ some form of source file tweaking idea or two.
But, I'm usually dicecting "filtered" outputs (from AVIsynth or vdub)

So, why do I use vdub in this way ?? Why not just create my own video window
w/ my AVS scripts (like in Delphi) ?? ..well, actually I have, but it's not
effeciant, not flexible, a little slow, and color is not nailed, etc., etc.
I trust vdub more than my own home-brew AVS GUI.
And also because I use vdub's filters (lots of them) and/or there
are things I can do in vdub that I can't do in AVIsynth or whatever ie, like
working w/ Audio for one, etc. I just trust vdub's output window more than
any other form of output window that I could create (at this time)
So, vdub it is.

This process is very quick. I do this in my sleep every day.
If anyone is interested for further details, I'll try and explain further,
my process.

Well, it's 7:26pm and raining lightly here in NY.
To everyone, TGIF..
-vhelp