How to use Clamp node in Oraphim

Type ID: motion.value.clamp
Category: Utility

What this node does

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

The current Oraphim runtime registers 5 sockets and 3 properties for this node. Its main registered inputs are Value, Minimum, Maximum; its main outputs are Value, Was Clamped. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Value	in_value	Float
Minimum	in_min	Float
Maximum	in_max	Float

Outputs

Socket	Key	Type
Value	out_value	Float
Was Clamped	out_was_clamped	Bool

Controls

Control	Key	Type	Group	Registry default
Value	value	Float	Defaults	0.0
Minimum	minimum	Float	Range	0.0
Maximum	maximum	Float	Range	1.0

How to use it

1. Add Clamp from node search. Use motion.value.clamp 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 Value, Minimum, Maximum 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 Clamp. Feed a compatible source into Value. Change Value 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.

Related nodes

• Curve Map — motion.value.curve
• Map Range — motion.value.map_range
• Math — motion.value.math
• Quantize — motion.value.quantize
• Smoothstep — motion.value.smoothstep

Return to the complete Oraphim node reference.