ShapeShifting with Charlex

ShapeShifting with Charlex

Shapeshifter_featured

A dark car speeding through the night bursts suddenly into a thousand pieces, forming brilliant metallic creatures on the surface of an alien planet. Such is the action in ShapeShifter, a short film entirely conceived and created by New York studio Charlex. Here’s my article at fxguide about how the film, directed by Charlex founder Alex Weil and narrated by Gabriel Byrne, came to be.

The Guardian Project

HOM and Stan Lee develop a short film as part of their launch efforts for new superhero franchise titled The Guardian Project

Real-time 3D photorealistic Reality

NeuroSystems released a video showing realtime 3D photorealistic Augmented Reality and Computer Vision achieved with its technolog…

Digital Matte Artist.

A Toronto based vfx studio is currently looking for a Digital Matte Artist.

Requirements:

Experience designing and creating 2D paintings, including 2.5-D matte paintings and 3D camera-mapping shots.

Experience in designing and executing 3D environments, as well as 3D matte paintings featuring camera projection setups.

Strong understanding of color, perspective and mood.

http://www.smoothdevil.com/index.php?page=job&job_id=1558

closes: 31 Mar 2011

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
 

Snowy Mountains Maya Camera Projection

Hi

I recently finished a matte painting. I won’t have time to work on it again for a while, but I’m planning to collate all my works into a showreel over the summer, so any and all advice is welcomed.

Considerations:
> I’ve been told to work on the image metrics. Scale of the chorten (building) to make it a building humans could interact with.
> I probably need to add more trees and variations on them. Any kind of procedural randomized colour adjustment in maya materials would be great here.
> I’m probably going to lose the maya material display, concept image, nuke nodetree, and reverse the playback when I integrate it into a reel.

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

write node behaviour – turn on read file parameter

hi i’m confused with the write node.. while i turn on the ‘read file’ , it will load the images from disk instead of its input, but then why can’t i disconnect the input since it doesn’t need its input anymore ? coz in this stage it will load from disk, why i got error (blank) when trying to disconnect it? is there any good reason? can anyone explain it?
Also why that ‘read file’ only works for reading image sequences, what about .mov ?

thanx