Thanks so much for the video! It's really helpful to understand aces workflow in nuke. But I have a question. If I want to render out the image only for the web eg. uploading on you tube or fb or artstation, what output transform should I chose in the write node?
You want to bake the output transform for the targeted display into the media. In the case of the web (that is computer monitors) that would be sRGB. However, I prefer to use a pure gamma 2.2 EOTF rather than the piece-wise sRGB which can crush shadows. So on my OCIO config I only include the pure power function gamma 2.2 instead of sRGB. So on my OCIO config that would be ACES 1.0 - SDR-video (Gamma 2.2 - Display).
@@derekfloodVFX Thanks so much for replying! I have another question. I rendered out an image in Maya and imported it into nuke for the post work. (I'm following ACES workflow both in maya and nuke). If I hover my cursor across the image, I see rgb value of some highlight areas are above 1. If I turn on the exposure warning, I see lost pixels in those highlight areas. I want to know, is it problematic? Value over 1 means overexposed? Should I always keep rgb value between 0-1? Or it doesn't matter at all? I am very naive and trying to learn all by myself. So it's really confusing for me. If u can clear this... 🙏
@@lazyartist5163 A physically based render should have values that go above one, and an EXR can contain those values. This is a core concept of a scene-linear workflow that is used in both Maya and Nuke (really in all VFX DCC apps). ACES will tonemap those values scaling values between 0 and 16 to a 0-1 range and clipping values above 16. The idea is that the render contains the full dynamic range of the light in the scene, just like a professional film digital cinema camera would. Nuke needs these real-world physical values to properly do things like motion blur or bokeh. Similarly, Maya needs these values to properly do things like GI bounce. You can read more about ACES tone mapping on my Github here: sharktacos.github.io/OpenColorIO-configs/docs/tonemap.html
The main reason is that this video was made before the ACES cg config was released. That said, it is the intention of OCIO that configs are modified according to the needs of studios. My config has several things that were otherwise not available. Some examples are ARRI and RED Display Transforms, Reference Gamut Compression, and Output Transforms (sRGB & Rec.709) for the Write node.
Nice Video Dude I have one video request from you for making a video for Maya Arnold AOV Multi-layer Compositing and merging with the scene also included ACES workflow. we really searching for a video like that, and if possible, please show this workflow with an example of asset glass render in Maya. it would really be more helpful to understand it. Thank you so much fro the hard work you are doing for us.
Thanks so much for the video! It's really helpful to understand aces workflow in nuke. But I have a question. If I want to render out the image only for the web eg. uploading on you tube or fb or artstation, what output transform should I chose in the write node?
You want to bake the output transform for the targeted display into the media. In the case of the web (that is computer monitors) that would be sRGB. However, I prefer to use a pure gamma 2.2 EOTF rather than the piece-wise sRGB which can crush shadows. So on my OCIO config I only include the pure power function gamma 2.2 instead of sRGB. So on my OCIO config that would be ACES 1.0 - SDR-video (Gamma 2.2 - Display).
@@derekfloodVFX Thanks so much for replying! I have another question. I rendered out an image in Maya and imported it into nuke for the post work. (I'm following ACES workflow both in maya and nuke). If I hover my cursor across the image, I see rgb value of some highlight areas are above 1. If I turn on the exposure warning, I see lost pixels in those highlight areas. I want to know, is it problematic? Value over 1 means overexposed? Should I always keep rgb value between 0-1? Or it doesn't matter at all? I am very naive and trying to learn all by myself. So it's really confusing for me. If u can clear this... 🙏
@@lazyartist5163 A physically based render should have values that go above one, and an EXR can contain those values. This is a core concept of a scene-linear workflow that is used in both Maya and Nuke (really in all VFX DCC apps). ACES will tonemap those values scaling values between 0 and 16 to a 0-1 range and clipping values above 16. The idea is that the render contains the full dynamic range of the light in the scene, just like a professional film digital cinema camera would. Nuke needs these real-world physical values to properly do things like motion blur or bokeh. Similarly, Maya needs these values to properly do things like GI bounce. You can read more about ACES tone mapping on my Github here: sharktacos.github.io/OpenColorIO-configs/docs/tonemap.html
Great video! Can i ask why did you use your own custom OCIO config instead of the ACEScg one that is built in with nuke? Thank you!
The main reason is that this video was made before the ACES cg config was released. That said, it is the intention of OCIO that configs are modified according to the needs of studios. My config has several things that were otherwise not available. Some examples are ARRI and RED Display Transforms, Reference Gamut Compression, and Output Transforms (sRGB & Rec.709) for the Write node.
@@derekfloodVFX awesome thank you
Nice Video Dude
I have one video request from you for making a video for Maya Arnold AOV Multi-layer Compositing and merging with the scene also included ACES workflow.
we really searching for a video like that, and if possible, please show this workflow with an example of asset glass render in Maya. it would really be more helpful to understand it.
Thank you so much fro the hard work you are doing for us.
I’ll see what I can do