Choose the section matching your symptom. Change one thing at a time and start with one fixture. This helps distinguish a connection problem from a profile or venue-setting problem.

Guide version: development version dated 2 October 2026. This first version collects information known from source code and previous investigations. A checklist does not mean a symptom always has the same cause. Verified user findings will be added later.

1. Start with these checks

  1. Check the correct Project and Stage setup.
  2. Record any error message exactly before changing settings.
  3. Check the fixture's channel mode and start address against the application profile and universe.
  4. Check network connectivity and the receiver's address.
  5. Limit the test to one light and one function, such as dimming.

Save a working starting point before making broad changes. Do not delete a project or rebuild a profile solely because of one symptom.

Remember: lighting tests and LIVE can control real devices. STOP and BLACKOUT intentionally leave path lights on while output is functioning. Manual effects are separate controls.

2. LIVE will not start or the audio meter does not move

Empty project or stage

LIVE is not an audio-only test button. Starting requires a configured lighting rig. If the application reports that no Art-Net fixtures or enabled WLED effects are configured, create the required setup first.

Close Stage Setup before starting the show. Starting is blocked while the editor is open.

Computer music is not detected

  1. Confirm music is actually playing.
  2. Check the music application's playback device: speakers, headphones or a USB interface, for example.
  3. Select the matching SYSTEM AUDIO (WASAPI) entry under Audio input.
  4. Once the rig is ready and LIVE is running, check Audio input level.

If music switches to another playback device, the previously selected SYSTEM AUDIO source may no longer capture it. Restart LuDioMix if the device was connected after the application started.

Mixer or audio interface input is missing

Known development-version limitation: on Windows, device enumeration may return only SYSTEM AUDIO sources and omit direct audio interface inputs. A missing INPUT option does not then prove a cable or driver fault.

First check the interface's or Windows' input meter to confirm that mixer audio reaches the computer. A missing direct input selection in LuDioMix is a separate software limitation, not fixed by this guide.

Audio clips

Reduce level at the audio source or interface input. Attenuating later in software cannot repair a signal already clipped upstream. Check application Input gain too if needed.

3. A light stays dark

  1. Check that the physical light is added to the current stage. A saved Fixture Editor profile alone is not enough.
  2. Check the fixture's DMX channel mode and start address.
  3. Check receiver, universe and Art-Net connectivity.
  4. Check the profile's Dimmer and required colour channels.
  5. Check whether the device needs a shutter-opening value.

A common cause: shutter value 0 closes the beam even when dimmer and colours are active. Set an opening value using Fixture Editor's Add channel default, following the actual device's DMX table.

Channel 11 / value 48 in the Fixtures guide is an example from one table, not a universal shutter value. Another device may use that channel for something entirely different.

If the light works with a calibration auxiliary channel but not during the show, check the permanent profile default. Additional calibration channels is for temporary testing only.

4. The wrong function responds or two lights act together

Wrong channel function

First check the device's channel mode: the same channels may serve different functions in 8CH and 16CH modes. Match the profile's DMX channel count and definitions to the active mode.

Also check that profile Channel fields contain fixture-relative numbers, not the stage's absolute DMX addresses.

Overlapping addresses

A 25-channel light starting at 101 occupies 101–125. Another independently controlled light must not accidentally start within that range in the same universe.

Sort by DMX start helps inspect addresses. It only sorts the list; it does not change addresses.

Several functions share a channel

If shutter, strobe and pulse use different ranges on one channel, do not map its entire 0–255 range to dimming. Limit DMX min / DMX max to the intended function.

5. A moving head moves incorrectly

Speed works backwards

Check Fixture Editor's Movement speed direction:

  • Higher DMX value = faster movement: larger numbers increase speed.
  • Higher DMX value = slower movement: larger numbers decrease speed.

Do not try to fix speed by swapping left and right movement limits.

Direction or limits do not match the stage

Check calibration on the actual light. Left and Right use the viewpoint from the audience towards the stage. Their DMX numbers may be in either numerical order.

Confirm you are editing the correct physical light, its Location is correct and its home position lies in the intended area. A copied stage may still contain the previous venue's calibration.

Slow movement looks stepped

Known limitation: Pan fine and Tilt fine can be assigned, but the automatic show holds them at zero. True 16-bit movement control is not yet used. Changing movement limits may therefore not eliminate stepping.

6. The gobo does not rotate or shows the wrong pattern

  1. Check Gobo ranges: Spot, Pattern and any Pattern shake ranges must use the correct gobo-wheel channel.
  2. Check the separate Rotation channel, Stop rotation, Rotation slow and Rotation fast.
  3. Ensure Slow and Fast belong to the same rotation direction. Their numbers may ascend or descend.
  4. Ensure the normal Pattern range does not include continuous wheel scrolling or another special function.

