StudioEnsemble is a family of accessible, open control surfaces for the tools of a production — cameras, lights, meters, and (coming) audio. This is the family's orientation: what makes these separate programs one coherent family rather than a bag of apps.
Every StudioEnsemble product follows the same shape:
- It is a headless daemon exposing a control plane — a WebSocket API — and an accessible, screen-reader-first web UI that is just another client of that API, never a privileged back channel.
- It is brand-generic (it controls a class of device, not one vendor's), scriptable, and first-class on macOS, Linux, and Raspberry Pi.
- It speaks the shared contract, so the family interoperates at runtime — see CommonTongue below.
A new program belongs to the family when it implements that shape.
Each product stands on its own. Above them sits one more surface that speaks every product's control plane through the same interface, conducting them together as a single ensemble rather than a drawer of separate apps. Its shape is still open.
StudioEnsemble defines no standards of its own. It conforms to the shared substrate published by CommonPractices and incorporates it by reference:
- CommonMind — the principles (the why and the rules).
- CommonFraming — the shapes (how to build a recurring kind of thing; a hardware-controller service is one of them).
- CommonTongue — the contracts (the versioned wire language every product speaks).
Per the Single-Source-of-Truth Doctrine, each of those has exactly one home; this overview points at them and never restates them.
- Accessibility — first-class, not a retrofit. A control a screen reader or a script can't use is not done.
- Ease of use — for the primary flow; depth kept behind an Advanced reveal.
- Speed — especially controlled hardware settings changes.
- Choice — prosumer. Options, not one opinionated path.
A simple way in for the individual just getting into photography or video, an open API for the hacker who wants to control and automate, one console for the small studio, and a full ensemble for the growing production — the same system, met at the layer you need.
A new product implements the shared shape (control plane + accessible web UI), speaks the CommonTongue contract, and conforms to the North Stars and the CommonPractices doctrine. That is membership.