Add to your phone
Install this dashboard for one-tap access.
Install this dashboard for one-tap access.
Restricted to authorised Iziko / UWC operators. Enter your email to get a one-time code.
Each fleet reboot: how long every player took to come back online. Newest first.
Every audio start/stop the Q-SYS master fired: how many buses started and whether all of them did. Use it to spot a reboot where audio didn't fully come up.
Any Q-SYS component the master Lua's WATCHERS list is configured to poll (projector power, source-switch position, audio mute, etc) — logged on every state change. Newest first.
Entries from the Q-SYS Core's Event Log (component errors, network, design load), pushed live.
Logs auto-trim to the last 5 days. Download all + purge saves the full current log as a
.txt then deletes anything older than 5 days. Purge Q-SYS stale clears a frozen Live Q-SYS
digest and asks the Wall to push a fresh one (re-sync) — use it when the Live Q-SYS tab shows stale data.
What each player is showing (low-res, pushed every few minutes). Not real-time.
The show starts and stops on the Q-SYS Core itself, not from here.
ON is fired by startup_timer.lua and OFF by
shutdown_timer.lua, both running on the Core with a
bridge-synced clock. They need nothing outside the Core — no laptop, no
network, no dashboard.
Remote Play/Stop and the web schedule were removed deliberately. That path
ran dashboard → cloud → on-site app → bridge → Core, polled only every 30 s
when nobody was watching, and did nothing at all when the on-site PC was
asleep. It failed silently more than once. To change show times, edit
StartTime / StopTime on the timer components in
Q-SYS Designer.
Version …. The Wall self-updates; this is for a fresh install.
Load the show's video frames + audio stems, play them on one master clock, and read the exact %, milliseconds and frame at the playhead so you can confirm A/V sync on-site. Files are saved to the cloud (shared across operator devices). Green = video, blue = audio.
Pick a video file — the browser isolates its audio to a .wav, adds it as a synced audio track (with the video as a reference frame), and downloads the .wav so you can import it into Q-SYS later. Runs entirely in your browser; nothing uploads until you press “Upload all”. Best with MP4 (H.264/AAC) or WebM.
“Upload all” pushes every loaded file + the layout to the cloud. Other operator devices then “Load from cloud”. Keep individual files under ~90 MB (Worker upload limit) — use the compressed show clips, not masters.
Pull the current CLOUD set back out as a ZIP, each file named by its slot
(e.g. a6__H1.mp3, v1__Frame_1.mp4) plus a MANIFEST.txt slot→label→file map —
so someone on-site can re-load the right content onto the right zone. Large video sets zip in memory;
if a package stalls, use the per-row ⤓ to grab files one at a time.
Desktop app for operators: batch-convert WAV stems to MP3 (128–320 kbps) on the PC before uploading them here. Runs locally — nothing leaves the machine. MP3 is lossy: keep the original WAVs if they're your reprovisioning masters. First run shows a Windows SmartScreen warning (unsigned) → More info → Run anyway.
🔒 Operator-only — this page is OTP-gated; do not share. Auto-login is ON (boots straight to the Iziko desktop), and a daily reboot scheduler loads the Q-SYS design before showtime. Remote in via the CRD session below.
Chrome Remote Desktop is already configured on the museum PC. Clicking Open remote desktop below launches the CRD session in a new tab (CRD blocks iframe embedding, so it can't render inside this page). Bookmark the link in your browser once the session URL is saved.
If you're inside the museum LAN (or on a VPN to it), the Wall serves the same UI it shows on the operator's screen — see the players' live thumbnails directly. Outside the LAN this won't load (the Wall doesn't expose a public address; that's intentional).
A live read of the Q-SYS Core (sync lock, show state, schedule, audio). Pushed from the on-site Wall over QRC — read-only, it cannot change the show. Goes stale if the Wall is off or the Core is unreachable.
How the installation fits together — network map, what code runs on which machine, the end-to-end show-start path, and how each piece of software reaches its target. Drawn 2026-08-22 from the working tree.
Complete technical reference for the team taking over the install — architecture,
network map, Q-SYS wiring + verified control pins, BrightAuthor presentation design, roSync + audio-sync
setup, daily operation, deploy/re-inject, and the full field-troubleshooting runbook. Consolidated from
the repo README.md (snapshot 2026-06-02).
Download technical handover (PDF)
Step-by-step guide to building (or rebuilding) the 6 BrightSign presentations
in the no-reboot, Core-direct model — states, roSync (domain 6, Leader/Follower), UDP destination
+ control inputs, S0/L0 markers, the SYNC:<id> heartbeat, publishing Standalone,
a pre-ship audit, and the traps to avoid.