How to use Oscillator node in Oraphim

Type ID: motion.signal.oscillator
Category: Time

What this node does

The Oscillator 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 Value, Phase. 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
Phase	out_phase	Float

Controls

Control	Key	Type	Group	Registry default
Waveform	waveform	String	Signal	Sine
Frequency	frequency	Float	Signal	1.0
Amplitude	amplitude	Float	Signal	1.0
Offset	offset	Float	Signal	0.0
Phase Cycles	phase	Float	Signal	0.0
Square Duty	duty	Float	Signal	0.5

How to use it

1. Add Oscillator from node search. Use motion.signal.oscillator 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 Waveform, Frequency, Amplitude 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 Oscillator. Feed a compatible source into Time. Change Waveform 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

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

Return to the complete Oraphim node reference.