Oraphim LogoOraphim
Beta soon

Compositing

Layers

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

Updated August 28, 2026

Layers

Layers are ordered visual or control elements inside a composition.

Visual reference

Layered composition in Oraphim

Layer order controls what is in front, while each layer keeps its own transforms, effects, masks, and animation.

Layer types

Oraphim supports media, solid, text, shape, brush, camera, light, and nested composition layers. Available controls adapt to the selected layer type.

Core controls

Every compatible layer exposes visibility, locking, timing, blend mode, transforms, opacity, parenting, masks, and effects. A 3D-enabled layer also exposes depth-aware transforms and material controls where supported.

Ordering

Higher layers render over lower layers unless a blend, matte, mask, or 3D scene relationship changes the result.

Parenting

Parenting lets one layer inherit motion from another. Child values remain editable relative to the parent.

Timing

Drag a layer bar to change when it appears. Trim its ends to change its active duration without altering the source asset.

Use Layers 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 Layers 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 layers 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.