Skip to content

Colour management

Last updated

Lumit composites in scene-linear Rec. 709, in floating point, whatever your footage arrived in.

Without a configuration Lumit reads what footage files contain and shows the working space encoded to sRGB. An OpenColorIO configuration is for when that is not enough.

File ▸ Project settings… ▸ Colour holds one row, Configuration, with Choose… and Clear beside it.

Under the row explains what happened, what was loaded, or why the configuration could not be used.

Below it, Working space states what the arithmetic runs in.

The configuration is a property of the project, saved in the .lum. A missing or unusable configuration never stops a project opening: the preview falls back to the built-in handling and every assigned colour-space name is kept.

Right-click a footage row in the Project panel and open the Colour space submenu.

  • As the file says is the default.
  • Under From the configuration are the configuration’s own colour-space names. Pick the one the footage was shot or graded in.

The Viewer bar carries a colour-pipeline picker. What it reads is the current view/face.

FaceMeans
Linear → sRGBThe built-in transform.
viewdisplayA view out of the configuration, on one of its displays.
Config not in forceThe project names a configuration that cannot be used; the built-in transform is used.

Open it and the built-in transform is the first row, then one heading per display. Tone mapping sits at the foot, if enabled in Settings.

The Viewer’s exposure and tone mapping settings never reach an export; while either is engaged the badge says preview. These are both solely for helping viewing while compositing.

The export dialogue’s Colour section gains the configuration’s spaces in its Colour space list, under a From the configuration heading. Managed by reads the configuration’s path.

  • A file written through the configuration’s transform is left untagged.
  • An export naming a space this build cannot transform to is refused.