Input = Output?

[trance]

I've been at this for a days now. My output looks exactly like my input (source) when i preview .avs script. Filters DO NOT seem to be affect the output. I've tried several filters with different settings and even parameters at extreme just to see if it affects the output BUT it does not. I also noticed that when I encode, the resulting video are ALL the same with different filters. I have following installed:

Keopi's XviD-24062003-1 with settings
GordianKnot.CodecPack.1.3
GordianKnot.RipPack.0.28.5.1 (which has VDM v1.5.1.1a & AVS 2.5)

My XviD settings:
FIRST PASS
6 Ultra High
MPEG
XVID
4 Wide Search
300/1 (min/max frame interval)
Chroma Motion
Quarterpel

2/150/100/0 B frame
DX50 B-VOP

Debug: Auto Detect & Chroma Optimiser

2ND PASS is the same setting with default on the rest of the tabs.


Here is my script:

# PLUGINS
SetWorkingDir("D:\Program Files\DVD\Gordian Knot")
LoadPlugin("D:\Program Files\DVD\Gordian Knot\mpeg2dec3.dll")
LoadPlugin("D:\Program Files\DVD\Gordian Knot\Convolution3d.dll")
# SOURCE
avisource("E:\DVD\BAND_BROTHERS_Ep1.avi")
#
Convolution3d("moviehq")

[Leuf]

Are you just saying that in virtualdub the input and output windows look the same? When you use avisynth the output of avisynth is what virtualdub sees as its input. There's only a difference between the two windows if you use filtering within virtualdub itself. Perhaps I misunderstand you though. Convolution3d with the moviehq isn't going to make a huge visual difference, so it might appear to be the same, depending on the source, compare the output filesizes. If that doesn't answer your problem you should ask in the avisynth usage forum.

[trance]

After a few hours of more testing, I figured it out. There were differences but very minor or not very noticable with filters. I had to use a solarize filter/add grain to check.