Posts for Vit

Posted: 9/11/2011 12:15 AM
Quote
Vit
Joined: 9/7/2011
Posts: 2
QTGMC does many things, but blending frames not yet (next version will actually, but that's some way off). You're feeding it duplicated frames, from an interlacing point of view. That will, by chance, create frames that are very slightly nudged towards the mid-way blend. But only very slightly. So unfortunately your result is barely any different than 
#interleave(selectevery(4,0),selectevery(4,3))
with the uneven movement that creates.
Posted: 9/8/2011 9:22 PM
Quote
Vit
Joined: 9/7/2011
Posts: 2
nanogyth: A note from the avisynth world. I think you may have misunderstood the masks you are using. MMask with kind=1 gives you a "SAD mask" of the analyzed motion (Sum of Absolute Differences). This is not an indication of what is moving. This mask indicates which parts of the image had poor motion matches with the (previous or next) frame. You can get a poor motion match on a moving or a stationary object. Poor motion matches are caused by objects appearing or disappearing or by objects changing their shape, look or color radically from one frame to the next. Can also occur when there are small objects moving in front of larger ones creating two speeds of motion in the same area (the ropes in the Roadrunner clip). You can get masks showing the motion by using different settings for "kind". But typically the SAD mask is most important because you can't trust motion information if the match is poor. Another important detail: The forward vectors hold the motion from the previous frame into the current one, so the forward SAD mask shows the parts of the current frame that could not be matched with the previous frame. Similarly, the backward SAD mask shows the parts of the current frame that could not be matched with the next frame. This is extremely counter-intuitive, but definitely how it works (check the docs on the MAnalyse "isb" setting). The approach you are taking is correct, merging forward and backward masks. However, I think you will be able to refine it more effectively if you understand what MVTools is telling you (and what it isn't). I have made some refinements to my variant, but I still need to work on the problem noted by partyboy1a when objects are invisible on even frames rather than odd.