One Svelte 5 codebase driving three Crestron front-ends — tabletop TS-1070, wall TSW-1070, and browser WebXPanel — for a fully commissioned MCCCD classroom.
Note: This is the public overview of a private project. The implementation lives in a private repository (it targets a live MCCCD classroom deployment). Reach out if you'd like to talk shop.
Classroom AV control is usually built as one panel, one UI, one form factor. A real deployment needs the same room controllable from a tabletop panel, a wall panel, and a browser (for remote support and testing) — and displays, audio, cameras, USB switching, projector screens, and system power all need to behave like one coherent system, not five disconnected device drivers someone has to remember to keep in sync.
The system splits into two halves that talk over a Crestron Contract signal bus — a named set of commands and feedbacks, so the panel and the processor never need to know about each other's internals:
- Panel UI — Svelte 5 + TypeScript, compiled to a CH5 (Crestron HTML5) archive, deployed identically to the TS-1070 tabletop panel, the TSW-1070 wall panel, and a WebXPanel in the browser. Same UI, same interactions, three physical surfaces.
- Processor backend — a SIMPL# Pro (C#) program on a Crestron RMC4, structured as one service per device domain: display routing, USB switching, projector screen relays (pulse-to-limit with interlock), and system power sequencing with source restore on power-up.
- Audio — a 7-microphone Shure chain (DSP plus ceiling mic arrays) feeding program audio and automatic mixing.
- Cameras — PTZ camera control wired into a Q&A-mode decision engine: mic gate activity from the Shure array automatically steers presenter/group camera framing, commissioned and verified on-site against live audio.
- Role-gated UI — the panel boots in a plain User mode; a hidden unlock reveals a Technician mode with per-channel audio trims, camera PTZ/zone controls, and advanced routing, auto-reverting after a few minutes idle.
The panel/processor split is deliberate: the panel only ever publishes commands and subscribes to feedbacks over the named contract, so either side can be rebuilt without the other caring. Live camera video is rendered through a native CH5 video element rather than a plugin. The backend is a modern, SDK-style .NET project (no IDE bootstrap required to build), with each device family — DSP, cameras, USB matrix, screens, displays — owning its own service class rather than one monolithic control loop.
Field-commissioned: version 0.14.x, frontend and backend both deployed and
running on the tabletop and wall panels in the room. The 7-mic Shure audio
chain is live, and Q&A-mode camera automation has been commissioned and
verified on-site.
AV systems integration & automation — @jscales4000 · jordan.automateit@gmail.com