Troubleshooting (General Information) DMXC3

	Article describe DMXControl 3.3.1 Stand: 11.11.2025	Troubleshooting (General Information) DMXC3
Table of contents A Autoprepare B Bedienoberfläche (GUI) Blackout Bühnenansicht (Stage View) C Chat D Dateien im Projekt (Project Files) DDFs im Projekt aktualisieren (Update Project DDFs) DMX-Schnittstellen (DMX-Interfaces) Device Manager (Add Device Dialog) DDF Library DMX-In DMX-Out-Zuordnung (DMX-In DMX-Out-Mapping) E Effekte und Filter (Effects and Filters) Effektvisualisierung (Effect Visualizer) Einfrieren (Freeze) Eingangszuweisung (Input Assignment) Executor Executor Seite (Executor Page) F Fanning Farbliste (Color List) G Gerät (Device) Gerätegruppe (Device Group) Gerätesteuerung (Device Control) Gobo-Ähnlichkeiten (Gobo Affinity) Goboliste (Gobo List) Group Handling H Hardware Abstraction Layer (HAL) Hauptschalter (Main Switch) Hervorheben (Highlight) HTP-, LTP- und LoTP-Mischung (HTP-, LTP- and LoTP-Mixing) K Kanalübersicht (Channel Overview) Kernel (Server) L Lastmanagement (Electricity) Launcher M Macroboard Master Matrix MIDI-Verwaltung (MIDI Manager) N Netzwerkfunktionalitäten O Ordnungsliste (Item List) P Panel-Konzept Patching Plugin-Verwaltung (Plugin Manager) Positionsliste (Position List) Preset Programm- und Projekteinstellungen (Application und Project Settings) Programmer Programmer Filter Projektverwaltung (Project Administration) Projektexplorer (Project Explorer) Projektaufgaben (Project ToDos) Protokolldateien (Log Files) R Radix Relative und absolute Werte (Absolute and Relative Values) S Softdesk Softdesk Designer Steuerungsfenster (Control Panel) Szenenliste (Cuelist) Szenenlistegruppe (Cuelist Group) Szenenzeitkonfiguration (Cue Timing Editor) T Timecode Player Tracking U Umbra

Some issues that occur when using DMXControl 3 can be systematically resolved by the user at the end—especially when the software doesn't behave as expected, as it did previously. This article outlines the most frequently reported problems and describes how to troubleshoot them.

If errors occur in the software or a function is missing, it would be appreciated if these could be reported as a new ticket in our Bugtracker.

Some of the issues mentioned below are known and will be addressed in a future version. An overview of these points can be found under Known Bugs.

Installation and (first) start

Umbra and / or kernel do not start

Problem If you start the kernel and / or Umbra via the launcher or via the direct shortcuts in the start menu, the console window disappears again after a short moment. The corresponding application is then no longer listed in the Task Manager, and the launcher does not report “Active” or “Active (hidden)” under the respective program section.

Solution All four packages must be installed on the PC. Usually, the installer takes care of this. In some situations, however, the automatic installation may not be possible, or the installer may not recognize the installed packages correctly. A typical case is when there was no active Internet connection available during installation. If Kernel and / or Umbra do not start, you must manually install the four packages listed below.

• .NET 6 Desktop Runtime (32bit): https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-x86.exe
• .NET 6 Desktop Runtime (64bit): https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-x64.exe
• ASP.NET Core 6 (32bit): https://aka.ms/dotnet/6.0/aspnetcore-runtime-win-x86.exe
• ASP.NET Core 6 (64bit): https://aka.ms/dotnet/6.0/aspnetcore-runtime-win-x64.exe

After installation, it is recommended to restart the PC. The installer for DMXControl 3 does not need to be run again after installing the packages. The program data required for DMXControl 3 is then already available.

Working "within" DMXControl 3

Devices stay dark

Problem In the Stage View, multiple Devices or even Device Groups are selected, and their functions are shown in the Device Control or the Control Panel. Regardless of how the devices are controlled in the project, whether through device control or various control windows, they remain dark in three places. This means there is no response:

• in the Stage View.
• in the Channel Overview, where the DMX channels for dimmers and/or the color of the respective devices remain at 0.
• in reality, even though the DMX Interfaces are activated and otherwise working properly.

