Oraphim LogoOraphim
Beta soon

Getting started

System requirements

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

Updated August 27, 2026

System requirements

Oraphim currently targets 64-bit Windows 10 and Windows 11.

  • A modern multi-core Intel or AMD processor.
  • 16 GB RAM for normal HD work; more for large compositions, 4K media, and simulations.
  • A Vulkan-capable GPU with current drivers.
  • An SSD for the application, project files, cache, and active media.
  • Enough free disk space for source media, autosaves, image sequences, and delivery files.

Before reporting a performance problem

Update the GPU driver, close memory-heavy applications, confirm that the media drive is healthy, and test the same shot at a lower viewer scale. Do not assume a codec or hardware encoder is supported unless it appears in the current Export panel.

Use System requirements 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 System requirements 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 system requirements 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

  • 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.