Node reference

How to use Interpolate node in Oraphim

Use the Interpolate node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.animate.interpolate.

Updated August 28, 2026

How to use Interpolate node in Oraphim

Type ID: motion.animate.interpolate
Category: Time

What this node does

The Interpolate node is registered in Oraphim's Time category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 2 sockets and 6 properties for this node. Its main registered inputs are Value; its main outputs are Value. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Value in_value Float

Outputs

Socket Key Type
Value out_value Float

Controls

Control Key Type Group Registry default
Input Min inputMin Float Input 0.0
Input Max inputMax Float Input 1.0
Output Min outputMin Float Output 0.0
Output Max outputMax Float Output 1.0
Easing easing String Output 0.0
Clamp clamp Bool Output 1.0

How to use it

  1. Add Interpolate from node search. Use motion.animate.interpolate when you need the exact registry entry.
  2. Connect a compatible Float source to Value. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Input Min, Input Max, Output Min first so you can see the node's effect in isolation.
  4. Route Value (Float) into a compatible downstream node, viewer, or output path.
  5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Interpolate. Feed a compatible source into Value. Change Input Min away from its registry default and compare the result. Connect Value to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

  • If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
  • If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
  • If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
  • If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Return to the complete Oraphim node reference.