Oraphim LogoOraphim
Beta soon

Editing

Cuts and Trimming

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

Updated August 28, 2026

Cuts and trimming

Editing operations change the clip instance on the timeline, not the underlying media.

Visual reference

Timeline used for trimming

Trim with enough timeline zoom to see the cut, then play across the edit before moving on.

Split

Choose the Razor tool or the split command, then cut a video, audio, or composition clip at the chosen time.

Trim

Drag a clip edge to change its in or out point. The pointer and edge highlight indicate which side will move.

Ripple delete

Ripple delete removes the selected material and closes the resulting timeline gap where the active track configuration allows it.

Slip and slide

Slip changes the source range while preserving the clip's timeline position and duration. Slide moves a clip while adjusting neighboring edit points. Check the Program Monitor while making either edit.

Precision

Zoom into the edit and use frame stepping for frame-accurate work. Snapping can align edits with the playhead and nearby boundaries.

Use Cuts and Trimming in a production project

  1. Open Edit workspace and select the intended clip, edit point, track, or timeline range.
  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 Cuts and Trimming 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 cuts and trimming 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

  • Play through the edit at normal speed and check upstream/downstream timing.
  • 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.