Multi-User Sessions
Multiple consoles can work on the same show at once. Each connected console is a station; stations form a session with one master. The Station window is where sessions are managed.
How It Works
- One console becomes the session master (Station window → Become Master).
- Other consoles join the session (Station window → Join as Standby, entering the master’s address). On join, the member’s own show is auto-saved, and the member’s show data is replaced by the master’s show so everyone starts from the same state.
- The master controls who can write. Members join read-only by default; the master grants or revokes write access per member from the session roster.
- Failover: a standby keeps the master’s live output ready to send. If the master goes silent, the standby can take over output so the show does not drop.
Station States
| State | Meaning |
|---|---|
| Standalone | Not part of any session; runs the local show only |
| Idle Master | Pointed at a session; promotes automatically if the master is lost |
| Global Master | The authoritative session master |
| Session Master | Owns session creation and coordination |
| Replay | Joined the session; runs local DMX for its own universes |
What Members See
- The session roster: every station in the session with its state.
- Live membership and liveness updates from the master.
- The shared show data (synced from the master on join).
Per-user workspaces, view-only user roles, and per-user fixture restrictions are not available in the current release — access control is per-station (read-only or write), granted by the master.
Related Documentation
- Device Connectivity — connecting each station
- System Overview