Outputs
Video, sound and control data sent out of the graph, to lighting rigs, other apps, hardware and the network.
Drop an output node anywhere in the graph, wire a value into it, and that value streams out every frame while the graph runs. Most live setups use both directions at once: a controller comes in, a processed look or control data goes out.
Unlike most of the control inputs, output nodes open their own connections, so what follows is what actually leaves the machine.
Control-data outputs
These send numbers and messages to other gear and software.
MIDI Output (MIDI Output): one CC or note per node, to instruments, synths, lighting desks and DAWs.
valueis 0 to 1 and is scaled to the 0 to 127 wire value for you, so feeding it a raw 127 sends 127 as full scale. Itsdevicedropdown lists the ports your machine actually has, by name, rescanned every few seconds so a synth plugged in mid-session appears; the default0means no port is chosen and nothing is sent. Picking by name rather than by position means unplugging one device does not silently retarget the node at another.OSC Output (OSC Output): one address to one host and port, sending a float, an int, a vec2, a vec3 or a colour. It sends numbers and vectors; there is no string send.
DMX Output: lighting fixtures and LED installations.
protocolpicks ArtNet or sACN, and a full 512-slot universe is framed and sent either way. Feedchannelsan array, or set the first six channels individually.WebSocket Output: values pushed to a web page, a browser dashboard, or any service that speaks WebSocket. It takes the widest range of values, including a number array. Set
modetoclientand give it aurl: the defaultservermode reportsWebSocket server not runningand sends nothing, because the built-in server is never started.MQTT Publish: values published to an MQTT topic.
sendis off by default, so nothing leaves the node until you turn it on.
Serial has no output node of its own. The bidirectional Serial node writes back to the port through its send parameter.
MIDI, OSC, DMX and WebSocket all carry a send_on_change parameter, on by default, which suppresses a resend when the value has not moved. MQTT Publish has no such control.
Video outputs
NDI Output (NDI Output) streams video over your network to any NDI-capable app: other creative tools, switchers, capture software. Other machines see it under whatever you set as source_name. It runs on macOS, Windows and Linux wherever the NDI runtime is installed, at 1 to 2 frames of latency locally.
Syphon Output (Syphon Output) shares frames GPU-to-GPU with another app on the same Mac, at under a frame of latency, which suits feeding a VJ app or compositor running alongside. macOS only: on any other platform the node reports that and does nothing.
Wire an image-producing branch of the graph into one of these to publish it live. Neither publishes anything with its image pin unwired.
Audio output
Audio Output (Audio Output) is the terminal node for an audio chain. Wire a signal into left, and right as well for stereo, and the samples are written to the output device. Leaving right unconnected duplicates left for mono. It carries volume and mute, both applied at the device rather than in the graph, so they respond immediately, and it reports the current RMS level and the device's actual sample rate for upstream nodes to match. The chain that feeds it is covered in Audio.
To bake a finished mix to a file instead of playing it live, see Exporting.
Some output paths are platform- or build-specific. Syphon is macOS only. NDI and DMX rely on your network being set up to carry them. In a web export the output nodes still exist in the graph but every one of them degrades to a pass-through, so nothing is sent.