Message board
Questions, show files, screenshots, plugin links, bug reports — this is the place. Sign in with Google, pick a username, and post. You can delete anything you wrote.
Anything with a human on the other end: how do I get this fixture patched, why is my Art-Net not arriving, here is a show file, here is a look I built, here is a plugin I wrote, is this a bug or is it me. Screenshots welcome — they usually answer the question faster than the words do.
Once something is reproducible and clearly wrong — a crash, a fixture profile with the wrong channel order, a feature that does not do what the guide says — it belongs in the tracker where it can be closed by a commit. Post here first if you are not sure; someone will tell you which it is.
Open the trackerThis is the name you post under. 3–24 letters, numbers, dashes or underscores.
The five chips
Pick a category when you post and the chips above the thread list will filter to it. None of them are policed — pick the closest one and carry on.
House rules
Four things to know before your first post. There is no application, no moderation queue and no email list.
Every thread is public. Browse, search by category, open anything, link to it. Signing in only matters when you want to write something — and a thread's link works for anyone you send it to.
Sign in with Google, then pick a handle: 3 to 24 letters, numbers, dashes or underscores. That handle is what appears on your posts. Your Google account name never does.
PNG, JPEG or WebP, up to 4 MB, on a thread or on any reply. Click the image in a post to open it full size. Crop to the part that matters — the Inspector, the channel row, the Network checklist.
A delete link sits on anything you wrote. Removing a thread takes its replies with it. Nobody else can touch your posts, and nothing you delete stays behind in someone else's view.
Posts are plain text and line breaks are kept, so paste a log excerpt or a snippet of JSON straight in. Titles run to 120 characters and a post to 10,000. Threads sort by the most recent reply, so a good answer pulls an old question back to the top.
Show files
DMXexpress writes everything as human-readable JSON, so sharing a show is a matter of finding the right file and pasting it into a post.
A complete show is saved as a config; a reusable arrangement of fixtures, truss and towers is saved as a setup. Give it a name you would recognise in a list of other people's rigs.
Configs live under configs/ and setups under setups/, inside your show-data folder. Both are plain JSON you can open in any editor before you hand them over.
The board takes text and one image per post, not arbitrary files — put the JSON in a GitHub gist or repository and paste the link into a Show files thread.
Which fixtures it patches, how many universes it fills, whether the stage layout matters. A setup built around eight movers on a truss is useless to someone with four pars unless you say so.
# Windows
%APPDATA%\DMXpress\configs\
%APPDATA%\DMXpress\setups\
# macOS
~/Library/Application Support/DMXpress/configs/
# Linux
~/.local/share/DMXpress/configs/inspector.json out of it.Panel preferences — which Inspector tab is open, how wide it sits, which sections are folded, what the stage draws — belong to your machine, not to your show. They are kept out of saved configurations on purpose, so a show you download never rearranges your workspace.
Worth posting
Half the useful threads on a board like this are somebody showing what they built. These are the windows people most often screenshot.
Elsewhere
Every window and concept in the console, written out: patching, the Programmer, palettes, phasers, stacks, decks, output and troubleshooting. Most "how do I" questions are already answered there.
Read the guideScripts that add effect layers, control windows or a whole console re-tint. Post a rough draft on the board for feedback, then submit the finished link to the registry, where it is reviewed before it appears.
Browse pluginsBefore you report a bug, check you are on the latest release — the download is one standalone file and installing over the old one changes nothing about your show data.
Get the downloadFixture profiles, documentation fixes and code are welcome too. See the repository for how to contribute, and verify channel mappings against the manufacturer's documentation before you submit a profile.