Troubleshooting
The window stops responding
The light at the right end of the bottom bar is the connection to the engine: green while connected, with Connecting… or Reconnecting… beside it when not. The window reconnects by itself once the engine is back; a tablet does the same.
Nothing reaches the lights
- Is the fixture responding at all? In Setup, select it and use Test channels to hold a channel at a value. If that does nothing, the problem is the patch or the network, not the show.
- Is the universe routed? In Setup's Output panel, check the universe is on, set to sACN or Art-Net as your node expects, and sent to the right address. Art-Net universe numbers start at 0. See Sending DMX.
- On a Mac, is Local Network allowed? macOS asks the first time the engine sends sACN. If sending fails with "No route to host", allow it for DMX Engine in System Settings → Privacy & Security → Local Network.
- Is the grand master up, and the track not muted? See Faders, mute and solo. A fixture's brightness trim in the patch can also keep it dim.
- Does the address overlap? The DMX map hatches channels two fixtures share; Fix overlaps moves them.
The lights are fine but the show won't change
Editing is probably locked. The lock in the header starts closed; click it or press ⌘L. See Editing, undo and the lock.
There is no audio, or the tempo is wrong
- Click the audio meters (or No audio input) in the header and pick an input. macOS asks for microphone access the first time; if you said no, allow it in System Settings → Privacy & Security → Microphone.
- To react to music playing on the Mac itself, route it through a loopback device such as BlackHole and pick that.
- A red input light means the sound card is clipping; only the interface's own gain fixes that. A tempo that is half or double what you expect can be corrected with Tap or by moving the detected range (
--min-bpm). See Tempo and audio.
A tablet can't connect
The engine has to allow other devices: the desktop app does; the headless engine needs --bind 0.0.0.0. Use the address and QR code under Tablet in the header, or http://dmx-engine.local:7400/remote, and make sure the device is on the same network. On a Mac, DMX Engine also needs Local Network access in System Settings → Privacy & Security; without it tablets can't connect and dmx-engine.local isn't found. See Touch remote.
Pro DJ Link doesn't follow the decks
Connect the computer to the decks' network and play a track with a valid tempo. If other DJ software holds UDP ports 50000–50002, the tempo controls report the conflict. See Tempo and audio.
A fixture looks wrong
Fixtures from the Open Fixture Library (marked OFL) haven't been checked on the fixture. Try them with Test channels, and compare them with our own profiles. Channels the engine doesn't drive yet stay at their default.
Reporting a problem
Say what you did, what you expected and what happened, and include the show file if you can. Problems and suggestions go to the project's issue tracker.