ACES workflow in OctaneX in C4D

[RegSquires]

Following some tutorials online for working in the ACES colourspace and in Octane X I cannot find a colormanagement tab in the settings. Is this something deliberately missing or has the ACES workflow been updated. There seem to be viewport support for ACES and I have tried these with the output set in renders to ACES. This seems to work. I know I would then have to convert srgb tex to ACES or run them through at Gamma 1.

Also I am running C4D R23. When is the timeline for and R24 build

Macbook Pro 15" 2.9GHz 6-Core Intel i9 32GB Ram Radeon Pro 560X + Sonnet EGPU with AMD Radeon Pro WX 9100 Big Sur 11.3

[bepeg4d]

Hi,
Color management and OCIO support has been added in 2020.2 SDK, while OctaneX is still based on 2020.1 SDK.
We need to wait for stable 2021.1 SDK to have both Metal and CUDA versions on the same page.

Happy Mac GPU rendering,
ciao Beppe

[RegSquires]

Hi,
Color management and OCIO support has been added in 2020.2 SDK, while OctaneX is still based on 2020.1 SDK.
We need to wait for stable 2021.1 SDK to have both Metal and CUDA versions on the same page.

Happy Mac GPU rendering,
ciao Beppe

Thankyou. That clears things up

[bollella]

Any progress on OCIO support for OctaneX?
Thanks,
Greg

[SSmolak]

Main reason that ACES is better is that you still have compressed highlights and brighter dark areas on your Live Viewer and after saving it you still have 32bit depth for editing purpose. Also Filmic Blender color space doesn't support 32 bit depth on output.

[SSmolak]

Ok, so what is difference between Filmic tone mapping and Highlight Compression in Octane Camera Imager ? In my test they both looks near the same and have the same limitations while saving to output linear file.

[SSmolak]

An other advantage of the Filmic OCIO package is that it can be applied in post and is generally speaking, "post-friendly" since it can be re-applied independently from the renderer, while Octane's Camera Imager's Hightlight Compression is limited to Octane internally and so, prevents from exporting a linear-scene-referred floating point output - in other words, the output has to be display referred as an integer file format (JPG, PNG, etc) and so, limiting what can be done in post.

The problem is that saving Filmic OCIO as 32bit EXR do nothing - it lose 32bit depth and it looks the same as saving using Highlight Compression. I compared it in Photoshop and Affinity Photo. Exporting OCIO from Cinema 4D Octane even as 32bit linear EXR flatten it to 8 bit. Maybe this is bug ? Exporting as ACES works fine.

[SSmolak]

Theoretically... but please see here, something is wrong with exporting via OCIO in Octane : viewtopic.php?f=85&t=78286&start=50#p404607

[SSmolak]

Are you exporting "HDR (Float 32-bit)" as PNG?

No ! it was saved as 32bit EXR. PNG was only PrintScreen screenshoot

[SSmolak]

I am a bit in a hurry and rushed it but here is a quick test.
The gif file might not auto-play automatically unless opened in a new tab or downloaded.

And do the same with Filmic OCIO - you will have 8 bit output. I've just tested it in Octane Standalone too. Standard ACES works fine.