OCIO Octane Settings not accessible in python
Posted: Thu Nov 14, 2024 11:33 am
Hello,
I'm doing some pipeline dev work in python for a vfx/motion studio. I'm setting the OCIO view (Settings->Imager->OCIO->OCIO view) and the Live Viewer view mode to 'OCIO:viewtransform'. It works normally if there has been an user interaction inside the Octane Settings window but if the Settings Window is called via CallCommand the parameters are only partially accesible.
The main issue with this is that in order to setup the scene for the artists, we are requiring them to do some cumbersome manual interaction to be able to automatically setup the OCIO settings. Another main issue is that we are sometimes Initializing (means getting all the information of the shot that are stored in a database like frame range, fps, format and OCIO) via c4dpy on a render farm, which allows us to initialize any number of shots (can be 5 shots or 100 shots).
Also this is not only limited to OCIO, it's almost all of the settings. In the video you can see the difference of IDs after each interaction.
Another issue is that i can't call the OCIO color space button (VP Octane Renderer>Main>Color space 'OCIO:' > Select OCIO color space) via python.
What could be done to ease this process? For me the issue is that all of the settings lives in a Custom GUI Window which has all of it's settings in a BaseContainer, which is initialized after launching the Octane Settings windows which activates Octane. Then you need to modify one setting manually then you can access all of the data via python.
For example in Redshift the OCIO settings are accessible in the RenderData/VideoPost 'Redshift' as well as Octane but it's limited to the "Overwrite Kernel Settings". Expanding these settings to all of the Octane settings would solve a lot of stuff in python.
Thanks for reading and i hope you can provide a solution.
I'm doing some pipeline dev work in python for a vfx/motion studio. I'm setting the OCIO view (Settings->Imager->OCIO->OCIO view) and the Live Viewer view mode to 'OCIO:viewtransform'. It works normally if there has been an user interaction inside the Octane Settings window but if the Settings Window is called via CallCommand the parameters are only partially accesible.
The main issue with this is that in order to setup the scene for the artists, we are requiring them to do some cumbersome manual interaction to be able to automatically setup the OCIO settings. Another main issue is that we are sometimes Initializing (means getting all the information of the shot that are stored in a database like frame range, fps, format and OCIO) via c4dpy on a render farm, which allows us to initialize any number of shots (can be 5 shots or 100 shots).
Also this is not only limited to OCIO, it's almost all of the settings. In the video you can see the difference of IDs after each interaction.
Another issue is that i can't call the OCIO color space button (VP Octane Renderer>Main>Color space 'OCIO:' > Select OCIO color space) via python.
What could be done to ease this process? For me the issue is that all of the settings lives in a Custom GUI Window which has all of it's settings in a BaseContainer, which is initialized after launching the Octane Settings windows which activates Octane. Then you need to modify one setting manually then you can access all of the data via python.
For example in Redshift the OCIO settings are accessible in the RenderData/VideoPost 'Redshift' as well as Octane but it's limited to the "Overwrite Kernel Settings". Expanding these settings to all of the Octane settings would solve a lot of stuff in python.
Thanks for reading and i hope you can provide a solution.