What about using two Output AOVs?
One with color correction for Live View preview, and the other without it for compositing in post.

You can use the same nodes connected to both Output AOVs, and add the color correction only on top of the first one.

ciao,
Beppe


That would work, true - though ...

Sorry, I cannot reproduce the issue.
Output AOVs are untonemapped, so you need to apply the same color conversion with layers, to obtain the same result you have in Main pass, and Live View color dropdown menu shouldn't have any effect on Output AOVs :roll:

Could you share an example scene that ...

Setting the Live Viewer to "sRGB: ACES 1.0 SDR-video" does not seem to affect how Output AOVs are displayed in the LV, creating a color/gamma mismatch between them and the Main pass. They only match if I set the LV back to "None". Is this expected behavior?

As a workaround, I can temporarily apply ...

Tested the update and my scene from 1.9.0 has now kept its look in this new version, so this solves the issues I mentioned in the last thread. Thanks! : )

One more thing I noticed when rendering an existing scene from 1.9.0 in 1.9.1: Some node heavy materials change their look a bit. I think it might be connected to usage of the Gradient Node and you do list this node under the "improved color conversion" section. Could this be possible, even for ...

This was an oversight. I'll see if we can fix this.


Aah, perfect, thank you! : )

One more thing I noticed when rendering an existing scene from 1.9.0 in 1.9.1: Some node heavy materials change their look a bit. I think it might be connected to usage of the Gradient Node and you do list this ...

Ah, but the Material Link node is amazing - looks extremely useful, thx! Just this morning I was looking for a way to blend between two existing comp materials without having to resort to the old mix material or copying a large amount of nodes.

Only downside I've noticed so far is that the LV doesn ...

One small bug I just came across: The depth dropdown in the Render AOV Manager starts off as 16 Bit in a clean new scene, but once you change it to 32, it shows as blank and can't be changed to either 16 or 32, it stays empty.

That guide is outdates. The 1.9.1 build should now always copy over color data correctly to octane, regardless of the colorspace that C4D is using. So you can just leave C4D OCIO settings the default, octane should copy over the colors correctly then.
When it comes to the view colorspace you can ...

@ChrisHekman: Thank you for shedding more light on this!

So in a clean, default C4D scene - what settings should users typically change so that it works with the current iteration of the plugin?

From what I understand, we would usually want to stick with the new C4D default (ACEScg) render space ...