Show control and media software for live events: build or buy?

Every live event has a system that decides what happens when: which video plays, when the lights change, when the pyro fires, when the presenter's walk-on music starts. That system is show control, and the software that plays the visuals is usually called a media server. Production teams face the same question on almost every project: use the tools everyone already knows, or build something custom? This guide sets out how to decide.

What show control and media software actually do

• Show control runs the timeline. It triggers cues manually, from timecode or from other systems, and sends commands to video, lighting, sound and stage machinery over protocols such as MIDI, OSC, DMX, Art-Net and SMPTE timecode.
• Media servers play and process the visuals: layering video, mapping it onto LED walls and projection surfaces, and outputting to many screens at once.
• Real-time engines generate visuals live, often reacting to audio, performers or data, rather than playing pre-rendered files.

On a big show these are often separate tools from separate vendors, tied together by a show caller and a lot of careful patching.

The case for buying

Off-the-shelf software is the right answer for a large share of events, and a good software partner should tell you so. Established tools include cue-based playback such as QLab on macOS, VJ and media server software such as Resolume, node-based real-time platforms such as TouchDesigner, and dedicated media server systems from several hardware vendors. Their strengths:

• Proven on thousands of shows. The common failure modes have already been found and fixed.
• Operators already know them. In Mumbai and across India, rental companies and freelance operators are trained on the popular tools, so staffing is easy.
• Ready immediately. No development time, only programming the show.
• Predictable cost. A licence or a rental line, not a development budget.

If your show is mostly video playback with lighting and sound cues, and an experienced operator is running it, buying is almost always right.

When custom software pays off

Systems that do not talk to each other

A performer's custom controller, a sponsor's data feed, a voting app, a legacy lighting desk and a media server rarely speak the same language. A small custom bridge that translates between them is often the cheapest, most reliable part of the whole show.

Behaviour the tools were not designed for

Visuals that follow a band that does not play to a click, content generated from live audience input, or audio-reactive effects tuned to a specific artist's sound can be stretched out of general tools, but sometimes the stretch becomes the risk. Purpose-built software can be simpler and steadier.

Permanent and unattended systems

Museums, experience centres and retail spaces need software that starts itself, follows a schedule, recovers after power cuts and reports problems remotely, and that a non-specialist can run with one button. General-purpose show tools can do some of this, but a custom shell around them, or a dedicated application, usually does it better.

Touring and repeat formats

If the same show runs dozens of times, a custom tool that removes setup steps and operator decisions pays for itself in saved hours and fewer mistakes.

Branded or audience-facing interfaces

When the public or a client touches the interface, such as a kiosk, a host's tablet or an artist's controller, it needs to be designed for them, not for an AV technician.

The hybrid approach most shows end up with

Build versus buy is rarely all or nothing. The most common pattern on well-run shows is:

• Buy the media server and show control backbone that operators already trust.
• Build the parts that make the show unique: a custom visual engine feeding the media server over NDI, Spout or Syphon, a bridge for unusual hardware, or a simple operator panel that hides complexity.

This keeps the risky, well-understood parts on proven tools and spends the development budget only where it changes what the audience experiences.

A quick decision checklist

• Can an experienced operator build the show in an existing tool in the time available? If yes, buy.
• Does the show depend on a connection or behaviour no existing tool supports? Build that piece.
• Will it run unattended, or be operated by non-specialists? Lean towards custom, at least for the interface.
• Will it run many times? The case for custom grows with every repeat.
• Is there time to test custom software on the real gear before the show? If not, buy, or simplify.

Reducing the risk of custom show software

If you do build, insist on the habits that make live software safe:

• Prototype early and test on the actual equipment, not just a laptop.
• Standard protocols at every boundary, so any part can be swapped for an off-the-shelf tool if needed.
• A manual fallback for every automated cue.
• Backup machines running in sync, with a fast switch-over.
• Rehearsal time with the full production team, not just the developer.
• Documentation and a handover so the rental company or venue team can run it without you.

What it costs

Buying costs licences, rental and an operator's time. Building costs development, testing and rehearsal support, with a small tool or bridge typically in the low lakhs and a full custom show system considerably more. We break the numbers down in how much custom AV software costs in India.

Working with DareDive

We build custom AV software from Mumbai: show control, playback, control bridges and audio-reactive visual engines that work alongside the tools your team already uses. For concerts and touring shows, see live show visuals and stage AV; for museums and brand spaces, interactive installations. Tell us about the show below, and if an off-the-shelf tool is the better answer, we will say so.