Connected Show Control

01 / The problem

What needed to change.

A modular show system needs a shared understanding of fixtures, scenes, cues, and device state. Each interface must make that information understandable before the whole system can be trusted together.

02 / The approach

A focused way forward.

The work is grouped as one project family: an Android planning interface, embedded device interfaces, a field-router direction, and the protocol work connecting them. Simulation, observation, and physical output are developed as distinct stages.

03 / The work

What has been built.

• An Android prototype for offline show storage and editing.
• Virtual fixture patching, scene and cue editing, and deterministic playback.
• Audio-reactive previews driven by synthetic or recorded audio frames.
• Manually requested, read-only status checks for compatible device services.

04 / Current state

Where it stands.

The Android prototype supports planning, virtual playback, and device observation. The wider embedded work gives the system a common development direction.

The current portfolio entry describes simulation and observation. It does not claim a completed Android-to-DMX control path or qualified physical output.

05 / Next

The next useful step.

Validate the interfaces between software and devices, then establish the evidence needed for a complete live control path.