Oraphim LogoOraphim
Beta soon

Color

Scopes

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

Updated August 28, 2026

Scopes

Scopes provide objective image measurements alongside the viewer.

Visual reference

Color workspace with scopes

Use scopes as measurement and the viewer as perception; neither should replace the other.

Waveform

The waveform plots image levels against horizontal image position. Use it to judge exposure distribution and clipping.

RGB parade

The parade separates red, green, and blue channels. Channel alignment in neutral areas helps identify color casts.

Vectorscope

The vectorscope displays hue direction and saturation distance. It is useful for skin tones and broadcast saturation checks.

Histogram

The histogram summarizes tonal distribution. It does not show where values occur in the frame.

Refresh behavior

Scopes update from the active Color viewer result and use cached data where valid. If a scope appears stale, confirm the selected clip, node, viewer mode, and playback state.

Use Scopes 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 Scopes 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 scopes 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.