Oraphim LogoOraphim
Beta soon

Workspaces

Audio workflow

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

Updated August 27, 2026

Audio workflow

Oraphim includes audio media, waveform, track, mixer, and production-audio surfaces. The current public documentation does not promise third-party plug-in formats or external control-surface protocols.

Basic mix

  1. Import dialogue, music, and sound effects through the Media Pool's audio category.
  2. Place each role on a separate audio track when practical.
  3. Trim clips and add fades so edits do not click.
  4. Use track mute and solo to diagnose the mix.
  5. Adjust clip or track level and pan while watching the meters.
  6. Leave headroom; avoid sustained clipping at the master output.
  7. Export a video with audio or choose the Audio WAV preset for a PCM mix.

Example layout

Use one track for dialogue, one for music, and one or more for sound effects. Lower music under speech, then audition the opening, loudest section, and ending on both headphones and ordinary speakers.

Use Audio workflow 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 Audio workflow 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 audio workflow 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.