Update Project DDFs DMXC3

	Article describe DMXControl 3.3.0 Stand: 02.03.2025	Update Project DDFs 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

The function Update Project DDFs is required whenever a DDF needs to be updated in an existing project after it has been modified or a bug has been fixed. This way, no manual changes need to be made to the project itself.

Usage

Prerequisites for Updating

Before the function can be called in DMXControl 3, the following points must be considered so that DMXControl 3 can recognize that a newer version of an already used DDF exists:

• The modification of the existing DDF or the correction of a bug took place in the directory "UserDevices". Any changes in the program directory may be lost due to missing write permissions or when the installer is run again.
• The filename of the DDF that was modified has not changed, and it matches the filename of the DDF used in the project. You can verify this in the settings for the respective Device.
• In addition to the content change in the DDF, the version number has also been adjusted, for example, from 1.0.1 to 1.0.2 for a minor change, or from 1.0.3 to 1.1.0 if the changes are more extensive.
• The modified DDF is technically correct, meaning the XML syntax is fundamentally correct, and only functions that are listed in the DDF Documentation have been added.

To verify that extensive changes to the DDF have been implemented correctly, it can be helpful to first load the modified version of the DDF in a new, empty project and, if necessary, cross-check it with the details in the manual using the Channel Overview.

Updating DDF

DDFs can only be updated in a project that is currently loaded in DMXControl 3. If the DDF is to be updated in other projects as well, these projects must also be loaded afterward, and the steps described below must be performed.

The function Update Project DDFs can be found under « File (Datei) »⇒ « Update Project DDFs ».

This opens the associated window, which lists all DDFs that are (possibly) outdated. In addition to the name of the DDF, the window also compares the version numbers of the DDFs between the project and the file system (Filesystem). This is the reason why the version number should always be adjusted when making changes. In the "Prefer file system" column, you can selectively choose whether a DDF should be updated in the project or not. After confirming the selection, you will receive a notice that the update of the DDFs will only occur after the project is saved and reloaded. Therefore, you should:

1. do exactly that to ensure the project can be loaded without errors with the updated DDFs and
2. save the project promptly after loading it to ensure the new DDFs are stored in the project file.

If problems arise when loading the project with the updated DDFs, you can open an older version of the project in the Project Administration.

Links and References