uvSticker v1.0


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Marco Romeo
This gizmo unwraps an image along a UV space. In practical terms it allows you to draw something on top of a frame and convert it to a texture that can be remapped using the STMap along a whole animation. The gizmo contains a BlinkScript node that implements the computation kernel on the GPU.
Requirements:
8.0 or later
Linux, Mac, Windows
26 May 2014
902

The UVSticker is a Nuke gizmo which integrates a Blink Script that unwraps an image following the UV texture coordinates of another image.
In this way it is possible to draw an image on top of one frame of a rendered animation and remap it through the whole sequence.
This gizmo may be used to add 2D animation on top of rendered 3D animations, it could also be used to create animated maps and masks attached to the surface of a rendered object.

Nuke UVSticker from Marco Romeo on Vimeo.

Please login in order to download these files.

Comments   

 
+2 # Frank Rueter 2014-05-26 08:22
fantastic, thanks for sharing Marco!!
 
 
# Marco Romeo 2014-05-28 18:05
Thanks Frank, please share any result you'll get with the gizmo.
I'm curious to see how people will use it :-)
 
 
+1 # Michael Garrett 2014-05-29 14:42
Thank you very much for uploading this Marco, I would be interested to try and use it as part of getting a sticky camera projection working!
 
 
# Marco Romeo 2014-05-29 15:14
Michael, I believe that the best way to do it would be:
- overlay an image at a certain frame
- compute the result of my gizmo once and store output as image
- adjust the image on an external program to fix artifacts
- plug the fixed image inside an STMap
That should work.
 
 
+3 # Norbert Ruf 2015-09-09 17:53
The gizmo is not working in my environment (Nuke 8 and 9, Ubuntu, Nvidia Quadro 4000)
this is the error message: ERROR: Group1.BlinkScr ipt1: Error running kernel on GPU. The kernel successfully compiled. However, OpenCL returned error (-36) while executing on the device.
Any ideas why this is happening or a workaround?
Thanks
 

You have no rights to post comments

We have 2450 guests and 141 members online