The only time the devices respond is when manually controlled via the Channel Overview.

Cause In DMXControl 3, there are several factors that can cause a device to remain "dark," and multiple of the mentioned issues may occur simultaneously:

• The Blackout function
• The Freeze function, once activated, prevents the device from turning on again.
• The devices have both a dimmer and a shutter, and the shutter has not yet been opened.
• The Group Master.
• The Grand Master.
• Active Cuelists with a higher priority than the Programmer.
• The Blind function in the Programmer, which ensures that the values set in the programmer are not output to the DMX Interfaces or the Stage View.
• Various modules, including the DMX Interfaces, are disabled via the Main Switch.

Solution This issue typically occurs when programming a new lighting scene and less often when the show is running. To reset everything to 0, follow these steps:

1. Stop all Cuelists using the [Stop all cuelists] button.
2. Reactivate the DMX Interfaces using the Main Switch.
3. Clear the Programmer using the [Clear] button.
4. Open the Programmer and disable the [Blind] option. The default setting is [All].
5. Check if the Blackout is disabled.
6. In the window showing all Master, set both the Grand Master and the Group Master for the affected devices back to 100%. Be sure to observe the dependencies between group masters, as described in the relevant article.
7. When trying a new lighting scene, both raise the dimmer and open the shutter if the devices have both functions. This can be done manually or by pressing the [Lumos] button in the Control Panel for intensity.

If these four steps do not resolve the issue, a restart (if possible) might help as it also resets everything to 0. After loading the project, check if the Group Master slider is set to a very low brightness value.

Cuelist won't start

Problem A properly programmed Cuelist doesn't start, despite multiple presses of the [Go] button or pressing a linked button in the Softdesk.

Cause For each Cuelist, the fade factor (Fade factor / Timing) can be individually set. Due to various external influences—whether intentional or unintentional—the value of the associated slider has been set to 0.

Solution Open the affected Cuelist(s) from the Project Explorer and set the fade factor (Fade factor / Timing) slider back to a value greater than 0. If the Cuelists are triggered via a Softdesk, a MIDI controller, or similar devices, you can also add a slider in the Input Assignment to centrally control the fade factor.

Last Softdesk changes disappear

Problem The custom design of a Softdesk is not saved, or the last changes disappear when the project is reloaded.

Cause The command to save the last changes to the Softdesk is only transmitted when the Softdesk Designer is closed.

Solution To ensure all changes to the Softdesk are properly saved, always close the Softdesk Designer before saving the project. For "pure" live operation with the Softdesk, it is recommended to open the Softdesk only in display mode. This also ensures that menu elements for selecting and adjusting the controls are completely hidden, preventing accidental changes.

Various windows not displayed

Problem You receive a project from another user or switch PCs while working on the project. On the new PC, not all windows can be opened because the monitor size and resolution appear to differ.

Cause In each project, it is precisely recorded where each window was last displayed on the screen. This is based on the available screen resolution. When loading a project and confirming that the stored window layout should be used, the last local settings are overwritten.

Figure 1: Layout prompt when opening a project

Solution To bring lost windows back into the main screen display area, go to the following menu entry: « Settings »⇒ « Layout »⇒ « Move floating windows to primary screen » (see also Figure 2). This function moves all windows back into the main screen display area. Alternatively, you can load a custom window layout you've created. This can be done through the main menu « Settings »⇒ « Layout »⇒ « Load... ». In the following example, two saved window layouts named Club-Setup and Programming-Setup are stored in the loaded project.

Figure 2: Reset window layout and load custom window layouts

If this function doesn't yield the desired result, you can reset the current window layout through the entry « Settings »⇒ « Layout »⇒ « Reset window layout ». The default arrangement will be loaded as seen after the first start of DMXControl 3. This is also covered in the article User Interface.

DMX Output

Art-Net output not working

Problem The Art-Net output cannot be activated. The corresponding rows in the DMX Interfaces table remain grayed out even though the checkboxes for "Interface enabled" and "DMX-Out enabled" are checked.

Cause The PC might be missing an updated version of the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019.

Solution Manually install the 32-bit version (x86 version) of the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019. After installation, DMXControl 3 needs to be restarted.

Download link: https://support.microsoft.com/de-de/help/2977003/the-latest-supported-visual-c-downloads