Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > ainvfx-paintaplate > Color Space (OCIO)

ComfyUI Node: Color Space (OCIO)

Class Name

PaintAPlate_ColorSpace

Category
AInVFX/Paint a plate
Author
AInVFX (Account age: 580days)
Extension
ainvfx-paintaplate
Latest Updated
2026-11-05
Github Stars
0.03K

How to Install ainvfx-paintaplate

Install this extension via the ComfyUI Manager by searching for ainvfx-paintaplate
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ainvfx-paintaplate in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

Color Space (OCIO) Description

Converts image batches between OCIO color spaces and model viewing or linear-light spaces.

Color Space (OCIO):

PaintAPlate_ColorSpace, displayed as “Color Space (OCIO),” converts image frames between colour spaces using OpenColorIO, a colour-management system commonly used in visual effects and animation. Colour spaces describe how image numbers represent colour and brightness; converting between them helps you move images consistently between AI generation, linear-light editing, and colour-managed production workflows. The node processes several frames at once and supports both colour spaces defined by an OCIO configuration and convenient shortcuts for the model’s viewing space and its linear-light counterpart. Its model-space handling uses sRGB-encoded Rec.709 with ComfyUI core’s tone mapping for values above 1.0, helping bridge model-facing images and production imagery with brighter-than-display values. Alpha, which represents transparency or coverage, is not colour-converted. This is a colour-space conversion tool rather than an automatic colour correction or a creative grading effect.

Color Space (OCIO) Input Parameters:

image

Required input of type IMAGE containing the image or batch of frames you want to convert. The existing pixel values must be interpreted in the correct starting colour space for the conversion to produce meaningful results; the node does not provide automatic source-space detection. For example, an ordinary model-facing image and a scene-linear production plate can look similar in a preview while requiring different interpretations of their stored values. Colour conversion affects the colour information, while alpha, if present, is not converted. No default image, numerical minimum, maximum, or image-size restriction is declared in the node schema.

config

Required STRING selecting the OpenColorIO configuration that defines the available colour spaces, aliases, roles, and conversion rules. The default is the package constant ocio.BUILTIN; the supplied source does not show the literal configuration identifier stored in that constant. The tooltip explicitly supports $OCIO, which uses the configuration named by the OCIO environment variable, and built-in configuration identifiers such as ocio://studio-config-latest. Your choice determines which colour-space names are valid and how transformations between them are calculated, so matching the configuration used by the rest of your project is important for consistent results. This is a text field rather than a fixed-option dropdown, and no numerical minimum or maximum is applicable.

source

Required STRING describing the colour space in which the incoming image values are currently encoded. The default is @model. Accepted forms are a colour-space name, an alias, a role supported by the selected configuration such as scene_linear, or either special shortcut @model or @linear. The @model shortcut represents the sRGB-encoded Rec.709 space the models see, with ComfyUI core’s tone mapping applied when entering that space from values above 1.0; @linear represents that space in linear light. Linear-light values express light intensity directly, making them appropriate for operations such as adding light or performing certain compositing calculations. Selecting the wrong source tells the node to interpret the image incorrectly and can produce unexpected brightness or colour changes. There is no fixed list of configuration-specific names and no numerical minimum or maximum.

destination

Required STRING specifying the colour space in which the result should be encoded. The default is @model. Like source, it accepts a name, alias, or role from the selected OCIO configuration, as well as @model and @linear. Choose @model for the node’s model-facing sRGB-encoded Rec.709 representation, @linear for its linear-light counterpart, or an appropriate configuration-defined space when connecting to a production pipeline. This setting changes how colour and brightness are represented in the resulting image; it does not change the intended meaning of alpha. If the source and destination strings are exactly identical, the node immediately returns the original image without running a conversion. There is no numerical minimum or maximum and no fixed dropdown of options.

Color Space (OCIO) Output Parameters:

image

Output of type IMAGE containing the converted image or batch of frames, with colour values represented in the requested destination space. This is the image you connect to subsequent processing, preview, or saving nodes, and those downstream steps should interpret its values in the same destination space to avoid unintended colour changes. A linear-light result can look darker than expected in a preview that treats its values as ordinary display-encoded imagery, so preview appearance alone does not establish whether the conversion is correct. Alpha, if present, is not colour-converted. When the source and destination strings are identical, this output is the original input image rather than a newly converted result; the node provides no separate colour-space metadata output.

