AOV for Denoiser Beauty Tweet

[Andreas_Resch]

I can't find an AOV node for Denoiser Beauty. Any idea how I can add that pass to my AOV outputs?

[linograndiotoy]

You can find the Denoised Beauty in the Octane Composite environment.

No need to add it to the AOVs, since is already selectable along with the Beauty pass, in the Render AOV Output node.

[Andreas_Resch]

Yeah. I'll stay away from those AOV editors for now. They are too confusing. Seems to be better integrated in Cinema 4D where there's just one AOV editor. Maybe it makes more sense there. As long as the Blender Compositor is supported, I should be fine.

[J.C]

Yeah. I'll stay away from those AOV editors for now. They are too confusing. Seems to be better integrated in Cinema 4D where there's just one AOV editor. Maybe it makes more sense there. As long as the Blender Compositor is supported, I should be fine.

C4D has also node editor for AOVs, but as you noticed it has much easier access to them using simplified nodeless interface.

[Andreas_Resch]

You can find the Denoised Beauty in the Octane Composite environment.

No need to add it to the AOVs, since is already selectable along with the Beauty pass, in the Render AOV Output node.

Not sure what I did, but somehow the Denoiser AOV is now written out without the need of a Composition AOV setup. I'll take that and I hope it stays.

But there one other thing. As you can see, the "Object ID" and "Material ID" outputs are labeled differently when you use the Classic Render Passes or the AOV outputs. Maybe synchronizing them makes sense, as all the other outputs (in this setup) share the same label. Not sure if that applies to other outputs that I haven't used as well - maybe worth going through the whole list.

[Andreas_Resch]

I was just reminded, why I don't use the AOV output option for Octane. Its implementation is horrible. Not only it is extremely confusing. It's also badly labeled. Not sure how it works in C4D, but the fact that I can't simply output the denoised image as a separate pass is not great. I need to create an extra Compositor node setup to achieve that. And then it doesn't even work.

All that on top of the Prefix/Postfix problems. So it's still not time to use AOV's instead of the classic Blender Compositor. But at some point this needs addressing. In the end this will be a viable option to the Blender compositing.

There's also a bug where the selected node setup is always set back to not be visible when you either choose another setup in Octane Render AOV or Octane Composite editor.

[linograndiotoy]

We'll check this!
Thanks Andreas!