F34.us
Menu

Project overview · 2 MIN READ

The Signal Layer Between Music and Light

An overview of MixMan Coordinator's normalized playback state, tailored downstream payloads, and operational visibility.

Let one musical state reach the room

The music player knows what is playing. The video system and the lights need that knowledge too, in different forms. MixMan Coordinator sits between them: it receives playback data, normalizes it, and translates it for each visual consumer.

A systems portrait of the coordinator translating one music state into purpose-built visual and lighting payloads.

Concept illustration for mixmancoordinator; not a product screenshot.

Normalize before distributing

Its primary source can be MixMan's public current-playback projection, polled at a configurable interval. It can also accept external now-playing updates through the same normalized pipeline, allowing a side-stream source to keep visual systems active when MixMan is unavailable or intentionally not configured. Both paths produce a consistent internal representation of track identity, playback state, timing, color, intensity, and available metadata.

One input, two visual destinations

Each destination receives its own representation of the same normalized musical state.

flowchart TD
    MixMan[MixMan playback] --> State[Normalized state]
    External[External now-playing update] --> State
    State --> Video[Visualizer Stream payload]
    State --> Light[DungeonOPC payload]

Keep partial failure survivable

Each downstream receives a purpose-built payload. Visualizer Stream gets the track and recommendation context it needs to construct a video presentation, while DungeonOPC receives the compact now-playing state used to guide a physical lighting environment. Raw upstream responses are not forwarded wholesale, reducing coupling and preventing one consumer from becoming dependent on unrelated source details.

The coordinator is designed to remain useful during partial outages. Its process health does not fail merely because a dependency is unreachable, and disabled services are represented explicitly. Status, current state, diagnostics, traffic summaries, and delivery counters give an operator enough information to distinguish a healthy coordinator from a healthy source or a successful downstream delivery.

PROJECT

More from MixMan Coordinator

F34.us Background Image