Replace all frames with MoComp-practical usage

[Terka]

a while ago a "Replace all frames with MoComp" appeared
http://forum.doom9.org/showthread.php?t=140869&highlight=Replace+frames+MoComp
as the idea itself looks crazy, what about use this in praxis.
when comparing original to mo-comp clip, we can become places,
where the mo-comp is failing. this could be useful for further mo-comp processing of the clip.
is this an correct idea?

[Didée]

Nothing new in it. MVTools already does compare the compensations to the original frames. The validity of a compensation is expressed by SAD between original block and compensated block, and the "thSAD" parameter in various functions deals for controlling how much difference is, or is not, acceptable.

For some functions (i.e. those that use the compensations explicitely, like MVDegrain) you can manually dig up comparison schemes other than SAD ... however, most likely you'll end up with only tiny improvements, coming at an enourmous price.

Other functions like MVFlowFPS don't use the compensations directly. The SAD of a compensated block is used to rate the attached vector, and only after that, another compensation (by fraction-of-vector's-length) is made according to vector's validity.
With such functions, you can do *nothing at all* in that direction. (At least not at the script level. Feel free to modify the core of MVTools.)