NUspeed v1.3


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Alexey Kulikov
A tool for non-uniform map-dependent speed change. Update v 1.3 - Added support for Nuke up to 11.0
Requirements:
11.0, 10.5, 10.0, 9.0, 8.0, 7.0 or later
Linux, Windows
09 Sep 2019
430

Update v 1.3 - Added support for Nuke up to 11.0

Update v 1.2 - fixed the bug on the border of region of work, fixed wrong order of inputs on disabled state

NUspeed - a tool for non-uniform speed change in different parts of the picture depending on the map provided. A brother of the NUoffset gizmo.

You need 2 inputs - source sequence and the one with the map(a single channel is enough).

It is done through TimeWarp and OFlow/Kronos, meaning that you go away from integer values on frames and with OFlow you actually get very smooth results.

You can choose the number of levels of the map which are used for the final picture. As the gizmo can't possibly use unlimited number of frames to generate the result, you'll need to specify it - this is sort of a discretisation parameter for the map. For me, 300 was limit with the OFlow method, this means the node generates 300 constructions with Merge and Oflow nodes which is sure a lot, so be careful.

There is also an option of mixing of map levels which is actually a simple alpha blur, but with low number of levels it may help to smooth the transitions between frames.

I'm uploading it as a group, just because if you use it as gizmo, it doesn't save the inner structure and you'll need to hit the Calculate button when you restart the script.

Tips about the usage the can be found in the help section of the node.

explosion comp 001flower comp 001

Please mention the author if the product is used in your project. Copyright (c) 2014 Kulikov A.G. [email protected] All rights reserved.
Please login in order to download these files.

Comments   

 
0 # Donat Van Bellinghen 2017-10-13 14:54
Hi,

This gizmo does not seem to work for me. I checked the internals and the input is directly connected to the output, no time nodes...

Regards
 
 
0 # darren coombes 2022-10-19 07:06
Does this work in Nuke 12.2 ?
 
 
0 # darren coombes 2022-10-19 07:37
would also be great to be able to change motion estimation for Kronos from local to regularized
 

You have no rights to post comments

We have 2587 guests and 59 members online