I/O
I/O is where the show graph meets the room. Connect control paths first, then audio sinks and lighting endpoints.
Control paths
BPShowServer speaks the same show graph from multiple surfaces:
- UI — browser console (always on)
- OSC — fire and feedback from desks and tools that speak OSC
- HTTP — cue and status over simple requests
- MCP — assistants and agents on the same graph (API / MCP overview; configure under AI → MCP)
- CLI — scripts and headless boxes
You do not pick one forever. Mix them. Overview and Control stay coherent either way.
Add Endpoint (providers)
Use I/O → Add Endpoint when you need provider endpoints on the show graph, including:
- Voice LLM (
voice-llm) — enable Voice LLM for intercom / Assistant - ElevenLabs — API key for SFX Generation (see AI and Control)
MCP (short)
- Prefer on-prem MCP via AI → MCP (
/mcp, title MCP Server) for first-timers and demos. - Already operate a Cloud-capable ShowServer? Cloud MCP uses the same field family — see API / MCP overview.
- Thin detail: API / MCP overview · guided: Getting Started · 06.
Network audio sinks
AES67 / ST2110 / Sonos / garden speaker / console·Q-SYS sinks let a headless or Pi-class box put cartwall SFX and program on a network audio device without a local sound card ritual.
| Fact | Detail |
|---|---|
| Differentiator | Network sinks via GET /api/v1/audio/sinks — not a local sound-card ritual |
| Where they appear | I/O → Devices / Integrations endpoints; also the sinks API |
| Bind for spatial | Control → Audio → Spatial Layouts → Add Speaker → Audio Output → Select output… (not a separate System sink editor) |
| Local Pulse | Demo-box validation only — do not lead production docs with it |
| AES67 | Strong example — not the only network audio device story |
| Guided path | Getting Started · 04 · Overview cartwall SFX → network audio device |
| Spatial wow | After 04, treat sinks as speakers and move the bed (Getting Started · 05) |
Holiday & seasonal lighting endpoints
Twinkly and WLED are first-class realtime RGB(W) endpoints on the show graph.
- Named together — WLED is always listed with Twinkly.
- Drive RGB(W) from cues, automation, Action Deck, and OSC / HTTP / MCP / CLI.
- Falcon Player / xLights consume the same show timing over Art-Net / sACN.
- Need a custom bridge (for example Light-O-Rama)? Use Plugin Builder.
Connect order and detail: Holiday lighting I/O.
Seasonal lighting is a peer Use Cases lane.
Connect order that works
- Confirm UI session on Overview.
- Add OSC or HTTP if an external surface will fire cues.
- Confirm network audio devices under I/O → Devices / Integrations (and/or
GET /api/v1/audio/sinks) if the room sink is on the network. - Add Twinkly + WLED (or Art-Net/sACN universes) when the room needs RGB(W) endpoints.
- Move to Control and bind tiles on Action Deck (and Spatial Layouts speakers when doing 05).
- Optional: AI → MCP for on-prem assistants; Cloud MCP only if you already operate Cloud-capable ShowServer.
- Optional: AI → Plugin Builder when you need a custom controller bridge.