Troubleshooting reference

Start with the smallest reproducible problem. Randomly resetting layouts, moving files, deleting caches, changing drivers, and replacing project settings at the same time destroys useful evidence.

Fast diagnosis order

1. Selection/context — confirm the intended project, timeline, composition, clip, layer, node, track or export resource is active.
2. Media — confirm source files are online. Relink moved media instead of importing unrelated duplicates.
3. Enable state — check clip/layer visibility, mute/solo, locks, bypassed effects, node connections and render range.
4. Playback load — try proxy media or a lighter preview setting for heavy sources/effects; final export still uses originals.
5. Runtime requirements — confirm Vulkan-capable driver, packaged media/color runtimes, optional AI model state, and available encoder capability where relevant.
6. Persistence — save, close/reopen a copy, and check whether the problem is project state or transient UI state.
7. Export — reproduce on a short range and inspect the actual generated file/log.

Performance problems

Generate proxies for difficult camera media rather than changing the project timeline resolution merely to make playback easier. For expensive VFX/volumes, lower preview/simulation quality during iteration and raise final settings after timing is approved.

Reporting a reproducible issue

Include Oraphim version/build, exact steps, project dimensions/frame rate, source format, affected workspace, hardware/driver, error text/log, and whether the issue appears in preview, saved/reopened state, final export, or all three. A tiny reproducible project is usually more useful than a screenshot of a large broken project.