How to use Map Range node in Oraphim

Type ID: motion.value.map_range
Category: Utility

What this node does

The Map Range 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 9 sockets and 7 properties for this node. Its main registered inputs are Value, Input Minimum, Input Maximum; its main outputs are Value, Factor, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Value	in_value	Float
Input Minimum	in_input_min	Float
Input Maximum	in_input_max	Float
Output Minimum	in_output_min	Float
Output Maximum	in_output_max	Float
Clamp Factor	in_clamp	Bool

Outputs

Socket	Key	Type
Value	out_value	Float
Factor	out_factor	Float
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Value	value	Float	Defaults	0.0
Input Minimum	inputMin	Float	Input	0.0
Input Maximum	inputMax	Float	Input	1.0
Output Minimum	outputMin	Float	Output	0.0
Output Maximum	outputMax	Float	Output	1.0
Interpolation	interpolation	String	Output	Linear
Clamp Factor	clamp	Bool	Output	1.0

How to use it

1. Add Map Range from node search. Use motion.value.map_range 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, Input Minimum, Input 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 Map Range. 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

• Clamp — motion.value.clamp
• Curve Map — motion.value.curve
• Math — motion.value.math
• Quantize — motion.value.quantize
• Smoothstep — motion.value.smoothstep

Return to the complete Oraphim node reference.