exrdisplay

Hey everyone….

I’m starting to write a Nuke version of ILM’s exrdisplay plugin. There’s an AE version out there, as well as even a Shake version, but no Nuke version believe it or not. So I wanted to check on the boards and see if anyone out there has already done this.

I would love to at least check out another script to compare my math against to see if what I’m trying to mimic in Nuke is in the same vein as ILM’s command line program.

deJello v0.4 – Rolling shutter removal gizmo

Hello internet. I present to you the results produced by this little gizmo I started about 1.5 years ago.
It’s an attempt at reducing heavy distortions produced by rolling shutter. It uses Nuke’s Camera motion vectors to correct the image. The only requirement is a camera node that has been previously tracked.

I’ll post more information when I’ll find the necessary time. If there are people out there that find this interesting, please drop a comment.

youtube link: http://www.youtube.com/watch?v=1lOxdQKrnzM

Camera Tracker – Object slipping slightly

Hello Friends,
I am having this weird basic problem which I am unable to solve. I track the attached footage in NukeX and any object I place in the scene slips slightly and never sticks. This happens with any footage which I have. This inspite me giving the correct focal length and the film back values.

Steps
1. Shot using Canon 550D using a 25mm lens (1920 x 1080 – 24 fps)
2. Using After Effects I render out the sequence in JPEG (conforming to 24 fps)
3. In Nuke, I track it by inputting the focal length (25mm) and the film back values (22.3 mm x 14.9 mm).
4. Do Auto track
5. Solve Error is 0.71, which is pretty good
6. I select a Point in the point cloud, right click and add a Cube.
7. Playback the sequence, and the Cube object is ever slipping 🙁

I repeated for different footages but everywhere this slip is happening.

Attached is the sequence and the Nuke script.

Please help!

Tx,
Haf

Attached Files
File Type: zip room.zip (30.64 MB)
File Type: nk cam.nk (2.42 MB)
File Type: zip out.zip (4.93 MB)

Frame Range Globals

Hi,

I am new to Nuke and I am asking myself what is the best way to move a whole sequence (positioned on the timeline depending on the frame numeration) to start at frame 1 for exemple (or could be every other frame). The other question is, what is the best method to render a sequence beginning with 0001 in its numeration, no matter what global timeline I am using – so for exemple the file sequence in the read node starts with 2352 and I do not want to change the global timeline position (like mentioned in my first question), but I want to write the new sequence beginning with 0001.
And what if I am offsetting a sequence to start at 1 with the help of the retime node and I want to work on the flow before the offset and after it – how can I switch my timelines to display the accordant timeline ?
Sorry for sounding so newbie, but I used Fusion before, where you can easily change global timeline controls in the read node.

Thanks for your help !!

Nuke roto shape to mocha or AE

Hi,

Is there any way to export nuke roto shape to mocha or After effects?

thanks in advance.

Front Source Gizmo

A while back I got a great response about how to front source in Nuke.

For those of you unaware, front sourcing is a common retouch and beauty work technique in Flame. You matte a section that you want to fix (say a pimple) and then shift your video under it- blurring, messing with opacity and color correcting as needed.

I took that original advice and added to it and created this little Gizmo. I think especially if you are doing a lot of retouch and clean up or if you are coming from a Flame background you will benefit from this.

You have controls for transforming your front source, blurring your matte/video as well as color correcting your front source.

Attached Files
File Type: py Front_Source.py (173 Bytes)
File Type: gizmo Front_Source.gizmo (4.1 KB)

How to put Nuke’s Paint node into a Gizmo.

Hi folks,

I’m bulding a new gizmo from my basis tree node, but I don’t have any succes from Paint node and some other nodes.

Does anybody has any succes or clues how to put Paint into gizmo pane tools. For now I can only make a group and make a Gizmo with no acces to Paint parameters. Any helps will be appreciate! Thank you!

rendering multiple write nodes huge RAM consumption

Hi,

Is there a way to cut the RAM consumption when rendering multiple Write nodes? When I selected more than 20 Write nodes in the script and F7 to render, the Memory usage and VM size (under WinXP 64bit) went up and up to a degree that slows down the whole operation of OS. (I have 12 GB of RAM)

All the images being written are only 640×360 in resolution though are multi-channel EXR.

Thanks.

background render

Hi all, small issue
i am rendering in Background and my command line looks like this:

"C:/Program Files/Nuke6.1v1/Nuke6.1.exe" -x Z:/PROJEKTE/Egypt/SHOTS/PLA_310/2D/PLA_310_1_Comp_ak_v005.nk Write7(600,851)

my problem – Nuke is rendering all Enabled write nodes and not only specified one, how can i render only the node i want?

Btw here is a python script i wrote to send a script to bg render (i know it is not so aesthetic but better than type it 🙂
you need just select the write node, run the script, copy the command and paste in cmd

Attached Files
File Type: py BGRender.py (734 Bytes)

Nuke 6.1v3 Released

This is a maintenance release of Nuke with feature enhancements and bug fixes.

Version
Nuke 6.1v3

Release Date
1 November 2010

Supported Operating Systems
• Mac OS X 10.5 “Leopard” and 10.6 “Snow Leopard” (32- and 64-bit)
• Windows XP SP2, XP64
• Linux CentOS 4.5 (32- and 64-bit)

New Features
There are no new features in this release.

Feature Enhancements
• BUG ID 13880 – You can now zoom in and out in the Keyer node’s keying range control and set values above 1.0.

Bug Fixes
• BUG ID 12629 – A crash occurred when clearing a customer script.
• BUG ID 13345 – Pro-Res 422 HQ output gave a low quality result.
• BUG ID 13803 – QuickTime: Clicking Advanced when a node didn’t have an input produced unexpected behavior.
• BUG ID 14221 – The default squeeze ratio of an exported FBX camera was 0.5 and not 1.
• BUG ID 14239 – The playback rate was rounded incorrectly with Avid DNxHD movies.
• BUG ID 14305 – QuickTime was crashing Nuke when using a Japanese locale.
• BUG ID 14317 – Write: A customer script hanged when advanced was clicked.
• BUG ID 14483 – Nuke crashed at launch when GenArts OFX plug-ins were installed.
• BUG ID 14508 – There was a color shift in pro-res encoded QuickTime movies exported from Nuke.
• BUG ID 14766 – There was an error with the EXR edge code metadata that prevented rendering.

ETC…..

Release Notes

Product Website