Troubleshooting
Find what you see in the tables below: each row gives the likely cause and the fix. If none fits, check Known limitations, then ask in the
discussions or report it on theissue tracker.Outputs
| What you see | Likely cause | Fix |
|---|---|---|
| The connection stays Disconnected or shows Conn error | The gateway isn't running, or listens elsewhere | Desktop app: restart it. Browser: start the gateway, then Connect again. Check IP 127.0.0.1 and Port 4515 |
| Connected, but no light reacts | The universe isn't streaming | Open the universe: set its Output, then Start streaming in Stream |
| Streaming, but no light reacts | Wrong node address, network, or Art-Net universe | Check the node's IP in Host, that your computer is on the node's network, and that the node listens to the same universe number |
| Streaming, but the wrong lights react, or faders do the wrong thing | Addresses or modes don't match the lights | Studio counts addresses from 0: a light set to 1 goes at 0. Set each fixture's Fixture mode to the mode set on the light |
| The Outputs log says "Unsupported protocol" | The gateway can't send that protocol yet | Use ARTNET (what's verified) |
| Everything worked, then stopped after reopening the show | Outputs aren't saved yet | Connect again and set each universe's Output and Stream again |
| Lights flicker or answer slowly | Two programs send to the same node, or a busy Wi-Fi network | Close the other lighting software; use a cable for the network |
Fixtures and GDTF
| What you see | Likely cause | Fix |
|---|---|---|
| A light isn't in the fixture list | Not in the built-in library | Search part of its model name (aura); else import its GDTF file (Fixture Library) |
| A GDTF import shows an error | The file isn't a valid GDTF fixture | See the import messages; download the file again |
| Missing fixtures when opening a show | The show uses GDTF fixtures this device hasn't imported | Import their .gdtf files in the popup, or Open anyway (details) |
| Imported fixtures disappeared | The browser's site data was cleared, or it's another browser or a private window | Import the .gdtf files again |
| A fixture shows in the list but stays dark in the visualizer | Its dimmer or shutter is closed, or it was opened with Open anyway | Open its dimmer and shutter in the universe view; import its GDTF file and reopen the show |
| Patching is refused (out of universe bounds) | Not enough free addresses after the one you chose | Pick a lower Address, fewer fixtures, or another universe |
Saving and Showfiles
| What you see | Likely cause | Fix |
|---|---|---|
| My show is gone when I come back | It wasn't saved (Save Showfile Locally), or the browser's data was cleared | Open your last exported file; from now on export regularly (Showfiles) |
| Studio opens the demo show | First run, another browser, a private window, or cleared data | Load Showfile your exported show |
The * stays after saving | Something changed since | Save again with Ctrl+S |
| Load Showfile did nothing | The file isn't a Studio showfile | Pick a .json file exported from Studio |
| A shortcut does nothing on a Mac | Shortcuts use Ctrl, not Cmd | Use Ctrl (Shortcuts) |
Visualizer
| What you see | Likely cause | Fix |
|---|---|---|
| No 3D view, or a message that WebGL is needed | The browser or graphics driver has WebGL turned off | Enable hardware acceleration in the browser's settings, update the graphics driver, or try Chrome or Edge |
| The view stutters | The computer can't keep up at this quality | Set Quality to auto or low, lower Render resolution (Settings) |
| Beams don't show in the air | Haze Density is 0, or exposure is low | Raise Density and Exposure in Preferences → Visualizer |
| The camera is lost | It was moved far away | Scroll to zoom out; turn auto-focus on and select a fixture to fly to it |
Desktop App
| What you see | Likely cause | Fix |
|---|---|---|
| macOS says the app is from an unidentified developer or damaged | The build isn't signed | System Settings → Privacy & Security → Open Anyway (First launch) |
| Windows says it protected your PC | Same | More info → Run anyway |
| "Failed to start WSC Gateway" | The bundled gateway couldn't launch | Reinstall the app |
FAQ
Do I need lights to use Studio? No. The visualizer shows what your lights would do; you can program a whole show without them and plug the rig in later.
Which DMX interface should I buy? An Art-Net node: it's what Studio's gateway sends today. USB DMX interfaces aren't verified yet.
Can I use Studio and another lighting program together? Not on the same lights: both would send to them. Use one at a time.
Does the browser version work offline? Partly: once loaded, the show you're working on keeps running, but Studio downloads fixture descriptions when it first needs them, so patching new fixtures and reloading the page need the connection. The desktop app works offline.
Is my show sent anywhere? No. Your show stays on your computer (in the browser's or the app's storage, and the files you export).