NDI Output
Send video over the network with NDI.
What it does
NDI Output sends the image wired into it out over the network using the NDI protocol, for other machines and apps on the same network to receive as a live video source: vision mixers, other DNA sessions, playback software. With Image disconnected it captures the canvas itself.
Source Name is the name receivers see when they browse for NDI sources on the network. Enabled switches the feed on and off without deleting the node or its connections.
When to use it
A live feed sent from DNA to another machine or app over the network: a vision mixer, a media server, another NDI-capable tool
The canvas itself broadcast live, with no separate output pass, by leaving Image disconnected
A network feed toggled on and off during a show without tearing down the graph
| Parameter | Type | Default |
|---|---|---|
image | Any | — |
source_name | String | "NodeTool" |
enabled | Boolean | true |
strength | Number | 1 |
Gotchas
NDI requires the NDI Tools runtime on the machine. Without it the sender does not reach receivers.
Sending over NDI brings the image back from the GPU to the CPU before it goes out, which is slower than a GPU-to-GPU output. Expect NDI Output to cost more per frame than a same-machine sink.
Worked example
Add an NDI Output node.
Set Source Name to something recognisable. This is what shows up when a receiving app browses for NDI sources on the network.
Wire an image into Image, or leave it disconnected to send the canvas as-is.
Open your NDI-receiving app on another machine on the same network and pick your source by name.
Use Enabled to pause or resume the feed without disconnecting anything.
See also
Syphon Output · NDI Input · WebSocket Output · Rasters (images)