One shared show state
Keep the band aligned around what is playing now and what comes next, whether performers join from a native Apple client or a browser.
Local-first performance software
LiveStage Pro keeps songs, setlists, shared cues, and the flow of a performance in sync across Mac, iPhone, iPad, Apple Watch, and the web—shaped by rehearsal, independent review, and real performances.
The Satellites
DABmG
Streetlights hum in time tonight
DAGG
We follow every fading line
BmGDA
Hold on through the neon weather
01 / Overview
Keep the band aligned around what is playing now and what comes next, whether performers join from a native Apple client or a browser.
Search Songs or Setlists beside the live Queue, then add, reorder, remove, or move any waiting Song to Next without hiding transport controls. Concurrent requests are serialized against authoritative state while the current performance continues uninterrupted.
High-contrast Preview makes private inspection unmistakable and puts Add Next or Add to Queue beside the Song. Chart appearance, Display Key, instrument, spelling, and capo remain local to the performer and device.
“Make it go. Make it dependable. Then earn the next layer.”
02 / Design philosophy
The show should not depend on a distant service. Performance data stays close, responsive, and under the band’s control.
Shared playback, Queue, and Performance Key remain authoritative for the Band. Preview, workspace, and Display Key remain personal to each performer and device.
High-frequency actions stay visible, confirm success, and recover cleanly. Large targets, readable charts, and quiet reconnection help musicians keep moving under stage pressure.
An experiment can succeed without becoming a feature. Audio, MIDI, lighting, and automation expand only when real hardware, rehearsals, and performances show that they make the system more dependable.
03 / Development journey
LiveStage Pro is moving from a working prototype toward a trusted show system through small, testable milestones.
Established the core model for bands, songs, members, libraries, and setlists.
Connected Mac and browser clients around authoritative show state, with clear separation between shared performance and private preparation.
Added native performer workspaces, local session discovery, queue and setlist tools, private Preview, and a compact Watch transport companion.
Repeated rehearsals and live shows now drive the design: safer Queue editing, unmistakable Preview, consistent transport controls, adaptable charts, quieter reconnection, and explicit recovery tools.
A production-level review turned the run-up to the October 24 Sovereign Estates Winery Chilifest show into a focused reliability gate. Command recovery, Host authority, asset delivery, Watch intent, client takeover, content discovery, and package replacement now have stronger boundaries and regression coverage; physical rehearsals decide what reaches the stage.
04 / Documentation
A high-level tour of the system, its audience, and the problems it is designed to solve.
Coming soonHow the Mac host, embedded server, native clients, WebClient, and shared models fit together.
Coming soonThe operating model for transport, queue, preview, workspace, and performer roles.
Coming soonPublic documentation will be added as the prototype matures. No private application source is published here.
05 / Current status
LiveStage Pro is in a focused pre-show hardening cycle for the October 24 Sovereign Estates Winery Chilifest gig. The latest production-level review was treated as an opportunity to remove uncertainty from existing workflows—not as an excuse to add another layer of features before the show.
Connection changes now retire pending commands cleanly so an old response cannot strand or disturb the current session. Host and Connected Client authority are enforced more consistently, large assets stream through bounded paths, local-only controls have tighter network boundaries, and shutdown behavior gives audio, MIDI, and the embedded server a defined completion path.
Watch state rejects older snapshots and carries the performer’s explicit Play or Pause intent instead of reinterpreting a toggle later on the phone. When two tabs or devices present the same saved identity, the retired client stays retired until the performer deliberately takes over; ordinary Wi-Fi recovery remains automatic. Physical Safari takeover and basic native reconnection have passed focused checks, while paired Watch and full-network rehearsal remain promotion gates.
Content recovery received the same treatment. Hidden staging and recovery packages no longer appear as installed Songs, Setlists, Members, Bands, or Libraries, and replacing bundled samples preserves the original until the new package is safely installed. Failure paths retain recoverable data and report what happened instead of silently converting cleanup trouble into content loss.
The show plan remains intentionally conservative: freeze a rehearsed build, verify the Mac Host, iPhone, iPad, Watch, browser clients, MIDI destinations, audio, lighting, reconnection, and recovery on the production network, then let the gig provide the next evidence. Setlist overrides, presentation persistence, iPad hosting, and router-free native networking remain later steps—not pre-show scope.
Back to the top