# Report a problem with RDMBench

- **MCP resource:** rdmbench://help/report-problem
- **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

When RDMBench itself goes wrong, rather than the fixture, a problem
report is how you report the bug: it tells the people who make RDMBench
what happened. It is one `.zip` file
that you send by email to darin@rdmbench.com.

## What goes in it

- What made it: the version of RDMBench and of your computer's system.
- The last error RDMBench showed you, in its own words.
- The last *internal error*, if one was recorded: something inside
  RDMBench went wrong that it could not handle, and it wrote down where.
- RDMBench's own logs. The app, the command line and the AI assistant
  connection each keep one. A log is a list of what the program did and
  what failed, kept on this computer.
- The wire log of the connection you have open, or of the one an unplug
  just ended. This is the packets themselves, so the problem can be
  played back exactly as it happened. See [Read the wire log](/help/wire-log/).

Before anything is written, RDMBench checks every line for passwords,
cookies and tokens and hides anything shaped like one, including the
GDTF Share password. Nothing about your fixtures goes in except the
packets. You can open the file and read all of it before you send it.

## Making one

**On macOS:**

Choose **Help → Report a Problem…**. You don't need to be connected. The file
is saved on your Desktop, and Finder opens with it selected.

If RDMBench recorded an internal error last time, it says so when it
next opens and offers to make a report then.

The app does not make one yet. Use the command line instead (below). *(Windows, Linux)*

From the command line, on any computer:

```
rdmbench-cli report-problem --to ~/Desktop
```

Add `--wire FILE` to include a wire log you exported from the app or
saved from the captures folder, so the packets can be played back.

## Sending it

Attach the `.zip` to an email to darin@rdmbench.com, and say in the
email what you were doing when it went wrong. A reply comes from a
person.

## A security problem

If you have found a way to make RDMBench do something it should not —
reach a fixture it was not asked to, read a file it should not, or get
past a password — send it to the same address, darin@rdmbench.com,
rather than posting it anywhere public. What to include and what
happens next is on <https://www.rdmbench.com/security/>.

## Nothing is sent by itself

RDMBench never sends a report, or anything else about your bench, on
its own. The file stays where it was saved until you choose to send it.
The logs stay on this computer, a few megabytes at most, and backups
leave them out.
