Oraphim LogoOraphim
Beta soon

Color

Workflow

Use workflow in Oraphim with a production-safe workflow, practical example, verification steps, and common failure checks.

Updated August 27, 2026

Workflow

Workflow is part of the Color workflow. Begin by selecting the correct timeline, clip, composition, or media source.

Workflow

  1. Display a useful scope and inspect the uncorrected image.
  2. Apply the smallest correction that solves the problem.
  3. Separate major operations into clear nodes when possible.
  4. Compare before and after and review neighboring shots.
  5. Play the result at normal speed.

Example

Use the tool to correct one visible issue—such as exposure, channel imbalance, or an isolated color—then check that neutral objects and skin remain believable.

Verify the result

Confirm that the correction affects the intended source and region, does not clip important channels, and stays stable through the shot.

Use Workflow in a production project

  1. Open Color workspace and select the intended explicitly selected clip or color source.
  2. Establish the correct input state first—timing, media link, layer/node enable state, project settings, or source selection as relevant.
  3. Apply or adjust Workflow with one clear goal. Change the smallest set of controls needed to reach that goal so the result remains understandable and reversible.
  4. Review the complete affected range in context. Scrub difficult frames and also play at normal speed when motion or audio is involved.
  5. Save a named milestone before moving into another major operation, especially after graph changes, tracking, AI processing, relinking, simulation, or delivery setup.

Practical guidance

Use workflow only where it solves a defined creative or technical problem, and compare the result against the untreated state.

A useful test is a short 5–10 second section containing both an easy case and a difficult case for this feature. Tune against the difficult moment without breaking the easy one. If two approaches are plausible, duplicate/version the project state and compare them rather than stacking both together blindly.

Verify the result

  • Check scopes, normal viewer output, and a rendered review rather than trusting one still frame.
  • Toggle/bypass the operation where possible and make sure the change you intended is actually responsible for the result.
  • Check selection, visibility/mute/solo state, node connections, track locks, range, and source identity when the result appears missing.
  • Save and reopen before treating a complex setup as reusable.
  • If this feature changes final pixels or audio, render a short review and inspect the file outside Oraphim.