We proudly present: DMXControl 3.3.0 - the fourth release candidate!

In this news we can start directly with good news: we were finally able to find and fix the problem that prevented those of you who work with an Enttec USB Pro DMX interface from properly testing DMXControl 3.3.0. With our fourth release candidate, DMXControl 3.3.0 will now be able to address these DMX interfaces again as usual and therefore be able to send DMX values.


Furthermore, in the third release candidate there was a problem with starting the kernel in certain constellations if several graphics cards were installed in your system. The workaround last described in the forum with the specific assignment of which graphics card should be responsible for the kernel should also no longer apply with this new version.


Addition from 26.11.2024: In the past few days it has become apparent that the output via Art-Net is defective and does not allow the kernel to work properly - to the point that it no longer starts. So if you are dependent on Art-Net for testing and working with DMXControl 3.3.0, please stay with RC3.

What else has happened in the meantime?

Apart from the issues with the interfaces, there was no other general focus that was “tweaked”. Rather, there were numerous small things that were corrected and improved both as a result of feedback from you and during internal tests. Our bug tracker contained the following tickets, which have now been worked on for the fourth candidate release:

What should you look out for?

In our news about the release of DMXControl 3.3.0 RC1, we already gave you a few important tips along the way. These also apply with the release of this new version.

DMXControl 3

Final words

With the steady path towards the final version, the bug fixes and optimizations may not seem particularly extensive or even spectacular at first glance. However, they are another step towards the final release. We hope you continue to enjoy working with DMXControl 3.3.0. If you notice anything else, please ask or create a ticket in our bug tracker.


Yours :dmxclogo DMXControl team :dmxclogo