# Questions

> Who builds RDMBench, whether it stays free, what it cannot read, which fixtures it has met, Windows and Linux, and where a problem goes, answered by the person who makes it.

- **Version:** 0.12.0
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Needs:** An Enttec DMX USB Pro with its DMX/RDM firmware (major version 2), or, on a rig, an Art-Net 4 node with RDM on at its ports
- **Price:** Free

## Who builds it?

I do: Darin Pope. RDMBench is a one-person project, and
PlanetPope, Inc. publishes it. It has been run at a real bench since
September 2026, on an [Enttec DMX USB Pro](https://www.enttec.com/product/dmx-usb-interfaces/dmx-usb-pro-professional-1u-usb-to-dmx512-converter/), and every version is on
[Releases](/releases/). [About](/about/)
says what has been proven on real fixtures and what only on the
simulator.

## Will it stay free?

That's a loaded question. Free, all of it: there is no Pro
tier, no licence key, and nothing held back from any build. What I plan
to sell is work, not software: onboarding a shop's fixture models into
the public library, and priority support as a yearly subscription.
Neither is offered yet ([Services](/services/)). I chose it this way
because it is low hassle for everyone, me included, and the paid work
and the free app pull the same way: what onboarding finds goes into the
library every bench uses. Also, if I ever decide to sell RDMBench to someone, I can't guarantee what that new owner would do.

## What can't it read?

Anything the fixture does not report. RDMBench reads a fixture over RDM,
so it knows what the fixture says about itself and nothing else. A unit
that reports no sensors gives the report less to go on, and a belt, a
lens or an emitter it has no sensor for is invisible to it. The report
does not hide the gaps: anything the fixture did not answer is listed
under **Problems during read**, and the
[behavior check](/help/behavior/) says how far to trust what it did
answer. When nothing it reports explains the complaint, the report says
that too, and where to look instead
([Troubleshooting](/troubleshooting/)).

## Which fixtures has it met?

The ones in the [fixture library](/fixtures/), each with what it gets
wrong and how that was found. The first was an
[ADJ 5PX HEX](/fixtures/adj/5px-12px/), which answered on the first try
and then turned out to break the RDM standard in six ways,
among them an identify that works backwards. A
[SHEHDS GlamoPar07A](/fixtures/shehds/glamopar-07a/) reports a
manufacturer ID registered to no one, under the name of a different
company, Canara, whose registered ID is another. The rest of what it
has been run against is the built-in simulator, which [About](/about/) lists area by area.

## Windows or Linux?

Windows and Linux are planned and not started. It runs on macOS 15 Sequoia or later,
Apple silicon or Intel ([Requirements](/requirements/)).

## Where does a problem go?

A security problem goes to [Security](/security/), which says what to
send and what happens next. Anything else, a wrong reading, a fixture
it trips over, a report that says something it should not, goes to
darin@rdmbench.com. Say which fixture, its firmware, and what the
report said, and attach the report if you can.
