Automating Lower-Third Graphics with MIDI

Automating visual lower-third graphics using MIDI commands allows live broadcast directors to trigger accurately timed on-screen titles, speaker names, and lower-third overlays without manual switching. By mapping standard MIDI messages—such as Note On, Note Off, and Control Change values—from hardware surfaces, digital audio workstations (DAWs), or show-control software to broadcast vision mixers, production teams achieve frame-accurate synchronization between audio, lighting, and visual overlays.

The MIDI Automation Pipeline

The automation architecture relies on three primary layers: the MIDI transmitter, a routing bridge, and the broadcast graphics engine.

1. MIDI Transmitter (Source): This can be a timeline-based DAW (such as Ableton Live or Reaper), specialized show-control systems (such as QLab), or physical MIDI controllers (such as a Novation Launchpad). The source outputs standard MIDI commands tied either to a fixed timeline or to specific operator cues.
2. MIDI Interface/Bridge: If the transmitter and the graphics engine are on different machines, standard 5-pin DIN or USB-MIDI hardware interfaces are used, or MIDI over Ethernet (RTP-MIDI) is employed across a local network. On a single computer, virtual MIDI loopback software (such as loopMIDI for Windows or the IAC Driver on macOS) routes the signals internally.
3. Graphics Engine (Receiver): Broadcast applications like vMix, OBS Studio (with MIDI plugins), NewTek TriCaster, or CasparCG interpret incoming MIDI messages and translate them into visual trigger events.

Step-by-Step Implementation

1. Signal Assignment and Protocol Selection

Directors utilize distinct MIDI message types depending on the required graphic behavior:

• Note On / Note Off: Ideal for binary actions. Sending a Note On event (e.g., Note 36 / C1) triggers the lower third to animate in (TransitionIn). A subsequent Note Off or a secondary note can trigger the exit animation (TransitionOut).
• Control Change (CC): CC values range from 0 to 127. They can control continuous parameters, such as adjusting the opacity of a graphic or scrubbing a graphic's position dynamically across the screen.

2. Software Mapping and Shortcuts

Within the broadcast software, directors enter the "Shortcuts" or "Hotkeys" menu and select MIDI as the input type:

• vMix: The software features native MIDI support. Directors use the "Find" feature, send the designated MIDI command from the controller or DAW timeline, and map it to OverlayInput1In or a specific Title preset.
• OBS Studio: Utilizing plugins like obs-midi-mg, directors map incoming MIDI channels to toggle source visibility or fire specific Advanced Scene Switcher macros that manage transition timings.
• TriCaster: Incoming MIDI notes are assigned directly to the internal Macro engine to fire automated sequence scripts that cue Lower Third presets.

3. Managing Dynamic Text and Data Sources

To update names, titles, and topics automatically alongside the visual cue:

• Lower thirds are linked to data sources like Google Sheets, CSV files, or local JSON databases.
• Directors configure the broadcast software so that specific MIDI commands not only trigger the graphic entrance but also advance the data row (NextRow command), ensuring the correct speaker information displays on cue without manual typing during the live event.

Why Broadcast Directors Use MIDI Automation

• Frame-Accurate Synchronization: By embedding MIDI notes into the same master audio or video timeline driving a production, graphics appear at exact, repeatable moments.
• Reduced Operator Workload: A single automation track can simultaneously manage audio levels, lighting scenes, and lower-third overlays, minimizing the risk of human error during complex live transitions.
• Universal Compatibility: MIDI is an uncompressed, low-latency, and platform-agnostic protocol supported by thousands of hardware and software devices across the live event and broadcast industries.