Shape Nodes (Vector Graphics)

In Oraphim, shapes are vector-based graphics. Because they are mathematically drawn rather than pixel-based (like a photograph), you can scale them infinitely without losing quality or experiencing pixelation.

The Shape Node Pipeline

Shape nodes operate slightly differently than standard image nodes. In the node graph, shape tools are prefixed with an "s" (e.g., sRectangle, sEllipse, sPolygon).

When you connect shape nodes together, they do not require standard Merge nodes. They have their own dedicated sMerge node.

1. Add an sRectangle node.
2. Add an sEllipse node.
3. Pipe both of them into an sMerge node.
4. At this stage, the data is pure mathematical vector data. You cannot pipe it into a standard ColorCorrector or MediaOut yet.
5. To convert the vector shapes into actual visible pixels, you must pipe the output of the sMerge into an sRender node.
6. The sRender node rasterizes the vectors into pixels, allowing you to pipe the result into a standard Merge or MediaOut.

Shape Properties

When you click on an sRectangle or sEllipse and look at the Inspector, you have profound control over its appearance:

• Border Width: Increase this to draw an outline instead of a solid shape.
• Join Style: Determines if the corners of your outline are sharp, rounded, or beveled.
• Solid Color / Gradient: You can fill the shape with a solid color, or switch the mode to Gradient (Linear or Radial) to create dynamic shading.

Boolean Operations

The sMerge node is highly powerful because it supports Boolean operations.

If you have a large circle, and you want to punch a smaller star-shaped hole out of the center of it:

1. Connect the Circle to the background input of the sMerge.
2. Connect the Star to the foreground input of the sMerge.
3. In the Inspector for the sMerge, change the Operator from Over to Subtract.
4. The Star will act as a cookie-cutter, carving a hole through the Circle.

Use Shapes 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 Shapes 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

Shape layers are resolution-independent design elements. Keep path construction simple, use fill/stroke deliberately, and animate transforms or path properties only when the motion supports the design.

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