Ocio config

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. If nothing happens, download GitHub Desktop and try again.

ocio config

If nothing happens, download Xcode and try again. If nothing happens, download the GitHub extension for Visual Studio and try again. Skip to content. Dismiss Join GitHub today GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. Sign up. Python Branch: master. Find file. Sign in Sign up. Go back. Launching Xcode If nothing happens, download Xcode and try again.

OCIO Color Management

Latest commit. Latest commit 0bbc Feb 19, This repository contains all the default color configurations, for use with OpenColorIO. Visit opencolorio.

ocio config

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.

1v5 clutch ( config in description )

Jun 4, ACES 0. ACES 1. Mar 22, Jan 15, Fix incorrect "Canon BT. Feb 17, Matches sRGB, but with extra ra…. Feb 28, Feb 1, Aug 27, OpenColorIO is primarily controlled by a central configuration file, usually named config. This page will only describe how to syntactically write this OCIO config - e. This page alone will not help you to write a useful config file! See the Configurations section for examples of complete, practical configs, and discussion of how they fit within a facilities workflow.

This config file is a YAML document, so it is important to have some basic knowledge of this format. OCIO configs typically use a small subset of YAML, so looking at existing configs is probably the quickest way to familiarise yourself just remember the indentation is important!

Use the ociocheck command line tool to validate your config. For more information, see the overview of ociocheck. Currently there is only one OCIO profile version, so the value is always 1 one. Each directory is checked in order to locate a file e. It will look in the luts directory, relative to the config. Paths can be relative to the directory containing config. Multiple paths can be specified, including a mix of relative and absolute paths.

Each path is separated with a colon :. For more information, see the examples in Looks. Valid values are true and false. Default is true assuming a config is present :. However, if the colorspace cannot be determined and strictparsing: trueit will produce an error. If the colorspace cannot be determined and strictparsing: falsethe default role will be used. Application authors should note: when no config is present e.

These are the luminance coefficients, which can be used by OCIO-supporting applications when adjusting saturation e. The luma value is not respected anywhere within the OCIO library. Also very few if any applications supporting OCIO will respect the value either. A typical role definition looks like this, taken from the spi-vfx example configuration:.

Use an OCIO configuration file for color management

All values in this example such as cpflg10 and ncf refer to colorspaces defined later the config, in the colorspaces section. This section defines all the display devices which will be used. These views provide different ways to display the image on the selected display device. Examples of common views are:.OCIO configuration files are designed to be used across a facility and are supported by many software applications.

By using the same OCIO configuration file in Maya and other applications, you can ensure the compatibility of colors between them. When you use a configuration file, you can select only the color spaces that are specified by the file.

The natively supported color spaces are not available. In addition, different items may be available in different menus, if the configuration file defines specific roles for the color spaces.

In particular, the author of the configuration file can define the "rendering" role to preset the Rendering Space preference to the desired value. Note: As an alternative to specifying a configuration file in the preferences, you can set the OCIO environment variable. In addition, OCIO config path is set to the path defined by the environment variable. Note also that the OCIO environment variable is overridden if you are using a color management policy as described in Use color management policies external preference files.

Parent topic: Configure color management.Descriptions for the colorspaces in the different families are provided below. For ease of use across a broader number of applications, the family name of each colorspace is pre-pended to the colorspace name when the configuration is authored. Those prefixes will be omitted in this document, but will show up when the configuration is loaded and used.

These colorspaces produce code values ready for display on hardware devices calibrated to the standard used to name the colorspace. There are a variety of Input Transforms covering different cameras manufacturers, gamuts, transfer functions and camera settings. See below for specifics. These colorspaces are used to convert from camera-specific formats and encodings to ACES. References and descriptions are provided for each group of Input Transforms below.

Canon ACES landing page. Clog white paper. C Drivers and Software. A collection of colorspaces that are used to facilitate the creation of LUTs and other basic functionality. The alias colorspaces are named with all lower-case letters and no spaces, dashes, parentheses or other characters that would not work well in a filename.

