IPR saving ACES EXR

[nospitters]

hi,

can someone direct me on how to save out an raw ACES EXR from the IPR Window?
when selecting .EXR it saves the image with a double sRGB curve.

and i am totaly confused about IPR windows...
when switching IPR to MPlay in the options i get totally different image colors!
What is the right way and what view to trust?

[ricky_otoy]

Hi there, I'd go by what you see for IPR if you have ACES set etc.

IPR ACES displayed (LEFT) / IPR EXR un-tonemapped (CENTER) with transforms applied / ROP EXR aces with transforms applied (RIGHT)

There is a separate output colorspace setting on ROP, but the main reason Mplay looks different is also due to it not having a display transform.

Mplay without display transform (CENTER)

Hope that makes sense.
Ricky

[nospitters]

hi ricky,

thx for the reply.
i am on h20.5.445 and its by default ocio color managed. mplay also, i have the image controls set to aces 1.0 sdr view.
switching the ipr to mplay-mode in the octane options gives me these differences.
i would expect the same image appear in both...

saving to disk from the ROP and viewing the output in comp it looks like the image from the Qt5-IPR....

saving EXR (not tonemapped) from the IPR menue i get no "raw" image, a sRGB curve is applied on top. you can test it yourself and bringing that into DJV with ocio aces for example...

or do i have to disable ocio completely in houdini to see the same colors?
so maybe you have some advice how to setup octane for houdini properly for aces workflow, so what i see is what i get....

[nospitters]

octane seems not to support ocio v2.3, which houdini 20.5 has.
with houdini 20.5 ocio v2.3 config octane isnt show up any ocio views...

also with ocio v2.1 octane has difficulties, with that i get these inconsistency in color display on mplay-IPR and qt5-IPR.
So, what ocio version octane 2024.1.2 supports now?

[ricky_otoy]

Hey there, the release notes have it as known issue:

"Octane is still working on supporting OCIO V2.3 (the version that Houdini 20.5 uses). The workaround for now is to use the Houdini 20.0's OCIO files when you use Houdini 20.5. e.g."...

You can add the OCIO as a package like this:

Code: Select all

{
  "enable" : true,
  "show" : true,
  "load_package_once" : true,
  "env": [
	{"OCIO" : "${OCIO-C:\your\path\to\config.ocio}"}
  ]
}