What exactly do "combos" do?

[helix]

I've seen a few scripts around here with two filters put in the same line. I've look in the AVIsynth manual and have been unable to anything relating to this. Some examples are...


TDeint().Decimate(mode=2,quality=2)

or...

Msmooth(threshold=5, strength=3).Convolution3d("animelq")


whats the difference with just doing...


TDeint()
Decimate(mode=2,quality=2)

or...

Msmooth(threshold=5, strength=3)
Convolution3d("animelq")


Does it change the effect of the filters in any way, or make the script any faster?

[scharfis_brain]

it is just a matter how you like it.


function1().function2()

equals to

function1()
function2()

equals to

function2(function1())

[stickboy]

Only if function1 returns a clip and function2 takes a clip as its first argument, but close enough. :)

Yes, it's just a stylistic preference.

[Mug Funky]

the dot syntax becomes useful when you work with variables.

for example, a common way of treating interlaced material with filters made for progressive frames is:

avisource("blah.avi")

even=last.separatefields().selecteven().filter().nextfilter()
odd=last.separatefields().selectodd().filter().nextfilter()

interleave(even,odd).weave()

this is easier to handle than the equivalent:

avisource("blah.avi")
clip=last

clip
separatefields()
selecteven()
filter()
nextfilter()
even=last

clip
separatefields()
selectodd()
filter()
nextfilter()
odd=last

interleave(even,odd)
weave()

[helix]

Oh alright, I see now. I was under the immpression that the "dot" actually changed how the filters were used in a script. Thanks for clearing that up.