Oraphim LogoOraphim
Beta soon

Troubleshooting

Performance Issues

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

Updated August 27, 2026

Performance Issues

Use this checklist when diagnosing performance issues.

Isolate the problem

  1. Save the project and note the exact action that triggers the issue.
  2. Confirm the intended clip, layer, node, source, or export job is selected.
  3. Test a short, simple range with one effect or operation disabled at a time.
  4. Check free disk space, source-media availability, and the output folder.
  5. Restart Oraphim and reopen the project if the state appears inconsistent.
  6. Preserve an autosave or recovery copy before destructive experiments.

Useful evidence

Record the project name, Oraphim build, Windows version, GPU and driver, source format, exact steps, and whether the problem appears in the viewer, the rendered file, or both.

Diagnose systematically

Diagnose performance by simplifying one variable at a time: media decode, resolution, effects, simulation quality, cache state, or GPU pressure. Proxies and lower preview quality should not change final-source export policy.

  1. Save the current project under a safe milestone when possible and preserve any crash/error logs.
  2. Reproduce the issue with the smallest useful clip, layer, node, track, media file, or project resource.
  3. Check the basic state first: active project, selection, source availability, visibility/mute/solo, locks, graph connections, range, and required runtime/model/GPU prerequisites.
  4. Change one variable at a time. If reducing preview quality, disabling one effect, using original media, or bypassing one graph branch fixes the symptom, you have a useful boundary for diagnosis.
  5. Repeat the original operation, save, reopen, and verify the fix survives a normal project cycle.

When collecting evidence

Record the Oraphim version/build, exact steps, source format, project dimensions/frame rate, relevant hardware/driver details, error text, and whether the problem occurs in preview, final export, or both. For media/export problems, include the source/output codec and a minimal test asset when licensing permits.