They are only references, aliases for the base colorspaces with more user-friendly names. Additionally, a number of colorspaces that are gaining wider adoption have been added to the config. Their names and assignment are:. The release contains a number of file renames and the new ACEScct color space and a number of minor bug fixes and small additions, but is otherwise very similar as the master ACES 1. The script used to generate these transforms and the transforms themselves were the product of work and conversations with a number of people.

Thanks go to:. Host applications should be used to apply an full-to-legal scaling needed. Technical information References and descriptions are provided for each group of Input Transforms below. Conversations with David Newman of GoPro. The 48 nits spaces cover Should be applied to data in the ACES colorspace.

ocio config

Aliases Description The alias colorspaces are named with all lower-case letters and no spaces, dashes, parentheses or other characters that would not work well in a filename. These colorspaces should not generally be used by most artists.

If a Look is added to the config, a new set of Views will be added, one for each of the Views listed above except Raw and Log, that includes the Look.

The Views with Looks will be interleaved in the View list with the original Views. Created using Sphinx 1.Descriptions for the colorspaces in the different families are provided below.

For ease of use across a broader number of applications, the family name of each colorspace is pre-prended to the colorspace name when the configuration is authored. Those prefixes will be omitted in this document, but will show up when the configuration is loaded and used. These colorspaces produce code values ready for display on hardware devices calibrated to the standard used to name the colorspace. There are a variety of Input Transforms covering different cameras manufacturers, gamuts, transfer functions and camera settings.

See below for specifics. These colorspaces are used to convert from camera-specific formats and encodings to ACES. A collection of colorspaces that are used to facilitate the creation of LUTs and other basic functionality.

The role colorspaces are aliases to the colorspaces used for the OCIO 'roles' functionality. The alias colorspaces are named with all lower-case letters and no spaces, dashes, parentheses or other characters that would not work well in a filename. They are only references, aliases for the base colorspaces with more user-friendly names. Additionally, a number of colorspaces that are gaining wider adoption have been added to the config. Their names and assignment are:.

The configuration depends on the ACES 1. The release contains a number of minor bug fixes and small additions in the utilities folder but is otherwise the same as the master ACES 1. The script used to generate these transforms and the transforms themselves were the product of work and conversations with a number of people.

Thanks go to:. Skip to content. Branch: master. Create new file Find file History. Latest commit Fetching latest commit….OpenColorIO OCIO is a complete color management solution geared towards motion picture production with an emphasis on visual effects and computer animation. OCIO provides a straightforward and consistent user experience across all supporting applications while allowing for sophisticated back-end configuration options suitable for high-end production usage. OpenColorIO is released as version 1.

Most users will likely want to use the OpenColorIO that comes precompiled with their applications. See the Compatible Software for further details on each application. Example images are also available. For assistance customizing. If you are on a platform that is not envvar friendly, most applications also provide a menu option to select a different OCIO configuration after launch. Please be sure to select a profile that matches your color workflow VFX work typically requires a different profile than animated features.

If you need assistance picking a profile, email ocio-user. Download a. Please see the Developer Guide for more info, and contact ocio-dev with any questions.

Created using Sphinx 1. All Rights Reserved.An OCIO look typically exists as a flexible addendum to a defined viewing transform. Examples of looks may be a neutral grade, to be applied to film scans prior to VFX work, or a per-shot DI grade decided on by the director, to be applied just before the viewing transform.

Looks are defined similarly to colorspaces, you specify a name and a transform possibly a GroupTransform containing several other transformsand optionally an inverse transform. Where looks differ from colorspace definions are in how they are applied.

A look is a top-level OCIO configuration object. All of the changes below to the. You could also specify a. This lets application in the viewer provide options which use the looks. You can also use this for multiple levels show, shot, etc. Advanced option: If some shots use. Caveat: this only works in 1.

Advanced option: If you are writing your own OCIO integration code, getProcessor will fail if the per-shot lut is not found, and you may want to distinguish this error from other OCIO errors. Example look definition in a OCIO config: looks : -!

Created using Sphinx 1. Step 2: Update the Display to use a look. Step 3: Get per-shot looks supported. Example: -!


thoughts on “Ocio config

Leave a Reply

Your email address will not be published. Required fields are marked *