Hasta La Motion!

Aug 22

R3d files won’t open correctly in Nuke 6 v2

Hello again,

I’ve just received some r3d footage from a client and it is the first time I have ever worked with this format so I am a complete noob with this. Now from what i have seen Nuke works with RED natively so I thought it would be as easy as 123 to get it working. I bring in the R3d file but the strange thing upon the import in the read node is that on the preview window it says it is only 640 x 480 resolution and only has one frame. And when i connect it to the viewer it simply states "Error: Reader did not set the bounding box." But when I have read this in REDCINE the file plays back fine at full resolution and can be converted to dpx etc. However I believe my client wants the footage to stay as R3d footage for the colourist, and from what I can see REDCINE cant convert dpx back to r3d. So where on earth do I go from here? Is there a setting that I am missing because I have tried almost all the combinations in project settings, but the file simply refuses any play back. Any help would be greatly appreciated! Oh and I am also running on windows 7 64 bit if that’s any help towards what the problem might be.

Thanks in advance!

Aug 22

Do you really use cineon LUT to read dpx??

Posted in: NUKE from The Foundry

Hi, I’m in some doubt about the cineon LUT setting in the read node.
I usually use linear or "raw data" setting cause you must have some LUT assigned LUT to the viewer or the end of the tree(like the ARRI HD from FrameCycler) to work with a realiable preview to the final result.

What I cant understand is the function of the cineon LUT is meant to be. The cineon LUT isn’t almost near to the ARRI HD cube which is the real thing. Reading the dpx footage with cineon and looking through the ARRI HD LUT looks bad so, what’s the point??

Just take the famous Marcie.cin, read the file like cineon and assign a LUT like SRGB or ARRI HD. The result is an overexposed burned out image. The hair will be clearly burned out. Instead, if I read the file in linear or "raw data" it looks ok through the correct LUT.

I would like to know why do you use cineon to linear.

Thanks

Aug 20

Noob Question: Good Approach For Noisy Key?

Posted in: NUKE from The Foundry

Hi FVXTalk,

I’m really new to Nuke, and fairly new to compositing.

I have a challenge I’m trying to overcome where I have a set that looks like a basement window. Outside the window we put bluescreen material. I’m trying Primatte as the keyer. Starting out though the way it was shot and put together, the key has a ton of grey noise in the shot. It’s supposed to be a dusty basement window so I have that as a hedge, but I’d like to perfect it the best I can.

What’s the common way to approach really noisy keys? Should I first try and color contrast the read before even keying the shot? Or is there a better approach?

Any feedback appreciated.

Aug 20

Camera tracker won’t track undistorted plate

Posted in: NUKE from The Foundry

Hello there, I was hoping to get some pointers in the right direction. I’ve done a few searches of the forum and this problem hasn’t come up so its probably something incredibly obvious and in my face. I have just undistorted a scene using an STmap node, which has my motion plate rendered back in as a single plate.exr. And the scene has become nicely undistorted, but the camera tracker just wont track it anymore. I works fine on the original plate but through the st map node and lens distortion node it just skips to the end frame and acts as if nothing has happened. As I said before its probably something incredibly simple that I am missing.

Any advice would be much appreciated, thanks in advance 🙂

This also doesn’t track when of course the lens distortion tool isn’t connected and its solely the original plate with the STmap and motion shuffled lens analysis plate. Which I really cant understand why it isn’t tracking.

Aug 19