Theatre
Clear cue state, deliberate execution, and rehearsal-friendly editing.
Realtime show automation for Windows
Connect, automate and run the show.
Showmesh brings media, realtime graphics, control signals, and external systems into one cue-centered workspace for theatres, concerts, installations, and live events.
Early product direction · capabilities are labeled by development state
Product thesis
One operator workspace for the systems that make a show.
The cue list stays at the center while resources, actions, timing, routing, and live status remain in context. Editing another object does not hide what is live or change what GO will fire.
07 · PLAYING08 · NEXTGO · 08
Resource → Action → Trigger
One model for media, control, and realtime systems.
Resources expose capabilities, actions describe a change, and triggers define when it happens. Native media playback remains part of the cue lifecycle—not an artificial action card.
- 01
Resource
What can be controlledVideo, audio, an output, a connection, or an external realtime engine.
- 02
Action
What changesFade opacity, set volume, route output, or send a control message.
- 03
Trigger
When it happensGO, cue lifecycle, timecode, OSC, MIDI, or deliberate manual execution.
Operator workflow
Know what is happening before pressing GO.
Live playback, the ready cue, timing, cue actions, warnings, and system health remain readable without taking the operator away from the run order.
- Playing
- Coral rail, progress, label, and remaining time
- Next
- Green rail, explicit NEXT label, and GO target
- Recovery
- Warnings stay attached to the affected cue
Windows-first engine direction
Built around the machines that run the room.
Showmesh is being designed around native media and output paths, separation between operator UI and playback work, and visible timing and health. Architecture shown here is product direction while implementation develops.
PROCESSOperator UISeparate from playback work · in development
OUTPUTNative media pathsWindows-first direction · in development
HEALTHTiming and telemetryVisible operator evidence · planned
Connections and integrations
Connect systems by role, not by logo count.
Every capability is labeled by development state. Protocols and integrations are grouped around the work they perform.
Media and output
- Video and audio playbackCore
- Images and textCore
- NDI and Spout routingPlanned
Control and time
- OSC and MIDI controlPlanned
- DMX and timecodePlanned
Realtime systems
- Notch BlocksExploratory
- Unreal EngineExploratory
- TouchDesignerExploratory
Reliability direction
Trust comes from visible evidence.
Warnings belong beside the cue they affect. Output, audio, frame timing, network state, and recent activity stay available as calm telemetry rather than constant notifications.
10Dim to blackoutAction target cue not foundWARNING
OUTPUT Program · 1080p60AUDIO 48 kHz · 512 smpENGINE 93 fpsNETWORK OSC · MIDI
Validation, logs, autosave, backups, and recovery are development areas and are not presented here as shipped features.
Built for live work
Different rooms. The same need for operator clarity.
Concerts
Media, realtime graphics, and control signals in one run order.
Installations
Long-running system context with visible connections and health.
Live events
A Windows-first operator surface built for shared technical workflows.
Early access
Connect, automate and run the show.
Showmesh is in early development. Get in touch if your production needs a Windows-first approach to realtime show automation.
Email [email protected]