I just used it on a job as well and the client loves it! It was pretty quick and easy to change as well when the edit “unlocked”. So I second the thank-you to the devs!
I’m using the morph node extensively on a current project. Not to cover jump cuts but to smooth transitions.
One thing I’ve noticed in one shot, that over the 14 frame range the resulting images (comped back on full shot via Action & mask) is randomly moving up and down by 1 pixel creating noticeable jumps. Over the 14 frames there is like 3-4 frames were a 1 pixel shift occurs.
Is that a known limitation? Would be less noticeable if it were full-frame (can’t do that in this case). Temporal instability?
Besides this problem, it’s working really well.
The plot thickens. Seeing the same one pixel steps up and down in timewarp set to ML.
Ugh, that’s not good news.
Seems like there’s a rounding error in the code where it flips one way or the other for no apparent reason.
Must be time for a ticket… (unless you already created one?)
Just saw it. Checking if it’s in 16 and 32 caches
@allklier @cnoellert Please report it to support.
Based on @cnoellert buried lead, I just switched my morph node to 32fp and it’s not happening there. It seems unique to processing in 16fp. Also Linux in GPU and ML Engine cache mode, though I haven’t tested it in other modes.
And yes, will report it once I get through this set of shots.