Templates

Use templates inside a composition, where layers, timing, the viewer, the Inspector, and procedural processing remain connected.

Workflow

1. Open or create a composition that matches the intended delivery.
2. Add and name the required layers or nodes.
3. Select the item you want to edit and expose its controls in the Inspector.
4. Set the static appearance before adding keyframes or procedural behavior.
5. Preview the complete duration and inspect important frames closely.
6. Reuse the composition in Edit or render a review.

Example

Build one clear visual result with the feature—such as an animated title, a masked treatment, or a reusable graphic—before combining it with other effects.

Verify the result

Confirm layer order, timing, transparency, motion, and viewer output. Save, reopen, and check that the setup persists.

Use Templates in a production project

1. Open Composition workspace and select the intended text, shape, layer, animation property, or procedural system.
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 Templates 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

Templates accelerate common designs while keeping underlying controls editable. Replace text/media, adapt timing, and check fonts, safe areas, and brand colors before delivery.

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

• Preview the full animation and compare the rendered output with the interactive viewer.
• 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.

Related guides

• Animation and Keyframes
• Dissolve
• Fire
• Motion Graphics Overview