How to use Time Remap node in Oraphim

Type ID: motion.time.remap
Category: Time

What this node does

The Time Remap 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 3 sockets and 6 properties for this node. Its main registered inputs are Time; its main outputs are Time, Progress. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Time	in_time	Float

Outputs

Socket	Key	Type
Time	out_time	Float
Progress	out_progress	Float

Controls

Control	Key	Type	Group	Registry default
Input Start	inputStart	Float	Input	0.0
Input End	inputEnd	Float	Input	1.0
Output Start	outputStart	Float	Output	0.0
Output End	outputEnd	Float	Output	1.0
Easing	easing	String	Output	Linear
Clamp	clamp	Bool	Output	1.0

How to use it

1. Add Time Remap from node search. Use motion.time.remap when you need the exact registry entry.
2. Connect a compatible Float source to Time. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Input Start, Input End, Output Start first so you can see the node's effect in isolation.
4. Route Time (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 Time Remap. Feed a compatible source into Time. Change Input Start away from its registry default and compare the result. Connect Time 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

• Loop Time — motion.time.loop
• ADSR Envelope — motion.signal.envelope
• Frame Driver — motion.input.frame
• Interpolate — motion.animate.interpolate
• Oscillator — motion.signal.oscillator

Return to the complete Oraphim node reference.