How to use Pulse Event node in Oraphim

Type ID: motion.event.pulse
Category: Time

What this node does

The Pulse Event 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 4 properties for this node. Its main registered inputs are Time; its main outputs are Active, Pulse, Index. 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
Active	out_active	Bool
Pulse	out_pulse	Float
Index	out_index	Int

Controls

Control	Key	Type	Group	Registry default
Interval	interval	Float	Pulse	1.0
Duration	duration	Float	Pulse	0.10000000149011612
Phase	phase	Float	Pulse	0.0
Enabled	enabled	Bool	Pulse	1.0

How to use it

1. Add Pulse Event from node search. Use motion.event.pulse 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 Interval, Duration, Phase first so you can see the node's effect in isolation.
4. Route Active (Bool) 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 Pulse Event. Feed a compatible source into Time. Change Interval away from its registry default and compare the result. Connect Active 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

• ADSR Envelope — motion.signal.envelope
• Frame Driver — motion.input.frame
• Loop Time — motion.time.loop
• Spring Animator — motion.animate.spring
• Stagger — motion.animate.stagger

Return to the complete Oraphim node reference.