> Is there a problem with this?
It's like mixing apples and oranges in my opinion. Occlusion (i.e. "cover-uncover") mask is (theoretically
) allows FlowFps to use only one src frame when processing areas covered in the other frame.
I believe that occ. mask in MMask is just wrong, SVP (SVSmoothFps) calculates totally different mask (look at frame edges while panning, they are always blurred with MMask's occ. mask, and are perfectly clear with SVP's 21/23th shaders),
BUT mixing it with SAD mask ... I dunno ![]()
Isn't your "blown-away quality" achieved by masking most of the frame area? ![]()