Quote:
Originally Posted by frustum
Shouldn't you be doing
A = video.autolevels()
...
super = A.MSuper(pel=2, hpad=12, vpad=12, rfilter=1, levels=1, isse=true)
|
Yes, definetly. MVTools2 does not store the vectors in the super clip, so that's not an issue. But doing the autolevels first is a) faster because of less image area to process (the super clip is *much* bigger), and b) avoids the dark/bright flickering issue. This issue was directly caused by the unlucky autolevels usage: in case of (exact) framerate doubling, the even frames are just the untouched original input frames, hence they aren't affected by the autolevels.
* * * *
BTW, why are all those "realtime" framerate doubling scripts using search=3/searchparam=2? This IMHO is plain silly! search=3 is very slow, and then the speed problem is fixed by using a very small search range and few superclip-'levels'.
Jeremy, that script has a search range of only 1 or 2 pixel! (levels=1, searchparam=1/2). "Motion search" is something else.
Really, there is no point in using the best-but-slowest search method, and then cripple it so badly that it becomes worse than other, more sane search methods would be to start with.
