Skip to content
CUE++
ProductsServicesStudioThe StoryContact

System Integration.

Connect the consoles, applications and equipment your event depends on. Build and test the behaviour your team needs before handover.

Different systems. One intended behaviour.

Start with the signal: what sends it, what receives it and what should happen. The connection can serve one project or become a reusable tool.

Cues across systems

Connect a console, playback application or custom interface to the systems it should trigger. Define the cue flow and test the responses together.

Timecode & tempo

Work through SMPTE, LTC, MTC or tempo-based connections. Agree the timing requirements and verify them against the relevant setup.

A shared control surface

Bring the controls or status your team needs into one interface. Connect existing software through OSC, MIDI, APIs or a custom bridge.

Data & preparation tools

Move show state, logs or production data between applications. Automate a repeated preparation task and keep the result visible to the people using it.

What you take forward.

We agree the deliverables around the question you need to answer and the team using the result.

The agreed connection
A configured integration, software bridge or control interface, built around the systems and versions in scope.
A verified signal path
Test notes describing the behaviour, timing requirements and what happens when an input or connection is missing.
A handover your team can use
Setup instructions, configuration and the operating checks agreed for your team and its environment.

How the work comes together.

  1. Map the connection

    Trace the source, destination and protocol. Agree the required timing, control and feedback behaviour.

  2. Build & test

    Develop the connection, then check normal operation and agreed failure cases against software and available equipment.

  3. Document & hand over

    Review configuration, limitations and recovery steps. Prepare the files and instructions for your team.

Common questions

Can you work with a setup we already use?

Yes. Share the systems, versions and current configuration. We review what can stay, where the missing connection sits and what access is needed to develop and test it.

Which protocols do you work with?

Connections include OSC, MIDI, DMX, Art-Net, sACN, APIs and timecode. We choose the approach around the source, destination and response requirements, and confirm compatibility for the specific setup.

Can this become a tool we reuse?

Yes. Tell us whether the connection is for one project, several shows or a tool your team will keep using. That changes how we scope configuration, packaging, documentation and ongoing maintenance.

What needs to talk to what?

Tell us the systems involved and the behaviour you need. You can start with a simple example and add the technical detail later.

Pick what fits

Which systems need to talk to each other?

Pick the gear and software involved. Anything missing goes in the next step.

Rather just talk? Book a call →