OCIO problem in 29.19 (bug?)

[dopelessdesign]

Hello, I can not change OCIO views on Blender Octane 29.19
I can change views, but it has on effect in a viewport.
It works as it should in Octane standalone.
Can please somebody check, if you have this issue too?

It worked fine at my side in previous verisons.
Thanks

[linograndiotoy]

Sure, we'll check this.

[dopelessdesign]

I've tested it at my side - it works fine in 29.18, but does not work in 30.0 beta1. So I think there really is a bug in 29.19, that were trasfered to 30.0

[linograndiotoy]

We'll fix this.

Meanwhile, my advice would be to use the (relatively) new AOVs feature, wich definitely expands Octane's AOVs and Compositing area.

[dopelessdesign]

Thank you.

I'll try it out with AOVs feature.
It was pretty challenging for me to find a way to achieve color consistency between applications in my workflow (blender octane -> 32bit exr -> after effects -> 8bit -> photoshop) on my monitor, and setting ACES:Rec2020 in OCIO view is essential step for me.
But I'll take a look at AOVs. Maybe there is a better way.

BTW, I've seen an suggestions in latest article on color management in docs, that the OCIO view has always be set to sRGB, but I don't think, it's the case (at least with Blender). If I set it to sRGB, I get oversaturated colors in viewport (if the Monotor not in the sRGB mode), and then I become washed out image in post.

[dopelessdesign]

OpenEXR at 32-bit is technically unnecessary for outputs other than data AOV.

I'm talking only about still images now. Not video sequences. And yes, I'm using AOVs in post, so I do need 32 bit exr. And the images get printed, so sRGB is not a best choice for me )

Maybe, I'll use Octane compositor instead of After Effects. I've just never used Blender Cycles compositor, as I don't like it too much, so I've ignored the Octane's one. Will take a look.

[dopelessdesign]

If storage and optimization is "absolutely not a concern", then all the above isn't much pertinent but on a technical level, valid.

In my case storage - is one of the last concerns as renders (even 32bit exrs) take maybe 10-20% of the overall project disk space.

That's a common misconception.
sRGB "is fine", and Octane is a spectral renderer; its internal calculations are not limited to sRGB chromaticity primaries "gamut". What's more concerning is in post, particularly with Adbe software in the mix

I do understand, how the octane render works. And you are absolutely right, that it's a slippery way including adobe software in a workflow. Bud I did found a way, that works in my enviroment, how to get the same (at least same enough to become desired results) colors from the start to the finish of the projects, leaving monitors in same wide gamut mode.

For anything more sophisticated/advanced, Nuke and Fusion remain the primary (but paid) choices

Sure, Nuke is a better soulution in many ways. But I don't think it's worth an investment for a small agency, just to composite still images. As far as AE (that I have installed anyways) is doing it's thing (and it's doing it pretty well), I'll stick with it ))

But as I've told, I'll definitely take a look at octane's compositor. Last time I've tried to use Blenders compositor was mayby 12-13 years ago, and I'm pretty sure, things have changed since then )


Btw. I appreciate you're spending your time trying make my (and not onlt my) life easier. Maybe it looks, like I'm trying to defend my point of view (and maybt I am )) ), but your input is very valuable - I'm sure, it'll do good in one or another way.

[linograndiotoy]

The problem has been fixed already in the latest builds.