From dc36776ebcdeddf8983c92159301fe6b8e79e208 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Je=C5=BEek?= Date: Mon, 16 Jan 2023 14:19:31 +0100 Subject: [PATCH] Update website/docs/dev_colorspace.md Co-authored-by: Roy Nieterau --- website/docs/dev_colorspace.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/dev_colorspace.md b/website/docs/dev_colorspace.md index eea0a63fb5..5acba33da5 100644 --- a/website/docs/dev_colorspace.md +++ b/website/docs/dev_colorspace.md @@ -55,9 +55,9 @@ The *colorspaceData* are stored at root of representation dictionary during publ } ``` -2. Use any mechanism to set OCIO config to host app resolved from `openpype\pipeline\colorspace.py:get_imageio_config` - - either set OCIO environment during host launching via pre-launch hook - - or to set workfile ocio config path if host api is available +2. Set the OCIO config path for the host to the path returned from `openpype.pipeline.colorspace.get_imageio_config`, for example: + - set the `OCIO` environment variable before launching the host via a prelaunch hook + - or (if the host allows) to set the workfile OCIO config path using the host's API 3. Each pixle related exporter plugins has to use parent class `openpype\pipeline\publish\publish_plugins.py:ExtractorColormanaged` and use it similarly as it is already implemented here `openpype\hosts\nuke\plugins\publish\extract_render_local.py` - **get_colorspace_settings**: is solving all settings for the host context