Oraphim LogoOraphim
Beta soon

Getting started

First Launch

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

Updated August 27, 2026

First Launch

This page explains first launch in the current Oraphim Windows workflow.

Workflow

  1. Open the workspace or panel named in this guide.
  2. Select the media item, clip, layer, node, or project resource you intend to change.
  3. Make one visible adjustment at a time.
  4. Preview before and after the change.
  5. Save the project after a meaningful milestone.

Practical example

Apply the feature to a short test section first. Once the result is correct, repeat or extend it through the complete timeline or composition.

Verify the result

Play through the affected range, inspect the first and last frame, and confirm that the change survives save and reopen. For delivery-related work, inspect the rendered file as well.

Use First Launch in a production project

  1. Open Project Hub / editor and select the intended active Oraphim project.
  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 First Launch 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

On first launch, confirm authentication/project access, GPU/driver readiness, and that the project hub opens normally before starting production work.

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

  • Save and reopen the .orp project and confirm the expected media, workspace, and timeline state.
  • 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.