Export

Codecs

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

Updated August 27, 2026

Codecs

This guide covers codecs in the current Windows beta. Supported delivery targets are MP4 H.264, MOV H.264, PNG sequences, and WAV audio.

Use it

  1. Open Export and confirm the selected source resource.
  2. Choose the preset or supported format that matches the delivery.
  3. Set the frame size, frame rate, range, quality, audio option, and output path.
  4. Add the job to the Render Queue and inspect its summary.
  5. Render it, then open the generated file or sequence and review it.

Practical example

For a normal web review, choose an H.264 MP4 preset. For compositing handoff, use a PNG sequence. For an audio-only mix, use WAV.

Verify the result

Confirm the file exists, has the expected duration and dimensions, includes audio when requested, and plays without missing or repeated frames.

Use Codecs in a production project

  1. Open Export / Render Queue and select the intended selected exportable timeline, composition, color session, or audio mix.
  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 Codecs 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

Choose a codec from the delivery/mastering requirement: H.264/HEVC for efficient distribution, ProRes/DNxHR for professional masters, and image sequences for frame-based handoff.

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

  • Open the generated deliverable independently and verify range, codec, dimensions, frame rate, audio, and file integrity.
  • 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.