Node reference
How to use Blend Transforms node in Oraphim
Use the Blend Transforms node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.transform.blend.
Updated August 28, 2026How to use Blend Transforms node in Oraphim
Type ID: motion.transform.blend
Category: Transform
What this node does
The Blend Transforms node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.
The current Oraphim runtime registers 6 sockets and 2 properties for this node. Its main registered inputs are A, B, Factor; its main outputs are Transform, Factor, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| A | in_a |
Matrix |
| B | in_b |
Matrix |
| Factor | in_factor |
Float |
Outputs
| Socket | Key | Type |
|---|---|---|
| Transform | out_matrix |
Matrix |
| Factor | out_factor |
Float |
| Valid | out_valid |
Bool |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Factor | factor |
Float |
Blend | 0.5 |
| Mode | mode |
String |
Blend | TRS |
How to use it
- Add Blend Transforms from node search. Use
motion.transform.blendwhen you need the exact registry entry. - Connect a compatible
Matrixsource to A. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Factor, Mode first so you can see the node's effect in isolation.
- Route Transform (
Matrix) into a compatible downstream node, viewer, or output path. - 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 Blend Transforms. Feed a compatible source into A. Change Factor away from its registry default and compare the result. Connect Transform 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.
Related nodes
- Look At Transform —
motion.transform.look_at - Convert Transform Space —
motion.transform.space_convert - Layer Transform Animator —
motion.transform.layer - Compose Matrix —
motion.matrix.compose - Matrix Math —
motion.matrix.math
Return to the complete Oraphim node reference.