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

You've been waiting a long time. Here is the new version - at least as a public test version in advance. As mentioned in many places, the changes in the substructure were simply too extensive to test them fully in a shorter period of time.

Some background information

For this reason, for the upcoming version of DMXControl 3 we are now taking up something that we last did before the initial release of DMXControl 3.0.0 - at this point you will get access to the pre-release version, i.e. the first release candidate. Now that we have reached the point in the beta test that the main use cases have been considered and the version has run reliably in this area, we would now like to go into the broader masses with the public release candidate. After all, each of you uses the software differently - and it's possible that one or two problems will come to light that weren't even noticed during internal testing. So, if you are confronting with a problem, please enter it in our bug tracker - together with the log files and the project with which the error occurred. However, please also use the search function beforehand so that you don't have to go to the trouble of reporting an already known bug again. All in all, we hope to further stabilize DMXControl 3.3.0 together with you until the final release. The final release will therefore not (be able to) appear in the next few weeks.

Important notes on use

If you are going to use the Candiate release of DMXControl 3.3.0, please note the following information:

  • Be aware that errors can still occur during operation with this version. Our experience has shown that these always come to light when you don't need them. So, if you want to use RC1 in a productive environment, ideally have a backup solution in place. In addition, please test your existing projects thoroughly before using them live for the first time. If you don't do this and you're left in the dark, you'll have to take yourself to task - because we've given you plenty of tips along the way.
  • The projects you want to work with must be added to DMXControl 3.3.0 using the import procedure. If you then want to edit a project, from now on you will have to use the new Project Administration. You can no longer open projects directly from the drive.
  • The projects from DMXControl 3.2.3 are compatible so far. Manual adjustments are only required at some points:
    • Light shows with the "audio cue workaround" must be moved to the timecode player. The audio scenes no longer internally return timecode to the cuelist.
    • The gobo affinity must be recreated due to the new workflow if you have used it at all.
    • You currently must recreate all executor pages and fill them with life.
  • However, it may happen that some old projects cannot be loaded. This may be due to outdated DDFs. We have further expanded the checking mechanisms. We therefore recommend that you check the DDFs you are using by inserting them into a completely new project. If you are still unable to load them, we require a ticket in the bug tracker with the project and the associated log files in order to identify the problem more precisely.
  • Working with multiple GUIs on one project is only included as an experimental function in DMXControl 3.3.0 (even after the later final release). The focus in the beta test was on a 1-1-1 setup to cover the main use case. How you distribute the kernel, Umbra and the GUI does not matter.
  • When starting DMXC 3.3.0 in more complex network configurations, the individual program parts may not connect automatically. Possible influencing factors here are, for example, active VPN connections. In this case, you may need to "push" the program manually. We would be particularly grateful for detailed feedback in this area in order to further improve the process.
  • Some parts of DMXC 3.3.0 require new versions of the .net framework. This is generally installed via the installer. However, the beta test has already shown that although the desired versions are recognized by the regularly delivered updates via Windows Update, they are still not up to date.If triggering the Windows updates is not sufficient, the latest versions of .net must be installed manually. The links are attached at the end of the news.
  • We do not guarantee across the board that projects created or edited with the RC will also work in the final version. Our focus is on compatibility within the scope of what is technically possible when switching from an official final release to the next higher version.

The final, probably most important note: do not simply delete your old projects from DMXControl 3.2.3 after you have imported them into DMXControl 3.3.0. Although DMXContol 3.3.0 will continue to work with a copy during the import, you may notice later that something doesn't quite work in the new version. Projects created and edited in DMXControl 3.3.0 can no longer be opened in DMXControl 3.2.3 - they are not downward compatible. However, it is generally possible to install both versions in parallel on your PC and then use them alternately. If you want to be on the safe side here, install DMXControl 3.3.0 in a different directory and use the option of separating your user data with the help of an environment variable.

DMXControl 3


All four packages must be installed on the PC! However, the installer usually takes care of this.

Our closing words

Finally, we hope you enjoy the first release of DMXControl 3.3.0! We hope you enjoy this new (preliminary) version and look forward to a constructive exchange - whether general questions or joint bug fixing and improvements.

Your :dmxclogo DMXControl-Team :dmxclogo

PS: If you need another overview of the new functions, take a look at our livestreams on our YouTube channel. There we have already shown you in many places how individual points work. We will gradually create corresponding documentation in our wiki - especially on the points mentioned above.