Workspaces

Edit workspace

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

Updated August 27, 2026

Edit workspace

The current Edit workspace.

Build an edit

  1. Import footage into the Media Pool.
  2. Drag a clip to V1 and its audio to an audio track when present.
  3. Move the playhead and use the split control to cut at the current time.
  4. Drag clip edges to shorten or extend available media.
  5. Select a clip and adjust its Video, Speed, Animation, Adjustment, or audio-related properties in the Inspector.
  6. Add transitions, effects, captions, or templates from the Media Pool categories.

Layering rule

A visible clip on a higher video track appears over clips below it. Audio tracks mix together unless a track or clip is muted. Use track visibility, lock, mute, and solo controls to isolate problems.

Verify the timeline

Play across every edit, watch the Program Monitor, and listen through transitions. Scrub the first and last frame of each clip to catch gaps, unintended black frames, or clipped audio.

Use Edit workspace in a production project

  1. Open named Oraphim workspace and select the intended resource that workspace operates on.
  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 Edit workspace 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 edit workspace 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

  • Switch away and back, confirm selection/state persistence, and validate the result in preview or export.
  • 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.