# Color-managed Timeline ## What "color-managed" means A **colour-managed timeline** keeps the image in a single wide-gamut, scene-referred working space (ACES AP1 / AP0, DaVinci Wide Gamut / DaVinci Intermediate, ARRI Wide Gamut, etc.) and only converts to the display's colour space when the signal is about to be rendered for viewing. The advantages: every source camera feeds through its own IDT into the same space, creative operations (lift/gamma/gain, curves, qualifiers) all run in a mathematically consistent linear environment, and the final delivery transforms are swapped in or out without re-grading. The catch: **the picture is not display-ready in the working space**. If you feed it to a monitor or a scope that assumes it's already in a display colour space, the image looks flat and muddy because the tone-mapping / gamma / RRT steps haven't been applied. This is why OmniScope needs to know the timeline colour space — otherwise its scopes would plot scene-linear numbers against display-referred graticules. ## ACES Monitoring OmniScope has built-in ACES support via OpenColorIO. When using an ACES colour-science timeline in DaVinci Resolve, OmniScope can decode the ACES colour space directly — no CST sandwich nodes or 3D LUTs required. Internally OmniScope applies the matching ODT (Output Device Transform) from its bundled ACES config, so what you see in the Source Signal view and on every scope matches what Resolve would show through its own ACES ODT. ### Step 1: DaVinci Resolve project setup In **Project Settings / Color Management**, set Color science to **ACEScct** or **ACEScc** and select the desired ACES version.

DaVinci Resolve ACES project settings (ACEScct)

DaVinci Resolve ACES project settings (ACEScc)

### Step 2: OFX plugin settings In the OmniScope Connect OFX plugin settings, set **Image Format** to **RGBA 32bit** and **Timeline** to match your Resolve color science (**ACEScct** or **ACEScc**).

OFX plugin settings — RGBA 32bit and ACEScct timeline

{% hint style="warning" %} You must select **RGBA 32bit** Image Format when working with ACES or DaVinci Wide Gamut. The default 8-bit mode does not have enough precision for these colorspaces. {% endhint %} ### Step 3: OmniScope ACES version In OmniScope **Preferences / OpenColorIO**, select the bundled ACES config version that matches your Resolve project — **ACES 1.3** or **ACES 2.0 (compat)**.

OmniScope Preferences — Bundled ACES config version

You can also point OmniScope to a custom OCIO configuration if your facility requires bespoke transforms. ### Step 4: Verify input colorspace OmniScope automatically detects the ACES colorspace from the OFX plugin and configures the input color management accordingly. You can verify and adjust the active colorspace in the **Input Settings** panel — the input colorspace should show **ACEScct** or **ACEScc** matching your timeline. OmniScope uses its bundled OCIO config to convert from the ACES working space to the display colorspace for correct monitoring on your scopes and source signal view. ## DaVinci Wide Gamut ### Color Space Transform nodes (CST) When you use Nobe OmniScope with DaVinci Resolve in Color Managed timeline and DaVinci Wide Gamut the preview will appear washed out. It's because Nobe OmniScope shows you the raw image data as is in the timeline. There's no display transform applied to the image at this stage yet.

DaVinci Wide Gamut in Color Managed timeline

In order to see the correct image in Nobe OmniScope we need to use 2 built-in OFX plugins called Color Space Transform, one before Nobe OmniScope Connect plugin, and one after:

Here are the settings that we should use in the node before Nobe OmniScope Connect:

And these are the settings to get back to DWG:

### DWG to Rec.709 3D LUT If you prefer not to use the CST node in Resolve to go back and forth between DWG and Rec.709 there's another way. You can use a 3D LUT to go from DaVinci Wide Gamut to Rec.709 directly in OmniScope. Here's the 3D LUT file for download:\ :link:**DaVinci Wide Gamut**: \ :link:**ACEScc**: Go to Options / 3D Luts in OmniScope and load up the file, then in the Input Settings select it from the list:

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.timeinpixels.com/nobe-omniscope/sources/davinci-resolve-ofx/color-managed-timeline.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.