Integrations

NDI & Syphon

R3NE is built to live next to other show software. Pick the protocol that matches how the rest of your rig talks: Syphon for everything on the same Mac, NDI when it has to cross the network.

When to use Syphon

  • Receiver runs on the same Mac (Resolume, MadMapper, OBS with the Syphon plugin, TouchDesigner via TDSyphon).
  • Zero-copy GPU handoff, there is no encoder in the path, so latency stays sub-frame.
  • Lossless: the receiver gets the exact texture the graph produced.

When to use NDI

  • Receiver runs on another machine, or on Windows.
  • You need to feed several receivers from the same source over a gigabit-class network.
  • You can tolerate compression and ~1 frame of network latency.

Enabling an output

The fastest way is the Render menu — it streams the final composite (whatever feeds the Root) directly:

  1. Toggle Syphon Output (⌘⌥1) or NDI Output (⌘⌥2).
  2. Set the Syphon Server Name / NDI Source Name from the same menu — that’s what shows up in the receiver’s picker.

Alternatively, add a Syphon Output or NDI Output node and wire a texture into it — useful when you want to publish a specific branch of the graph rather than the full composite.

The stream resolution follows the source texture (the project resolution for the composite); set it in Project Settings (⌘⇧,), or upstream with a Render To Texture node for a fixed size.

Common pairings

ReceiverRecommended protocolNotes
Resolume ArenaSyphonPick the R3NE server in the source list.
MadMapperSyphonNative receiver, no plugin needed.
OBS (macOS)SyphonInstall the obs-syphon plugin first.
OBS (Windows)NDIUse the obs-ndi plugin.
TouchDesignerEitherSyphon In TOP for local, NDI In TOP for cross-machine.