02 · I/O connect
From Default, make the first intentional I/O choices: confirm the browser UI path, optionally add OSC/HTTP or lights, then move on to Action Deck in step 03.
Before you start
- Step 01 done — Overview healthy at http://localhost:7474 with Default (or Blue Lamp — Theater Show if you already loaded it).
- Reference: I/O. Holiday detail: Holiday lighting I/O.
Steps
- Open I/O.
- Confirm the UI control path is online — the browser session is your first surface. You do not need a second protocol to continue.
- Optional: Add OSC or HTTP if an external desk or script will fire cues later. Skip if you are only using the browser.
- Optional lights: When the room needs them, connect Twinkly and WLED together as realtime RGB(W) endpoints.
- Always name both.
- Drive RGB(W) from the show graph — cues you own, not a consumer FX catalog browser.
- Confirm they appear on Overview’s I/O strip when online.
- Optional show-protocol consumers: Art-Net / sACN if Falcon Player or xLights will consume the show. Details on the holiday lighting page.
- Optional custom bridge: Need Light-O-Rama or another controller without a native endpoint? Use Plugin Builder (AI → Plugin Builder) later — not required for this step.
- Leave I/O when the UI path is confirmed (and any optional paths you care about are intentional). Next: build or load Action Deck.
What you can connect here
| Capability | Path |
|---|---|
| Twinkly + WLED as realtime RGB(W) endpoints | Always name both; configure under I/O |
| Falcon Player / xLights | Art-Net + sACN from the same show timing |
| Custom controller bridge (e.g. Light-O-Rama) | Plugin Builder when you need it |