OTOY Forums

Tried the workflow with ACES and After Effects. Just incredibly slow, can't work with it.
Not sure if it's the EXR in general still, or the ACES conversion or both.

Probably works better with Nuke or Fusion.

whersmy wrote:Do you have a reference photo/render that illustrates your point? Or do you mean that you can have a low intensity HDRI letting light in the scene, and having extra smaller lights to fill the room?

When you setup with a ACES workflow, since there is accurate energy going into the scene, you don't need to mess with extra lights etc. You're only concern is having the color workflow setup correctly. Remember color workflow using ACEScg in this case; is about giving enough colors as the Input display transform, accurate colors as in real life, more energy into the scene; realistic looking renders. From there you choose your output display transform, which is just sRGB or AdobeRGB or better yet, DCI-P3 or although still lacking in full gamut Rec2020 if your display can show more then atleast 80% of it's colors.

I noticed that, I think it`s important to have a correct workflow from standalone to Photoshop/Post first..

I have been trying kind of every setting, but can`t get the image I get in Octane correctly exported still.
The image still looks washed/desaturated or highlights are burned when I take it into PS, but in the Octane viewport it looks delociously, scrumptious and lightful
What is still missing??

whersmy wrote:I noticed that, I think it`s important to have a correct workflow from standalone to Photoshop/Post first..

I have been trying kind of every setting, but can`t get the image I get in Octane correctly exported still.
The image still looks washed/desaturated or highlights are burned when I take it into PS, but in the Octane viewport it looks delociously, scrumptious and lightful
What is still missing??

As you mentioned, you should setup Photoshop for ACES. Photoshop was never designed for such large color gamut's, it's unfortunate. Although we can be thankful this what I said is irrelevant as you can setup ACES in Photoshop and experience ACES in Photoshop. As I mentioned, setup ACES in Photoshop, then the images should look the same in both Octane and Photoshop.

I'll be setting up ACES in Photoshop very soon, so if you need help; let me know.

I`m digging into it right now, will post results if successful

I would really appreciate some help with this topic.

I tried a few different scenes to test houdini/octane/aces workflow but cant get it right. The colors are wrong, greenish, over contrasty, dark. I must miss something.

Here is simple test scene, just a texture and an HDRI.
What I did:
- Set to OCIO env variable to ACES config file
- Convert texture and HDRI to Aces with PYCO colorspace converter, set gamma to 1
- Connect OCIO view node
- Octane ROP > intermediate colorspace = ACES2065, color space = OCIO, ocio color space role = ACES2065

Do I miss something?

Also I read this:

Here: https://chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces/
So why ACES2065 instead of ACEScg then?

Thanks in advance!

k3xx wrote:I would really appreciate some help with this topic.

I tried a few different scenes to test houdini/octane/aces workflow but cant get it right. The colors are wrong, greenish, over contrasty, dark. I must miss something.

Here is simple test scene, just a texture and an HDRI.
What I did:
- Set to OCIO env variable to ACES config file
- Convert texture and HDRI to Aces with PYCO colorspace converter, set gamma to 1
- Connect OCIO view node
- Octane ROP > intermediate colorspace = ACES2065, color space = OCIO, ocio color space role = ACES2065

Do I miss something?

Also I read this:

170566670_449449109670781_194729041631252930_n.png

Here: https://chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces/
So why ACES2065 instead of ACEScg then?

Thanks in advance!

I have the same issue and same question