OTOY Forums

Hi Guys,

We work with the ACES workflow for some projects. With this we set setup an .ocio file inside the color management settings of Octane. But these settings don't get stored with the project itself for some reason.

Reasons why we need this:

- So we can give the project to another designer.
- So we can switch between projects and don't have to setup the .ocio file each time.

Even beter would be if you can also use relative paths. (So you can just enter config.ocio and it will look inside the project folder for the file) This makes sharing even easier.

Hopefully this is an easy change for you guys:)

Thanks!

It's designed as how designed in Standalone side. I don't consider to make any changes about, new problems if I do.

aoktar wrote:It's designed as how designed in Standalone side. I don't consider to make any changes about, new problems if I do.

Hi Aoktar,

Thanks for your response,

That is unfortunate, another suggestion can you make it accessible through python? With this we can create our own script and fix it this way.

There must be a way to go around this issue?

Any suggestions are welcome.

Thanks!

Ok, Sorry for that! But I'll think for this, maybe something that I can do on my side. But there are some potential problems with storing and transferring the OCIO configs. It's not enough to pass one file or storing absolute filenames.

aoktar wrote:Ok, Sorry for that! But I'll think for this, maybe something that I can do on my side. But there are some potential problems with storing and transferring the OCIO configs. It's not enough to pass one file or storing absolute filenames.

If we can set it through python we don't need to ability to save it. Let us know if you can do something for us, with over 30 workstations with octane we need a beter workflow.

@jwzegelaar, how do you have your OCIO set up? Do you use the Environmental Variable method, or a local directory?

jayroth2020 wrote:@jwzegelaar, how do you have your OCIO set up? Do you use the Environmental Variable method, or a local directory?

HI Jayroth,

Currently we have it on a network drive that all workstations can access. How can you work with Environment variables with this? Can that solve anything?

The OCIO directory can be set up as an environmental variable so that any application on a given computer can access it, or it can be loaded individually into Octane. If config.ocio is set up as an environmental variable, it can be accessed easily by any OCIO-aware application, such as Octane, Affinity, and so on.

This may or may not help with your current situation, but it does make managing OCIO between applications easier overall.

jayroth2020 wrote:The OCIO directory can be set up as an environmental variable so that any application on a given computer can access it, or it can be loaded individually into Octane. If config.ocio is set up as an environmental variable, it can be accessed easily by any OCIO-aware application, such as Octane, Affinity, and so on.

This may or may not help with your current situation, but it does make managing OCIO between applications easier overall.

https://opencolorio.readthedocs.io/en/l ... -variables

So these environment variables work with octane? If that is so it can definitely help. Only thing we need now is to detect if the project is using a OCIO file.

Yes, Octane will automatically detect the OCIO environmental variable; you can choose to use the version installed that way, or, you can also specify a different OCIO file if you wish -- and you can easily toggle back and forth.

I have included a handy ACES/OCIO cheat sheet which may help.