try adding a gamma node set to .454545 ahead of the write node.
Type: Posts; User: schmoby; Keyword(s):
try adding a gamma node set to .454545 ahead of the write node.
If it's washed out it's probably getting double-gamma'ed. What colorspace are you working in
DD also created Nuke in the first place :D
There's too many different kinds of passes, many of which are optional, named differently by different places, and ways to use them to tell you how to comp them all. But a very general way to think...
Agreed that depth passes should not be filtered or anti-aliased. Doing so will give you inaccurate depth info at the edges; those pixels will have a mix of foreground and background depth values,...
Do a simple test with a new comp, with only one node like a blur, set to something absurd like 200, then see what your cpu usage is. If it's still far below 100% per core, there is a command to check...
Any reason you don't use Nuke's previewer?
Hopefully it's because the Foundry gives it a low priority. Have to agree with Stu on this one, I've seen issues with 3d apps rendering to compressed formats too... basically it's because neither of...
Hard for me being a non-Shake user to understand what you're scrubbing, but would the color wheel at the far right of each slider be what you need?
You can also click the '4' next to that, then...
Just a thought, can you try tweaking your depth pass - it's not 255 white in that jpg at least - or more radically, create matte from the lightpost color to isolate it, use that to blur it out 1 pix...
Do you have your zdepth copied into the tree above the zblur node? Could your zblur settings be out of range, have you adjusted it with the focal-plane setup? (sorry I only know the zblur node) Then...
Very generous of you guys!
Thank you!
Shift+command+3; captures the whole screen and saves it to your desktop
Shift+command+4; lets you draw a region, or hit the spacebar and click on a window you want captured.
Add the control key...
Hard to say without knowing what your passes are / how much they're broken out and what the naming conventions are, but some basics :
passes that brighten your image, like light passes, global...
nook rulez!
I think it's because Nuke auto-detects what you're loading. Load a JPG and Nuke will apply a gamma to it right away. If you then change it to 'linear' you'll see it change again.
Click the "2" at the far right of the 'size' slider, and you'll get a field for each x and y. This works the same way as in color sliders when adjusting colors individually.
As soon as I have a chance to try it out I'll post something!
Cool, thanks!
Yes, but the projection image is much larger, and the renderer was scaling it down to the project size, that was the problem.
Ok I found it, it was the root format/no bg connected to the scanline - but why would it scale down the image before rendering instead of after?
I've got every resolution and quality setting I can find (anti-aliasing, samples, viewport res, proxy off) at maximum, and messed with every setting that might be related like different filters, but...
Ok I turned it off, but now it's even more different! No big deal, as long as it's doing what it's supposed to. I rarely go from pshop straight to nuke.
Thanks a lot beaker!
Ok you were right! Looks like the alpha is displayed linear no matter what, in both the viewport and the pixel value display - which kinda makes sense since you wouldn't put a curve on an alpha...