MIDI lighting control: mapping faders, pads and blackout

Treat MIDI as a source

A fader is a continuous value. A pad is a trigger. A rotary is usually another continuous value, sometimes endless. Lighting software learns those messages and writes them onto dimmers, cues, colours or graph pins. The fixture still speaks DMX. MIDI is how your hands talk to the software.

You do not need a lighting-brand console to have a useful surface. A cheap USB MIDI fighter with eight pads and four faders will run a club override layer if you map it with intent.

Learn, channels and banks

MIDI learn: move the control, the software captures the message. Then you assign the destination. That is faster than typing channel 1 CC 17 by hand — until two devices shout on the same channel.

Give the lighting surface its own MIDI channel if the same laptop also talks to a synth or DJ deck. Channel fights look like haunted faders.

Banks let a small controller do more jobs. Bank 1: intensity and blackout. Bank 2: colour. Bank 3: cue fire. Label the banks on tape. Memory is the first thing that fails when the booth is loud.

Map the boring things first

Blackout on a pad you can hit without looking. Master dimmer on a fader. Haze on a fader or a latching button. Strobe enable on a gated pad, not a toggle you will forget is on.

Colour override as a handful of pads (warm, cold, red, company colour) beats a single encoder you must stare at. Movement freeze is underrated: one button that holds heads where they are while the wash keeps reacting.

Feedback is a bonus. If the controller has LEDs, use them for blackout armed and strobe armed. If it does not, do not pretend it does.

Velocity, pickups and jumps

Pad velocity can scale a bump. It can also make blackout unreliable if a light tap does nothing. For kill and haze, ignore velocity. For a snare bump, velocity is fun.

Pickup (or takeover) modes matter when a fader in software is at 80% and the hardware fader is at 10%. Jump-to-value will slam the wash. Pickup waits until you cross the current value. Use pickup on masters.

When MIDI is the wrong tool

If the surface is another application on the network, OSC or an HTTP API will be clearer than a virtual MIDI cable. If the destination is a fixture, you still end in DMX. MIDI does not replace the patch.

Controllers that survive beer

Prefer latching or clearly lit buttons for haze and strobe enable. Prefer a large pad for blackout. Tiny unmarked encoders are for the studio, not a wet booth. Tape a legend on the chassis; printed overlays fall off.

USB hubs fail. Plug the lighting surface into the PC, not through the same hub as a phone charger. If you need a hub, power it and test it for an hour before you trust it.

Bring a spare class-compliant controller. Drivers that require a vendor installer are a load-in risk on a house laptop you cannot admin.

A default map worth stealing

Fader 1 master dimmer, fader 2 haze, fader 3 wash temperature. Pad 1 blackout, pad 2 safe wash, pad 3 strobe enable, pad 4 freeze heads. That is eight controls and a whole night. Everything else is luxury.

If you add cue-fire pads, number them on tape to match the software bank. “The green one” is not a cue name when the houselights are out and two people are shouting.

After you map, unplug the controller and plug it back in. If learn assignments vanish, you have a port-order problem. Fix it before doors, not during the opener.

MIDI through a snake

USB is fine on a laptop in the booth. If the surface is at FOH and the PC is in a rack, use a proper MIDI line or a network MIDI you have tested. Cheap USB-over-Ethernet gadgets fail like cheap DMX adapters: rarely, then always, on a Saturday.

Clock MIDI (the musical kind) is not lighting timecode. Do not wire a DAW clock into a blackout pad and call it locked. Different jobs, different cables. If a guest insists on their own surface, give them one empty bank rather than rebuilding your map at 22:00.

Related

• MIDI vs OSC vs DMX →
• External I/O →
• MIDI lighting control →