How to use ADSR Envelope node in Oraphim

Type ID: motion.signal.envelope
Category: Time

What this node does

The ADSR Envelope 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 4 sockets and 6 properties for this node. Its main registered inputs are Time; its main outputs are Value, Stage, Active. 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
Value	out_value	Float
Stage	out_stage	String
Active	out_active	Bool

Controls

Control	Key	Type	Group	Registry default
Gate Start	gateStart	Float	Gate	0.0
Gate Duration	gateDuration	Float	Gate	1.0
Attack	attack	Float	Envelope	0.10000000149011612
Decay	decay	Float	Envelope	0.20000000298023224
Sustain	sustain	Float	Envelope	0.699999988079071
Release	release	Float	Envelope	0.30000001192092896

How to use it

1. Add ADSR Envelope from node search. Use motion.signal.envelope 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 Gate Start, Gate Duration, Attack 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 ADSR Envelope. Feed a compatible source into Time. Change Gate Start 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

• Oscillator — motion.signal.oscillator
• Pulse Event — motion.event.pulse
• Frame Driver — motion.input.frame
• Interpolate — motion.animate.interpolate
• Loop Time — motion.time.loop

Return to the complete Oraphim node reference.