The story of the DMX USB Pro

The ENTTEC DMX USB Pro (70304) is a single-universe USB to DMX512 interface that has been in continuous production for more than two decades. By most working definitions it is the default USB-DMX interface: the one lighting software authors test against, the one rental houses keep in a drawer, and the one whose serial protocol other products describe themselves as compatible with. This article is the story of why: the timing problem it solved, the engineering decision that solved it, and what "industry standard" does and does not mean when people apply the phrase to this product.

The problem: DMX timing on a desktop operating system

DMX512 (formally ANSI E1.11) is an asynchronous serial protocol running at exactly 250 kbit/s. Each frame starts with a break (a low condition a receiver must accept at 88 microseconds or longer; DMX512-A requires transmitters to hold it at least 92 microseconds), then a mark after break, then up to 513 slots of 11 bits each: a start code plus 512 channel values. A full universe therefore takes roughly 23 ms on the wire, which caps full-frame refresh at about 44 frames per second. If you want the background on the protocol itself, see What is DMX512?.

Those numbers are the crux of the story. A fixture does not receive a command once and remember it; it expects the full frame again and again, on a steady clock. Generating that stream is trivial for dedicated hardware and surprisingly awkward for a general-purpose computer, because a desktop operating system makes no real-time promises. USB traffic is polled, buffered, and scheduled; USB-serial converters batch data on a latency timer; and the OS preempts the control application whenever it likes. The result, when the host generates the timing itself, is frame-to-frame jitter: stretched breaks, uneven refresh, and on some fixtures visible stutter or flicker. It usually works. It cannot be made to always work, because the timing authority is in the wrong place.

The first attempt: Open DMX USB, deliberately minimal

ENTTEC's first USB-DMX product was not the Pro. It was the Open DMX USB (70303), a radically simple device: FTDI's FT245 USB chip, then the first of its kind, wired to an RS-485 line driver (RS-485 is the differential electrical standard DMX rides on), and almost nothing else. There is no processor in the box. Every byte of the DMX stream, including the break timing between frames, is produced by software running on the host computer, and the box just converts voltage levels.

The name was literal: the decision was made to open-source the design, hardware and software both, and ENTTEC released it under a GPL licence. The context explains the impact. DMX hardware at the time meant expensive slotted PC cards or dedicated hardware consoles; this was the first time DMX output reached enthusiasts at genuinely low cost, using the PC's own CPU to generate the signal. ENTTEC describes it as the first USB to DMX interface on the market, and the published schematic and example code seeded a generation of hobbyist and open-source lighting projects. The device is still sold today as a low-cost entry point.

The Open DMX USB also demonstrated, at scale, exactly where the minimal approach breaks down. When the host computer gets busy, the DMX stream stutters. That is not a defect, it is the design working as intended; the trade-off is documented in Latency on USB to DMX products. It is the problem the DMX USB Pro was built to remove.

The decision that mattered: put the clock in the box

The core idea of the DMX USB Pro fits in one sentence: the interface contains its own microprocessor and frame buffer, so the DMX timing is generated inside the box, independent of the host computer.

In practice it works like this. Your software sends channel values over USB whenever it has new ones. The Pro stores the current frame in its internal buffer and retransmits it onto the DMX line continuously, with correct break timing on every frame. If USB traffic pauses for a moment because the computer is busy, the lights do not flicker; the Pro simply keeps repeating the last frame it was given. The fixtures on the line see an uninterrupted, spec-compliant DMX stream regardless of what the operating system is doing.

The timing parameters are explicit and configurable, which matters when you meet equipment that does not quite follow the standard:

• Output refresh rate configurable from 1 to 40 frames per second (40 FPS being consistent with the roughly 44 Hz ceiling the protocol itself imposes on a full universe).
• Break time configurable from 96 microseconds to 1.3 ms.
• Mark after break configurable from 10.6 microseconds to 1.3 ms. The 10.6 figure is the API's granularity: MAB is set in units of 10.67 microseconds, minimum one unit. DMX512-A requires transmitters to hold MAB at least 12 microseconds, so keep it at or above that in practice.

The production design added more things that matter on real jobs:

• Electrical isolation. The DMX port is isolated from the computer to 1500 V on both data and power lines. If a fault on the lighting line puts dangerous voltage on the cable, the isolation barrier protects the computer connected to the other side.
• DMX input as well as output. The Pro has a female XLR5 output and a male XLR5 input, so it can receive DMX into the computer, which made it useful as a capture and analysis tool as well as an output device.
• RDM support. The Pro speaks ANSI E1.20 RDM (Remote Device Management), a companion standard that lets the controller talk back and forth with fixtures over the same DMX cable, to identify them and change their settings remotely. Details are in DMX USB Pro: RDM.

