Newbie question – How to composite file with red matte

I’m also using Vue, and I exported a tiff sequence of a 20 frame animation, along with an alpha channel of that same 20 frame animation as a tiff sequence. The alpha channel is red and black, which I thought was strange since Im used to working with white and black mattes.

Is this red and black matte usable in Nuke? Or would I have to convert it somehow to black and white only?

Does anyone have an example Nuke script I can check out, to do a simple composite of applying a matte to an image?

Im sure I can find a way to apply the matte to the image, and composite over a checkerboard, but Id rather know the correct way to do this.

Just for reference, the animation is a mountain peak, which is supposed to have the top half matted out, so I can composite over a sky.

If anyone can do a mockup of this or something similar, with a checkerboard, that would be great, I just dont know how to get the mountain image to read the matte to get the transparency.

Thanks.

Displacement map Zbrush/Maya —> to Nuke

Hi,
Is there a difference between using a displacement map in a 3D app and using the same displacement map in Nuke with the DisplaceGeo node.
(Displacement map for a Character for example)
Thanks.

tab search modification

Hi,
I was wondering if you can change the behavior of search nodes (wen u press Tab key)
Now we have to find the name written from scratch, which is very uncomfortable.

It is possible modify it so you can find strings writing only some part of them?

thanks

3D card has jaggy edges

Hello, I did a camera projection on a card, and I notice the card has jaggy edges when I zoom in real close in 3D space or scanline render. Does anyone know why?
Thanks

Real time playback in Nuke

Hey guys!

I’m planning to upgrade my Mac Pro in order to archive a "almost real time" playback in Nuke (HD ucompressed 10bit and maybe 2k). I currently have an external hdd enclosure with 4 HDDs in Raid 5 connected via eSata so I thought it could be a good idea to get a 32GB OCZ ssd for cache and 3 WD caviar blue in Raid 0 for the files I’m working on (living the OS in another ssd on the optical bay and the external as "backup").
Do u guys have any experience with this kind of setup? Any suggestions?

Cheers

DPX or EXR?

Hey guys!

From your experience, what’s the best file format to convert HD footage (ProRes 422 or uncompressed 10bit) to work in Nuke? DPX or EXR? If EXR, what kind of compression?

Cheers

Colorspace in Nuke

Hey guys!!

I’m a little confused about the colorspaces in Nuke and hope u could help me out.

As far as I know, Nuke linearizes every image data from the Read nodes. When we read in a file, the colorspace setting on the Read node is telling Nuke what to convert FROM to get the image data into linear light space. Since the vast majority of monitors in use today are calibrated or have a preset for displaying images in sRGB space, we can choose sRGB (default) or Rec709 in the vLUT. This performs a conversion of the data in the viewer and not actually changes the image. It just puts a "filter" between us and the image data so you can view it correctly.

A lot of times a noticed that the colors on my output render doesn’t match what I had on Nuke’s viewer. For example, If I read in a Gamma 1.8 footage it looks more washed out on the viewer (in sRGB) than it looks but if I flipbook it (also in sRGB). The flipbook always shows more saturated colors. If I play this same footage with quicktime it looks washed out but if I play on whatever other playback option (even on the web browser or FCP) it looks more saturated. This gamma shift Is not a big deal if I don’t need to grade the final cos I can make all the images match (the ones in different colorspaces that need to be added to the comp), but it can be a little annoying otherwise.

How do you guys deal with this kind of situation? How do u keep the colors u see on the Nuke viewer consistent to the colors on the output render? Should I change the colorspace on the Write node to sRGB? But then wouldn’t it be inconsistent with the colorspace of another non-vfx clips in the editing app? Or it should be fine if all of the clips on time line have a final grade before finishing? What would be the best workflow?

Any help will be appreciated!!!!

Cheers

Image based difference Key? IBK? Difference? How to key?

Hi there 🙂

I’m pretty new to Nuke – so hope u don’t mind a Beginner-Question.

I can’t make up how to key it out:

1. I got a Clean-Plate, an image-sequence without the Actor (no green-/ or bluescreen)

2. The Actor in front of the same plate. Nothing changed, Lighting is the same, camera angle the same.

I have different plates with the Actor, want to mix them together into one (like this "multiple-personality-thing" 🙂 )

I saw that IBK is capable of bad greenscreen-keying, but there is no greenscreen – but it should be "image-based". It’s more like a difference key – while the difference key doesn’t bring up a good result.

Is there a way keying this footage without rotoscoping by hand? 🙂

best regards,
Banqo


Nuke and AE viewing LUTs – comparasion

I’m trying to set up a Nuke and AE workflow where I can use the same LUTs in the two programs and have them look the same. But I have ran into some problems. I have loaded a linear EXR sequence in Nuke and AE and it doesn’t look the same.

Settings Nuke: Read Linear, ViewerLUT sRGB.
Settings AE: Workingspace sRGB, Linear Blending, 32bpc.

I though these two settings would match. But if you look at the attached screenshot, they differ quite a bit. I have a Colorspace node in the Nuke script btw, but it doesn’t do anything, I just added it for you to see if I should have some other "D65" settings, but none of them seem to match.

If I render out a EXR from Nuke and import it into AE they look identical, so it’s just a viewing thing.

Anyone know anything about this?

Attached Thumbnails

Click image for larger version

Name:	Nuke_AE_comparasion.png
Views:	N/A
Size:	693.3 KB
ID:	11336
 

again apple prores gamma issue using 6.2 vs 6.1

Hi, I think this issue has been fixed in 6.1v2 but now 6.2v1 gave me back the problem. The prores has wrong gamma interpreted. Someone said that the prores use gamma 2.2 but in fact i found and use gamma 1.8 correctly in nuke 6.1v2.

Here the test, i use ‘read’ node then render it out directly using ‘write’ node. I’m reading a prores format, then render out as prores too.

case #1 : Perfect result using 6.1v2
read prores using default (gamma 1.8) then write using default (gamma 1.8)
input and output are perfectly match, no gamma shift. nothing to worry about.
using this version , i can work smoothly read dand write without any problem

case #2 : using 6.1v3
the workflow above is not working anymore, gamma is wrong. I got different gamma.

case #3 : using 6.2v1
same problem like case #2
to work this out, i ussually do a little trick. Read using 2.2 and write out using 1.8, this way i can get the output the closest possible to the original, but still there’s a bit gamma shift. But that’s all i can get.

The problem got complicated when i want to pipe out/branch in the middle of the workflow. Let say i want to pipe/write out a dpx file. The trick in case #3 will give me dpx with wrong gamma, it gets darker. To fix, i have to insert additional node (colorspace node) and do conversion in:1.8 out:2.2. This i can get the correct gamma back.

Again, using 6.1v2 , i can write it out dpx without to worry about gamma. All the output and original will keep the same gamma. Just Read it and then Write it. no headache. Well, 6.2 …. i love the dopesheet , but hate this gamma thing.

Anyone want to share better workflow ?

thanx