NDI out,
NDI in

What it is for

A cue list whose pictures go out over the network instead of down a cable: into a vision mixer, a streaming PC, a recorder, an LED processor with an NDI input, or another machine running Deckboy. And the other way round: somebody else's NDI source — a camera, a graphics machine, a laptop on stage — taken as a cue and played like a clip.

Send

1. Install NDI Tools on the machine. It is free, from the people who make NDI, and it carries the runtime Deckboy loads. Without it Deckboy says NDI is unavailable rather than failing quietly.
2. Add an output and turn on NDI. It appears on the network as an NDI source, and it can send a separate key source for the alpha.
3. Take cues as usual. Every output keeps its own settings, and each output can show a different deck, so one machine can send several different pictures as several NDI sources.

Receive

SOURCE → NDI Source Cue puts an NDI source in the cue list. It fades, holds and takes effects like any other cue, and it can be the inset of a picture-in-picture cue over whatever else is live.

Alongside everything else

At the same time as NDI	What that means
A fullscreen output, SRT, RTMP, Blackmagic SDI or SMPTE ST 2110	The same programme can leave by several routes at once.
A recording	What went out is what gets kept.
NDI-metadata triggers, TSL tally, ATEM	A switcher can tell Deckboy what is on air; the NDI trigger works even without the runtime.
Stream Deck, Companion, OSC, MIDI, timecode	The desk drives it; see Stream Deck and Companion.

Platforms

NDI input and output are in every published build for Windows, macOS and Linux. --self-check prints ndi-sdk: headers detected when NDI is in the build, so it is one command to be sure.

The manual: outputs, sources and running Deckboy