To make lights react to music you need three things: a light that speaks DMX (the standard control language of stage lighting), a USB-to-DMX interface to connect your computer to that light, and software that listens to audio and converts it into lighting commands. ENTTEC's EMU does that last part and is a free download for Windows and macOS: no dongle and no trial expiry; the free tier outputs one universe, and optional paid licences (which become perpetual) unlock more. The total cost of a working sound-reactive rig is one interface plus whatever lights you already own.
This guide assumes zero lighting background: which approach fits your situation, then the software route step by step.
What you actually need
First, the mental model. Stage lights are not like household smart bulbs: they do not connect to Wi-Fi and they do not listen to your phone. Almost every stage light made in the last three decades, from a budget LED par can to a moving head, has a socket on the back (usually 3-pin or 5-pin XLR, the same connector family as microphone cables) that accepts DMX512, an open standard (ANSI E1.11). DMX is a one-way stream of numbers: up to 512 channels, each carrying a value from 0 to 255, with the full set refreshed roughly 44 times per second. Channel values tell the fixture how bright to be, what colour to show, where to point. If the concept is new, the primer What is DMX512? covers it in ten minutes.
So the shopping list is short:
- Any DMX fixture. A "fixture" is just the lighting-industry word for one light. LED par cans, bars, moving heads, any brand. Check the back panel for an XLR socket labelled DMX IN.
- A USB-to-DMX interface. Computers have no DMX port; DMX is an RS-485 serial bus running at 250 kbit/s, so a small converter box bridges USB to DMX. ENTTEC makes three: the Open DMX USB (the budget option: your computer generates the DMX timing itself, and the output is not electrically isolated), the DMX USB Pro (an onboard processor with its own frame buffer keeps the DMX stream running at a steady rate even if your computer stutters, plus 1500 V isolation between the USB side and the DMX line), and the EMU Hardware Interface (built specifically for EMU, which is exactly this article's use case: opto-isolated, both 3-pin and 5-pin XLR outputs for one universe, a TRS jack for footswitch or MIDI triggering, and it comes bundled with an EMU Premium licence). All three work with EMU; if you are buying hardware for EMU, the EMU Hardware Interface is the one ENTTEC recommends. The comparison article Compare ENTTEC's DMX USB devices goes through the differences in detail.
- A cable. The Open DMX USB and DMX USB Pro have a 5-pin DMX output; many budget fixtures use 3-pin XLR, so you may need a 5-to-3-pin adaptor (the EMU Hardware Interface has both 3-pin and 5-pin ports). Once your chain grows, read DMX Basics: Signal Loss on cabling and termination.
- Sound-to-light software. EMU is free to download, with a paid Premium tier that is optional (paid licences become perpetual). The free tier includes the audio engine, effect generators, GDTF fixture import (manufacturers publish free profiles at gdtf-share.com) and a custom fixture editor; the full built-in Crescit fixture library is a Premium feature. Either way, you do not need a separate lighting console or a paid media server to get lights moving to music tonight.
The three ways lights can follow music
People mean three quite different things by "lights reacting to music", and picking the wrong one is the most common way beginners waste money:
| Approach | How it works | Setup effort | Control you get | Best for |
|---|---|---|---|---|
| Fixture built-in sound-active mode | A microphone inside each light triggers its own pre-baked program on loud beats | None: press a button on the fixture | Almost none: no colour choice, no coordination between lights | Trying things out; a single light at a house party |
| Audio-reactive software (sound-to-light) | Software on a computer listens to a mic or line input, analyses beats and frequency bands, and drives all fixtures together in real time | Low: an evening to patch fixtures and tune the response | High: you choose which lights do what, on which part of the music, in which colours | DJs, bands, bars, home setups; this is what EMU does |
| Pre-programmed sync (timecode / DAW-driven) | Every lighting cue is programmed in advance and fired at exact points in the track, usually by MIDI or timecode from a DAW (digital audio workstation, e.g. Ableton Live) | High: hours of programming per song | Total: frame-accurate choreography | Touring acts with a fixed setlist, theatrical shows |
A few honest notes on each:
- Built-in sound-active mode is genuinely zero setup and worth trying first if your fixture has it. People outgrow it fast, for concrete reasons: the internal mic responds to whatever is loudest in the room (crowd noise included), and every light runs its own preset with no awareness of its neighbours, so eight fixtures do eight unrelated things. It reacts to volume, not to music, and there is no way to say "blue verses, red chorus".
- Audio-reactive software is the sweet spot for most readers of this article. The software hears one clean audio feed and coordinates the entire rig from it, so the lights behave as one system rather than a collection of twitchy individuals. The step up from sound-active mode is precisely the step from "the lights are flashing" to "the lights are doing what I designed, on the beat". It is still reactive, though: see the limits section below.
- Pre-programmed sync is how large touring shows work, and it produces the tightest results possible because nothing is being guessed in real time. The cost is programming time and rigidity: every song must be programmed in advance, and improvised sets break it entirely. For sets that change on the fly, audio-reactive control is the better fit. EMU can sit in the pre-programmed world too; see Configuring EMU with Ableton if you go that way later.
Setting it up with EMU, step by step
The full path from nothing to lights on the beat:
- 1. Download and install EMU. Get it free from the EMU product page for Windows or macOS. No account or dongle required.
- 2. Connect the interface. Plug the DMX USB Pro or Open DMX USB into a USB port. On Windows the FTDI driver may need installing first: Install FTDI Drivers. EMU should list the device in its output settings; if an Open DMX USB does not show up, EMU does not detect Open DMX USB covers the usual fixes.
- 3. Cable the fixture. Run a DMX cable from the interface's DMX output to your fixture's DMX IN (5-to-3-pin adaptor if needed). If you have several fixtures, daisy-chain them: OUT of the first into IN of the second, and so on.
- 4. Patch your fixture. "Patching" means telling the software what light is connected and at which DMX address, so EMU knows that, say, channels 1 to 6 belong to your LED par. Get your fixture's profile into EMU: on the free tier, import a GDTF file for your model (most manufacturers publish them free at gdtf-share.com) or build the profile yourself in EMU's custom fixture editor; a Premium licence unlocks the full built-in Crescit fixture library. Then set the fixture's address in EMU to match the address configured on the fixture itself (usually via a small display or DIP switches on the back). If addressing is new to you, Addressing your fixture explains it, and if you cannot find a profile for your exact model you can request it.
- 5. Sanity-check with faders. Before adding audio, push the fixture's intensity channel up manually in EMU. If the light responds, the whole DMX chain works and anything that goes wrong later is audio-side, not cabling.
- 6. Enable audio input. In EMU's Preferences, select your audio input device: the computer's built-in microphone works for a first test, a line feed from your mixer or audio interface is better because it hears the music cleanly without room noise. EMU takes a single stereo input, sampled at 48 kHz, and splits it into frequency bands. If you want EMU to hear audio that is playing on the same computer (a DJ app, a stream, a DAW), that needs a routing step; the Audio Input article covers both virtual routing tools and the simpler analog loopback method, plus the per-program Sound Tracker settings.
- 7. Map the music to effects. Build a scene or effect you like with the audio disabled first, so you know what the look is. Then drive it from the sound-to-light engine, which exposes the beat and the frequency bands (bass, mids, highs) as triggers you assign to effects. Kick drum to dimmer on the bass band is the classic first patch and it works. Tune the input gain so normal playback level sits comfortably in range; too hot and everything slams to full on every beat, too quiet and nothing fires. Then layer more fixtures and effects.
From plugging in the interface to a fixture pulsing on the kick is realistically under 30 minutes the first time.
Honest limits of audio-reactive lighting
- It is reactive, not choreography. The software hears audio as it happens; it cannot know the drop is coming in four bars, black out on the exact bar before a chorus, or tell verse from bridge. A well-tuned reactive rig looks energetic and musical, but never frame-accurate. If you need narrative cues, that is the pre-programmed lane, or a hybrid: run reactive effects as the base layer and fire manual or MIDI cues over the top (EMU's MIDI learn, a Premium feature, maps any controller; see MIDI).
- Latency exists on some setups. The chain is audio buffer, detection processing, USB transfer, then the DMX frame itself: a full 512-channel frame takes about 23 ms on the wire at 250 kbit/s, roughly 44 frames per second maximum, so the protocol is rarely the bottleneck. Large audio buffers, virtual-routing apps, and an overloaded laptop are the usual culprits when the lights feel a beat behind. On a well-set-up machine with a line input the delay is short enough to read as "on the beat". If yours is not, see Latency on USB to DMX products for what actually contributes and what you can change.
- Interface choice matters under load. The Open DMX USB has no onboard processor: your computer generates the DMX timing, so a CPU spike (the same laptop running your DJ software, for instance) can make the output stutter. The DMX USB Pro keeps its own frame buffer and its output timing stays constant regardless of host load, which is exactly why it costs more.
- Mic input is the weak link. A room mic hears the crowd, the PA reflections, and its own noise floor. Feed EMU a line-level signal from the mixer whenever you can.
Where to go next
Once one fixture pulses on the beat, the rest is scale and taste: more fixtures on the same universe, better-designed scenes, a MIDI controller for live overrides. Still assembling the rig itself? Start with DMX lighting for DJs and small bands: a starter guide, which covers fixtures, interface, cabling and addressing. Useful next reads: Audio Input for routing DJ-software or DAW audio into the engine, MIDI for triggering EMU scenes from a controller or DAW, the USB-DMX interface comparison if you have not bought hardware yet, and EMU: Free to Download, Premium is Optional for exactly where the free tier ends. EMU stays free the whole way; you only pay for the optional Premium features.