Full specifications are in the datasheet.

The ecosystem effect: a published protocol everyone implemented

Hardware alone does not create a de facto standard. What did it for the DMX USB Pro was the API: ENTTEC published the serial message protocol the box speaks over USB, the DMX USB Pro API, so any developer could add support without a licence fee or a non-disclosure agreement.

Over twenty years that compounding worked in one direction. Software authors implemented the Pro because it was documented and its timing was trustworthy; users bought the Pro because their software supported it; the next software author supported it because their users already owned one. By ENTTEC's own estimate the two devices put computer DMX output in the hands of thousands of people early on, then tens of thousands, and by now likely hundreds of thousands: an audience that did not exist when DMX required dedicated hardware, and one that went on to write its own lighting software in remarkable numbers. Today the list of programs that talk to it spans free and commercial packages across Windows, macOS and Linux; the current list is maintained at USB>DMX: Compatible USB software. The FTDI-based USB layer helps too: FTDI's drivers ship with, or install cleanly on, all three operating systems. ENTTEC's own control software, EMU, supports the Pro as well, and unlike the dongle-locked packages in this market, EMU is a free download.

A side effect of a published protocol is that other manufacturers can implement it, and some third-party interfaces advertise compatibility with the Pro's API. That is evidence of the point rather than a problem: when other people's hardware describes itself in terms of your protocol, the protocol has become the reference.

The relatives: Open, Pro, and Pro Mk2

Three devices make up the family tree. The comparison below is the short version; the full breakdown is in Compare ENTTEC's DMX USB devices.

Neither end of that table makes the other a bad product. The Open DMX USB is the budget sibling on purpose: fewer parts, lower cost, and timing quality that depends on how well your software and OS behave. The Pro costs more because the parts that make timing unconditional are physically in it.

The Mk2 extended the formula with a second universe, MIDI, and a standalone show playback mode, and served for years before being retired to legacy status; its features largely migrated to other parts of the range (Ethernet nodes for multi-universe work, S-PLAY for standalone playback). The original Pro outlived its own successor in the catalogue, which says something about how well the original scope was chosen. It remains deliberately single-purpose: one universe in or out, no standalone mode, no MIDI, connected over USB 2.0 Type-B, with a 3-year return-to-base warranty.

Twenty years on

In 2022 ENTTEC marked the milestone with a Limited Edition Anniversary DMX USB Pro (70304-20): 200 individually numbered units worldwide, functionally identical to the standard 70304, in a brushed anodised metal case with Neutrik XLR5 connectors, a Samtec high-retention USB port, and a 20-year warranty (conditions applied). The run sold out. It also hints at the timeline: ENTTEC has not published an exact launch date and frames the 2022 milestone loosely (the company itself was founded in 1999), but the product's own anniversary branding suggests the Pro dates from around 2002.

What "industry standard" actually means here

It is worth being precise, because the phrase gets used loosely, including on ENTTEC's own product page. The DMX USB Pro is not a standard in the formal sense. DMX512-A (ANSI E1.11) and RDM (ANSI E1.20) are standards; the Pro is a product that implements them, and no standards body certifies USB-DMX interfaces. When the industry calls it the industry standard USB-DMX interface, the claim rests on two measurable things. First, breadth of software support: the Pro's protocol is the one most third-party lighting software implements and tests against, to the point that other manufacturers build interfaces that emulate it. Second, longevity: the same product, speaking the same published protocol, has remained available and supported for more than twenty years, so an interface bought long ago still works with software written today. Those two properties, not a certificate, are what people mean when they call it the standard.

Where it fits today

The Pro remains a one-universe device, and that is the boundary of its role. For a single universe driven from a laptop, at front of house, on a test bench, or in a small venue, it is still the straightforward choice, and its onboard timing means the stream stays clean even on a struggling computer. When a project grows beyond one or two universes, the industry has moved to sending lighting data over Ethernet networks and converting to DMX near the fixtures; if that is your situation, start with setting up an Art-Net to DMX node. Those network nodes inherit the Pro's founding idea: dedicated hardware owns the DMX timing, and the computer just supplies the data. That principle, put the clock in the box, is the actual legacy of the DMX USB Pro. Then publish the protocol, and keep making the thing.