No rotation may be intentional: an open Spot, calm scene, pause, inactive light or stopped state does not start gobo rotation. Rotation applies to an active pattern gobo during a rhythmic music passage.

The stop value is not necessarily zero. Follow the fixture manual. Full independent control of two gobo wheels is not yet supported.

7. Colours are wrong or a colour test changes several lights

First check RGB, White, Amber and UV channel numbers. Colour calibration cannot fix an incorrect channel assignment.

For a colour-wheel fixture, check Color Calibration → Named Color wheel values, the Available selections and exact Color wheel DMX values. Use stable-colour ranges, not rainbow-rotation ranges.

Changing several lights during testing is intentional: colour calibration tests matching-profile lights in the current stage. Saved calibration belongs to the profile and may affect other stages in the same project.

Load universal defaults is a starting point, not a measurement for your fixture model. Check the actual colours and save with Save color calibration.

8. STOP or BLACKOUT does not turn everything off

Check whether the remaining light is an Other-area path light. Path lights intentionally remain on in STOP and BLACKOUT while lighting output is working.

Manual effects remain available too. Check Effect buttons and its Push and Release values if a device stays in the wrong state after release. Release does not automatically mean zero.

If an ordinary show light unexpectedly stays on, record which light, operating state and channel value it needs to turn off. Do not assume zero on every channel always means the intended device behaviour.

9. WLED or phone remote control does not respond

WLED

  1. Check device power, network connectivity and current IP address.
  2. Try opening WLED's own control page in the computer's browser.
  3. Compare that address with the current stage's WLED settings.
  4. Check enabled effects and that settings were saved.

If the control page cannot open, investigate network connectivity first. If it opens but LuDioMix does not control the light, check device and effect definitions in the application. The previous venue's address may have been copied into this stage.

Phone remote control

  1. Confirm LuDioMix is running on the computer.
  2. Check that phone and computer share a local network. Guest-network isolation can block access.
  3. Open exactly the address on the REMOTE CONTROL line, including its port.
  4. If needed, use Enable Remote Control and approve the requested Windows firewall setting.

Remote LIVE cannot start while Stage Setup is open. Close the editor first. Do not disable the entire firewall to test connectivity.

10. A profile, stage or setting seems missing

  • A new project is empty: this is intentional. It does not inherit other projects' profiles, lights or stages.
  • An old profile is missing: check Project. After migration, existing equipment initially appears under Nykyinen kalusto (Existing rig), unless renamed.
  • The profile exists but the light is missing: add a physical light with Stage Fixtures → Add to stage.
  • A profile cannot be deleted: the current edited stage or another saved stage uses it. Check other venues too.
  • Movement calibration was not retained: Save calibration for selected light updates the editor. Also use Save stage setup.
  • Colour calibration was not retained: use Save color calibration; it is stored in the profile.
  • A change affects another stage: profiles are shared within a project. Profile channel or colour changes can affect all stages using them.

Edit data in one application window at a time. Separate running processes are not synchronised in real time.

11. A field or button is missing

Use horizontal scrolling in wide tables to reach right-hand columns or Remove buttons. Some sections depend on fixture type or location: not every calibration area appears for every light.

If a new function is absent entirely, check the application version. These guides describe the 2 October 2026 development version; older packages may lack those functions. Updating a guide page does not update the application. Restart LuDioMix after updating its code.

Normal and developer views share show and Stage Setup functions. Extra developer analysis does not mean a separate rig or separately maintained profiles.

12. Known limitations and reporting a problem

Current limitations

  • Windows direct audio inputs may be omitted when SYSTEM AUDIO sources are found.
  • A profile has one main Dimmer and Strobe function. A hybrid's spot and wash sections do not yet receive two fully independent controls.
  • The automatic show does not use Pan/Tilt fine for true 16-bit movement.
  • Full independent control of two gobo wheels is unavailable.
  • Focus and prism are not dedicated automatic functions. Fixed values can be set through channel defaults.
  • Project-package export and importing profiles from another project are not yet available.

Randomly changing DMX channels will not resolve these limitations. First determine whether the symptom matches a known limitation or a configuration problem.

Information that helps investigation

  • What did you try, and in what order?
  • What did you expect, and what actually happened?
  • The exact error message and a screenshot of relevant settings.
  • Application version, normal/developer view and state: editor test, LIVE, STOP or BLACKOUT.
  • Fixture manufacturer, model, DMX mode and the corresponding channel table.
  • Profile name, physical fixture start address and universe.
  • Control route: Art-Net, WLED or remote control. For audio issues, include the audio device and selected Audio input.
  • Whether it affects one or all lights, and whether the same steps reproduce it.

Do not send passwords, licence keys or other credentials. A verified solution can later be added here with device and version details.

Verification: this page collects behaviour and limitations known from current source code and earlier programmatic checks. No physical lighting or audio-interface tests were run while writing it. A new user report is initially recorded as an observation, not automatically as a proven cause or universal fix.