Log in

View Full Version : New to AviSynth


Zerox20
20th April 2003, 20:50
I have been reading the forums like crazy and Been trying filters etc, I just have a question on just doing scripting in general, from what I read on the homepage etc. I noticed sometimes you don't even give scripts paremters,

asharp(2,2,1,true)
Undot()
unfilter(5,5)
TemporalCleaner(2)
MSharpen()
deen()
limiter()


Thats my current script for instance, does not giving the script paremeters just assume defaults? or does it make it adaptive? Or Anybody know some good numbers to experiement with (I know they probably change depending on the video) I am encoding anime and trying to learn how to use this I have heard its a very powerful tool.

Thanks in advance!
-Zero

Niņo
20th April 2003, 21:01
() means default, read the readme.txt of the filter and you`ll see what the default values are.
Sure you can customize your filter, depending on your video source.

Zerox20
20th April 2003, 21:32
I always check readme.txt and it confuses the **** out of me hehe,
example from deen:
mode :
with "c3d", it's the weight matrix.
- 0 <121> matrix (default)
- 1 <111> matrix (softer)
with other methods, it's the spatial raduis.
default : 0

Its like whoaaaa? I usually understand once i see results, but as you know doing massive encoders take a long time. I am right now trying different settings with it. and Hoping to understand all of these filters better.

Acaila
20th April 2003, 21:47
Translation to english:

- 1 <111> matrix (softer)
For every pixel, it creates the new pixel value by averaging the vertical and horizontal neighbouring pixels (as well as previous/next frame).

- 0 <121> matrix (default)
Same as above, but uses a larger weight for the current pixel's old value. i.e. it causes less blending with the neighbours and retains more of the original.

Zerox20
20th April 2003, 21:51
Now that cleared it up a lot actually, why can't they just PUT THAT IN THE README.TXT!!! I am trying default values right now with Deen and Msharpen checking results n stuff.

Thx for the help!

Acaila
20th April 2003, 22:17
Well, that function of Deen was inspired by Convolution3D (a great filter if you're encoding anime), so I suggest you search for that if you want to know more about it. That's also why for Deen it isn't explained very well. And Marc FD (creator of Deen) isn't exactly known for his ability to write great readmes, although he tries. On the other hand he does write great filters :).

Zerox20
20th April 2003, 23:05
Wasn't there a post about that somwhere? I'll keep looking if you get time can you post the link and some good settings to mess withe tc with it (I'll read the readme.txt too)..

Also I am currently trying to an anime and I am noticing I am getting lots of blockyness in my encode:

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\UnFilter\UnFilter_Avisynth_2.5_Alpha\UnFilter.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\UnDot\UnDot.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\temporalcleaner\TemporalCleaner.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\asharp.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\SmoothHiQ.dll")
asharp(1.5,2,1,true)
Undot()
unfilter(10,10)
TemporalCleaner(2,10)
converttoyuy2()
SmoothHiQ(3,254,12,12,6)
limiter()

That is my current script, Any other settings to apply/try or mess with? Also I went ahead and I am trying the Convolotion3D Script, Convolution3D(0, 6, 12, 6, 8, 2.8, 0)
are the settings I am trying, I am encoding this into ffvfw Mpeg 4 Version 3.

kaitsuburi
21st April 2003, 09:16
Hi!

Your script has a little too much filtering IMHO. Since you are encoding anime, it's generally good to have some sort of temporal cleaning, some sort of 2D cleaning and some sort of edge-enhancing sharpening. I would suggest getting rid of SmoothHiQ (slow, plus you need to convert to yuv2) and trying something like deen("a2d",2,10,12) (to act as a 2d noise smoother). Try without unfilter too -- you are already using another sharpener. But of course it depends on your source - experiment.

In my experience, temporal smoothing (temporalcleaner etc) followed by 2d noise cleaning (e.g. deen "a2d") before resize and sharpening (asharp, awarpsharp, warpsharp, etc) after resize has produced very eye-pleasing results.

Just some thoughts. Trust your eyes ;)

-kaitsuburi