- Typical configuration files used
Re: Typical configuration files used
toggle quoted messageShow quoted text
I'd honestly say it depends on the time you have and your grasp of what problems you're trying to solve.
In truth the larger hill of difficulty is from generating you're own luts and/or decomposing colorspaces into the relevant ocio transforms, since there isn't as much helpful tooling around this.
If you do go down the path of creating your own config from stratch (not merely culling the list of an existing one) I'd suggest using the API to generate your config. In my opinion there is no reason to be manually editing the YAML by hand.
On Thu, 22 Nov 2018, 5:23 pm Simon Therriault <mos...@...
During my integration of the OCIO library, I have mainly used the configuration files that can be obtained from the OCIO website, mainly nuke and Aces. I was wondering what is the typical use case by users of the library. Do people start from the Aces configuration and strip it down for what they need, do they start from scratch, do they keep the Aces configuration as is?
I'd be interested to have your input on this!
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.
Join email@example.com to automatically receive all group messages.