The Write node passthrough does make certain assumptions when your output is exr. Try writing the file out and compare the written frames to your last node.
-sean Sent from my cellular device On Sep 24, 2011, at 2:16 PM, "Anthony Kramer" <[email protected]<mailto:[email protected]>> wrote: NukeX 6.3v2 Windows 7 On Sat, Sep 24, 2011 at 2:11 PM, Anthony Kramer <<mailto:[email protected]>[email protected]<mailto:[email protected]>> wrote: It gets worse.. Seems like it's also calculating a few other key operations in my comp differently when selecting EXR as the output format in a write. Besides the neg values below which seem to be coming from a grade, it also makes my Zblur and LensDistortion look different. If I disable those 3 nodes, I get no difference between the last node and the write. If I enable ANY ONE of those nodes I get a slight difference in their calculation when viewing the write node only. Bizarre. Serves me right for working on a Saturday. -ak On Sat, Sep 24, 2011 at 1:06 PM, Anthony Kramer <<mailto:[email protected]>[email protected]<mailto:[email protected]>> wrote: So I have a fairly simple comp here and at the end when it goes to the write node, all of a sudden I get negative values. Take a look at the screen caps below and let me know if you seen anything like this. If I switch the write node to dpx/Cineon the problem goes away. If I switch to exr/Cineon the problem stays so it seems to be something with the filetype being exr, not the colorspace. -ak <image.png> _______________________________________________ Nuke-users mailing list [email protected]<mailto:[email protected]>, <http://forums.thefoundry.co.uk/> http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
