Device Connectivity
PRISM runs on any device. Each console runs its own lightweight server that handles DMX output, and your other devices connect to it as clients.
Running the Server
The server is bundled with the app — installing PRISM is all there is to it. When you open the app, it starts the server for you (or connects to one that is already running), so you never have to start a server manually.
- The server keeps running if you close the app — a live rig is never cut dark by an app quit. It restarts automatically if it ever crashes.
- To stop it, use Shut down server at the bottom of the Connectivity window. Only do this when the rig is not needed.
- On a dedicated rig machine (for example a Raspberry Pi), the server can also run standalone without the app.
Reliability metrics
To help find reliability problems, the app can send a small metrics file to PRISM’s servers about every 6 hours: the app version and a set of counters (boots, cues saved, GOs run, DMX tick health, RPC errors, crash counts). It never includes show data, fixture names, or file names. Your IP address is recorded at the server for rate-limiting abuse and is never displayed; the dashboard shows OS-level aggregates only.
The switch is Connectivity → Reliability metrics. It is on by default in the beta; turn it off at any time and nothing is sent.
Connecting a Device
On the Same Machine
If the PRISM app runs on the same machine as the server, it connects automatically — no pairing, no codes.
On the Network (Pairing)
- Open the Connectivity window on the client and enter the server’s address.
- The server presents a short pairing code.
- The operator of the primary console approves the pairing.
- The client remembers the connection — after the first pairing it reconnects automatically.
Not Yet Available
- mDNS/Bonjour auto-discovery — the client can scan for PRISM consoles, but the server does not advertise itself yet, so enter the address manually.
- Cloud discovery / relay — finding and reaching a console across networks is not implemented.
Completely Offline (Export/Import)
For completely isolated consoles, program on a network-connected instance, export the show file to a single file (in the Show Files window), move the file (USB drive or local transfer), and import it onto the offline console. Importing replaces the console’s current show; a snapshot of the previous show is saved first so you can import it back if needed.
Supported Devices
| Device | Role |
|---|---|
| iPad | Full programming surface |
| Android tablet | Programming or operation |
| Phone | Playback and master control |
| Laptop/Desktop | Design workstation with multiple windows |
Device Layouts
The UI adapts to each device:
- Phone — Single-column layout focused on playback status and master control
- Tablet — Split layouts pairing the programming surface with playback or pools
- Desktop — Multi-window workspace with all tools visible simultaneously