SUMMARY
When working with Color Management, there are a number of colorspace defaults that can be set within the Mari project. These defaults are determined by OCIO (OpenColorIO) Config file Roles.
This article explains why we introduced Mari-specific OCIO roles and how using these roles can benefit your colorspace pipeline.
MORE INFORMATION
Throughout their pipeline, VFX houses are likely to work with Color Management across various software in order to reach the final image result. Unfortunately, most applications interpret the given OCIO Roles in different ways, which often means that studios are forced to modify Configurations within the pipeline process, or need to maintain individual Configs for each application. This can be time consuming and may be troublesome for TDs who may be unsure of how Role assignments affect each application.
Mari's specific Roles improve the colorspace workflow between applications. These Roles are, as follows:
These Roles greatly streamline the colorspace pipeline. Previously, setting these options had to be done via Python in Mari. Now, with the ability to define the Mari specific Roles within the OCIO Config file, users can manage one global Configuration instead of one per artist.
By introducing these Mari specific Roles, we eliminate conflict between applications where the same OCIO defaults would have been assigned to different Roles; and inconsistencies in production are avoided.
FURTHER READING
To learn more about OCIO Roles, please refer to the OpenColorIO official documentation:
OCIO Docs: Authoring Configurations > Roles
For more information on Color Management and Roles in Mari, please refer to our documentation:
Mari Docs: Color Management > Roles
FURTHER HELP
If you are experiencing difficulties please create a support ticket and provide us with the information requested in this article:
Q100090: Information to send Support when reporting a Mari issue
For more information on how to open a Support ticket, please refer to this article:
Q100064: How to raise a support ticket
We're sorry to hear that
Please tell us why