Morph_Dissolve v1.1


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Erwan Leroy
Website: www.erwanleroy.com
Allows to morph between two moving plates automatically, or can be used to improve manual Morphs. Inspired by Avid Fluid Morph or Adobe's Morph Cut.
Requirements:
13.1, 13.0, 12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11 or later
Linux, Mac, Windows
26 Oct 2022
4914

Update 1.1: Fix a concatenation bug happening in Nuke 13+

 

Allows to morph between two moving plates automatically, or can be used to improve manual Morphs.

 

Inspired by Avid Fluid Morph or Adobe's Morph Cut.

 

Will work best on visually similar plates or for invisible jump cuts. The more different the two plate to morph, the more artefacts will be present.

 

Can be used to improve manual Morphs (splineWarp or Gridwarp) by feeding the distorted A in one input and the distorted B in the other input. The Morph_Dissolve will look for the small details you may have missed or ignored with your manual morph.

 

video loop

See tutorial/example on how to use Morph dissolve to make a seamless infinite loop here: http://erwanleroy.com/morph_dissolve-gizmo-for-nuke/

Please login in order to download these files.

Comments   

 
0 # Lucas Pfaff 2017-12-12 08:16
Hi Erwan,

thank you very much for your tool! :) I remember the discussion on the forums, great to see it here. Gave it a quick go, seems to work really nice :)
 
 
0 # Mario Cazares 2018-11-25 10:02
This is a blessing seriously this actually saved me
 
 
0 # Matheus Jesus 2019-09-04 21:11
This is a blessing seriously this actually saved me!!!!!!!!
 
 
0 # Eion-Ray Patterson 2019-10-22 13:37
Awesome!
 
 
0 # Leath Mattner 2020-04-01 11:25
Worked so well, thanks Erwan!
 
 
0 # Alexey Ushakov 2022-02-23 08:00
iDistort does not work in nuke 13.1 after retime the node does not see the channels. Repaired by remove(keep) node before iDistort
 
 
0 # Frank Rueter 2022-03-16 20:48
Same, the IDistort option doesn't for me. My comp starts at frame 3000 and there seem to be some start values hard coded?!
 
 
0 # Erwan Leroy 2022-10-26 16:53
I've never received a notification for these comments so I'm only seeing all this now.
I'll look into what's going on, but no there shouldn't be a hardcoded start frame, there's only a hardcoded "reference point", but the process should zip frames, generate the vectors from that, then unzip, so that hardcoded frame is only there so that it can undo the zipping process.
 
 
0 # Erwan Leroy 2022-10-26 17:22
There's a weird bug in Nuke 13 where it would seem like putting an iDistort right after a retime/timeOffs et breaks iDistort. As Alexey mentioned, putting almost any node in between fixes it, so I put a remove to pop the channels I don't need anyways.
 
 
+2 # Gustavo calderon Delgado 2022-10-26 06:54
could you elaborate please?
 
 
+1 # Victor Chan 2023-09-22 10:48
iDistort method does not work in nuke 14..04, even added the remove node in between footage doesn't work as well so far that is without the presence of retime aswell. I guess you can only stick with Kronos then :3
 

You have no rights to post comments

We have 3720 guests and 70 members online