Compositing

Effects

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

Updated August 28, 2026

Effects

Effects are non-destructive processors attached to a selected layer or clip.

Visual reference

OpenFX and effects browser

Find an effect in the browser, apply it to the intended layer, then refine its parameters in context.

Add an effect

Open Effect Controls, choose Add Effect, and select a compatible effect. The applied stack displays each effect's enable state and editable controls.

Stack order

Effects evaluate in stack order. Reordering effects can change the visual result because each processor receives the output of the previous one.

Animation

Parameters that expose keyframe controls can change over time. The rendered result updates in the viewer and export path.

Compatibility

Not every processor is meaningful for every layer type. Oraphim disables or explains unsupported combinations instead of presenting an active control with no render effect.

Light-source effects

Compatible layers can receive 2D or 3D light-source behavior through Effect Controls. These controls use the existing composition lighting paths rather than a separate workflow.

Use Effects in a production project

  1. Open Composition workspace and select the intended layer, mask, matte, effect, or composition graph item.
  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 Effects 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 effects 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

  • Scrub the shot, inspect edges and timing, then render a short review range.
  • 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.