Log in

View Full Version : what is the fastest good looking mvtools framerate doubling script ?


thomaz909
9th October 2012, 14:09
atm i use this:


SetMemoryMax(64)
SetMTMode(5,4)
ffdShow_source()
SetMTMode(2)
super=MSuper(pel=1, hpad=0, vpad=0)
backward_1=MAnalyse(super, chroma=false, isb=true, blksize=16, blksizev=16, searchparam=3, plevel=0, search=3, badrange=(-24))
forward_1=MAnalyse(super, chroma=false, isb=false, blksize=16, blksizev=16, searchparam=3, plevel=0, search=3, badrange=(-24))
backward_2 = MRecalculate(super, chroma=false, backward_1, blksize=8, blksizev=8, searchparam=0, search=3)
forward_2 = MRecalculate(super, chroma=false, forward_1, blksize=8, blksizev=8, searchparam=0, search=3)
MBlockFps(super, backward_2, forward_2, num=FramerateNumerator(last)*2, den=FramerateDenominator(last)*1, mode=0)
SetMTMode(1)
GetMTMode(false) > 0 ? distributor() : last


but this script eats 3-4x more cpu than without mvtools.

is there anything i can do to speed it up ?

p.s.: my scripting experience with avisynth is nearly 0 :)

Didée
9th October 2012, 15:23
SetMemoryMax(666/6)
SetMTMode(5,4)
ffdShow_source()
SetMTMode(2)
super=MSuper(pel=1)
bvec=MAnalyse(super, isb=true, blksize=16)
fvec=MAnalyse(super, isb=false, blksize=16)
MBlockFps(super, bvec, fvec, num=0, mode=3)
distributor()
return(last)

That's much faster. But, of course: more effort --> better results, less effort --> worse results.

There's no hard rule to tell what is "good looking" and what not, or how much CPU effort can be spent, or how little the CPU effort has to be. All things depend on many other things.

StainlessS
9th October 2012, 23:30
The fastest way undoubtably does little.
the bestest way takes a little longer.

aegisofrime
10th October 2012, 20:12
The fastest way undoubtably does little.
the bestest way takes a little longer.

Do you have a recommendation for the bestest way? I'm currently using Interframe, but still getting some artifacts especially with fast moving hands.

Asmodian
10th October 2012, 20:27
You didn't like the results from Didée's suggestion? Like Didée already said:
But, of course: more effort --> better results, less effort --> worse results.

If you want to try increasing the speed you can start tuning options, there is a lot of room for tweaking.

MVTools (http://avisynth.org.ru/mvtools/mvtools2.html)

Maybe try messing with search, searchparam and blksize? Not that I really have any idea what quality and speed you need but these are what I would start messing with.

hint: maybe search = 4 or 5 with searchparam = 8 to 16? I must admit that any MVTools script I use is tuned for quality with almost no regard for speed.

bcn_246
11th October 2012, 21:20
Have a look at the SmoothVideo Project (http://www.svp-team.com/wiki/Main_Page).