View Single Post
Old 26th December 2005, 18:16   #219  |  Link
krieger2005
Registered User
 
krieger2005's Avatar
 
Join Date: Oct 2003
Location: Germany
Posts: 377
Quote:
Originally Posted by mg262
The truemotion algorithm is becoming confused because the foreground object is very fast moving around frame 84 of the input (~frame 261 of your script with return 1). Unfortunately, this means that the compensation isn't working properly.
But the predicted Vectors look ok? But... humen eyes



Quote:
Originally Posted by mg262
I am sorry not to be more helpful.
Is it possible to add/get an option or a mask, which show how good parts of the frames could be compensated by the filter?
Quote:
Originally Posted by mg262
EDIT: Try adding iterate = 4 to FindMotion... results look much better.
Thanks, i will try this.

Quote:
Originally Posted by mg262
For the purposes you are using this for, namely preprocessing for despot, that's not a catastrophe... the idea behind fast motion compensation with temporal filters is that while it is not always perfect, it should nearly always be better than using the filter without MC.
Despotting in general (not only with despot), for my optinion, is dangerous. So i would say, that when one don't know, that a filter can't compensate the frame good enough it is a catastrophe... But this is surely not the problem of your plugin. It make what it can...

Quote:
Originally Posted by mg262
but I couldn't reproduce the issue where omitting source = previous made a difference.
Sorry.. this was a mistake by myself.

Thanks for your help
krieger2005 is offline   Reply With Quote