Oraphim LogoOraphim
Beta soon

Reference

Panels

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

Updated August 28, 2026

Panels

This reference describes panels in the current Oraphim Windows beta.

Visual reference

Oraphim Inspector panel

Panel reference is most useful when paired with the selected object or clip that gives that panel its current context.

How to use this reference

Locate the named control in the relevant workspace, select the object it acts on, and compare the viewer or timeline before and after changing it. Controls can be context-sensitive, so an empty panel usually means the required clip, layer, node, track, or resource is not selected.

Verification

Test the behavior in a short project, save and reopen it, and inspect a rendered result when the feature affects delivery.

Use Panels in a production project

  1. Open relevant Oraphim workspace and select the intended object, resource, or command described here.
  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 Panels 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

Panels are selection- and workspace-sensitive. When a panel looks empty, first confirm the active project resource and selection rather than resetting the layout immediately.

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

  • Test the behavior in a disposable project before depending on it for production.
  • 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.