Steve,
Thanks for your response. I understand the occlusion issue. As a sometime compressionist (I believe I spoke to you at NAB Post NYC about WMV output on Media100 using Flip4Mac at the very end of the show – they sent Boris the 1.0.6 update) I was thinking in terms of IBP type GOPs in which an algorithm can be told where to look for an I frame. In this case B/P type frames would be the newly created frames. This could helped by a 2 pass encode, wouldn’t it?
I’m having some confusion about some of the settings like for example Bi Directional Mix and Nearest Mix as sort of look both ahead and behind vs look at the nearest (either/or) I frame from a current B/P type frame, in predicting motion. The preconceived notions I had might be leading to my misinterpretation of these functions in Optical Flow.
I also thought that maybe Low Velocity Correction (“If the Optical Flow moves an area that should not move”) and Velocity Limit (“percentage of the size and resolution of the Source Layer”) as sort of “sensitivity” adjustments as to both where it looks ahead/behind in the in the nearest frame (sort of like the region used in Image stabilization). My thinking was that a faster moving object might need to look at a wider region in the frame to find where it came from/should go to.
I’m also confused about Min. Edge Contrast which “sets the threshold for the minimum amount of detail in a region.” Just not sure how edge detail or contrast on those edges are affected by Optical Flow given one is avoiding the softening of Frame Blending.
I thought displaying the Vectors would help in my tweaking but I find the vectors aren’t visible in Draft Only. They are when set to Render, which I can then turn off before the render. The problem is when doing Option-p (FCP – Play all Frames) and try to park on a frame at issue, it jumps to another frame.
I know other editors are grappling with these concepts. Any help on the above would be greatly appreciated.