More ACES / Mplay questions Tweet

[made.by.geoff]

The new beta release is much improved in its color management. The renders from Mplay and written to disk are a much closer match to what is seen and saved out of the IPR. But there's still a discrepancy.

You can see in the screenshot below the IPR renders come out slightly more saturated. For what its worth, the various color modes in the ROP (ACEScg, 2065-1, linear, etc) all match, although I'm confused why, when I switch to OCIO and select ACEScg or 2065-1 from the "Ocio color space rule" dropdown in the ROP, I get RGB value that are all clamped at 1.0 (no overbrights). That's not a big deal, since the ACEScg and 2065-1 settings work as expected. Just curious...

But the mismatch between Mplay and the IPR is still an issue (although now, at least, workable). Unless I'm missing something. Using the ACES 1.2 config...



Thanks.

[made.by.geoff]

Forgot to mention that the images look identical onscreen (in the IPR and MPlay windows). It's only when they are saved to disk that the images saved from the IPR seems to get shifted.

I've cleared the LUT and OCIO settings out of the Edit > Color Settings menu. Is there another setting I'm missing?

[hyde44]

I have the same problem , in exr i can't manage to have the same render as the mplay one , that drive me crazyyy there s so many different option and none seem to work properly

[elsksa]

(...) there s so many different option and none seem to work properly

Not that many. It's the contextual 3D DCC implementation that adds "layers of complexity" from a development and usability stand points.

[hyde44]

In redsh... you click and bim no problem (exept with the shitty nvidia driver)
Here you have toneMapping in output , also in imager , force tone mapping , neutral response , ace tone mapping , ocio ... same for lights , between spectron , and all the option scattered on lot of different menu , also the documentation for houdini doesn't help that much , its easy to get lost . Its a battle to make some good rendering

[elsksa]

In redsh... you click and bim no problem (exept with the shitty nvidia driver)
Here you have toneMapping in output , also in imager , force tone mapping , neutral response , ace tone mapping , ocio ... same for lights , between spectron , and all the option scattered on lot of different menu , also the documentation for houdini doesn't help that much , its easy to get lost . Its a battle to make some good rendering

It's only ~2 clicks to get the color management setup! Octane color management is simpler than it looks. Most of the other options are usually unnecessary (but welcomed in case they are needed). This Octane Color Management Guide page is applicable to any Octane plug-in flavor.

Let me know if it helped. If not, feel free to message me.

[ThomasHelzle]

Yeah, I have the same issue. Using the built-in ACESgc etc. works, but OCIO (1.2 here) creates broken output.
Windows 10/11, Houdini 19.5.435, OctaneRender 2022.1 for Houdini production build 2022.1.0.6
Something is definitely wrong here...

Cheers,

Tom

P.S. @elsksa: spamming every thread with your stuff doesn't help.
Your explanations are well meant I'm sure, but a.) your pages end up being just as confusing as everything else in colour management and b.) No, using your favourite colour profile is NOT the solution for everybody.

[elsksa]

P.S. @elsksa: spamming every thread with your stuff doesn't help.
Your explanations are well meant I'm sure, but a.) your pages end up being just as confusing as everything else in colour management and b.) No, using your favourite colour profile is NOT the solution for everybody.

Hi Thomas, this isn't spamming. Just a way to not rewrite the same text to every post, I wrote it down on a page.

a) If it doesn't help or you are still confused, please, I will gladly help you further and improve my pages. Do not hesitate to drop a DM.
b) It's not subjective. To explain why would confuse you even more. Unless you have time and a large caffeine stock.

[james_conkle]

I too experience this color inconsistency in the Houdini plugin. The cinema plugin does not have this behavior.

To my eye the original post provides examples that show the plugin is setup properly, but still resulting in inconsistent behavior.