Weird edge around garbage matte.

Hey guys,

Sorry if this is a nooby question but bear with me. I’m still trying to transition over from AE.

I’m trying to key out a non-evenly-lit greenscreen in multiple takes. Normally how I would do it in After Effects is split the footage up into sections with rough garbage mattes, key each section, then re-combine all the images into 1 by merging the alpha’s.

Whilst creating the first pass in Nuke, the Bezier seems to be creating this thin black edge around where the bezier has been drawn (see attached screenshot).

Second problem is when re-combining the alpha’s, the table seems to go transparent, even though the matte is pure white.

Thanks for the help!

Attached Thumbnails
Click image for larger version

Name:	t.jpg
Views:	N/A
Size:	34.9 KB
ID:	8044
 

importing problem

i got exr scene 1-210
all in 1 folder arrenged* by name

when i import to nuke:

i need that in 1 node
ty guys

python script buttons from start up

so i know how to add knobs to a node
i have mad a button on a toolbar too which creates a node and add a new tab and python script button

now when i add the script is where i get issues

Code:

expo = nuke.PyScript_Knob("exports", "Export")
newNode.addKnob(expo)
expo.setValue(exportScript)


however because this script will write to a file i need it to write \n
but when it loads the script it reades the \n and performs it so in the button if i edit it it will be

Code:

writeTo.write('
please code me'
#i want it to be
writeTo.write('\nplease code me')


i tried making the button conation a function call but it would call the function as soon as nuke starts loading

any ideas

cheers

edit::
never mind
got it working now

Nuke Pyton Modules

Is it possible to setup a module to work with nuke and use nuke functions?

I just want a function such as creating a node be called from a Python Button by importing the module. (keep the function up to date and consistent across all instances of being called).

But I get a "NameError: global name ‘nuke’ is not defined"

But the script is being executed in nuke:

import module
module.createNode()

so nuke should be a global name.

RollingShutter 1.0v1 for Nuke from the Foundry

Helps correct skew and distortion created by the rolling shutter in certain CMOS chips in modern digital cameras. Using Local Motion Estimation technology, objects in the frame are individually corrected based on their motion relative to the camera.


RollingShutter 1.0v1

This is the first release of RollingShutter.

Release Date
3 August 2009

Requirements

  1. Nuke 5.1 (tested on Nuke 5.1v6)
  2. Mac OS X (tested on 10.4 PPC and 10.5.7 Intel), Windows (tested on XP32, XP64), or Linux (tested on Centos 4.5 32bit and 64bit)
  3. Foundry FLEXlm Tools (FFT) (5.0v1 or later) for floating license support.

New Features

This section will describe new features in later versions. There is one plug-in in this release.

Improvements

This section will describe improvements to existing features in later versions.

Bug Fixes

This section will describe fixed bugs in later versions.

Known Bugs and Workarounds

BUG ID 8356 – Memory Considerations. RollingShutter is a memory intensive plug-in and will use a lot of RAM during processing. This can raise issues on Windows 32bit machines where memory management can get fragmented. If processing a 4K plate on a windows 32bit machine, you may find that RollingShutter easily runs out of memory. There is currently no solution to this.

Product Website

Foundry Website

Nuke “Element Library” Menu

Hey guys,

I’m starting on a new project today that has a ton of practical elements associated with it. And I’d love to organize all of them into a drop down "Elements Library" menu that’s dynamically generated by the folder structure it’s looking in.

Are there any python wiz kids out there that can give me a hand in starting out? How would you get Nuke to even recognize an outside directory structure, let alone list them all out into menus and submenus? Ideally it would use the first frame as a thumbnail as well.

Thank ya much!

– Doug

NUKE and colorspace handling Issues

Hey Guys,

I wanted to ask around who used nuke in different facilities and in what way does it influence the colorspace handling.
I used it in its early (not DD early) days at The late Orphanage. We had no external color pipeline.

standard FiLm 10bit LOG DPX -> Nuke -> File in converts it into float srgb linear -> comp -> write node 10bit log dpx with cineon conversion -> final

In one shop they had to have more color continuity and linearized all LOG plates into 16bit linear exr sequences.

standard FiLm 10bit LOG DPX -> LINEARIZE 16bit linear exr -> Nuke -> File in converts it into float srgb linear (just a bit depth change)-> comp -> write node 16bit exr linear-> LOG CONVERSION outside nuke -> final

—————————————————-

I am asking because a certain big studio in culver city started to use Nuke and they have a complicated inhouse proprietary color pipeline. from off the shelf maya to LUTS in shake and nuke to film scanners and calibrated sweatboxes.

At the moment I feel my nuke is crippled. Im am getting dpx plates that are supposed to be linearized but still look log to me. we have the color IP toggle on linear (that looks wrong to me) and a Film Lut toggle to mimic the end result that looks fine.
the problem of all this is that some things break (e.g IBK) or work poorly.
this is all a temp solution as Alice in Wonderland is the first show to use nuke as far as I am aware.

Any thoughts?

Multiples questions …

Hello
I’m new to nuke but I like it so much and of course, I have lots of questions

1) Is there a way to change the arrow color between nodes?
I’d like to give different colors. For example, when I create a gizmo, I’d like to give a different color for each entry.

1a) When making a gizmo or when using a node with multiple entries, like a front, a background and a mask for example,
is there any shortcut to display each one?
On flame, for example, you have F1, F2, F3, F4 —> front, back, matte, result
It’s very usefull to check what the entries are.

2) Is there a way to prevent the software to open the property related to a node when inserting a node?
(imagine a pane with 3 tabs: node graph, curve editor and properties)

3) Is there some kind of collapse function for a group of node
I don’t want to make a group but just collapse visually some nodes together and if needed, I uncollapse in order to adjust some parameters …

4) Ctrl + t allows me to go from a tab to another,
is there a way to assign a shortkey to specific tabs? (imagine 3 tabs on the same pane)

5) Is there a way to display the same viewer in 2 different tabs?
If I zoom in viewer 1, it zooms in viewer 2 but I’d like to see the R on the left and the G on the right tab. (or RGB and alpha) with the same value of zoom
But zooming works exaxtly in the same way on both viewers.

6)Is there a way to increase the size of a node
I usually rename my node and it’s bigger than the node 🙂

Thanks

2012 – Nuke TD

This week I will be wrapping on the up and coming disaster film 2012 by Rohland Emmerich. 11 months of hard work by everyone and most likely to be my last hurrah with Nuke 4.x, god rest the tcl monsters soul.

The Nuke pipeline turned out to be pretty extensive and there is just to much to explain in words everything which was done. So below is a link to the cool eye candy features which I was lucky enough to develop over the course of the past 11 months. Most are C++ plugins which a few tcl scripts thrown in the mix.

In what little spare time I’ve had the past few months I’ve been getting the plugins working in 5.x so look for them soon.

Enjoy

www.nfxplugins.com/downloads/nathan_dunsworth_2009_hd720.mov

Dynamic updating of panel?

Is it possible to refresh an enumeration’s options?

When the user selects a drop down I want the options in the second drop down to change?

(In psuedo code):

enum 1[colors shapes]

on changed:
if 0:
enum2 = [red green blue]
else:
enum2 = [square triangle]