Render model concepts

Oraphim combines layered composition state with node/effect processing. The important production principle is non-destructive authorship: keep source media and authored parameters intact, let operations evaluate in order, and verify the final result rather than assuming the viewer represents every delivery condition.

Evaluation order matters

An effect/node receives the output of upstream processing. Reordering operations can therefore change the image even when every individual setting stays the same. In a layered composition, layer order, blend/matte relationships, masks, effects and 3D relationships also affect the result.

Typed graph data

Oraphim graphs can carry more than flat RGBA pixels. Geometry, scene/3D, particles, splines/paths, fields and volumes can require an appropriate renderer/materialization step before they become final pixels. Connect compatible sockets and use graph validation rather than forcing unrelated data types together.

Preview, caching and final render

Preview paths may use caches or lower-cost settings to keep interaction responsive. Changes to source state, graph parameters, timing, effects, transforms or dependent resources must invalidate the relevant cached result. Heavy particles/volumes/3D should be tested cheaply first, then rendered at final settings after timing is approved.

Precision and clipping

Do not assume an extreme correction can always be mathematically reversed later. Operations that clamp, quantize, key, blur, resample or otherwise discard information can make recovery impossible. Keep technical/color transforms deliberate and avoid needless destructive extremes in the middle of a chain.

Verify

For a complex comp, test the first, middle and last frames, save/reopen, compare preview and final render, and inspect alpha/edges when transparency is part of the deliverable.