Color Space (OCIO) Usage Tips:

  • For linear-light work starting from an image already in the node’s model-facing representation, set source to @model and destination to @linear. After the linear-light operation, use another instance with source set to @linear and destination set to @model if the next step expects model-facing imagery.
  • Do not assume @linear means every possible linear production space. It is specifically the linear-light counterpart of the node’s model space; for a plate in another linear space, use its actual configuration-defined name or an appropriate role.
  • Use the same config throughout a colour-managed workflow. Select $OCIO when your environment already points to the project’s intended configuration, or use a supported built-in identifier such as ocio://studio-config-latest when that configuration suits your project.
  • Check the exact names and aliases available in your chosen configuration before entering production spaces. A name used in one configuration may not exist in another, and scene_linear refers to whichever space that configuration assigns to the role.
  • Keep both fields at their default @model values only when you want a pass-through. Identical source and destination strings skip conversion entirely, which avoids unnecessary processing but also means this setting does not test whether your configuration is usable.
  • Send an image batch through one node when all frames share the same source and destination spaces. The node is designed to process several frames at once; split mixed-space material into separate conversions so each group receives the correct interpretation.
  • Be cautious when sending high-dynamic-range imagery to @model. The documented model-space entry includes tone mapping of values above 1.0, so do not assume that converting to model space and back will preserve the original HDR values exactly.
  • Avoid converting an image twice by accident. Once you have converted to a destination space, treat that space as the source for the next colour conversion, and check whether your loading or saving nodes already perform colour management.

Color Space (OCIO) Common Errors and Solutions:

OCIO configuration cannot be loaded

  • Explanation: The selected configuration may be unavailable, invalid, or unsupported by the installed OpenColorIO environment. This is a troubleshooting description rather than a verified exception string; the supplied node class does not define its own configuration-loading error messages.
  • Solution: Check the config text for typing mistakes. Try the package default or a supported built-in configuration such as ocio://studio-config-latest. If you use $OCIO, verify that its environment setting points to the intended accessible configuration.

$OCIO is unset or points to an unavailable configuration

  • Explanation: The $OCIO option depends on the OCIO environment variable. If it is missing, incorrect, or points to a file that the ComfyUI process cannot access, the intended project configuration cannot be selected reliably; the exact resulting message depends on the underlying configuration loader.
  • Solution: Set the OCIO environment variable in the environment that launches ComfyUI, confirm access to the configuration and its required resources, and restart ComfyUI after changing the environment. Alternatively, select a supported built-in configuration.

Source or destination colour space cannot be resolved

  • Explanation: A supplied colour-space name, alias, or role may not exist in the selected configuration. For example, a production-space name copied from a different configuration may not be available. The exact exception wording is not shown in the provided conversion code.
  • Solution: Check spelling and use a name or alias listed by the active configuration. Confirm that a role such as scene_linear is actually defined there. Use @model or @linear only when those shortcuts accurately describe the intended spaces.

OCIO conversion cannot be constructed or required resources are missing

  • Explanation: A configuration can refer to external transform resources, such as LUT files. If required resources are missing or inaccessible, OpenColorIO may be unable to build the requested conversion even when the colour-space names are valid; the supplied context does not include an exact exception message for this condition.
  • Solution: Restore the complete project colour-management configuration, including its supporting files and expected directory structure. Check any resource paths reported in the ComfyUI log, or test with a supported built-in configuration to help isolate a configuration-resource problem.

The image looks too dark, washed out, or unexpectedly saturated

  • Explanation: This may be a colour interpretation problem rather than an execution error. Common causes include choosing the wrong source space, confusing @linear with another linear space, applying a conversion twice, or viewing destination-space values in a preview that expects a different encoding.
  • Solution: Establish the image’s actual starting space, set source accordingly, and check the conversion history of upstream nodes. Make sure the next processing or viewing step expects the chosen destination space. Evaluate production-space images through a suitable colour-managed viewing path.

The node produces no visible change

  • Explanation: When source and destination are exactly the same string, the node deliberately returns the input unchanged and does not run OCIO conversion. Different names can also refer to equivalent spaces, or the particular image may show only a subtle visible difference.
  • Solution: If you intended a conversion, select genuinely different and appropriate spaces, such as @model to @linear for a model-encoded image. Do not use an identical-space pass-through as a test that a configuration or colour-space name is valid.

Bright highlights do not match after a round trip through @model

  • Explanation: The documented @model behaviour includes ComfyUI core’s tone mapping when entering that space with values above 1.0. A round trip through this model-facing representation should therefore not be assumed to preserve the original high-dynamic-range values exactly.
  • Solution: Keep the original HDR plate available and avoid unnecessary conversions through @model when preserving production light values is essential. Use the appropriate production spaces for HDR processing and reserve model-facing conversion for steps that require it.

Color Space (OCIO) Related Nodes

Go back to the extension to check out more related nodes.
ainvfx-paintaplate
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

Color Space (OCIO)