A spotlight appears as an actor steps forward. A sound effect lands just after a door closes. A video begins as the stage fades into darkness. These moments may feel effortless to an audience, but each one depends on careful planning and well-timed cues.
MIDI Show Control (MSC) helps technical teams coordinate those actions. It gives compatible equipment a shared way to exchange instructions, allowing separate systems to respond to programmed commands. Understanding how it works starts with a simple idea: each system already knows its job; MSC helps tell it when to act.
What Is MIDI Show Control?
MIDI Show Control is an extension of the Musical Instrument Digital Interface, better known as MIDI. It supports communication between control equipment used in theatre, live performance, and multimedia environments. Its applications range from controlling a single lighting system to coordinating larger arrangements of entertainment equipment.
A useful way to picture MSC is as a digital cue instruction. Instead of someone pressing separate buttons on several systems, a controller can send messages that trigger prepared actions.
Those messages do not contain the show’s music, video, or lighting design. The receiving equipment must already have the necessary content and programming.
How MIDI Show Control Works
A basic setup has a sender, a communication connection, and a receiver. The sender creates an MSC message. The receiving device checks whether the message applies to it and carries out the supported command.
MSC messages use a form of MIDI communication called System Exclusive, often shortened to SysEx. A message includes information such as the device address, equipment category, command, and any required cue details. Beginners usually enter these values through software controls rather than writing the message by hand.
Imagine a sound computer that needs to trigger a lighting change. The lighting designer first saves the required scene on the lighting console. The computer then sends an MSC instruction identifying that cue. The console handles the actual lighting transition.
The Main Commands Explained
The most familiar MSC commands are GO, STOP, and RESUME. Their names are easy to remember, although operators should check how their equipment handles each one.
GO starts a cue or initiates the relevant playback action. STOP can pause an active cue rather than end it permanently. RESUME continues a paused action.
Other commands support more specific tasks. For example, grandMA2 supports TIMED_GO for a cue transition with a specified fade time, SET for certain fader controls, and FIRE for triggering macros. Command support varies between products, so a command available on one system may be unavailable on another.
This makes the equipment manual an essential part of programming. A familiar command name alone does not explain every detail of its behaviour.
Where MIDI Show Control Is Used
MSC suits productions where several technical elements need to follow planned cues. A theatre scene might combine a lighting transition, a background sound, and a projected image. A concert might need playback and lighting to respond to the same performance moment.
Multimedia presentations and installations can also use this approach when compatible systems need coordinated instructions. The MIDI Association describes MSC as intended for theatrical, live performance, multimedia, audiovisual, and similar environments.
The deciding factor is the production’s workflow. Some moments benefit from linked cues, while others need separate operators who can respond to changes on stage.
What Equipment Do You Need?
Start with equipment or software that explicitly supports MSC transmission or reception. A product having MIDI connections does not automatically mean it understands MIDI Show Control.
You also need a suitable communication route. Depending on the equipment, this may involve a MIDI interface, physical MIDI connections, or a supported connection between software applications.
Software such as QLab provides dedicated controls for sending MSC messages. Its settings include the destination, command format, command, device ID, and cue information. These fields let an operator build a message without manually entering its underlying data.
Before choosing a setup, establish which system will send instructions and which systems will receive them. That decision makes the rest of the configuration easier to follow.
Setting Up Your First Connection
Begin with one sender, one receiver, and one simple test cue. A basic lighting transition or a short sound makes the result easy to observe.
Enable MSC reception on the receiving system, then check its device ID and supported command format. Configure the sender to address that receiver and identify the intended cue.
Cue labels deserve particular attention. QLab’s documentation explains that MSC cue numbers are text strings: 1, 01, and 1.0 can identify different cues. Matching the visible numerical value may therefore be insufficient; the labels need to match exactly where required.
Once the first command works, add further cues gradually. This gives you a known working starting point if a later change causes trouble.
A Practical Example During a Play
Consider a scene in which an actor opens a window during a storm. The production needs a lighting change, a thunder sound, and moving clouds on a screen.
During programming, the team prepares each element on its own system. The lighting console stores the storm scene, the audio software holds the thunder effect, and the video system has the cloud sequence ready.
The team could then program a controller to send the appropriate MSC commands from one operator action. During rehearsal, they adjust the timing so that thunder follows the lighting flash naturally.
The operator still watches the actor. If the window sticks or the performance slows, the cue can wait for the correct moment. The benefit comes from combining prepared technical actions with human judgment.
Benefits and Limits to Understand
A well-planned MSC setup can make repeated cue sequences easier to run. Operators can spend less attention moving between controls and more attention following the performance.
It also encourages clear planning. Deciding which cues belong together often reveals timing problems before an audience sees them.
However, linking systems creates dependencies. One incorrect instruction can affect several parts of a scene. A production should therefore define which actions run together, which remain separate, and how operators recover from an unexpected result.
Reliable show control comes from the full setup: programming, connections, rehearsal, and crew knowledge.
Common Problems and How to Approach Them
If a cue fails, check the basics first: the selected output, the receiving input, MSC reception settings, device ID, command format, and cue label. Test one part of the connection at a time.
Unexpected cues also deserve investigation. QLab notes that some lighting-console workflows send MSC GO messages for every cue in an enabled list. Matching cue numbers elsewhere can then trigger actions unintentionally. Careful numbering helps control that behaviour.
Keep a clear record of the working settings. During rehearsal, practise starting from different scenes and recovering after an interruption. A setup that works from the opening cue should also be checked at the points where the crew may need to restart.
Conclusion
MIDI Show Control helps compatible entertainment systems exchange instructions so that lighting, sound, and video can follow a coordinated cue plan. Its value becomes clear when several prepared actions need to happen around the same stage moment.
The strongest results begin with a simple, tested connection and grow through careful programming. Clear cue labels, understood commands, and regular rehearsal turn a technical link into a useful part of the performance.
Frequently Asked Questions
What is MIDI Show Control used for?
MIDI Show Control sends commands between compatible entertainment systems. It can help coordinate prepared lighting cues, sound playback, video sequences, and other supported show actions.
Does MIDI Show Control transmit audio or video?
No. MSC sends control instructions. The receiving system stores or accesses the media and performs the requested playback action.
Is standard MIDI support enough to use MSC?
Not necessarily. Check whether the product specifically supports MIDI Show Control and whether it can send or receive the commands your production needs.
Can MIDI Show Control run an entire show automatically?
A controller can be programmed to send sequences of MSC commands. The amount of automation depends on the software, connected equipment, and cue design. Live productions may still need an operator to follow performers.
Why might an MSC cue fail to trigger?
Possible causes include an incorrect connection, disabled MSC reception, a mismatched device ID, an unsupported command, or a cue label that does not match the receiver’s programming.
