Please 馃憤this issue if you would like this feature implemented!
Describe the problem
Currently, the Deadline Cloud for Cinema 4D integration does not support OpenColor IO (OCIO). The OCIO definitions are not submitted in the service or used on the adaptor side. Customers have requested OCIO for Nuke. We would like to support it for Cinema 4D as well.
Proposed Solution
To do this, we will need to retrieve the location of the OCIO file on the local file system, send it alongside other job attachments, pathmap it in the adaptor, and apply it to the scene before it is rendered via the adaptor
We will use OCIO as a step environment, similar to how the Deadline Cloud for Nuke integration does it (but as a step environment rather than a job environment)
Example Use Cases
OCIO provides a generic color management solution.
Please 馃憤this issue if you would like this feature implemented!
Describe the problem
Currently, the Deadline Cloud for Cinema 4D integration does not support OpenColor IO (OCIO). The OCIO definitions are not submitted in the service or used on the adaptor side. Customers have requested OCIO for Nuke. We would like to support it for Cinema 4D as well.
Proposed Solution
To do this, we will need to retrieve the location of the OCIO file on the local file system, send it alongside other job attachments, pathmap it in the adaptor, and apply it to the scene before it is rendered via the adaptor
We will use OCIO as a step environment, similar to how the Deadline Cloud for Nuke integration does it (but as a step environment rather than a job environment)
Example Use Cases
OCIO provides a generic color management solution.