English DMXC-Wiki - User contributions [en]

Category:Tutorials DMXControl 2

2025-03-04T23:05:18Z

Jkuehn: Created page with "Category:Tutorials Category:DMXControl 2 de:Kategorie:Tutorials_DMXControl_2"

[[Category:Tutorials]]
[[Category:DMXControl 2]]
[[de:Kategorie:Tutorials_DMXControl_2]]

Category:Tips

2025-03-04T23:02:45Z

Jkuehn: Created page with "This category lists tips for DMXControl that can help you when using DMXControl and other DMXControl-related components."

This category lists tips for DMXControl that can help you when using DMXControl and other DMXControl-related components.

Change over from DMXControl 2 to DMXControl 3

2025-03-04T23:02:15Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0
| Content = x
}}

Switching from one software to another or upgrading to a newer version often presents several challenges. In the case of transitioning from DMXControl 2 to DMXControl 3, these challenges can be summarized as follows:
* DMXControl 3 operates differently in several areas compared to DMXControl 2, meaning you will need to start learning how to use it from scratch.
* You have a functioning system with DMXControl 2 that you are familiar with, but now you are faced with a new and seemingly complex system (simply because you are not yet accustomed to it).

This article aims to outline the main differences between DMXControl 2 and DMXControl 3 and to summarize and answer the frequently asked questions in the forum about transitioning from DMXControl 2 to DMXControl 3. By the end, you will hopefully feel more comfortable navigating DMXControl 3.

To address any concerns upfront: although DMXControl 3 may initially seem like a complete reinvention, there is no need to worry. Once you take a second look—perhaps after your first few attempts—you will realize that DMXControl 2 and DMXControl 3 share many similarities. Some features are just accessed differently or found in new locations.

{{Manual Box | en | Important | This article reflects the current implementation status of '''DMXControl 3.3.0'''. Technical changes due to ongoing development are possible at any time.}}

= Compatibility =
Projects from DMXControl 2 are not compatible with DMXControl 3. This also includes DDFs, which must be completely recreated due to the changed requirements. {{Manual Reference |arrow| More information on creating DDFs, including examples, can be found in the documentation section for {{Manual Windowcaption|[[DDF DMXC3|DDFs for DMXControl 3]]}}.}}

Extensive compatibility is not necessary because many improvements allow effects to be recreated in just a few minutes. In some areas, entirely new workflows have been introduced, based on and even surpassing the concepts of professional software. However, some tools from DMXControl 2, such as the audio player and the text book, have not yet been integrated into DMXControl 3. Furthermore, plugins (both output and regular plugins) are not compatible due to the modified interfaces.

= Migration Guide =
== General Recommendations ==
Every DMXControl 2 user should consider their own migration strategy based on the tables in the section [[Switching from DMXControl 2 to DMXControl 3#Version Comparison|Version Comparison]]:
* You can run DMXControl 2 and DMXControl 3 in parallel on the same PC, allowing you to gradually familiarize yourself with DMXControl 3.
* Gradually build a working setup in DMXControl 3. With parallel operation, you always have a fallback project that works as expected. However, don't overdo it at first—start slowly.
* If you are using a large number of devices, you will quickly benefit from features like {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} and the associated {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}} in DMXControl 3.
* Even if you still rely on DMXControl 2 for tools like the audio player, which is not yet available in DMXControl 3, start familiarizing yourself with DMXControl 3. This will help you understand the basic workflow and allow you to create small test shows. When the timecode player becomes available, you will only need to learn that specific tool.

{{Manual Box | en | Attention | As indicated in the system requirements, Windows 8.1 is the last officially supported operating system for DMXControl 2. While DMXControl 2 may still work on Windows 10 and Windows 11, this is at your own risk. Future updates to these operating systems may render DMXControl 2 unusable. Since DMXControl 2 is no longer being developed, no further updates will be provided if problems arise.}}

== Comparison of Key Features ==
A major difference to get used to: DMXControl 3 does not work with channels but rather with device functions and property values. This makes it crucial for DDFs (at least for required functions) to be accurately implemented. In DMXControl 2, you could manually adjust values via the channel overview. In DMXControl 3, this is no longer possible because the channel overview does not save values. However, the big advantage is that you can select and adjust multiple devices of any type simultaneously.

Another key difference: {{Manual Windowcaption|[[Effektsequencer DMXC2|Effects]]}} in DMXControl 2 are now called {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} in DMXControl 3. These combine the cuelists and effects you know from DMXControl 2. You use cuelists to store all your lighting effects, such as chases and movements. The workflow is quite similar to DMXControl 2. You configure your fixtures in the {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}, click {{Manual MenuText|Add Cue}}, select the device functions to save (similar to channel selection in DMXControl 2), and confirm with {{Manual Buttons|OK}} to insert a {{Manual Windowcaption|Cue}} into the {{Manual Windowcaption|Cuelist}}.

Additionally, DMXControl 3 includes {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}—mathematical functions like sine and sawtooth waves. These can be applied to almost any device property and adjusted live. Try dragging a {{Manual Objectcaption|1D Effect}} onto the dimmer of a {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}} to see how it responds.

== Initial Approach ==
For your first steps in DMXControl 3, start by adding some devices to your project. They don’t need to match your actual equipment. Ensure that device groups are automatically created during this process. Next, try creating some lighting moods by adjusting settings via the {{Manual Windowcaption|[[Control Panel DMXC3|Control Panel]]}} and {{Manual Windowcaption|[[Device Control DMXC3|Device Control]]}}. To reset, use the {{Manual Buttons|Clear}} button in the quick access bar.

After creating a few lighting moods, try saving them. In the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}}, create a new {{Manual Windowcaption|Cuelist}} and open it with a double-click. If a lighting mood exists in the {{Manual Windowcaption|Stage View}}, click {{Manual MenuText|Add Cue}} to save it. Clear the stage view and test playback using the {{Manual MenuText|Go}} button in the {{Manual Windowcaption|Cuelist editor}}.

{{Manual Box | en | Reference | ''A more detailed quick-start guide for DMXControl 3 is available in the '''[[Quickstart Guide DMXC3|Quickstart Guide]]'''.''}}

== Version Comparison ==
After describing the workflow in DMXControl 3, the following section provides a detailed comparison of DMXControl 2 and DMXControl 3.

== Environment ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Supported DMX Interfaces'''
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| Some DMX interfaces, such as output via Art-Net, offer additional features in DMXControl 3.
|-
| '''DDFs (Device Library)'''
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. Display of control elements in the DDF is configurable for each individual DDF. {{No|-}} DDFs must be downloaded manually.
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. DDFs are significantly simplified. They now only contain the pure device definition. The uniform display of the control elements is handled by DMXControl 3 itself, where all functions are displayed in real values. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF DMXC3|DDF Documentation for DMXC3]]}}.}} {{Yes|-}} DDFs from the DDFLibrary can be downloaded directly into DMXControl 3 and used in the project. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF Library DMXC3|DDF Library]]}}.}}
| In the {{DMXCWebLinks|DDFLib}}, fully functional DDFs can be provided for both DMXControl versions, each with different DMX modes. {{Manual Reference | warning |DDFs from DMXControl 2 cannot be used in DMXControl 3.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | System Requirements and Information}}

| '''Operating System'''
| '''Up to''' and including '''Windows 8.1'''.
| All Windows versions '''from Windows 7''' onwards.
| For detailed system requirements for DMXControl 3, see {{DMXCWebLinks|DMXC-HP|dmxcontrol-3/systemrequirements.html| Overview on DMXControl Homepage}}.
|-
| '''Program Language'''
| {{Yes|-}} German {{Yes|-}} English
| {{Yes|-}} German {{Yes|-}} English {{Yes|-}} French {{Yes|-}} Japanese
|
|-
| '''Documentation'''
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Handbuch_DMXControl_2 German Manual] {{Yes|-}} '''[[Manual_DMXControl_2|English manual in draft form]]''' {{Yes|-}} '''[[DDF DMXC2|DDF Documentation]]''' {{Yes|-}} Plugin interface
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Tutorials_DMXControl_3 German Tutorial] {{Yes|-}} '''[[Tutorials DMXControl 3|English tutorial]]''' {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Inhalts%C3%BCbersicht_Hauptprogramm_DMXC3 German Manual] {{Yes|-}} '''[[Manual_DMXControl_3|English Manual]]''' {{Yes|-}} '''{{DMXCWebLinks|YouTube|DMXC3 Playlists}}''' {{Yes|-}} '''[[DDF DMXC3|DDF Documentation]]''' including extensive examples and tutorials {{No|-}} Plugin interface
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Work Environment}}

| '''Hardware Environment'''
| {{Yes|-}} Single PC. {{No|-}} No distributed system.
| {{Yes|-}} Single PC. {{Yes|-}} Distributed system possible, where the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[Umbra DMXC3|Umbra]]}} can run separately from the {{Manual Windowcaption|[[GUI DMXC3|GUI]]}}.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Multi-User'''
| {{No|-}} Single user only.
| {{Yes|-}} Multiple GUIs in a multi-user environment. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Server-Client Concept DMXC3|Server-Client Concept]]}}.}}
| For effective work, do not use a WLAN connection between the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[GUI DMXC3|GUI]]}}.
|-
| '''Performance'''
| {{No|-}} Requires a CPU with a high clock rate on one core for using 2 DMX universes.
| {{Yes|-}} Due to efficient programming, even mid-range PCs can output multiple DMX universes. The separation of {{Manual Windowcaption|[[GUI DMXC3|GUI]]}} and {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} provides additional safety in case of an interface failure.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Project Management'''
| {{No|-}} Only manual, as required project data is stored "open" in a directory and DDFs are stored independently of the project in the installation directory. {{No|-}} Switching PCs requires manually sorting various files, including DDFs, DMX-In configuration, MIDI configuration. {{No|-}} Only simple automatic project backup without version history.
| {{Yes|-}} All data required for the project, including DDFs, is stored in a project file. {{Yes|-}} Only the project file is needed for switching PCs. {{Yes|-}} Automatic saving including storing a certain number of previous project versions.
| Project management in DMXControl 3 handles the complete organization of projects including the associated versions. Searching for storage locations is unnecessary. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Project Administration DMXC3|Project Management (Project Administration)]]}}.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | External Interfaces and Control}}

|-
| '''DMX Output'''
| {{Yes}}, maximum 2 DMX universes.
| {{Yes}}, up to 16 DMX universes, depending on PC/laptop performance.
|
|-
| '''DMX-In'''
| {{Yes}}, but a maximum of 1 DMX universe.
| {{Yes}}, 2 DMX universes.
|
|-
| '''Keyboard Control'''
| {{Yes}}, but only simple key assignments are possible.
| {{Yes}}, including support for multiple banks and key combinations.
|
|-
| '''MIDI Interface'''
| {{Yes}}, available.
| {{Yes}}, available, including native support for multiple MIDI controllers without additional tools.
|
|-
| '''Joystick Control'''
| {{Yes}}
| {{No}}, but an alternative control option is available via the 3Dconnexion plugin.
|
|-
| '''Macroboards'''
| {{No}}
| {{Yes}}, available, including support for multiple macroboards like Elgato Stream Deck. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stream Deck DMXC3|Stream Deck]]}}.}}
|
|-
| '''Timecode''' (Protocol)
| {{Yes}}
| {{No}}, but coming soon.
|
|-
| '''OSC Interface'''
| {{Yes}}, available via plugin.
| {{No}}
|
|-
| '''Terminal Interface'''
| {{Yes}}
| {{No}}, no replacement planned at this time.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Feature Extensions}}

| '''Plugins'''
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}}.
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}} or user plugins in the {{DMXCWebLinks|Forum|Board|161|Plugins and Addons}} section.
|
|-
| '''Plugin Interface'''
| {{Yes}}
| {{Yes}}
| The interface in DMXControl 3 is not compatible with DMXControl 2.
|}

== Functionality ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment

{{DMXC3 Manual-Tablesection | S1 | 4 | Prepare Project}}

| '''Personal Device Favorites'''
| {{No|-}} Selecting frequently used devices is not possible.
| {{Yes|-}} In the dialog {{Manual Windowcaption|[[Device Manager DMXC3|Add Device]]}}, you can select devices from the available list that are used frequently.
|
|-
| '''Groups (of Devices)'''
| {{Yes|-}} Supported in a simple form for quick selection of devices in the stage view.
| {{Yes|-}} {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} are a core concept of DMXControl 3 and are intelligently designed.
| Users with many devices performing the same lighting scenes have better tools with DMXControl 3.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Hardware Abstraction (HAL)'''
| {{No|-}} Limited abstraction of DMX values via DDFs.
| {{Yes|-}} {{Manual Windowcaption|[[Hardware Abstraction Layer (HAL) DMXC3|HAL]]}} is a core concept of DMXControl 3, providing complete abstraction of all device functions. Working directly with DMX values is no longer necessary.
| Users with similar (but not identical) devices can still program them uniformly in DMXControl 3.
|-
| '''Channel Overview'''
| {{Yes|-}} Available.
| {{Yes|-}} Available independently of DMX and includes highlighting of the selected device. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Channel Overview DMXC3|Channel Overview]]}}.}}
|
|-
| '''Graphical Stage View'''
| {{Yes|-}} Available as a rough orientation aid in the lighting setup.
| {{Yes|-}} Similar to DMXControl 2 but with extended animation possibilities like gobo projection. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}.}}
|
|-
| '''Visualizer'''
| {{Yes|-}} Supported via Magic 3D EasyView.
| {{Yes|-}} Supported via Magic 3D EasyView and other external visualizers accessible via Art-Net.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Saving Cues}}

| '''Cues'''
| {{Yes|-}} Supported.
| {{Yes|-}} Supported in an enhanced form, where there is no distinction by cue type anymore. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Cues are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Fanning'''
| {{No|-}} Only partially possible with a workaround using motion cues.
| {{Yes|-}} Explicit fanning support through special command syntax at various points like device functions, parameters in effects, fade times for cues, etc. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}}}}.
|
|-
| '''Relative Values'''
| {{No|}}
| {{Yes|-}} All numerical values for device functions such as dimmers, position, gobo rotation, etc., can be saved as relative and be calculated with other values during execution. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Absolute and Relative Values DMXC3|Absolute and Relative Values]]}}.}}
| The device function color is not included in the current version due to its complexity.
|-
| '''Motion Cues'''
| {{Yes|-}} Supported.
| {{Yes|-}} Motion cues are implicitly included in the "new" cues and effects and can be applied to all numerical device functions. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}}}.
| Motion cues from DMXControl 2 are not compatible with DMXControl 3.
|-
| '''Effects, Chasers'''
| {{Yes|-}} Supported, partially via tools like the running light generator or motion cue within the {{Manual Windowcaption|[[Chasers_tool_DMXC2|Chasers Tool]]}}.
| {{Yes|-}} Supported through the {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}} function with more effective definition options via various parameters, predefined effect library.
| Effects are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Dynamic Manipulation of Values'''
| {{No|}}
| {{Yes|-}} There are four types of {{Manual Windowcaption|[[Master DMXC3|Masters]]}} available, each of which can dynamically manipulate values of a function in a cue when the corresponding cuelist is executed. {{Manual Reference | arrow |For detailed explanations, see {{Manual Windowcaption|[[Master DMXC3|Master]]}}.}}. It does not matter whether it is a {{Manual Windowcaption|[[Cuelist DMXC3|Cue]]}} or an {{Manual Windowcaption|[[Effects and Filters DMXC3|Effect or Filter]]}}.
| All {{Manual Windowcaption|[[Master DMXC3|Masters]]}} can be addressed and modified live through various means like {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}, {{Manual Windowcaption|[[MIDI DMXC3|MIDI]]}}, and more using {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}.
|-
| '''Presets'''
| {{Yes|-}} Implicitly via the cue library.
| {{Yes|-}} Direct support as a programming element for advanced users. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Preset DMXC3|Preset]]}}}}.
| The preset concept is not compatible with DMXControl 2.
|-
| '''Command Concept'''
| {{Yes|-}} Only for simple dependencies, similar to an automated mouse click. {{No|-}} Logical, mathematical, or status-dependent commands cannot be executed.
| {{Yes|-}} In simple form within cuelists. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}}}. {{Yes|-}} Cross-linking of actions with various logical, mathematical, or status-dependent dependencies across all program functions using the Input Assignment. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}}}.
| Commands in DMXControl 2 are not compatible with DMXControl 3, as the capabilities in DMXControl 3 are much greater.
|-
| '''Command Line'''
| {{Yes}}
| {{No}}
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Execute Show}}

| '''Cuelists'''
| {{Yes|-}} Supported, multiple instances can be executed.
| {{Yes|-}} Supported including the possibility to execute multiple instances simultaneously. Additionally, extended trigger options for the execution in the cuelist are available. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Cuelists are the main control tool in DMXControl 3. The various "implicit" cuelists from different tools in DMXControl 2 are unified.
|-
| '''Value Mixing in Cuelists'''
| {{Yes|-}} HTP and LTP supported, but setting is global for the entire project.
| {{Yes|-}} Extended support with three modes (LTP, HTP, and LoTP). Definition of mixing behavior individually for each cuelist. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3|HTP-, LTP- and LoTP Mixing]]}}.}}
|
|-
| '''Command Box'''
| {{Yes|-}} Supported.
| {{Yes|-}} Developed further as Softdesk and offers completely customizable user interface with numerous control elements. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}}}.
| Softdesk is not compatible with the Command Box.
|-
| '''Master'''
| {{Yes|-}} Supported in simple form: two Grand Masters and one Speed Master for the entire project.
| {{Yes|-}} Available in an advanced form. In addition to the {{Manual Windowcaption|[[Grand Master (Master) DMXC3|Grand Master]]}}, you can create a {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Master]]}} for each {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}}. 
| By creating your own {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Masters]]}}, you can control the brightness of different groups of devices in a much more detailed manner.
|-
| '''Submaster'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available in an advanced form of the {{Manual Windowcaption|[[Executor DMXC3|Executors]]}}, for example, to control {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}. In a future version, the {{Manual Windowcaption|[[Master DMXC3|Masters]]}} will also be available in Executors.
| Direct control of DMX channels is no longer available due to the fundamentally different concept of DMXControl 3.
|-
| '''Audio Player'''
| {{Yes|-}} Supported.
| {{Yes|-}} Simple sound effects can be played within a {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}. For longer songs, the {{Manual Windowcaption|[[Timecode Player DMXC3|Timecode Player]]}} can be used.
| The Timecode Player in DMXC3 also allows playing excerpts of songs and fading them in and out.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Timecode Player'''
| {{Yes|-}} Supported, but only in simple form.
| {{Yes|-}} Offers the possibility to create complex music-synchronized light shows from multiple excerpts of songs with detailed and flexible display of audio frequencies. The light shows are built via the recording function of Executors or multiple parallel-played {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}.
|-
| '''Textbook'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available as a user plugin. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Textbook Plugin DMXC3|Textbook]]}}.}}
|
|
|-
| '''Manual Beat Control'''
| {{Yes|-}} Via BeatTool.
| {{Yes|-}} In an advanced form through the {{Manual Windowcaption|[[Speed Master (Master) DMXC3|Speed Master]]}}, which can be created in any number and specifically assigned to certain {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} or stored in {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}.
|
|-
| '''Automatic Beat Detection'''
| {{Yes|-}} Supported via Winamp plugin and external interfaces.
| {{Yes|-}} Supported via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}} and external interfaces.
|
|-
| '''Sound to Light'''
| {{Yes|-}} Via various plugins.
| {{Yes|-}} Via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}}.
|
|-
| '''Video Control'''
| {{Yes|-}} Via various plugins (Winamp, Beamertool) and Media Center.
| {{No|-}} Possibly via various plugins.
|
|-
| '''Scheduler (Task Scheduler)'''
| {{Yes|-}} Supported.
| {{No|-}} Not available as a separate module, but an alternative is available through cuelists with the trigger "Real Time Clock (RTC)".
|
|}

== Application Plugins ==
Some plugins are no longer required in DMXControl 3, as their functionality is already integrated. Others will not be available until updated by their authors. Plugins cannot be used without modification due to changes in the plugin interface and programming language.

{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Beamertool'''
| {{Yes}}, available.
| {{No}}
| The Beamertool for the Raspberry Pi can be used via Art-Net in both versions.
|-
| '''Matrix Control MadMaxOne'''
| {{Yes|-}} Available.
| {{No|-}} Will not be migrated.
| A new concept for matrix devices with corresponding effects is integrated into DMXControl 3. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Matrix DMXC3|Matrix]]}} and {{Manual Windowcaption|[[Radix DMXC3|Radial Matrix (Radix)]]}}.}}
|-
| '''PDA Control'''
| {{Yes}}, available.
| {{No}}
|
|}

[[Category: Tips]]

[[de: Umstieg_von_DMXControl_2_zu_DMXControl_3]]

Automatic creating of a running light

2025-03-04T22:59:17Z

Jkuehn:

== Scene Generator ==

Starting from version 2.11, DMXControl includes a scene generator/chaser generator. This is an assistant that allows you to create various basic scenes for devices in 3 steps. Wherever a scene can be created with the green plus sign, the entry "Automatically generated - From DDF" is now also offered in the context menu (right-click). When the scene generator is called from the scene list, the generated steps are entered as individual scenes in the scene list. All generated scenes also appear in the scene library.

{{Picture_with_subtitle|DMXC2_Manual_Szenenliste_AutomatischeSzenen.png|1|Automatic Scene Creation|center}}

=== Operation ===

The operation is demonstrated using the demo project configuration.

'''Step 1:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenGeneratorSchritt1.png|2|Scene Generator Step 1}}

From the list, the device is selected for which scenes should be generated.

 

'''Step 2:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenGeneratorSchritt2.png|3|Scene Generator Step 2}}

Here, the property is selected. In the right window, one or more values can be selected for which individual scenes will be generated later.

 

'''Step 3:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenGeneratorSchritt3.png|4|Scene Generator Step 3}}

Finally, additional devices of the same type can be selected. The generated scenes will then affect all selected devices.

 

'''Result'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenbibliothekErgebnis.png|5|Scene Generator Result}}

All generated scenes are stored in the scene library under the category "Automatically Generated".

== Chaser Generator ==

Starting from version 2.12, DMXControl includes a chaser generator. This is an assistant that allows you to create various chaser patterns in 3 steps. Wherever a scene can be created with the green plus sign, the entry "Automatically generated -> Chaser" is now also offered in the context menu (right-click). When the chaser generator is called from the scene list, the steps of the chaser are entered as individual scenes in the scene list. When the chaser generator is called from the effect sequencer, a new effect is created.

=== Operation ===

The operation is demonstrated using the demo project configuration.

'''Step 1:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_LauflichtGeneratorSchritt1.png|6|Chaser Generator Step 1}}

From the list, the devices are selected that should be included in the chaser. Attention: Only dimmer channels are displayed, so be sure to select the "Dimmer" type for chaser channels in the DDFs, even if, for example, a switch pack is used.

 

'''Step 2:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_LauflichtGeneratorSchritt2.png|7|Chaser Generator Step 2}}

Here, the pattern is selected. It can be previewed in the window. The base speed of the chaser can be set here. This can be modified later, for example, in the effect sequencer.

 

'''Step 3:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_LauflichtGeneratorSchritt3.png|8|Chaser Generator Step 3}}

Finally, the brightness is preset.

 

'''Result'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_EffektsequenzerErgebnis.png|9|Chaser Generator Result}}

This image shows the automatically generated effect "Chaser Pattern 2".

[[Category: Tutorials_DMXControl_2]]

[[de: Automatische_Erstellung_eines_Lauflichtes]]

Procedures functions (DDF-Syntax) DMXC3

2025-03-04T22:55:05Z

Jkuehn:

{{Manual Header
| Type = DMXC3 DDFs
| Version = 3.1.2
| LinkForwards = Procedures examples (DDF-Syntax) DMXC3
| TextForwards = Examples
}}

With the help of Procedures, functions are called that are usually not needed during live operation. Saving these functions in Cues is also not usually necessary. These include, for example, the complete reset of a device or individual motors, the activation or deactivation of pan and tilt inversion, or turning the light source on and off.

These functions are accessed not through Device Control, but in the Stage View via the context menu of the respective device, through the Procedures submenu.

=Structure=
Procedures in DDFs for DMXControl 3 all have the same structure, which usually consists of four elements:
* Name of the function for the associated Procedure
* <code>set</code>: Specifies the DMX channel and the DMX value
* <code>hold</code>: Hold time for the DMX value
* <code>restore</code>: Restoration of the initial state

If the <code>restore</code> element is omitted in a Procedure, the DMX value entered under <code>set</code> remains set.

=Available Procedures=
Currently, the following Procedures are already predefined in DMXControl 3, but Procedures with custom names can also be created. For the most common functions, unique symbols are automatically assigned to the names.
The naming can be freely chosen since Procedures directly address DMX channels with DMX values. It is therefore possible to start a complete device reset with the Procedure for turning on the lamp. However, this approach is not recommended.

{| class="wikitable toptextcells"
|-
! Procedure Name
! Description
! Note
|-
|style="width: 10em"| <code>lamp_on</code>
| Turns on the lamp of the corresponding device.
|
|-
| <code>lamp_off</code>
| Turns off the lamp of the corresponding device.
|
|-
| <code>reset</code>
| Triggers a reset on the corresponding device.
|
|-
| <code>reset_pan_tilt</code>
| Triggers a reset of the pan & tilt motors on the corresponding device.
| The device moves to its reference points for pan & tilt.
|-
| <code>reset_pan</code>
| Triggers a reset of the pan motor on the corresponding device.
| The device moves to its reference points for pan.
|-
| <code>reset_tilt</code>
| Triggers a reset of the tilt motor on the corresponding device.
| The device moves to its reference points for tilt.
|-
| <code>reset_gobo</code>
<code>reset_gobowheel</code>
| Triggers a reset of the gobo motor on the corresponding device.
| The gobo wheel moves to its reference points.
|-
| <code>reset_gobo2</code>
<code>reset_gobowheel2</code>
| Triggers a reset of the gobo 2 motor on the corresponding device.
| Gobo wheel 2 moves to its reference points.
|-
| <code>reset_color</code>
<code>reset_colorwheel</code>
| Triggers a reset of the color motor on the corresponding device.
| The color wheel moves to its reference points.
|-
| <code>reset_color2</code>
<code>reset_colorwheel2</code>
| Triggers a reset of the color 2 motor on the corresponding device.
| Color wheel 2 moves to its reference points.
|-
| <code>reset_effects</code>
| Triggers a reset of the built-in effects on the corresponding device.
|
|-
| <code>reset_zoom</code>
| Triggers a reset of the zoom function on the corresponding device.
|
|-
| <code>reset_shutter</code>
| Triggers a reset of the shutter on the corresponding device.
|
|-
| <code>reset_iris</code>
| Triggers a reset of the iris on the corresponding device.
|
|-
| <code>reset_focus</code>
| Triggers a reset of the focus function on the corresponding device.
|
|-
| <code>reset_prism</code>
| Triggers a reset of the prism wheel on the corresponding device.
|
|-
| <code>pan_invert_on</code>
| Inverts the pan channel on the corresponding device.
|
|-
| <code>pan_invert_off</code>
| Disables the inversion of the pan channel on the corresponding device.
|
|-
| <code>tilt_invert_on</code>
| Inverts the tilt channel on the corresponding device.
|
|-
| <code>tilt_invert_off</code>
| Disables the inversion of the tilt channel on the corresponding device.
|
|-
| <code>pan_tilt_swap_on</code>
| Swaps pan and tilt on the corresponding device.
|
|-
| <code>pan_tilt_swap_off</code>
| Disables the swapping of pan and tilt on the corresponding device.
|
|-
| <code>display_on</code>
| Activates the display of the corresponding device.
|
|-
| <code>display_off</code>
| Deactivates the display of the corresponding device.
|
|}

[[Category:DDF DMXControl 3]]

[[de: Procedures_(DDF-Syntax)_DMXC3]]

Procedures examples (DDF-Syntax) DMXC3

2025-03-04T22:54:09Z

Jkuehn:

{{Manual Header
| Type = DMXC3 DDFs
| Version = 3.1.2
| LinkBackwards = Procedures functions (DDF-Syntax) DMXC3
| TextBackwards = Functions
}}

The following table shows some examples of predefined as well as custom procedures.

{| class="wikitable toptextcells"
|-
! Tag !! Variant !! Code
|-
|style="width: 10em"| <code>reset</code>
|style="width: 10em"| Complete device reset
|style="width: 60em"| <syntaxhighlight lang="xml">
<reset>
<set dmxchannel="0" value="255" />
<hold value="6000" />
<restore dmxchannel="0" />
</reset>
</syntaxhighlight>
Reset
* Set DMX channel 1 to DMX value 255.
* Hold the DMX value for 6000 ms (6 s).
* Restore the original DMX value for DMX channel 1.
|-
| <code>lamp_on</code>
| Turn on lamp
| <syntaxhighlight lang="xml">
<lamp_on>
<set dmxchannel="0" value="255" />
<hold value="4000" />
<restore dmxchannel="0" />
</lamp_on>
</syntaxhighlight>
Turn on lamp
* Set DMX channel 1 to DMX value 255.
* Hold the DMX value for 4000 ms (4 s).
* Restore the original DMX value for DMX channel 1.
|-
| <code>lamp_off</code>
| Turn off lamp
| <syntaxhighlight lang="xml">
<lamp_off>
<set dmxchannel="0" value="50" />
<hold value="8000" />
<restore dmxchannel="0" />
</lamp_off>
</syntaxhighlight>
Turn off lamp
* Set DMX channel 1 to DMX value 50.
* Hold the DMX value for 8000 ms (8 s).
* Restore the original DMX value for DMX channel 1.
|-
| <code>procedure</code>
| Eco-mode for lamp
| <syntaxhighlight lang="xml">
<procedure name="Lamp eco mode">
<set dmxchannel="0" value="170" />
<hold value="4500" />
<restore dmxchannel="0" />
</procedure>
</syntaxhighlight>
Custom procedure named "Eco-mode for lamp"
* Set DMX channel 1 to DMX value 170.
* Hold the DMX value for 4500 ms (4.5 s).
* Restore the original DMX value for DMX channel 1.
|}

[[Category:DDF DMXControl 3]]

[[de: Procedures_(DDF-Syntax_examples)_DMXC3]]

FAQ DMXC3

2025-03-04T22:49:15Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.2}}

This article collects and answers various frequently asked questions that would otherwise only be found with a bit of searching in the {{DMXCWebLinks|Forum}}. This article is also somewhat dynamic, meaning that new questions are added irregularly, and outdated ones are removed.

= Getting Started with DMXControl 3 =
=== Can I switch DMXControl 3 to German? ===
Yes. This has been possible since the release of DMXControl 3.2. To do so, open the settings for the GUI via {{Manual_MenuText|Settings|Application Settings|GUI}} and change the entry {{Manual_Objectcaption|Language}} to {{Manual_Fields|de-DE}}. After restarting the GUI, the German user interface will be loaded.
If you install DMXControl 3 on a PC for the first time, the GUI will even start directly with the German user interface.
Due to the growing number of users from all over the world, it was decided to develop DMXControl 3 in English first. The translation into other languages, including German, was carried out in a second step.

=== How can I add my own DDFs to DMXControl 3? ===
For self-created DDFs, there is the directory {{Manual_Filepath|UserDevices}}. Where this directory is located and how to access it quickly is described in the article {{Manual_Windowcaption|[[Device_Manager_DMXC3#Wichtige_Merkmale|Device Manager (Add device dialog)]]}}.

=== My device XYZ does not appear in the device list. What can I do? ===
For each device, there is a so-called {{Manual_Windowcaption|[[DDF_DMXC3|Device Definition File]]}}, or DDF for short. This must be created for each device. Some devices have their DDFs available in the {{Manual_Windowcaption|{{DMXCWebLinks|DDFLib}}}}. If not, you have to create the DDF yourself. There is corresponding {{Manual_Windowcaption|[[DDF_DMXC3#Grundlagen|guidance in the DMXC Wiki]]}} for this.

=== How do I set up my MIDI controller to receive feedback? ===
DMXControl 3 currently does not support feedback for MIDI controllers. This means that it is not yet possible to visualize, for example, through the color of a button on a MIDI controller whether a {{Manual_Windowcaption|[[Cuelist_DMXC3|Cuelist]]}} is currently running or whether a specific {{Manual_Windowcaption|[[Device_DMXC3|Device]]}} is selected. If you need such feedback, you currently have to rely on the {{Manual_Windowcaption|[[Softdesk_DMXC3|Softdesk]]}} or a macro board such as the {{Manual_Windowcaption|[[Stream_Deck_DMXC3|Stream Deck]]}}.

= Software Development =
=== When will the next version of DMXControl 3 be released? ===
We always try to provide a rough schedule for the next release. However, since this is a volunteer software project, the professional obligations and personal circumstances of the team members take priority over association activities and work on DMXControl 3. Additionally, during an ongoing beta test, many small bugs are often discovered, requiring improvements before a new version can be released.
As soon as a new version is available, it will be sufficiently announced through our well-known news channels. Therefore, it is always worth checking the {{DMXCWebLinks|Forum|News-Category|4|DMXControl news section}} in the forum.

=== Is there a version of DMXControl 3 for Mac and Linux? ===
Currently, it is technically difficult to impossible to generate a complete Linux version of DMXControl 3. There are several reasons for this. Firstly, DMXControl uses the XNA framework<ref>More information on the XNA framework: https://en.wikipedia.org/wiki/Microsoft_XNA</ref> for graphics rendering and processing. This does not run on Linux, meaning that all components relying on XNA will not work under Linux. This includes GUI components such as the {{Manual_Windowcaption|[[Stage_View_DMXC3|Stage View]]}}, {{Manual_Windowcaption|[[Programmer_DMXC3|Programmer]]}}, {{Manual_Windowcaption|[[Input_Assignment_DMXC3|Input Assignment]]}}, as well as kernel components such as {{Manual_Windowcaption|[[Affinity_DMXC3|Gobo Correlation]]}} or {{Manual_Windowcaption|[[Matrix_DMXC3|Matrix Effects]]}}.
Another issue is the use of .NET Remoting<ref>More information on .NET Remoting: https://en.wikipedia.org/wiki/.NET_Remoting</ref> for communication between the GUI and the kernel. .NET Remoting is also not Linux-compatible. Currently, porting DMXControl 3 is not possible.

=== Can I open a project from DMXControl 2 directly in DMXControl 3? ===
No, DMXControl 3 is not compatible with DMXControl 2. We have listed the most important differences here: [[Change_over_from_DMXControl_2_to_DMXControl_3|Transition from DMXControl 2 to DMXControl 3]]

= Links and References =
<references/>

[[Category:Tutorials DMXControl 3]]
[[Category:DMXControl 3]]

[[de: FAQ_DMXC3]]

Macroboard DMXC3

2025-03-04T22:47:02Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

A {{Manual_Windowcaption|Macroboard}} is a button matrix with visual feedback that can be used in the {{Manual_Windowcaption|Input Assignment}} to control program functions. This can either be a purely virtual {{Manual_Windowcaption|Macroboard Profile}}, or it can be transferred to a physical device such as an Elgato Stream Deck.

{|
| style="min-width: 200px; line-height: 1.2em;" | __TOC__
| style="width: 25px;" |
| valign="top" | {{Picture_with_subtitle|DMXC3_Macroboard_Profile.png|1|6x4 Macroboard Profile with bitmaps assigned.}}
|}

= Overview =
A {{Manual_Windowcaption|Macroboard}} provides inputs and outputs in the {{Manual_Windowcaption|[[Input_Assignment_DMXC3|Input Assignment]]}}. The inputs can be used for various applications or actions. Graphics in the form of bitmaps can be placed on the outputs, which then respond to actions within DMXControl 3 and visualize the status.

Two basic use cases must be distinguished in the Macroboard area. Either a physical macroboard is controlled directly, in which case everything is linked to a specific macroboard. Alternatively, a virtual {{Manual_Windowcaption|Macroboard Profile}} can be used, which can later be transferred to a physical macroboard. Macroboard Profiles, in particular, simplify working with a macroboard because they are not tied to any physical device and can be prepared and tested at any time without one.

Currently, the following macroboards available on the market are directly supported by DMXControl 3.

{| class="wikitable" style="text-align:center;"
|- class="hintergrundfarbe10"
! rowspan="2" style="width: 125px;" | Type !! rowspan="2" style="width: 75px;" | Revision !! rowspan="2" style="width: 125px;" | Buttons !! rowspan="2" style="width: 125px;" | Resolution !! colspan="2" | Support !! rowspan="2" | Note
|- class="hintergrundfarbe10"
! style="width: 75px;" | Status !! style="width: 75px;" | DMXC- Version

{{DMXC3 Manual-Tablesection | S2 | 7 | Elgato}}

! rowspan="2" | StreamDeck Mini
| || rowspan="2" style="text-align:left;" | 2 x 3 buttons || rowspan="2" | 72 x 72 pixels || {{Yes}} || '''3.2.0''' ||
|-
| Rev. 2 || {{Yes}} || '''3.3.0''' || style="text-align:left;" |
|-
! rowspan="3" | StreamDeck (Standard)
| || rowspan="3" style="text-align:left;" | 3 x 5 buttons || rowspan="3" | 72 x 72 pixels || {{Yes}} || '''3.2.0'''
|-
| Rev. 2 || {{Yes}} || '''3.2.2''' ||
|-
| MK.2 || {{Yes}} || '''3.3.0''' ||
|-
! rowspan="2" | StreamDeck XL
| || rowspan="2" style="text-align:left;" | 4 x 8 buttons || rowspan="2" | 96 x 96 pixels || {{Yes}} || '''3.2.2'''
|-
| Rev. 2 || {{Yes}} || '''3.3.0''' || style="text-align:left;" |
|-
! Stream Deck +
| || style="text-align:left;" | 8 buttons, 1 touchbar, 4 encoders || rowspan="2" | varies || rowspan="2" | {{No}} || rowspan="2" | || rowspan="2" style="text-align:left;" | Extensive changes and additions required for support
|-
! Stream Deck Neo
| || style="text-align:left;" | 8 buttons, 1 infobar, 2 touchpoints
|}
{{Manual Box | en | Hint | New hardware revisions are usually accompanied by an update of DMXControl 3.}}

= Key Features =

= Usage =
== Creating a Macroboard Profile ==
{{Manual Objectcaption|Macroboard Profiles}} can be added in the {{Manual Windowcaption|[[Project_Explorer_DMXC3|Project Explorer]]}} under the Macroboard Profiles section. The context menu contains the entry {{Manual MenuText|Create Macroboard Profile}}. This command opens the window {{Manual Windowcaption|Add Macroboard Profile}}.

At the top of this window, there is an option to use a {{Manual Fields|Template}}. Currently, the following choices are available: {{Manual Fields|Custom}}, {{Manual Fields|Stream Deck Mini}}, {{Manual Fields|Stream Deck}}, {{Manual Fields|Stream Deck XL}}. Only with the custom template can the number of buttons per {{Manual Fields|Column}} and {{Manual Fields|Row}} be freely defined. The arrangement and number of buttons are predetermined for the specific macroboard templates.

At the bottom, below the settings, a preview of the macroboard profile is displayed.

{{Manual_Box | en | Attention | Once created, a {{Manual Objectcaption|Macroboard Profile}} cannot be modified in terms of the number of buttons.}}

It is possible to create any number of {{Manual Objectcaption|Macroboard Profiles}}. This allows a single macroboard to dynamically display multiple pages through appropriate routing in the {{Manual_Windowcaption|[[Input_Assignment_DMXC3|Input Assignment]]}}.

== Assigning Actions ==
For macroboards, the {{Manual_Windowcaption|[[Input_Assignment_DMXC3|Input Assignment]]}} contains separate folders in both the Input and Output trees. These folders list:

all physical macroboards recognized by DMXControl 3, identified by their serial numbers,

all virtual macroboard profiles available in the project.
Each folder then contains individual buttons corresponding to the number of keys on the physical macroboard or virtual macroboard profile.

{{Picture_with_subtitle|DMXC3_Macroboard_Profile.png|2|Linking a Macroboard Profile Node with a Macroboard Node.}}

== Displaying Macroboard Profiles ==
{{Picture_with_subtitle|DMXC3_Macroboard_Profile.png|3|Macroboard display window.}}
Through {{Manual MenuText|Windows|Macroboard Profile}} in the menu bar, the Macroboard window can be opened, displaying both a running output of a {{Manual_Windowcaption|Macroboard}} and a single {{Manual_Windowcaption|Macroboard Profile}}, allowing (simulated) control.

= External Control =
The {{Manual_Windowcaption|[[Input_Assignment_DMXC3|Input Assignment]]}} provides the following nodes for macroboards:
*[[Macroboard_(Input_Assignment)DMXC3|Macroboard]]
*[[Macroboard-Profile(Input_Assignment)_DMXC3|Macroboard Profile]]
Additionally, various converter nodes generate graphics for function representation on the buttons.

= Application Examples =
The article {{Manual_Windowcaption|[[Stream_Deck_DMXC3|Stream Deck]]}} collects and explains various examples of using a macroboard.

<noinclude>
[[Category: Manual DMXControl 3]]
</noinclude>

[[de: Macroboard_DMXC3]]

Automatic creating of a running light

2025-03-04T22:39:06Z

Jkuehn:

== Szenengenerator ==

Ab Version 2.11 enthält DMXControl einen Szenengenerator/Lauflichtgenerator. Dies ist ein Assistent, der es ermöglicht, in 3 Schritten verschiedene Grundszenen für Geräte zu erzeugen. Überall, wo eine Szene über das grüne Plus-Zeichen erzeugt werden kann, wird nun auch im Kontext-Menü (rechte Maustaste) der Eintrag "Automatisch erzeugt - Aus DDF" angeboten. Wird der Szenengenerator aus der Szenenliste aufgerufen, werden die generierten Schritte als Einzelszenen in die Szenenliste eingetragen. Alle generierten Szenen erscheinen auch in der Szenenbibliothek.

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_AutomatischeSzenen.png|1|Automatische Szenenerstellung|center}}

=== Bedienung ===

Die Bedienung wird anhand der Demoprojekt-Konfiguration gezeigt.

'''Schritt 1:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenGeneratorSchritt1.png|2|Szenengenerator Schritt 1}}

Aus der Liste wird das Gerät ausgewählt, für das Szenen generiert werden sollen.

 

'''Schritt 2:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenGeneratorSchritt2.png|3|Szenengenerator Schritt 2}}

Hier wird die Eigenschaft gewählt. Im rechten Fenster kann man einen oder mehrere Werte auswählen, für die man später (Einzel-)Szenen haben will.

 

'''Schritt 3:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenGeneratorSchritt3.png|4|Szenengenerator Schritt 3}}

Schliesslich kann man noch weitere Geräte des gleichen Typs wählen. Die generierten Szenen betreffen dann alle ausgewählten Geräte.

 

'''Ergebnis'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzenenbibliothekErgebnis.png|5|Szenengenerator Ergebnis}}

Alle generierten Szenen werden in der Szenenbibliothek unter der Kategorie "automatisch erzeugt" abgelegt.

== Lauflicht-Generator ==

Ab Version 2.12 enthält DMXControl einen Lauflichtgenerator. Dies ist ein Assistent, der es ermöglicht in 3 Schritten verschiedene Muster des Lauflichts zu erzeugen. Überall, wo eine Szene über das grüne Plus-Zeichen erzeugt werden kann, wird nun auch im Kontext-Menü (rechte Maustaste) der Eintrag "Automatisch erzeugt -> Lauflicht" angeboten. Wird der Lauflichtgenerator aus der Szenenliste aufgerufen, werden die Schritte des LAuflichts als Einzelszenen in die Szenenliste eingetragen. Wird der Lauflichtgenerator aus dem Effektsequenzer aufgerufen, wird ein neuer Effekt erzeugt.

=== Bedienung ===

Die Bedienung wird anhand der Demoprojekt-Konfiguration gezeigt.

'''Schritt 1:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_LauflichtGeneratorSchritt1.png|6|Lauflichtgenerator Schritt 1}}

Aus der Liste werden die Geräte ausgewählt, die in das Lauflicht einbezogen werden sollen.Achtung: Es werden nur Dimmerkanäle angezeigt, daher bei den DDFs bitte auf den Typ "Dimmer" der Lauflichtkanäle achten, auch wenn z.B. ein Switchpack verwendet wird.

 

'''Schritt 2:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_LauflichtGeneratorSchritt2.png|7|Lauflichtgenerator Schritt 2}}

Hier wird das Muster gewählt. Dieses kann in der Vorschau geprüft werden. Es kann die Grundgeschwindigkeit des Lauflichts eingestellt werden. Diese kann später, z.B. im Effektsequenzer modifiziert werde.

 

'''Schritt 3:'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_LauflichtGeneratorSchritt3.png|8|Lauflichtgenerator Schritt 3}}

Schliesslich wird die Helligkeit voreingestellt.

 

'''Ergebnis'''

{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_EffektsequenzerErgebnis.png|9|Lauflichtgenerator Ergebnis}}

Dieses Bild zeigt den automatisch generierten Effekt "Lauflicht Muster 2".

[[Category: Tutorials_DMXControl_2]]

Kernel DMXC3

2025-03-04T22:36:55Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

The {{Manual Windowcaption|Kernel}} of DMXControl 3 is the part of the software responsible for the actual calculation of all effects and handles communication with the connected interfaces.

{{Picture_with_subtitle|DMXC3_Manual Kernel_Window_after_start.png|1|Kernel of DMXControl 3 after startup.|800px}}

= Overview =
The {{Manual Windowcaption|Kernel}} is responsible for the actual calculation of all effects and communicates with the connected interfaces.

Typically, the kernel operates invisibly in the background for the user when the user interface and the kernel are started together, as is mostly common when using DMXControl 3 on a single PC. However, if desired, the kernel can be displayed using the command {{Manual MenuText|Help|Show Kernel}}. When the user interface is closed, the kernel is also shut down.
{{Manual Box | en | Hint | The kernel must not be terminated at any point while a show is running. If the kernel is ended prematurely, no DMX values will be output anymore, and all changes made to the project up to that point will be lost.}}

= Key Features =
Even though the kernel window offers the option to close it via the exit button, using this button is generally discouraged. The kernel goes through various processes when shutting down, such as terminating active {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}, disabling the DMX output, and ending communication with the DMX interfaces.
{{Manual Box | en | Hint | To properly shut down and terminate the kernel, enter the command <code>shutdown</code> as a command.}}

= Controls =
The {{Manual Windowcaption|Kernel}} is designed as a console window and therefore does not feature graphical controls. Control of the kernel is thus exclusively managed via command-line parameters.

== Command-Line Parameters ==
The kernel can be queried for more detailed information about its status using the following command-line commands, allowing users to learn more about the kernel's state. Simple tests are also possible. There is no German translation or German command-line parameters available here.

{{Picture_with_subtitle|DMXC3_Manual Kernel_Command_line_parameter.png|2|Command-line parameters of the kernel.|center|800px}}

{| class="wikitable"
|- class="hintergrundfarbe10"
! style="width: 250px;" | Command !! style="width: 500px" | Description !! Example
|- class="hintergrundfarbe11"
| colspan="3" | '''Group 1: Main Menu'''
|-
| <code>shutdown</code> or {{Manual Keyboard|Ctrl|C}} || Terminates the kernel.
|-
| <code>status</code> || Displays status information.
|-
| <code>menu</code> || Access to the control menu.
|-
| <code>clear</code> || Clears the console.
|-
| <code>notification {message}</code> || Sends a notification <code>{message}</code> to all clients. || <code>'''notification''' Please save the project!</code>
|-
| <code>notify {sessionNames} {message}</code> || Sends a notification <code>{message}</code> to selected clients {sessionNames}. || <code>'''notify''' LIGHT-PC1 Please save the project!</code>
|-
| <code>mixerdump</code> || Saves the current mixer information to a log file.
|-
| <code>width {character count}</code> || Sets the console width (number of characters).
|-
| <code>load "{file path}"</code> || Loads a project.
|-
| <code>save "{file path}"</code> || Saves the current project. || <code>'''save''' "C:\Users\Public\Documents\My Project.zip"</code>
|-
| <code>dmxout {DMX channel, value}+</code> || Sets DMX output values.
|-
| <code>dmxin {DMX channel, value}+</code> || Sets DMX input values.
|-
| <code>help</code> || Opens the help menu (also accessible via <code>?</code>).
|- class="hintergrundfarbe11"
| colspan="3" | '''Group 2: Menu'''
|-
| <code>1</code> || Menu for controlling DMX channels.
|-
| <code>2</code> || Menu for controlling RDM functions.
|-
| <code>3</code> || Information about DMX output.
|-
| <code>4</code> || Information about load management (Electricity).
|-
| <code>5</code> || Information about input assignment.
|-
| <code>6</code> || General monitoring information.
|-
| <code>7</code> || Information about available plugins in DMXControl 3.
|-
| <code>8</code> || Information about the Property Value Mixer.
|-
| <code>9</code> || Information about current connections (Sessions).
|-
| <code>10</code> ||
|-
| <code>11</code> || Information about active managers and services.
|}

{{Manual Box | en | Hint | If an entered path contains spaces, quotation marks are mandatory.}}

= Usage =
== Network Communication ==
For the separate operation of the {{Manual Windowcaption|[[GUI DMXC3|User Interface]]}} and the {{Manual Windowcaption|Kernel}} on different PCs to function, the following requirements must be met:
* All components of the DMXC3 network must be able to reach the PC running the kernel. This can be checked using a ping, especially when setting up a more complex configuration.
* To enable communication between components in the DMX3 network, the ports listed below<ref>List of standardized network ports (English): https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers</ref> must be opened in the firewall. Typically, the firewall prompts for this upon the first start and automatically adds them.

{| class="wikitable"
! style="width: 75px;" | Port!! style="width: 75px" | TCP !! style="width: 75px" | UDP || Description
|-
| 17474 || || Unofficial
| DMXControl 3 Network Discovery
|-
| 17475 || colspan=2 | Unofficial
| DMXControl 3 Network Broker
|}

{{Manual Reference |arrow| Further information on working with DMXControl 3 across multiple PCs is described in the article [[Network Concept DMXC3|Network Concept]].}}

== Startup Parameters ==
Startup parameters are typically passed to a shortcut to launch an application. To pass a startup parameter to the kernel, create a new shortcut to the application and adjust the target field in the properties. By default, this field only contains the full path to the application, such as:

{{Manual Filepath|C:\Program Files (x86)\DMXControl Projects\DMXControl 3.3.0\Kernel\Lumos.exe}}

It is important that the entire path is enclosed in quotation marks. The permitted startup parameters are appended sequentially after the path to the application, with each keyword preceded by two dashes. For example, to load a specific project directly upon starting the kernel, the full entry would look like this:

{{Manual Filepath|C:\Program Files (x86)\DMXControl Projects\DMXControl 3.3.0\Kernel\Lumos.exe" '''--load''' "{PROJECT-ID}#{VERSION}"}}

Following the keyword <code>--load</code>, the internal project ID is provided in quotation marks. Optionally, this can be supplemented with the project version, prefixed with a #. Specifying the project name is not possible.

{{Manual Reference |arrow| Additional notes on setting up an automatic start of DMXControl 3 with the direct loading of a specific project are provided in the article on {{Manual Windowcaption|[[System Configuration DMXC3|System Configuration]]}}.}}
{{Manual Box | en | Hint | The project {{Manual Filepath|{PROJECT-ID}}} is currently only located in the kernel's configuration directory, where projects are centrally stored and managed.}}

Multiple startup parameters are allowed per shortcut, as listed in the table below.

{| class="wikitable"
! style="width: 250px;" | Parameter !! style="width: 500px" | Description !! style="width: 375px" | Example
|-
| <code>--hidden</code> || The kernel runs hidden in the background and is not visible in the taskbar. ||
|-
| <code>--nonetwork</code> || Network functionality remains disabled, so the {{Manual MenuText|Connection}} entry in the main window’s menu bar will not appear in the GUI later. The nonetwork mode can be used when the kernel and GUI operate on the same PC. ||
|-
| <code>--load</code> || By specifying a project ID and optionally a version number, the kernel will load a specific project directly upon startup. || <code>--load "{PROJECT-ID}#{VERSION}"</code>
|}

== Configuration Directory ==
After the kernel is started for the first time, a directory is created in Windows Explorer where various settings are stored. By default, this directory is located at {{Manual Filepath|C:\Users\{USERNAME}\AppData\Roaming\DMXControl Projects e.V\DMXControl\Kernel\Config}}, where {{Manual Filepath|'''{USERNAME}'''}} should be replaced with the name of the current PC user. Alternatively, the directory can be accessed via {{Manual Filepath|%AppData%\Roaming\DMXControl Projects e.V.\Kernel\Config}}.

{| class="wikitable"
! style="width: 250px;" | File !! style="width: 500px" | Description !! style="width: 375px" | Example || Optional
|-
| <code>ApplicationConfig.xml</code> || Contains the general program settings of DMXControl 3. || || {{No}}
|-
| <code>DMXInterfaceConfig.xml</code> || Stores the settings of the integrated DMX interfaces. || || {{No}}
|-
| <code>GoboCorrelations_GPU.csv</code> || Saves the result of the gobo correlation. || || {{No}}
|-
| <code>KernelPluginConfig.xml</code> || Stores the status of plugins. || || {{No}}
|-
| <code>SavedAttachables.xml</code> || This file stores all effects from the Saved Effects tab. || || {{No}}
|-
| <code>Statistics.xml</code> || This file records the runtime of the last 100 sessions and the total sum of output DMX values. || || {{No}}
|}

= Links and References =
== Further Information ==
<references/>

<noinclude>
[[Category: Manual DMXControl 3]]
</noinclude>

[[de: Kernel_DMXC3]]

Speed Master (Executor) DMXC3

2025-03-04T22:33:48Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} In the area of {{Manual Windowcaption|executors}} in DMXControl 3, there is a variant for displaying a {{Manual Windowcaption|speed master (Speed Master)}} on the executor track. Using the {{Manual Windowcaption|speed master}}, the repetition speed of effects as well as the tempo for "switching" beat-controlled cue lists (cuelists) is influenced. ''For det..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

In the area of {{Manual Windowcaption|[[Executor DMXC3|executors]]}} in DMXControl 3, there is a variant for displaying a {{Manual Windowcaption|[[Speed Master (Master) DMXC3|speed master (Speed Master)]]}} on the executor track. Using the {{Manual Windowcaption|speed master}}, the repetition speed of effects as well as the tempo for "switching" beat-controlled cue lists (cuelists) is influenced. ''For details, see {{Manual Windowcaption|[[Speed Master (Master) DMXC3|speed master]]}}.''

The variant for the {{Manual Windowcaption|speed master}} provides several buttons and faders to control it accordingly. Additionally, there is a tailored variant for displaying the {{Manual Windowcaption|speed master}}. In the settings of the associated executor, there are the following options to assign actions to the faders and buttons:
{{DMXC3 Manual-Tableheader Executor actions | en}}

| rowspan="1" | '''Fader''' || Master || {{Yes|-}} || Controls the value of the assigned {{Manual Windowcaption|speed master (Speed Master)}}.
|-
| rowspan="6" | '''Button''' || Double || {{Yes|-}} || Doubles the current BPM value.
|-
| Half || {{Yes|-}} || Halves the current BPM value of the speed master.
|-
| Learn || {{Yes|-}} || Determines the new BPM value by pressing the button multiple times.
|-
| Sync || {{Yes|-}} || Synchronizes the speed master.
|-
| R.M.O.C || || Retains the current factor when learning another BPM value.
|-
| Stomp || || Temporarily sets the BPM value to the minimum value, with already started fades (e.g., in {{Manual Windowcaption|cuelists}}) still being completed.
|}

For the executor type {{Manual Objectcaption|speed master}}, there are also the following settings that influence the interaction with the assigned speed master. These can be found in the properties of each executor:
{{DMXC3 Manual-Tableheader Settings | en}}

| Toggle Stomp || {{Manual Setting entries | de | True-False |False}} || '''{{Manual Fields|False}}''': The button works as a push-button, so the action is only performed when pressed and held. '''{{Manual Fields|True}}''': The button is configured as a toggle button.
|}

<noinclude>
[[Category: Manual DMXControl 3]]
[[Category: Executor DMXC3]]
</noinclude>

[[de: Speed_Master_(Executor)_DMXC3]]

Parameter Master (Executor) DMXC3

2025-03-04T22:30:17Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} In the area of {{Manual Windowcaption|executors}} in DMXControl 3, there is a variant for displaying a {{Manual Windowcaption|parameter master (Parameter Master)}} on the executor track. Using the {{Manual Windowcaption|parameter master}}, various functions of devices can be stored in {{Manual Windowcaption|cuelists}} in such a way th..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

In the area of {{Manual Windowcaption|[[Executor DMXC3|executors]]}} in DMXControl 3, there is a variant for displaying a {{Manual Windowcaption|[[Parameter Master (Master) DMXC3|parameter master (Parameter Master)]]}} on the executor track. Using the {{Manual Windowcaption|parameter master}}, various functions of devices can be stored in {{Manual Windowcaption|[[Cuelist DMXC3|cuelists]]}} in such a way that they can be changed live by a corresponding assigned executor or via the similarly named node in {{Manual Windowcaption|[[Input Assignment DMXC3|input assignment]]}}. ''For details, see {{Manual Windowcaption|[[Parameter Master (Master) DMXC3|parameter master]]}}.''

The variant for the {{Manual Windowcaption|parameter master}} provides several buttons and faders to control it accordingly. Additionally, there is a tailored variant for displaying the {{Manual Windowcaption|parameter master}}. In the settings of the associated executor, there are the following options to assign actions to the faders and buttons:
{{DMXC3 Manual-Tableheader Executor actions | en}}

| rowspan="1" | '''Fader''' || Master || {{Yes|-}} || Controls the value of the assigned {{Manual Windowcaption|parameter master (Parameter Master)}}.
|-
| rowspan="5" | '''Button''' || Double || {{Yes|-}} || Doubles the current fader value.
|-
| Half || {{Yes|-}} || Halves the current fader value.
|-
| Max || || Sets the fader to the maximum value.
|-
| Center || || Sets the fader to the midpoint between the maximum and minimum values.
|-
| Min || || Sets the fader to the minimum value.
|}

<noinclude>
[[Category: Manual DMXControl 3]]
[[Category: Executor DMXC3]]
</noinclude>

[[de: Parameter_Master_(Executor)_DMXC3]]

Cuelist (Executor) DMXC3

2025-03-04T22:25:16Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} This executor type is designed for controlling {{Manual Windowcaption|Cuelists}}, to control and manipulate assigned cuelists during a show. In some cases, it may be useful to assign a cuelist directly to multiple executors. For this purpose, this executor type offers five different faders, along with five buttons for the standard actions of the executor itself, and a total of 18 differen..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

This executor type is designed for controlling {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}, to control and manipulate assigned cuelists during a show. In some cases, it may be useful to assign a cuelist directly to multiple executors. For this purpose, this executor type offers five different faders, along with five buttons for the standard actions of the executor itself, and a total of 18 different actions to choose from. Some actions may have dependencies on other cuelists assigned to an executor.

Based on this, the settings for the corresponding executor offer the following options for assigning actions to the faders and buttons:

{{DMXC3 Manual-Tableheader Executor actions | en}}

| rowspan="5" | '''Fader''' || Intensity || {{Yes|-}} || Sets the intensity of the cuelist and influences the dimmer device function. All values for device functions such as color, position, etc., will be output as set in the respective scenes of the active cuelist, even if the fader value is reduced, unlike the Temp fader.
|-
| Temp || || The Temp fader defines how much the device functions set in a scene, such as color, position, gobo rotation, etc., will be mixed into the output of the cuelist. This also automatically results in the maximum value for the actions {{Manual Buttons|Flash}}, {{Manual Buttons|Flash go}}, and {{Manual Buttons|Flash on}}. In the case of color, the Temp fader works according to the statement "blend the color ... to ... percent." Thus, the Temp fader controls the saturation of the color from 0% to 100%.
|-
| Limit || || The Limit fader can be used as a variable fader if you want to prevent the maximum intensity of the cuelist set via the intensity fader from being exceeded, while still being able to make live adjustments within the preset limit.
|-
| Effect speed || || Determines the playback speed of all {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects]]}} included in the scenes of the cuelist.
|-
| Timing || || Factors in the fade-in and delay times of all scenes in the assigned cuelist.
|-
| rowspan="18" | '''Button''' || Black || || Sets the intensity of the cuelist permanently to the minimum value, until a new value is manually set, for example, via the fader. The cuelist itself remains active unless the "Auto Stop" function is enabled.
|-
| Flash || {{Yes|-}} || Temporarily sets the intensity of the cuelist to the maximum value. This action can only be executed for cuelists that are active and outputting values at the time the button is pressed.
|-
| Flash go || || Temporarily sets the intensity of the cuelist to the maximum value and triggers the next scene. Inactive cuelists will be started upon the first press of the button.
|-
| Flash on || || Starts the assigned cuelist and temporarily sets the intensity to the maximum value. If the cuelist is active, this action works like a simple {{Manual Buttons|Flash}}.
|-
| Full || || Permanently sets the intensity of the cuelist to the maximum value until a new value is manually set, for example, via the fader.
|-
| Go || {{Yes|-}} || Executes the next scene in the cuelist or continues the crossfade between two scenes if they were previously paused.
|-
| Go back || || Triggers the previous scene in the cuelist.
|-
| Kill || || Ends all cuelists assigned to executors, unless the setting {{Manual Fields|Kill protect}} is enabled. If the assigned cuelist is not running when {{Manual Buttons|Kill}} is pressed, it will be started automatically.
|-
| Pause || || Pauses the crossfade between two scenes if they are currently being executed at the time the button is pressed.
|-
| Pause / back || || Like Pause. Additionally, from the second click onward, you can go back within the cuelist and mark an already executed scene for re-execution when the {{Manual Buttons|Go}} button is pressed.
|-
| Play || {{Yes|-}} || Resumes the crossfade between two scenes if it was previously paused. Unlike {{Manual Buttons|Go}}, pressing the {{Manual Buttons|Play}} button multiple times will complete the ongoing crossfade rather than prematurely triggering the next scene. Inactive cuelists will be started upon the first press of the button.
|-
| Stomp || || Suppresses the output of the cuelist as if it were not active. The intensity is temporarily set to the minimum value.
|-
| Stop || {{Yes|-}} || Stops the assigned cuelist and starts the set release time to fade out the cuelist.
|-
| Swop || || {{Manual Buttons|Swop}} temporarily sets the intensity of the assigned cuelist to the maximum value as long as {{Manual Buttons|Swop}} is active. Simultaneously, {{Manual Buttons|Swop}} executes a {{Manual Buttons|Stomp}} on all other cuelists that do not have {{Manual Fields|Swop protect}}. This action can only be executed for cuelists that are active and outputting values when the button is pressed.
|-
| Swop go || || Temporarily sets the intensity of the cuelist to the maximum value and triggers the next scene. All other cuelists are temporarily suppressed according to the description of the simple {{Manual Buttons|Swop}} function. If the cuelist is not active when the button is pressed, it will also be started.
|-
| Swop on || || Starts the assigned cuelist and temporarily sets the intensity to the maximum value. If the cuelist is active, this action works like a simple {{Manual Buttons|Swop}}. All other cuelists are temporarily suppressed according to the description of the simple {{Manual Buttons|Swop}} function.
|-
| Temp || || Executes the cuelist only while the button is pressed. The fade-in time of the scenes and the release time are taken into account.
|-
| Toggle || || Starts or stops the assigned cuelist.
|}

{{Manual Box | en | Important | The actions {{Manual Buttons|Swop}} and {{Manual Buttons|Kill}} and their variants, such as {{Manual Buttons|Swop go}}, have automatic dependencies on all other cuelists assigned to any executor on any page. This is broadly similar to a {{Manual Windowcaption|[[Cuelist Group DMXC3|Cuelist group]]}}. To control the dependencies for these functions, there are the settings {{Manual Fields|Swop protect}} and {{Manual Fields|Kill protect}} in the properties of the respective executors.}}

{{Manual Box | en | Hint | Although Stomp and Swop suppress the output of a cuelist, these functions are not equivalent to {{Manual Windowcaption|[[Blackout DMXC3|Blackout]]}}.}}

For the executor type {{Manual Objectcaption|Cuelist}}, there are also the following settings that particularly affect the interaction with the assigned cuelist:

{{DMXC3 Manual-Tableheader Settings | en}}


| Show programmer filter || {{Manual Setting entries | en | True-False |True}} || '''{{Manual Fields|True}}''': The {{Manual Windowcaption|[[Programmer Filter DMXC3|Programmer Filter]]}} is displayed when adding another scene.
|-
| Auto Go || {{Manual Setting entries | en | True-False |False}} || '''{{Manual Fields|True}}''': The assigned cuelist will start automatically once the intensity is not at the minimum value (usually > 0%). It does not matter whether the value is set via the fader or if the {{Manual Buttons |Full}} button is pressed.
|-
| Auto Stop || {{Manual Setting entries | en | True-False |False}} || '''{{Manual Fields|True}}''': The assigned cuelist will stop automatically once the intensity is at the minimum value (usually 0%). It does not matter whether the value is set to the minimum via the fader or if the {{Manual Buttons |Black}} button is pressed.
|-
| Auto Stop ignores release time || {{Manual Setting entries | en | True-False |False}} || '''{{Manual Fields|False}}''': Once the intensity of the assigned cuelist is 0, the release time will start and the cuelist will be finished. '''{{Manual Fields|True}}''': If the intensity of the cuelist is 0, it will be finished directly without executing the release time.
|-
| Flash / Swop ignores intensity || {{Manual Setting entries | en | True-False |False}} || '''{{Manual Fields|False}}''': The Flash or Swop reaches the maximum brightness selected via the Temp fader. '''{{Manual Fields|True}}''': When pressing {{Manual Buttons |Flash}} or {{Manual Buttons |Swop}}, the intensity will temporarily be set to 100%, even if the Temp fader is not at 100%.
|-
| Swop protect || {{Manual Setting entries | en | True-False |False}} || '''{{Manual Fields|True}}''': The cuelist will continue to output when the {{Manual Buttons|Swop}} function is executed on any other cuelist.
|-
| Kill protect || {{Manual Setting entries | en | True-False |False}} || '''{{Manual Fields|True}}''': The assigned cuelist will continue to output even if {{Manual Buttons|Kill}} is executed on another executor.
|}

<noinclude>
[[Category: Manual DMXControl 3]]
[[Category: Executor DMXC3]]
</noinclude>

[[de: Cuelist_(Executor)_DMXC3]]

Template:DMXC3 Manual-Tableheader Executor actions

2025-03-04T22:23:14Z

Jkuehn:

<includeonly>{{(!}} class="wikitable toptextcells"
{{!-}} class="hintergrundfarbe10"
{{#ifeq: {{{1}}} | de |
! rowspan="2" style="width: 150px" {{!}} Gruppe !! colspan="2" {{!}} Aktion !! rowspan="2" style="width: 50px" {{!}} Stand.- Wert !! rowspan="2" {{!}} Beschreibung
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} deutsche GUI !! style="width: 175px" {{!}} englische GUI
{{!-}}
}}

{{#ifeq: {{{1}}} | en |
! rowspan="2" style="width: 150px" {{!}} Group !! Action !! rowspan="2" style="width: 50px" {{!}} Dflt.- Value !! rowspan="2" {{!}} Description
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} English GUI
{{!-}}
}}</includeonly><noinclude>{{Documentation Language reference}}</noinclude>

Template:DMXC3 Manual-Tableheader Executor actions

2025-03-04T22:22:54Z

Jkuehn:

<includeonly>{{(!}} class="wikitable toptextcells"
{{!-}} class="hintergrundfarbe10"
{{#ifeq: {{{1}}} | de |
! rowspan="2" style="width: 150px" {{!}} Gruppe !! colspan="2" {{!}} Aktion !! rowspan="2" style="width: 50px" {{!}} Stand.- Wert !! rowspan="2" {{!}} Beschreibung
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} deutsche GUI !! style="width: 175px" {{!}} englische GUI
{{!-}}
}}

{{#ifeq: {{{1}}} | en |
! rowspan="2" style="width: 150px" {{!}} Group !! colspan="2" {{!}} Action !! rowspan="2" style="width: 50px" {{!}} Dflt.- Value !! rowspan="2" {{!}} Description
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} English GUI
{{!-}}
}}</includeonly><noinclude>{{Documentation Language reference}}</noinclude>

Category:Executor DMXC3

2025-03-04T22:13:30Z

Jkuehn: Created page with "This page summarizes all articles about the {{Manual_Windowcaption|Executors}}. Category: Manual DMXControl 3 de: Kategorie:Executor_DMXC3"

This page summarizes all articles about the {{Manual_Windowcaption|[[Executor DMXC3|Executors]]}}.

[[Category: Manual DMXControl 3]]

[[de: Kategorie:Executor_DMXC3]]

Category:Options DMXC3

2025-03-04T22:10:58Z

Jkuehn:

This page summarizes all articles on the {{Manual_Windowcaption|Options (Options)}}, which provide various program functions and modules, but which are not included in the main article due to their scope.

[[Category: Manual DMXControl 3]]

[[de: Category:Options_DMXC3]]

Category:Master DMXC3

2025-03-04T22:10:49Z

Jkuehn:

This page summarizes all articles about the {{Manual_Windowcaption|[[Master DMXC3|Masters]]}}.

[[Category: Manual DMXControl 3]]

Category:Effects and Filters DMXC3

2025-03-04T22:10:17Z

Jkuehn:

This page summarizes all articles about the {{Manual_Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}.

[[Category: Manual DMXControl 3]]

[[de: Kategorie:Effects_and_Filters_DMXC3]]

Category:Manual DMXControl 3

2025-03-04T22:08:03Z

Jkuehn:

[[Category: DMXControl 3]]
[[Category: Manuals]]

[[de: Kategorie:Handbuch_DMXControl_3]]

Category:DMXControl 3

2025-03-04T22:06:04Z

Jkuehn:

All article of DMXControl 3 are listed in this category.

[[de: Kategorie:DMXControl_3]]

Category:DMXControl 3

2025-03-04T22:05:44Z

Jkuehn:

All article of DMXControl 3 are listed in this category.

[[en: Kategorie:DMXControl_3]]

Category:Did you know? DMXControl 3

2025-03-04T22:04:13Z

Jkuehn: Created page with "Category: DMXControl 3 de: Kategorie:Schon_gewusst%3F_DMXControl_3"

[[Category: DMXControl 3]]

[[de: Kategorie:Schon_gewusst%3F_DMXControl_3]]

Installation DMXC3

2025-03-04T22:01:28Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.0.0}}

== Overview ==
This chapter explains the installation of DMXControl 3. This is the standard installation. The current installation file can be found in the download section of the DMXControl homepage<ref>DMXControl Homepage, download section: http://www.dmxcontrol.de/downloads/category/1-software.html</ref> 

== Installation Step by Step ==
The following screenshots describe the installation process step by step. Depending on the operating system and its language, some steps may slightly differ from those shown here.

=== Language ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Sprachauswahl.png|1|Language selection|272px|left}}
|| The installation wizard starts directly with the selection of the installation language. The dialog appears in the language set in the operating system, with the corresponding pre-selected entry.
|}
 

=== Welcome ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Willkommen.png|2|Welcome dialog|450px|left}}
|| On this screen, you will be informed about the software you are about to install. By clicking the {{Manual_Buttons|Next}} button, you will reach the license dialog.
|}
 

=== License ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Lizenz.png|3|License confirmation window|450px|left}}
|| The license dialog displays the end-user license of DMXControl 3 in both German and English. It outlines what the license includes, such as what the user is allowed to do with the software and what is not allowed. It is very important that this license agreement is accepted by clicking the {{Manual_Buttons|Picture_with_subtitleAccept}} button, and you agree to it. By accepting, you make the agreement legally binding, even though it is free software.
|}
 

=== Install EasyView? ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_3DEasyView.png|4|3D-Easy View installation prompt|450px|left}}
|| After accepting the license agreement, the question is asked whether the 3D visualizer 3D Easy View should be installed. On the home workstation, where the shows are prepared and the stage is simulated, the visualizer is a very useful tool. On the live laptop, which doesn't have as much 3D power as the desktop at home, the 3D display can be skipped.
|}
 

=== Target Directory ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Speicherort.png|5|Choosing the installation location|450px|left}}
|| The next step is to select the target directory where DMXControl 3 should be installed. The default path is already suggested, which you can choose if you have no special preferences. The suggestion varies depending on the operating system, version, and language. On a German 32-bit Windows (XP, Vista, 7), the suggestion is <tt>"C:\Programme\DMXControl 3"</tt>, while on the English 32-bit version, it is <tt>"C:\Program Files\DMXControl Picture_with_subtitle"</tt>. On a 64-bit Windows, the suggestions are <tt>"C:\Programme (x86)\DMXControl 3"</tt> or <tt>"C:\Program Files (X86)\DMXControl 3"</tt>. We chose a different installation folder (in our case <tt>"E:\DMXControl 3"</tt>).
|}
 

=== Program Features ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Komponenten.png|6|Choosing components to install|450px|left}}
|| Now it’s time to select the details of the installation. In the standard installation, all features are selected, and you can proceed directly to the next step. However, if you want to perform a streamlined installation on a system, you can leave out certain features by unchecking them. Since DMXControl 3 doesn't take up much disk space, it is recommended to install it completely.
|}
 

=== Start Menu Folder ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Startmenue.png|7|Start menu entry|450px|left}}
|| Finally, you will be asked for the name of the start menu entry. The default suggestion is '''DMXControl 3''', but it can be adjusted later.
|}
 

=== Installation ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Installiere.png|8|Installation progress|450px|left}}
|| The selected parts of DMXControl 3 are now decompressed and installed to the correct location.
|}
 

=== Download Easyview (optional) ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_EasyViewDownload.png|9|Downloading Easy View|450px|left}}
|| If the option to install EasyView was selected, the download of the EasyView installation program will start.
|}
 

=== Install EasyView (optional) ===
{|
|-
| {{Picture_with_subtitle |DMXC2_Manual_Installation_EasyViewInstallation.png|10|Installing Easy View|450px|left}}
|| The EasyView installation starts automatically and does not require any direct user input.
|}
 

=== Install EasyView Drivers (optional) ===
{|
|-
| {{Picture_with_subtitle |DMXC2_Manual_Installation_EasyViewWillkommen.png|11|Driver installation for Easy View|450px|left}}
|| During the EasyView installation, drivers are installed on the system. At this point, the installation dialog for device drivers provided by Windows appears. This can simply be started by clicking the {{Manual_Buttons|Next}} button.
|}
 

=== Complete EasyView Driver Installation (optional) ===
{|
|-
| {{Picture_with_subtitle |DMXC2_Manual_Installation_EasyViewFertig.png|12|Finishing the Easy View installation|450px|left}}
|| Once the drivers are successfully installed, this part can be finished and you will return to the EasyView installation wizard and then to the DMXControl 3 installation.
|}
 

=== Installation Complete ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Fertig.png|13|Installation complete|450px|left}}
|| At the end of the installation, you have the opportunity to review the installation process. You will also see where EasyView has been installed. This path is important if you want to integrate additional fixtures into EasyView. Therefore, you should note the path if necessary.
|}
 

=== Start DMXControl ===
{|
|-
| {{Picture_with_subtitle |DMXC3_Manual_Installation_Abgeschlossen.png|14|Installation completed|450px|left}}
|| The installation completion is the final window of the installation routine. DMXControl 3 is now successfully installed on your computer.
|}
 

== Links and References ==
Links
<references/>

[[Category: Manual DMXControl 3]]

[[de: Installation_DMXC3]]

Introduction DMXC3

2025-03-04T21:52:35Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.0.0}}

== Overview ==
DMXControl 3 is a powerful tool for creating, editing, and controlling light shows of all kinds. Whether it is a small party in the basement with a few LED spotlights, a small concert with several chase lights, a nightclub with many scanners and moving heads, or professional theater productions with many dimmer channels – DMXControl 3 can be used for light control at all types of events.

Due to the abstraction concept in DMXControl 3, different types of spotlights can also be assigned to an effect at the same time, even if the channel assignment of the devices is different. If a spotlight does not support the selected gobo or color, DMXControl 3 automatically selects the most suitable gobo or the closest color. Later adjustments, such as to other spotlight positions or newly added devices, are possible without reprogramming the show in a short amount of time.

== Key Features ==
The key features of DMXControl 3 are:
* runs on various Windows versions (Windows 10, Windows 11)
* supports 16 DMX universes with 512 channels each (Out and In)
* supports the DMX512 protocol for various DMX interfaces (an up-to-date list is available on the project homepage<ref>Supported interfaces: http://www.dmxcontrol.de/unterstuetzte-interfaces.html</ref>)
* supports various interfaces such as [[Glossar_DMXC2#ArtNet|ArtNet]] protocol, DMX-In (if supported by the DMX interface), MIDI, and in a later version, OSC
* includes options for creating and saving light show projects
* features an interactive graphical representation of the spotlight configuration (Stage View)
* offers various sound-to-light control options

== Links and References ==
Links
<references/>

[[Category: Manual DMXControl 3]]

[[de: Einleitung_DMXC3]]

Template:Manual Description

2025-03-04T21:49:22Z

Jkuehn: Protected "Template:Manual Description" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

To increase clarity, we highlight certain parts of the text. Below is a list of all the highlights:
* Window labels are marked as follows: {{Manual_Windowcaption|Window Label}} 
* Names of specific objects in the software: {{Manual_Objectcaption|Object Name}} 
* Buttons, checkboxes, faders: {{Manual_Buttons|Button Label or Name}} 
* Dropdown entries, input fields: {{Manual_Fields|Dropdowns}} 
* Menu items and menu entries: {{Manual_MenuText|Menu Item|Submenu Item|Subsubmenu Item}} 
* File and directory paths: {{Manual_Filepath|...\DMXControl\DMXControl.exe}} 
* Commands: {{Manual_Commands|Module|Device/Function|Channel}} 
* Flags: {{Manual_Flags|Flags}} 
* Keys and keyboard shortcuts: {{Manual_Keyboard|Ctrl|C}}

Template:Manual Description

2025-03-04T21:48:54Z

Jkuehn: Created page with "To increase clarity, we highlight certain parts of the text. Below is a list of all the highlights: * Window labels are marked as follows: {{Manual_Windowcaption|Window Label}} * Names of specific objects in the software: {{Manual_Objectcaption|Object Name}} * Buttons, checkboxes, faders: {{Manual_Buttons|Button Label or Name}} * Dropdown entries, input fields: {{Manual_Fields|Dropdowns}} * Menu items and menu entries: {{Manual_MenuText|Menu Item|Submenu..."

Foreword DMXC3

2025-03-04T21:44:57Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.1
}}

[[Image:DMXC3_Manual_Introduction_Splashscreen.png | center | Figure 1: DMXControl 3 Startscreen]]

= Welcome =
In this manual, we introduce the free software DMXControl 3, which offers you many possibilities for designing your light show. You can find the DMXControl project via the DMXControl homepage<ref name="DMXControl Homepage">DMXControl Homepage {{DMXCWebLinks|DMXC-HP}}</ref>. It is part of the non-profit association DMXControl Projektes e.V.<ref name="DMXControl Projektes e.V.">DMXControl Projektes e.V. Homepage {{DMXCWebLinks|Vereins-HP}}</ref>. 

In the manual, we provide a detailed overview of the individual program areas and give you useful tips for working with DMXControl 3. Additionally, our '''{{DMXCWebLinks|YouTube|DMXC3-Playlists}}''' on our '''{{DMXCWebLinks|YouTube}}''', several [[Tutorials DMXControl 3|tutorials]] in written form with step-by-step guides, and the DMXControl Forum<ref name="DMXControl Forum">Forum section for {{DMXCWebLinks|Forum|Board|157|DMXControl 3}} in the DMXControl Projects e.V. forum</ref> are available for further questions and suggestions regarding DMXControl. 



{{Manual Description}}

At appropriate places, individual hints, warnings, and references are highlighted using special fields:
{{Manual Box | en | Hint | This field contains useful tips and detailed considerations of individual module components.}}
{{Manual Box | en | Important | This field contains important tips that should be noted as they affect key program functions.}}
{{Manual Box | en | Attention | This box contains very important tips that, if ignored, may lead to malfunctions of DMXControl.}}
{{Manual Box | en | Reference | This field shows references to other, sometimes external, pages.}}

We are always happy to receive constructive suggestions and feedback on the software and the manual to improve them further. You can submit improvement proposals for the software in the DMXControl forum<ref name="DMXControl Forum"/>. With broad community approval, you can also submit these suggestions as a feature request in the {{DMXCWebLinks|FS}}. For comments on the manual articles, please use the manual section in the bug tracker<ref>Bug tracker for the {{DMXCWebLinks|FS|Project|8|manual for DMXControl 3}}</ref>.

Now we wish you lots of fun with DMXControl 3 and the manual, and we hope that DMXControl will bring you a big step closer to the goal of a perfect light show.

Your DMXControl Team

= Authors of the Manual =
== Publisher ==
DMXControl Projects e.V. 
Beuthener Straße 8b 
13125 Berlin

== Authors ==
* Stefan Kistner
* Jens-Peter Kühn
* Joseph Noetzel
* Johannes Ströbel

= Links and References =
Links
<references/>

[[Category: Manual DMXControl 3]]
[[de: Vorwort_DMXC3]]

Foreword DMXC3

2025-03-04T21:44:37Z

Jkuehn:

Here is the translation while maintaining the MediaWiki special characters:

---

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.1
}}

[[Image:DMXC3_Manual_Introduction_Splashscreen.png | center | Figure 1: DMXControl 3 Startscreen]]

= Welcome =
In this manual, we introduce the free software DMXControl 3, which offers you many possibilities for designing your light show. You can find the DMXControl project via the DMXControl homepage<ref name="DMXControl Homepage">DMXControl Homepage {{DMXCWebLinks|DMXC-HP}}</ref>. It is part of the non-profit association DMXControl Projektes e.V.<ref name="DMXControl Projektes e.V.">DMXControl Projektes e.V. Homepage {{DMXCWebLinks|Vereins-HP}}</ref>. 

In the manual, we provide a detailed overview of the individual program areas and give you useful tips for working with DMXControl 3. Additionally, our '''{{DMXCWebLinks|YouTube|DMXC3-Playlists}}''' on our '''{{DMXCWebLinks|YouTube}}''', several [[Tutorials DMXControl 3|tutorials]] in written form with step-by-step guides, and the DMXControl Forum<ref name="DMXControl Forum">Forum section for {{DMXCWebLinks|Forum|Board|157|DMXControl 3}} in the DMXControl Projects e.V. forum</ref> are available for further questions and suggestions regarding DMXControl. 



{{Manual Description}}

At appropriate places, individual hints, warnings, and references are highlighted using special fields:
{{Manual Box | en | Hint | This field contains useful tips and detailed considerations of individual module components.}}
{{Manual Box | en | Important | This field contains important tips that should be noted as they affect key program functions.}}
{{Manual Box | en | Attention | This box contains very important tips that, if ignored, may lead to malfunctions of DMXControl.}}
{{Manual Box | en | Reference | This field shows references to other, sometimes external, pages.}}

We are always happy to receive constructive suggestions and feedback on the software and the manual to improve them further. You can submit improvement proposals for the software in the DMXControl forum<ref name="DMXControl Forum"/>. With broad community approval, you can also submit these suggestions as a feature request in the {{DMXCWebLinks|FS}}. For comments on the manual articles, please use the manual section in the bug tracker<ref>Bug tracker for the {{DMXCWebLinks|FS|Project|8|manual for DMXControl 3}}</ref>.

Now we wish you lots of fun with DMXControl 3 and the manual, and we hope that DMXControl will bring you a big step closer to the goal of a perfect light show.

Your DMXControl Team

= Authors of the Manual =
== Publisher ==
DMXControl Projects e.V. 
Beuthener Straße 8b 
13125 Berlin

== Authors ==
* Stefan Kistner
* Jens-Peter Kühn
* Joseph Noetzel
* Johannes Ströbel

= Links and References =
Links
<references/>

[[Category: Manual DMXControl 3]]
[[de: Vorwort_DMXC3]]

DMX-Interfaces DMXC3

2025-03-04T21:41:21Z

Jkuehn: /* Columns */

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.3}}

In the window {{Manual Windowcaption|DMX Interfaces (DMX Interfaces)}}, all DMX interfaces in DMXControl 3 are managed centrally. There is no distinction based on connection type, whether the DMX interface is connected via USB or operates over a network.
{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_Overview.png|1|Overview of the DMX interfaces set up in DMXControl 3|center|960px}}
= Overview =
The {{Manual Windowcaption|DMX Interfaces}} window lists all DMX interfaces configured on the respective computer and available for DMX output. Here, you can specify which internal DMX universe is output to the connected DMX interfaces starting from which DMX address. The same applies to the DMX input.

It is generally possible to configure multiple different DMX interfaces in advance and activate them as needed. It is also permissible to use multiple DMX interfaces for the same DMX universes, allowing the system to function like a DMX splitterA DMX splitter distributes the incoming DMX signal to multiple outputs. Detailed explanations can be found at https://en.wikipedia.org/wiki/DMX_splitter.

= Key Features =
== Special Features of Configuration ==
=== Using DMX Interfaces ===

{{Manual Box | en | Important | To activate DMX output, checkboxes in two columns must be selected: both in the column {{Manual TableHeader|(DMX Interface) Enabled}} and in the column {{Manual TableHeader|DMX Output Enabled}}.}}

The configuration of all DMX interfaces is stored for the respective computer. When using another computer, these must be reconfigured and reactivated.

=== Background on DMX Interfaces ===
If all provided DMX interfaces are selected during the installation of DMXControl 3, they are generally active in the background when the kernel starts. This means that potential DMX interfaces are continuously monitored in the background. Although this process is not critical, it is advisable to only install the DMX interfaces you actually use. If additional DMX interfaces are needed later, they can be downloaded manually from the {{DMXCWebLinks|DMXC-HP|index.php|DMXControl}} website.

== DMX Value Reset at Startup ==
If a DMX interface is set up and active, the kernel performs a reset on the associated DMX outputs when starting. This means that the kernel sets all DMX values to 0. Only after successfully loading a project do the connected devices receive their initial values. If a kernel restart is required, be aware that there is no access to the devices during the period from DMX interface activation to successful project loading, and in most cases, everything remains dark.

== Differentiating DMX Interfaces ==
In DMXControl 3, DMX interfaces are categorized into two groups:
* "Intelligent" DMX Interfaces: These DMX interfaces transmit at least a unique identifier, such as a serial number, to the operating system when connected to the PC. These interfaces often have additional functions for software communication. They are listed in the interface selection dialog under their manufacturer and respective serial number.
* "Non auto-detect interfaces": These DMX interfaces require manual configuration upon first use, typically specifying the port through which they are addressed by the operating system. This category also includes interfaces that output DMX data via the network or in the form of a file without being physically connected to the PC.

= User Interface =
The user interface of the {{Manual Windowcaption|DMX Interfaces}} window primarily consists of a table listing all configured DMX interfaces. Adding, deleting, and configuring DMX interfaces is done through the menu bar above it.

== Menu Bar ==
{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_Menubar.png|2|Menu bar of the DMX Interfaces window.}}
{{DMXC3 Manual-Tableheader Menubars | en }}
{{DMXC3 Manual-Tableentry Menubars | en | L0 | DMXC3_Icon_V-Collection_add.png | Add Interface | Add a new or additional interface. }}
{{DMXC3 Manual-Tableentry Menubars | en | L0 | DMXC3_Icon_V-Collection_refresh.png | Refresh | Update the status of the interfaces listed in the table. }}
{{DMXC3 Manual-Tableentry Menubars | en | L0 | DMXC3_Icon_V-Collection_preferences.png | Advanced Interface Settings | Open the advanced settings for the selected interface. }}
{{DMXC3 Manual-Tableentry Menubars | en | L0 | DMXC3_Icon_V-Collection_delete.png | Delete | Delete the selected interface. }}
|}

== Table ==
=== Columns ===
{| class="wikitable"
|-
! Label !! rowspan="2" | Description/Functionality
|-
! style="width: 175px;" | English GUI
|-
| Interface enabled || Activates or deactivates the entire DMX interface.
|-
| Vendor || Name of the DMX interface manufacturer.
|-
| Model || Designation of the DMX interface.
|-
| Serial number || Serial number of the DMX interface, if available.
|-
| Port || Running number of the available ports on the DMX interface.
|-
| DMX-out address || Assignment of the internal DMX universe in DMXControl to the actual DMX output port.
|-
| DMX-out enabled || Activates or deactivates DMX data output on an individual DMX output without turning off the entire interface.
|-
| DMX-in address || Assignment of the internal DMX universe in DMXControl to the actual DMX input port.
|-
| DMX-in enabled || Activates or deactivates DMX data reception on an individual DMX input without turning off the entire interface.
|-
| Comment || Additional notes about specific DMX interfaces or their ports.
|}

=== Meaning of Colors ===
Rows in the table are highlighted in different colors depending on the status of the associated DMX interface:
* '''White''': DMX interface is enabled and operational (Figure 3). DMX values are being output or received. Both checkboxes in the columns {{Manual TableHeader|DMX Interface enabled}} and {{Manual TableHeader|DMX Output enabled}} are selected.

* '''Gray''': DMX interface or DMX output is disabled (Figures 4 and 5). The DMX interface is operational, but no DMX values are being output. Only one of the checkboxes in the columns {{Manual TableHeader|DMX Interface enabled}} or {{Manual TableHeader|DMX Output enabled}} is selected.

* '''Red''': Error activating the DMX interface (Figure 6). This usually occurs if a DMX interface identified by its serial number is not connected when DMXControl 3 starts. Both checkboxes in the columns {{Manual TableHeader|DMX Interface enabled}} and {{Manual TableHeader|DMX Output enabled}} are selected despite the error.
{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_DMX-out_enabled.png|3|DMX interface enabled and operational.|center}}

{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_Interface_disabled.png|4|DMX interface disabled.|center}}

{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_DMX-out_disabled.png|5|DMX output disabled.|center}}

{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_Interface_error.png|6|Error activating the DMX interface.|center}}

For some interfaces (such as the Nicolaudie SIUDI), a port can only function as either DMX-In or DMX-Out. In this case, checkboxes appear in the columns {{Manual TableHeader|DMX output active}} and {{Manual TableHeader|DMX input active}}.

= Usage =
== Open Window ==
The window {{Manual Windowcaption|DMX Interfaces}} can be accessed via {{Manual MenuText|Settings|DMX Interfaces}} in the menu bar of the main window.

== Add a New Interface ==
{{Picture_with_subtitle |DMXC3_Manual DMX_Interfaces_Add_DMX_interface.jpg|7|Adding an interface|right}}After pressing the button {{Manual Buttons|Add DMX Interface}}, a window opens listing all DMX interfaces currently supported by DMXControl 3. In this tree, select the desired DMX interface and confirm with {{Manual Buttons|OK}}. In all cases, the configuration dialog for the DMX interface will open immediately. Typical actions here include:
* Selecting the actual DMX interface if it has not registered with the PC using a serial number.
* Setting a different operating mode (e.g., for Nodle U1, Nodle R4S, or the DE-/FX5 interface) if the default value is not suitable.
* Choosing the network card (IP address) through which the DMX data should be sent to the network (especially for output via Art-Net and sACN).
{{Clear}}

== Working with Output and Input Addresses ==
Interfaces that support more than one DMX universe receive a row in the table for each DMX universe. The field '''Port''' indicates the corresponding input or output of the interface. In the columns {{Manual TableHeader|DMX output address}} and {{Manual TableHeader|DMX input address}}, you can assign a DMX universe to a port of an interface in DMXControl 3 by double-clicking. The entry must follow this format:
DMX-Universe.DMX-Start Channel
DMXControl 3 supports 16 DMX universes (Universe 1 to Universe 16) with 512 channels each (Channel 1 to Channel 512). For example, if the Nodle U1 is to output all channel values from Channel 83 in DMXControl Universe 4 and DMXControl should display the received DMX values from DMX-In in Universe 6, enter '''4.83''' in the corresponding field under {{Manual TableHeader|DMX output address}} and '''6.1''' under {{Manual TableHeader|DMX input address}}.

== Advanced Interface Settings ==
In the advanced settings for the DMX interface:
* Assign it to the available DMX interfaces if it does not register in DMXControl 3 with a unique identifier such as a serial number.
* Define the behavior of the DMX interface according to its functionality, e.g., setting the DMX-In and DMX-Out mode for the Nodle U1 or Nodle R4S.
* Modify signal properties (timings) if supported by the connected DMX interface.

{{Manual Box | en | Hint | Some DMX devices have issues with timings. These devices may respond incorrectly or only partially to sent DMX values. Adjusting values such as {{Manual Objectcaption|Breaktime}} may help. However, there is no universal solution, and some trial and error may be required to find the optimal values.}}

=== USB DMX Interface ===
The configuration options for USB DMX interfaces vary depending on the interface. For the Nodle R4S, for example, you can modify different parameters of the DMX signal in addition to the interface mode (see Figure 8). Since the Nodle R4S, along with the Nodle U1, the DE-/FX5 interface, and the Entec DMX USB Pro, is recognized by the operating system via a serial number and registers in DMXControl 3, there is no need to manually select the interface.

For USB DMX interfaces categorized as "Non auto detect interfaces," such as the Entec Open DMX USB or similar devices, manual selection is required after adding the interface (see Figure 9).

{|width="100%"
|{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_Settings_Nodle_R4S.png|8|Advanced settings of the Nodle R4S.|center}}
|{{Picture_with_subtitle|DMXC3_Manual DMX_Interfaces_Settings_Entec_Open_DMX_USB.png|9|Settings of the Entec Open DMX USB.|center}}
|-
|}

=== Art-Net Protocol ===
The Art-Net interface in DMXControl 3 falls under the "Non auto detect interfaces" category. With the Art-Net protocol, a specific Art-Net node from a particular manufacturer or type does not usually receive the DMX data. Instead, the DMX data output is determined by the configuration in DMXControl 3 and the Art-Net nodes present in the network. Thus, connected Art-Net nodes only process the data intended for them. Multiple Art-Net nodes can also be set to output the same DMX universes. In a way, this resembles the DMX protocol and DMX-capable devices.

{{Manual Reference | arrow | Detailed configuration explanations and usage instructions can be found in the article {{Manual Windowcaption|[[Art-Net (DMX Interfaces) DMXC3|Art-Net (DMX Interfaces)]]}}.}}

=== Nicolaudie Magic 3D Easy View ===
The interface to Magic 3D Easy View allows direct transmission of DMX values from DMXControl 3. This DMX interface is also categorized as "Non auto detect interfaces," even though it operates on a software level.

To enable output, under the advanced interface settings, you must select the installation directory of Easy View in the {{Manual Objectcaption|Path}} setting. In the example image, the directory is {{Manual Filepath|C:\Program Files (x86)\Nicolaudie\Magic 3D Easy View}}.

{{Picture_with_subtitle|DMXC3 Manual DMX Interfaces Settings Nicolaudie Easy View plugin.png|11|Advanced settings of the output plugin for Magic 3D Easy View.|center}}

Each time the DMX interface is reactivated or DMXControl 3 is started, Easy View will also start automatically. In this case, the {{Manual Windowcaption|Universe patch}} window contains an additional button labeled "DMXControl 3." Clicking this button activates the dropdown menus, allowing additional modifications of DMX universes within Easy View. However, it is generally recommended to keep the default mapping, as DMXControl 3 also provides this functionality.

{{Manual Box | en | Important | It may be advisable to restart both DMXControl 3 and Easy View after configuring the interface.}}

= External Control =
DMX interfaces can be controlled or provide feedback via the {{Manual_Windowcaption|[[Input_Assignment_DMXC3|Input Assignment]]}} using the following nodes:
* [[DMX-Interface_(Input_Assignment)_DMXC3|DMX Interface]]
* [[DMX-Interface-Port_(Input_Assignment)_DMXC3|DMX Interface Port]]

= Links and References =
== Video Tutorials ==
Available on our {{DMXCWebLinks|YouTube}} channel.
{|
{{DMXC3 Manual-Tableentry Videolink | _rOGX6hMHSw | Setting up and configuring interfaces}}
|-
{{DMXC3 Manual-Tableentry Videolink | RLUivUmHN2U | Basics of Art-Net}}
{{DMXC3 Manual-Tableentry Videolink | XwB33fY0so4 | Use of DMX-Workshop}}
{{DMXC3 Manual-Tableentry Videolink | eoJDN1fplBs | Error images with Art-Net}}
|}

== Further Information ==
<references/>

<noinclude>
[[Category: Manual DMXControl 3]]
</noinclude>

[[de: DMX-Interfaces_DMXC3]]

Template:DMXC3 Manual-Tableheader Settings

2025-03-04T21:34:40Z

Jkuehn:

<includeonly>{{(!}} class="wikitable toptextcells"
{{!-}} class="hintergrundfarbe10"
{{#ifeq: {{{1}}} | de |
! colspan="2" {{!}} Einstellung !! style="width: 175px" rowspan="2" {{!}} Möglicher Parameter !! style="width: 175px" rowspan="2" {{!}} Standardwert !! rowspan="2" {{!}} Beschreibung
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} deutsche GUI !! style="width: 175px" {{!}} englische GUI
{{!-}}
}}

{{#ifeq: {{{1}}} | en |
! Setting !! style="width: 175px" rowspan="2" {{!}} Possible Parameters !! style="width: 175px" rowspan="2" {{!}} Default value !! rowspan="2" {{!}} Description
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} English GUI
{{!-}}
}}</includeonly><noinclude>{{Documentation Language reference}}</noinclude>

Template:DMXC3 Manual-Tableheader Effect parameters

2025-03-04T21:32:15Z

Jkuehn:

<includeonly>{{(!}} class="wikitable toptextcells"
{{!-}} class="hintergrundfarbe10"
{{#ifeq: {{{1}}} | de |
! colspan="2" {{!}} Parameter !! style="width: 175px" rowspan="2" {{!}} Mögliche Werte !! style="width: 75px" rowspan="2" {{!}} Einheit !! rowspan="2" {{!}} Beschreibung
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} deutsche GUI !! style="width: 175px" {{!}} englische GUI
{{!-}}
}}

{{#ifeq: {{{1}}} | en |
! Parameter !! style="width: 175px" rowspan="2" {{!}} Possible values !! style="width: 75px" rowspan="2" {{!}} Unit !! rowspan="2" {{!}} Description
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} English GUI
{{!-}}
}}</includeonly><noinclude>{{Documentation Language reference}}</noinclude>

Template:DMXC3 Manual-Tableheader Effect parameters

2025-03-04T21:31:39Z

Jkuehn:

<includeonly>{{(!}} class="wikitable toptextcells"
{{!-}} class="hintergrundfarbe10"
{{#ifeq: {{{1}}} | de |
! colspan="2" {{!}} Parameter !! style="width: 175px" rowspan="2" {{!}} Mögliche Werte !! style="width: 75px" rowspan="2" {{!}} Einheit !! rowspan="2" {{!}} Beschreibung
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} deutsche GUI !! style="width: 175px" {{!}} englische GUI
{{!-}}
}}

{{#ifeq: {{{1}}} | en |
! colspan="2" {{!}} Parameter !! style="width: 175px" rowspan="2" {{!}} Possible values !! style="width: 75px" rowspan="2" {{!}} Unit !! rowspan="2" {{!}} Description
{{!-}} class="hintergrundfarbe10"
! style="width: 175px" {{!}} English GUI
{{!-}}
}}</includeonly><noinclude>{{Documentation Language reference}}</noinclude>

Circle (Effect) DMXC3

2025-03-04T21:28:20Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0 }} The {{Manual Objectcaption|Circle}} is an {{Manual Windowcaption|effect}} of the type {{Manual Objectcaption | 2D Effect}}. The Circle effect allows you to display various movements on a {{Manual Windowcaption|Device Group}}, all of which are based on a circle with arbitrary width and height. = Possible Applications = The {{Manual Objectcaption..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0
}}

The {{Manual Objectcaption|Circle}} is an {{Manual Windowcaption|[[Effects and Filters DMXC3|effect]]}} of the type {{Manual Objectcaption | 2D Effect}}. The Circle effect allows you to display various movements on a {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}}, all of which are based on a circle with arbitrary width and height.

= Possible Applications =
The {{Manual Objectcaption|Circle}} effect can only be applied to the Position function.

= Effect Parameters =
{{DMXC3 Manual-Tableheader Effect parameters | en}}

| Amplitude X || Angle || Degrees (°) || Deviation from the zero point along the X-axis (often the Pan-axis). Both positive and negative values are allowed.
|-
| Amplitude Y || Angle || Degrees (°) || Deviation from the zero point along the Y-axis (often the Tilt-axis). Both positive and negative values are allowed.
|-
| Frequency || Numeric value || Hertz (Hz) || Sets the repetition frequency, i.e., how long a full cycle lasts.
|-
| Phase || Angle || Degrees (°) || Specifies the range, i.e., the temporal gap between the first and last device in the selection.
|}

= Tips =
For the Circle effect, the following values for the parameters produce interesting results:
* Alternating, counteracting movement
* Movement only on the Pan or Tilt axis in the form of a wave motion

<noinclude>
[[Category: Manual DMXControl 3]]
[[Category: Effects and Filters DMXC3]]
</noinclude>

[[de: Circle_(Effect)_DMXC3]]

Chaser (Filter) DMXC3

2025-03-04T21:25:06Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0 }} The {{Manual Objectcaption|Chaser}} is an {{Manual Windowcaption|effect}} of the type {{Manual Objectcaption | Filter}}. The Chaser can be used to display various patterns on a {{Manual Windowcaption|Device Group}}. = Possible Applications = The {{Manual Objectcaption|Chaser}} can be applied to the following functions, among others. All possibl..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0
}}

The {{Manual Objectcaption|Chaser}} is an {{Manual Windowcaption|[[Effects and Filters DMXC3|effect]]}} of the type {{Manual Objectcaption | Filter}}. The Chaser can be used to display various patterns on a {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}}.

= Possible Applications =
The {{Manual Objectcaption|Chaser}} can be applied to the following functions, among others. All possible functions can be discovered by selecting the Chaser and applying it to a function using the {{Manual Buttons|Apply}} button.

= Effect Parameters =
{{DMXC3 Manual-Tableheader Effect parameters | en}}

| Peak || Function-dependent value || --- || Specifies the value that the devices will assume in the active state. The possible value depends on the function to which the effect is applied.
|-
| Duration || Numeric value || ms || Sets the duration for which the value stored under {{Manual Fields|Peak}} will be output.
|-
| Break steps || Numeric value || --- || This value defines after how many steps the time entered under {{Manual Fields|Break time}} should be triggered.
|-
| Break time || Numeric value || ms || The {{Manual Fields|Break time}} represents the time after which the effect will be paused once the {{Manual Fields|Break steps}} are reached.
|-
| Fade time || Numeric value || ms || Determines the time it takes for the effect to fade between two steps. The fade-in time is added to the {{Manual Fields|Playback time}}.
|-
| Size || Integer value || --- || Specifies how many devices will simultaneously assume the value stored under {{Manual Fields|Peak}}.
|-
| Step size || Integer value || --- || Specifies how many devices will be switched simultaneously when moving to the next step.
|-
| Fade curve || List || --- || With this parameter, you select a curve that defines how the fading should occur.
|-
| Play mode || List || --- || Here, you determine the pattern of the effect. This list also includes any self-defined patterns.
|}

= Special Functions =
This effect has the following special functions:
* Custom Chasers

== Custom Chasers ==
In the {{Manual Objectcaption|Chaser}}, you can also create your own patterns. This is done using a CSV file. The CSV file can be created in various ways, such as with Notepad++ or Microsoft Excel. The structure consists of three components:
# the keyword
# the name of the Chaser
# the block containing the steps to be executed

In the file, the first line must always contain the keyword <code>ChaserDefinitionFile</code>. Only when this keyword is present will DMXControl 3 use the CSV file as a basis for additional patterns for the Chaser, provided all subsequent checks are passed. In the second line, you specify the name of your pattern, which will then be added to the list of possible playback modes (Play modes) for the Chaser.

The block with the steps to be executed is a matrix. Each column represents a device according to the manual selection order in the stage view or the sorting in a device group. Each row represents a step. So, if you provide values in eight columns and two rows, the pattern consists of two steps and will repeat from the ninth device. Values between <code>0</code> and <code>1</code> are allowed for the cells. Intermediate steps are also possible, such as <code>0.45</code> or <code>0,45</code>. A comma <code>,</code> or a period <code>.</code> can be used as the decimal separator. The semicolon <code>;</code> is the separator for a new column.

{{Manual Box | en | Attention | No spaces are allowed within a row. Otherwise, the later import will fail. However, for better readability, additional paragraphs can be inserted.}}

Based on this description, a CSV file for a simple custom pattern might look like this:
ChaserDefinitionFile

MyChaser:
1;0;1;0;0;1;0;1
0;1;0;1;1;0;1;0

It is possible to store multiple patterns within a single CSV file. To do so, simply add a line with the name of the new pattern and the block with the values. It’s also allowed for the patterns to have different numbers of steps and to apply the pattern to a different number of devices before the pattern repeats.

ChaserDefinitionFile

Mirrored:
1;0.6;0.4;0;0;0.4;0.6;1
0;0.4;0.6;1;1;0.6;0.4;0

Sawtooth:
0,0;0,2;0,4;0,6;0,8;1,0
0,2;0,4;0,6;0,8;1,0;0,0
0,4;0,6;0,8;1,0;0,0;0,2
0,6;0,8;1,0;0,0;0,2;0,4
0,8;1,0;0,0;0,2;0,4;0,6
1,0;0,0;0,2;0,4;0,6;0,8

To provide your own patterns to the Chaser effect in DMXControl 3, you need to add the CSV file to the project as an additional file. The quickest way to do this is by opening the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}} and dragging the file into the table area. Alternatively, the context menu provides the entry {{Manual MenuText |Import files}}, which will open the corresponding file selection dialog.

After the CSV file is added to the project, the Chaser can be applied in the usual way.

{{Manual Box | en | Important | As with predefined patterns for the Chaser, the custom patterns also do not offer a parameter to change the playback order of the steps in the pattern. So, for example, if you want to play the Sawtooth pattern from the above example in reverse order, you need to create a completely new pattern for the Chaser and save it under a different name.}}

= Tips =
For the Chaser effect, the following values for the parameters create particularly interesting results that you might not expect from this effect at first glance:
* Random strobe or a thunderstorm effect with a continuously changing number of simultaneously active devices
* Running from the center with a step gap, linked with a {{Manual Windowcaption|[[Speed Master (Master) DMXC3|Speed Master]]}}

<noinclude>
[[Category: Manual DMXControl 3]]
[[Category:Effects and Filters DMXC3]]
</noinclude>

[[de: Chaser_(Filter)_DMXC3]]

Category:Effects and Filters DMXC3

2025-03-04T21:15:46Z

Jkuehn: Created page with "This page summarizes all articles about the {{Manual_Windowcaption|Effects and Filters}}. [Category: Manual DMXControl 3]] de: Kategorie:Effects_and_Filters_DMXC3"

This page summarizes all articles about the {{Manual_Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}.

[Category: Manual DMXControl 3]]

[[de: Kategorie:Effects_and_Filters_DMXC3]]

Default colors for the color picker (Did you know?) DMXC3

2025-03-04T21:12:46Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.2.1 }} Did you know that you don't have to select your frequently used colors in your DMXControl 3 projects every time in the {{Manual_Windowcaption|Colorpicker}}? In this "Did you know?" article, you’ll learn how to set your own default colors. You may have experienced this: In your project, you use a selection of standard colors for your devices. You’ve noted down the color v..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.1
}}

Did you know that you don't have to select your frequently used colors in your DMXControl 3 projects every time in the {{Manual_Windowcaption|[[Control_Panel_DMXC3|Colorpicker]]}}? In this "Did you know?" article, you’ll learn how to set your own default colors.

You may have experienced this: In your project, you use a selection of standard colors for your devices. You’ve noted down the color values somewhere and manually enter them repeatedly in the {{Manual_Windowcaption|[[Device_Control_DMXC3|Device Control]]}}. But did you know that DMXControl 3 can save you this work? In this "Did you know?" article, we’ll show you how.

= Creating a new color list =
First, you need to create a new {{Manual_Windowcaption|[[Color_List_DMXC3|Color List]]}} in the {{Manual_Windowcaption|[[Project_Explorer_DMXC3|Project Explorer]]}} under the directory {{Manual_Objectcaption|[[Item_List_DMXC3|Item Lists]]}}. To do this, click the button {{Manual_Buttons|Create Item List (Add Item List)}} in the menu bar. In the following window, select the "Color List" entry and confirm by clicking {{Manual_Buttons|OK}}. The newly created color list can be named according to your preferences. In this example, the color list is simply named {{Manual_Fields|Standard Colorlist 1}}. By double-clicking the entry, a new window opens where you can add any number of colors to this color list.
{|width="100%"
|{{Picture_with_subtitle|DMXC3_Didyouknow_Create_new_colorlist_01.jpg|1|Creating a new color list.|center|480px}}
|{{Picture_with_subtitle|DMXC3_Didyouknow_Create_new_colorlist_02.jpg|2|Naming the color list.|center|480px}}
|{{Picture_with_subtitle|DMXC3_Didyouknow_Create_new_colorlist_03.jpg|3|Selecting colors for the new color list.|center|480px}}
|}

= Setting the color list for default colors =
== Option 1: Via project settings ==
To use this color list globally in all your projects from the color picker, open the {{Manual_Windowcaption|[[Settings_DMXC3|Settings]]}} and go to the settings for the GUI under the section {{Manual_Objectcaption|Current Project Settings}}. In the only entry {{Manual_Fields|Colorpicker Colorlist Name}}, simply select the color list whose colors you want to use as default colors for the color picker. It’s also possible to create multiple color lists and then change the used color list for the default colors in the color picker depending on the situation. Once you save the changed GUI settings by clicking {{Manual_Buttons|OK}}, you can immediately get started. From now on, you’ll find an additional button in the color picker called "Default Colors." This will be visible when you select, for example, an LED spotlight or a moving head with a color wheel in the {{Manual_Windowcaption|[[Stage_View_DMXC3|Stage View]]}}. Thanks to the HAL, you can also use your own default colors for devices with a color wheel. The HAL will use the color of the moving head that is closest to the selected default color.
{|width="100%"
|{{Picture_with_subtitle|DMXC3_Didyouknow_Define_standard_colorlist_01.jpg|4|Settings for the color list for the color picker.|center|480px}}
|{{Picture_with_subtitle|DMXC3_Didyouknow_Define_standard_colorlist_02.jpg|5|Changing the color list.|center|480px}}
|}
This setting is saved per project. This means that you can set different color lists for the default colors in the color picker for different projects.

== Option 2: Via the color list name ==
In addition to the method described above, there’s a second option to create your own default colors for the color picker. Simply rename a color list to {{Manual_Fields|ColorpickerDefault}} – it’s important to use the American spelling of the word "color" (without the "u" after the second "o"). DMXControl 3 will then automatically use this color list for the default colors in the color picker.
{{Picture_with_subtitle|DMXC3_Didyouknow_Define_standard_colorlist_03.jpg|6|Defining the color list for default colors by renaming the color list.|center|480px}}

[[Category: Did you know? DMXControl 3]]

[[de: Standardfarben_für_den_Colorpicker_(Schon_gewusst%3F)_DMXC3]]

Overlay effects (Did you know?) DMXC3

2025-03-04T21:01:48Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.2.1 }} Many things in DMXControl 3 are structured differently than in DMXControl 2, including the effect engine. This incredibly powerful effect engine was explored in more detail in our {{DMXCWebLinks|Forum|News-Article|422|Did you know? from 22.01.2018}}. = Overlaying effects = Let’s first start with what an effect actually is. Unlike in DMXControl 2, effects in DMXControl 3 are various mathematical..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.1
}}

Many things in DMXControl 3 are structured differently than in DMXControl 2, including the effect engine. This incredibly powerful effect engine was explored in more detail in our {{DMXCWebLinks|Forum|News-Article|422|Did you know? from 22.01.2018}}.

= Overlaying effects =
Let’s first start with what an effect actually is. Unlike in DMXControl 2, effects in DMXControl 3 are various mathematically describable functions, such as a sine wave or a sawtooth, or lighting functions such as a chaser. These effects can be applied to almost all device properties. For example, a chaser can be applied to the dimmer of a group of devices, and the light beam will move from one lamp to the next. But here’s the trick: we can overlay this chaser with additional effects. This results in a combination of both effects being output. In our example, we overlay the existing chaser with another one that runs backward. This creates a Knight Rider-like running light effect. However, other effect overlays are also possible. There are many possibilities for the created effects. With simple tools, you can generate amazing lighting effects. Give it a try!

[[Category: Did you know? DMXControl 3]]

[[de: Effekte_überlagern_(Schon_gewusst%3F)_DMXC3]]

Did you know DMXC3

2025-03-04T20:51:28Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Content = x }} In the article series {{Manual_Windowcaption|Did you know?}}, individual functions of DMXControl 3 are presented at irregular intervals, or various tips and tricks are showcased. The focus when selecting the functions is primarily on those that are either not immediately obvious or on those whose scope and capabilities go beyond initial assumptions upon first contact. Many of the contents of these {{Man..."

{{Manual Header
| Type = DMXC3 Main-Software
| Content = x
}}

In the article series {{Manual_Windowcaption|Did you know?}}, individual functions of DMXControl 3 are presented at irregular intervals, or various tips and tricks are showcased. The focus when selecting the functions is primarily on those that are either not immediately obvious or on those whose scope and capabilities go beyond initial assumptions upon first contact. Many of the contents of these {{Manual_Windowcaption|Did you know?}} editions can be found in the [[Manual_DMXControl_3|manual]], when it comes to the actual description of the function. However, the {{Manual_Windowcaption|Did you know?}} articles focus more on concrete use cases and describe when you should ideally use the respective function and at what time.

Along with the constantly growing documentation for DMXControl, the {{Manual_Windowcaption|Did you know?}} articles will remain an integral part of DMXControl Projects' weekly releases. Therefore, the article series is always good for browsing. You can find it here: '''News Section''' in '''{{DMXCWebLinks|Forum}}''' under the category {{Manual_Windowcaption|{{DMXCWebLinks|Forum|News-Category|5|Did you know?}}}}.

Selected {{Manual_Windowcaption|Did you know?}} articles can also be found here in the Wiki, especially if they contain a useful tip that doesn’t fit into a manual article. The corresponding editions are listed in the [[Manual_DMXControl_3|contents overview of DMXControl 3]].

[[Category: Manual DMXControl 3]]

[[de: Schon_gewusst_DMXC3]]

Show structure DMXC3

2025-03-04T20:30:17Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.2.3 }} How can a show be structured efficiently in DMXControl 3? This is a question that should ideally be addressed at the start, especially for larger projects, so that you don’t get sidetracked while programming, particularly when it comes to adjusting individual lighting moods. A systematic approach from the beginning is helpful to quickly track your work even after some time. This article covers a..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.3
}}

How can a show be structured efficiently in DMXControl 3? This is a question that should ideally be addressed at the start, especially for larger projects, so that you don’t get sidetracked while programming, particularly when it comes to adjusting individual lighting moods. A systematic approach from the beginning is helpful to quickly track your work even after some time.

This article covers a few points of DMXControl 3 and tries to highlight the differences between various working methods. Additionally, comparisons to DMXControl 2 are made, which might be of interest, especially for those transitioning to DMXControl 3.

In principle, it is possible to use the respective concepts simultaneously — there are no software limitations. In such cases, however, it is highly recommended to follow a comprehensible methodology or make use of the various options for labeling and commenting, for example, in the {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} themselves.

= Conceptual Questions =
== Scene vs. Preset ==
{{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} do not necessarily have to consist solely of many individual {{Manual Windowcaption|Scenes (Cues)}}. Sometimes, you should consider whether using {{Manual Windowcaption|[[Preset DMXC3|Presets]]}} could be advantageous and whether they might simplify programming a show.

''Use case: I want to use a specific color of an LED light, such as a bright orange or magenta, at several points in my show. The color is fully mixed, meaning that in the case of {{Manual Value|Caption|orange}}, the RGB values are {{Manual Value||255; 102; 25}}.''

In principle, you can store the desired color or any other property manually in each {{Manual Windowcaption|Scene}}. However, in this case, {{Manual Windowcaption|Presets}} are the better choice, as a specific color, position, or movement might be used multiple times in the project. When using Presets, it's important to consider how the preset is applied. {{Manual Reference|arrow|Further explanations regarding the use cases of a single preset can be found under {{Manual Windowcaption|[[Preset DMXC3|Presets]]}}.}}
{{Manual Box | en | Hint | Despite the advantages of presets, this function should initially be disregarded when first starting with DMXControl 3. It is recommended to work with {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}, which will contain one or more scenes to familiarize yourself with the basic operation of DMXControl 3.}}

== Many Scenes vs. Many Cuelists ==
When is it advantageous to work with few {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} that contain many scenes? And when might the opposite scenario, where there are many cuelists with very few scenes, be the better option? This question can generally be answered as follows:
* Few Cuelists, but many scenes per Cuelist: Pre-programmed shows for musicals, plays, or true music-synchronized light shows in the form of a '''Setlist''' or '''Showlist'''
* Many Cuelists with only a few scenes: Live shows in clubs, discos, and parties, as well as concerts by, for example, cover bands, implemented as a '''Modular System'''

These general statements are based on the fundamental structure of the show and how it will be executed. The number and type of devices (simple LED lights, moving heads, etc.) used are secondary at this point.

=== Setlist / Showlist ===
If the setlist, play, or music for the light show is known in advance with sufficient lead time, the required lighting moods can be programmed quite specifically — you don’t need to think too much outside the box. You can focus on programming exactly what should happen on stage. As a result, the complexity of the project remains more manageable, which is particularly useful when adjusting a specific scene to fit the circumstances on-site. Simply load the {{Manual Windowcaption|Scene}} into the {{Manual Windowcaption|[[Programmer DMXC3|Programmer]]}}, adjust the values, and update the scene — done. There’s no need to search through the {{Manual Windowcaption|Cuelists}} to find the right one, open it, select the scene, and load it into the {{Manual Windowcaption|Programmer}}. If the {{Manual Windowcaption|Scenes}} contain one or more {{Manual Windowcaption|[[Preset DMXC3|Presets]]}}, the required correction can be made even faster. Additionally, you don’t set the duration of lighting moods in multiple {{Manual Windowcaption|Cuelists}}, but instead have one cuelist that contains all the times. There’s no need to worry about ending individual cuelists, which wouldn’t be necessary with a single cuelist containing all the lighting moods as scenes.

=== Modular System ===
==== Use Cases ====
The concept of working with many {{Manual Windowcaption|Cuelists}} is also highly relevant, as shown by the examples above: here, flexible lighting moods and a modular system are often required, allowing the show to be created live or created because a setlist, etc., isn’t available in advance. Therefore, this necessary flexibility must come from the project itself.

==== Implementation ====
In contrast to the setlist concept, where a new lighting mood is activated with just one click, the modular system executes multiple cuelists simultaneously. This means that you must start several cuelists or select a new one to achieve a different lighting mood.

When creating cuelists in the modular system, you divide them based on the significant functions of the devices you’re using. A common division might be:
* Brightness
* Color
* Movement or Position
* Gobo

==== Important Background ====
It is important to keep in mind that when addressing the dimmer of a simple LED light, for example, only one thing can be implemented: either setting the brightness to {{Manual Value||50%}} or {{Manual Value||72%}} — both at the same time is technically impossible. The same applies to moving heads for position and movement: the device can either remain at a specific position or perform a movement.

For example, if the light jockey is given five different movements for the same moving head group, with each movement saved in its own cuelist, all these {{Manual Windowcaption|Cuelists}} are then assigned to a {{Manual Windowcaption|[[Cuelist Group DMXC3|Cuelist Group]]}}, and only one cuelist within the group can be executed at a time. This allows the light jockey to choose a movement by starting one of the cuelists. With the {{Manual Windowcaption|Cuelist Group}} and the chosen option, all other cuelists in that group are automatically stopped. You can even use a carefully chosen release time to transition between cuelists, avoiding jumps in movements. However, this requires a certain level of creativity from the light jockey to always put together the best and most fitting components.

Thus, working with many cuelists is better suited for light jockeys and live light control, while storing everything in a single long cuelist with one scene per lighting mood is more advantageous for theater and/or musical productions.

= Comparisons to DMXControl 2 =
== Scenes vs. Presets ==
In DMXControl 2, a scene is actually a fixed state. Here, you save a fixed distribution of values for the device channels, and in most cases, a fixed (partial) lighting mood.

In DMXControl 3, a scene is also a storage of values, but of device property values. This means that an effect (e.g., a sawtooth on the color property) can also be stored in a scene. So, when using effects, there’s no need to save values in multiple scenes individually, which was particularly the case in situations where "brightness increases steadily across a series of devices." While you can still manually program such an effect in DMXControl 3, it wouldn’t be the best approach.

Instead, in a scene, you can use an effect like a sawtooth to store an entire running light. Thus, a scene in DMXControl 3 is more akin to a compositional scene than a simple scene. However, scenes in DMXControl 3 are assigned directly to cuelists, unlike simple scenes in DMXControl 2. There is no central scene library like the one in DMXControl 2, so multiple cuelists cannot reference the same scene.

== Cuelists ==
The comparison between the two concepts can be described in fewer words: essentially, there are no differences regarding the project structure in DMXControl 2. In DMXControl 2, different tools were used:
* Use case 1: Textbook, Audio/Timecode player, or cuelist
* Use case 2: Effect sequencer
In DMXControl 3, everything effectively happens within the cuelist domain, as cuelists are significantly more powerful than simple scenes in DMXControl 2.

[[de: Showaufbau_DMXC3]]

Manual DMXControl 3

2025-03-04T20:23:31Z

Jkuehn:

This is the German manual for the light control software DMXControl 3. Below you will find an overview of all articles contained in this manual. Besides the Quickstart and the Tips and Tricks, which primarily answer practical questions, under Program function all functions, windows etc. of DMXControl 3 are explained exactly in the corresponding context - so like a direct glossary. The tooltips from DMXControl 3 itself also refer to the respective article. In addition, we have published numerous Did you know? articles about DMXControl 3.

= General =
{| width=100%
| width="50%" valign=top |
[[Foreword DMXC3|Foreword about the manual]] 
[[Introduction DMXC3|Introduction]] 
|valign=top |
[[Installation_DMXC3|Installation of DMXControl 3]] 
|}

= Quick start =
{| width=100%
| width="50%" valign=top |
[[Showsetup DMXC3|Add new devices to the project]] 
[[First cuelists_DMXC3|Create cuelists and save cues]] 
Going from a button in Softdesk to a cuelist and backwards 
|valign=top |
[[Effect examples DMXC3|Examples around effects and filters]] 
|}

= Tipps and tricks =
{| width=100%
| width="50%" valign=top |
=== General questions ===
[[FAQ DMXC3|Frequently asked questions (FAQ)]] 
[[Change over from DMXControl 2 to DMXControl 3|Change over from DMXControl 2 to DMXControl 3]]

=== Troubleshooting ===
[[Troubleshooting (General Information) DMXC3|Frequently occurring problems (Troubleshooting)]] 
[[Workarounds (General Information) DMXC3|Tricks for certain use cases (Workarounds)]] 
[[Known Bugs (General Information) DMXC3|Known bugs]]

=== Working practices and project concepts ===
[[Operation DMXC3|Mode of operation and basic concept of DMXControl 3]] 
[[Show structure DMXC3|Basics of the show structure]]

|valign=top |
=== Small and big helpers ===
[[Stream_Deck_DMXC3|Stream Deck]] 
[[Key assignments and working aids_DMXC3|Key assignments and working aids]] 

=== Did you know? ===
[[Did you know DMXC3|Introduction]] 
 
[[Overlay effects (Did you know?) DMXC3|Overlay effects (Did you know? published at 22.01.2018)]] 
[[Copy-Paste Stage View (Did you know?) DMXC3|Copy&Paste inside the Stage View (Did you know? published at 19.02.2018)]] 
[[Multiple selection (Did you know?) DMXC3|Multiple selection (Did you know? published at 19.03.2018)]] 
[[Default colors for the color picker (Did you know?) DMXC3|Default colors for the color picker (Did you know? published at 24.07.2018)]] 
|}

= Program functions =
{| width=100%
| width="50%" valign=top |
=== A ===
[[Autoprepare (Cuelist) DMXC3|Autoprepare]]

=== B ===
[[GUI DMXC3|GUI]] 
[[Blackout DMXC3|Blackout]] 
[[Stage View DMXC3|Stage View]]

=== C ===
[[Chat DMXC3|Chat]]

=== D ===
[[File DMXC3|Project Files]] 
[[Update Project DDFs DMXC3|Update Project DDFs]] 
[[DMX-Interfaces DMXC3|DMX-Interfaces]] 
[[Device Manager DMXC3|Device Manager (Add Device Dialog)]] 
[[DDF Library DMXC3|DDF Library]] 
[[DMX-In DMX-Out-Mapping DMXC3|DMX-In DMX-Out-Mapping]]

=== E ===
[[Effects and Filters DMXC3|Effects and Filters]] 
[[Effect Visualizer DMXC3|Effect Visualizer]] 
[[Freeze DMXC3|Freeze]] 
[[Input Assignment DMXC3|Input Assignment]] 
[[Executor DMXC3|Executor]] 
[[Executor Page DMXC3|Executor Page]]

=== F ===
[[Fanning DMXC3|Fanning]] 
[[Color List (Item List) DMXC3|Color List]]

=== G ===
[[Device DMXC3|Device]] 
[[Device Group DMXC3|Device Group]] 
[[Device Control DMXC3|Device Control]] 
[[Affinity DMXC3|Gobo Affinity]] 
[[Gobo List (Item List) DMXC3|Gobo List]] 
[[Group Handling DMXC3|Group Handling]]

=== H ===
[[Hardware Abstraction Layer (HAL) DMXC3|Hardware Abstraction Layer (HAL)]] 
[[Main Switch DMXC3|Main Switch]] 
[[Highlight DMXC3|Highlight]] 
[[HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3|HTP-, LTP- and LoTP-Mixing]]

=== K ===
[[Channel Overview DMXC3|Channel Overview]] 
[[Kernel DMXC3|Kernel (Server)]]

| valign=top |
=== L ===
[[Electricity DMXC3|Electricity]] 
[[Launcher DMXC3|Launcher]]

=== M ===
[[Macroboard DMXC3|Macroboard]] 
[[Master DMXC3|Master]] 
[[Matrix DMXC3|Matrix]] 
[[MIDI Manager DMXC3|MIDI Manager]]

=== N ===
[[Network Explorer DMXC3|Network Explorer]] 
[[Network Concept DMXC3|Network Concept ***]] 

=== O ===
[[Item List DMXC3|Item List]]

=== P ===
[[Panel Concept DMXC3|Panel Concept ***]] 
[[Patching DMXC3|Patching]] 
[[Plugin Manager DMXC3|Plugin Manager]] 
[[Position List (Item List) DMXC3|Position List]] 
[[Preset DMXC3|Preset]] 
[[Settings DMXC3|Application and project settings]] 
[[Programmer DMXC3|Programmer]] 
[[Programmer Filter DMXC3|Programmer Filter]] 
[[Project Administration DMXC3|Project Administration]] 
[[Project Explorer DMXC3|Project Explorer]] 
[[Project ToDos DMXC3|Project ToDos]] 
[[Log Files DMXC3|Log Files]]

=== R ===
[[Radix DMXC3|Radix]] 
[[Absolute and Relative Values DMXC3|Absolute and Relative Values]]

=== S ===
[[Softdesk DMXC3|Softdesk]] 
[[Softdesk Designer DMXC3|Softdesk Designer]] 
[[Control Panel DMXC3|Control Panel]] 
[[Cuelist DMXC3|Cuelist]] 
[[Cuelist Group DMXC3|Cuelist Group]] 
[[Cue Timing Editor DMXC3|Cue Timing Editor]]

=== T ===
[[Timecode Player DMXC3|Timecode Player]] 
[[Tracking (Cuelist) DMXC3|Tracking]]

=== U ===
[[Umbra DMXC3|Umbra]]
|}

= Categories =
{| width=100%
| width="50%" valign=top |
'''[[:Category:DMXControl 3|DMXControl 3]]''' 
''[[:Category:Manual DMXControl 3|Manual]]'' 
''[[:Category:Did you know? DMXControl 3|Did you know?]]'' 
''[[:Category:Tutorials DMXControl 3|Tutorials]]'' 
| valign=top |
'''[[:Category:Effects and Filters DMXC3|Effekte and Filter]]''' 
'''[[:Category:Executor DMXC3|Executoren]]''' 
'''[[:Category:Input Assignment DMXC3|Input Assignment]]''' 
''[[:Category:Converter Nodes DMXC3|Converter nodes]]'' 
''[[:Category:Logic Nodes DMXC3|Logging nodes]]'' 
''[[:Category:Logic Nodes DMXC3|Logic nodes]]'' 
''[[:Category:Logic Nodes DMXC3|Value object nodes]]'' 
''[[:Category:Wrapper Nodes DMXC3|Wrapper-Nodes]]'' 
'''[[:Category:Options DMXC3|Options]]''' 
'''[[:Category:Master DMXC3|Master]]''' 
|}

= Links und Referenzen =
* {{DMXCWebLinks|YouTube}} from DMXControl Projects with numerous video tutorials about DMXControl 3

[[File: DMXC_Manual_Hauptseite_By-nc-nd.eu.png | link=http://creativecommons.org/licenses/by-nc-nd/3.0/de/deed.en |150px| By-nc-nd.eu-Lizenz]]

The manual of DMXControl 3.0 written by DMXControl Projects e.V. is provided under [http://creativecommons.org/licenses/by-nc-nd/3.0/de/deed.en Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Germany license].

[[de:Inhaltsübersicht_Hauptprogramm_DMXC3]]
[[Category:DMXControl 3]]

__NOTOC__ __NOEDITSECTION__

Known Bugs (General Information) DMXC3

2025-03-04T20:22:23Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.2.3}} This article loosely addresses various already known issues, which can often be worked around using a workaround, until the implementation of the missing function or the correction of the error is finalized. Known bugs are issues that are considered defects, but they do not negatively affect the use of the software when the following instructions are followe..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.2.3}}

This article loosely addresses various already known issues, which can often be worked around using a [[Workarounds (General Information) DMXC3|workaround]], until the implementation of the missing function or the correction of the error is finalized.

Known bugs are issues that are considered defects, but they do not negatively affect the use of the software when the following instructions are followed. For this reason, these points may only be addressed at a later time.

{| class="wikitable toptextcells"
|- class="hintergrundfarbe8"
! style="width: 125px;" | Ticket !! style="width: 75px;" | DMXC Version !! Description !! style="width: 125px;" | Notes !! style="width: 75px;" | Expected Fix
|-
! {{DMXCWebLinks|FS|Ticket|3784}}
| 3.2.0 || Internal markers for the Input Assignment || [[Workarounds (General Information) DMXC3|Workaround]] available || not set
|-
! {{DMXCWebLinks|FS|Ticket|4427}}
| 3.2.3 || Softdesk not saved when closing the GUI || [[Workarounds (General Information) DMXC3|Workaround]] available || 3.4.0
|}

[[Category: Manual DMXControl 3]]

[[de: Known_Bugs_(General_Information)_DMXC3]]

Workarounds (General Information) DMXC3

2025-03-04T20:19:26Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} This article gathers various known use cases that can often be solved with a workaround, until they are corrected in a new update or the function is added. {{Manual Box | en | Important | If errors occur in the software or a function is missing, it would be great if they could be entered as a new ticket in our '''{{DMXCWebLinks|FS|Project|3|Bugtracker}}'''.}} {{Manual Box | en | Hint | Some of the wo..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

This article gathers various known use cases that can often be solved with a workaround, until they are corrected in a new update or the function is added.

{{Manual Box | en | Important | If errors occur in the software or a function is missing, it would be great if they could be entered as a new ticket in our '''{{DMXCWebLinks|FS|Project|3|Bugtracker}}'''.}}

{{Manual Box | en | Hint | Some of the workarounds described below are known and will be fixed in a future version.
''An overview of the workarounds that will be achievable with a native function in a later version of DMXControl 3 can be found under {{Manual Windowcaption|[[Known Bugs (General Information) DMXC3|Known Bugs]]}}.''}}

= Effects and Filters =
== Dynamic Manipulation of Effects ==
'''Use Case'''

The audio level fluctuations of a group of LED spotlights or LED bars should be simulated, with the fluctuations being irregular and having various maximum values, as in reality. The base for this is the PWM-Static filter.

Manually, the fluctuations could be changed via the entered {{Manual Windowcaption|[[Master DMXC3|Parameter-Master]]}}. However, such an effect cannot currently be triggered via a {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.

'''Solution'''

You essentially have to loop back the appropriate parameter master to directly access it from the project. This loop can be created as follows:
# Create a dummy device, patched to an unused DMX address. For example, use a Generic Dimmer or Generic RGB device.
# In the {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}, create a connection set where you use the {{Manual Objectcaption|[[DMXC Mixer (Input Assignment) DMXC3|DMXC Mixer]]}} node to display the output values. Here, connect the {{Manual Commands|Intensity}} output of the {{Manual Objectcaption|DMXC Mixer}} node to the {{Manual Commands|Fader Value}} input of the {{Manual Objectcaption|[[Parameter Master (Input Assignment) DMXC3|Parameter-Master]]}} node.

= Softdesk =
== Multiple Information on a Button in Softdesk ==
'''Use Case'''

In a {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}, a button should display both the icon of a gobo and also switch a corresponding {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}} on and off. It should also visually indicate the status with two different colors.

'''Cause'''

The buttons currently have only one input, which can handle numerous different types of information:
* Status
* Button label
* Background image
* Color
If all this information is sent at once, usually only one value change is processed by the button.

'''Solution'''

To ensure the button processes all the different information, these must be passed in sequence and in a structured manner. This can be done by inserting a {{Manual Objectcaption|[[FiFo (Input Assignment) DMXC3|FiFo]]}} node before the button for the "structured transfer." Connect all signal paths that the button should handle to the inputs of the {{Manual Objectcaption|FiFo}} node. You may need to adjust the time value for the update rate and set it slightly higher than the default of <code>50ms</code>.

== Cuelist Monitor is Empty After Project Load ==
'''Use Case'''

In a Softdesk, one or more cuelist monitors are used to start and stop a selection of cuelists. However, these are always empty when the project is loaded.

'''Solution'''

The connection set that passes information to the Cuelist Monitor, indicating which cuelist group should be displayed, needs to be supplemented with a manual reset function. {{Manual Reference | arrow | For an explanation, see {{Manual Windowcaption|[[Cuelist Monitor (Softdesk) DMXC3|Cuelist Monitor]]}}.}}

= Input Assignment =
== Use the Same Value in Multiple Locations ==
'''Use Case'''

A specific value needs to be processed in several connection sets. However, this value is not coming from a MIDI controller, but is generated "within" the project.

'''Solution'''

Create a separate {{Manual Objectcaption|[[Parameter Master (Master) DMXC3|Parameter-Master]]}} that is solely used to receive (remember) a specific value and make it available again in any number of connection sets.

If only the value <code>0</code> or <code>1</code>, respectively <code>false</code> or <code>true</code>, needs to be stored, you can work without upstream and downstream nodes.

If you want to transfer a numerical value, for example between <code>0</code> and <code>160</code>, to other connection sets, set this value range centrally in the properties of the corresponding {{Manual Objectcaption|[[Parameter Master (Master) DMXC3|Parameter-Master]]}} in the {{Manual Objectcaption|[[Project Explorer DMXC3|Project Explorer]]}}. In the node that will "read" the values, change the setting {{Manual Fields|Relative Input Values}} from the default <code>true</code> to <code>false</code>. This tells the Parameter-Master node to expect a value between <code>0</code> and <code>160</code> instead of the usual <code>0</code> to <code>1</code>. To "read," use the output {{Manual Commands|Value}}.

[[Category: Manual DMXControl 3]]

[[de: Workarounds_(General_Information)_DMXC3]]

Troubleshooting (General Information) DMXC3

2025-03-04T20:01:23Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} 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. {{Manual Box | en | Important | If errors occur in the software or a function is missing, it would be appreciated if these cou..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

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.

{{Manual Box | en | Important | 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 '''{{DMXCWebLinks|FS|Project|3|Bugtracker}}'''.}}

{{Manual Box | en | Hint | 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 {{Manual Windowcaption|[[Known Bugs (General Information) DMXC3|Known Bugs]]}}''.}}

= Working "within" DMXControl 3 =
== Devices Stay Dark ==
'''Problem'''
In the {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}, multiple {{Manual Windowcaption|[[Device DMXC3|Devices]]}} or even {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} are selected, and their functions are shown in the {{Manual Windowcaption|[[Device Control DMXC3|Device Control]]}} or the {{Manual Windowcaption|[[Control Panel DMXC3|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 {{Manual Windowcaption|Stage View}}.
* in the {{Manual Windowcaption|[[Channel Overview DMXC3|Channel Overview]]}}, where the DMX channels for dimmers and/or the color of the respective devices remain at 0.
* in reality, even though the {{Manual Windowcaption|[[DMX-Interfaces DMXC3|DMX Interfaces]]}} are activated and otherwise working properly.
The only time the devices respond is when manually controlled via the {{Manual Windowcaption|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 {{Manual Windowcaption|[[Blackout DMXC3|Blackout]]}} function
* The {{Manual Windowcaption|[[Freeze DMXC3|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 {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Master]]}}.
* The {{Manual Windowcaption|[[Grand Master (Master) DMXC3|Grand Master]]}}.
* Active {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} with a higher priority than the {{Manual Windowcaption|[[Programmer DMXC3|Programmer]]}}.
* The {{Manual Windowcaption|[[Programmer DMXC3|Blind]]}} function in the {{Manual Windowcaption|Programmer}}, which ensures that the values set in the programmer are not output to the {{Manual Windowcaption|DMX Interfaces}} or the {{Manual Windowcaption|Stage View}}.
* Various modules, including the {{Manual Windowcaption|DMX Interfaces}}, are disabled via the {{Manual Windowcaption|[[Main Switch DMXC3|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:
# Stop all {{Manual Windowcaption|Cuelists}} using the {{Manual Buttons|Stop all cuelists}} button.
# Reactivate the {{Manual Windowcaption|DMX Interfaces}} using the {{Manual Windowcaption|Main Switch}}.
# Clear the {{Manual Windowcaption|Programmer}} using the {{Manual Buttons|Clear}} button.
# Open the {{Manual Windowcaption|Programmer}} and disable the {{Manual Buttons|Blind}} option. The default setting is {{Manual Buttons|All}}.
# Check if the {{Manual Windowcaption|Blackout}} is disabled.
# In the window showing all {{Manual Windowcaption|[[Master DMXC3|Master]]}}, set both the {{Manual Windowcaption|Grand Master}} and the {{Manual Windowcaption|Group Master}} for the affected devices back to 100%. Be sure to observe the dependencies between group masters, as described in the relevant article.
# 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 {{Manual Buttons|Lumos}} button in the {{Manual Windowcaption|[[Control Panel DMXC3|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 {{Manual Windowcaption|Group Master}} slider is set to a very low brightness value.

== Cuelist Won't Start ==
'''Problem'''
A properly programmed {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}} doesn't start, despite multiple presses of the {{Manual Buttons|Go}} button or pressing a linked button in the {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}.

'''Cause'''
For each {{Manual Windowcaption|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 {{Manual Windowcaption|Cuelist(s)}} from the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}} and set the fade factor (Fade factor / Timing) slider back to a value greater than 0. If the {{Manual Windowcaption|Cuelists}} are triggered via a {{Manual Windowcaption|Softdesk}}, a MIDI controller, or similar devices, you can also add a slider in the {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}} to centrally control the fade factor.

== Last Softdesk Changes Disappear ==
'''Problem'''
The custom design of a {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}} is not saved, or the last changes disappear when the project is reloaded.

'''Cause'''
The command to save the last changes to the {{Manual Windowcaption|Softdesk}} is only transmitted when the {{Manual Windowcaption|[[Softdesk Designer DMXC3|Softdesk Designer]]}} is closed.

'''Solution'''
To ensure all changes to the {{Manual Windowcaption|Softdesk}} are properly saved, always close the {{Manual Windowcaption|Softdesk Designer}} before saving the project. For "pure" live operation with the {{Manual Windowcaption|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.
{{Picture_with_subtitle|DMXC3 Manual Panel Concept Loadig window layout.png|1|Layout prompt when opening a project|center}}

'''Solution'''
To bring lost windows back into the main screen display area, go to the following menu entry: {{Manual MenuText|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 {{Manual_MenuText|Settings|Layout|Load...}}. In the following example, two saved window layouts named Club-Setup and Programming-Setup are stored in the loaded project.
{{Picture_with_subtitle|DMXC3 Manual Panel-Konzept Window layouts.png|2|Reset window layout and load custom window layouts|center}}

If this function doesn't yield the desired result, you can reset the current window layout through the entry {{Manual MenuText|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 {{Manual Windowcaption|[[GUI DMXC3|User Interface]]}}.

= DMX Output =
== Art-Net Output Not Working ==
'''Problem'''
The Art-Net output cannot be activated. The corresponding rows in the {{Manual Windowcaption|[[DMX-Interfaces DMXC3|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'''

[[Category: Manual DMXControl 3]]

[[de: Troubleshooting_(General_Information)_DMXC3]]

Key assignments and working aids DMXC3

2025-03-04T19:55:04Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.0.0}} Here are explanations of the assigned keys in DMXControl 3 and useful working aids. = Key Assignments = == Stage View == *'''{{Manual_Keyboard|Strg}} / {{Manual_Keyboard|Ctrl}}''': Select multiple devices. The order of selection is important. *'''{{Manual_Keyboard|F}} (Fanning)''': By pressing and dragging the mouse, the devices are aligned linearly to each other. *'''{{Manual_Keyboard|C}} (Circle -> Circ..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.0.0}}

Here are explanations of the assigned keys in DMXControl 3 and useful working aids.

= Key Assignments =
== Stage View ==
*'''{{Manual_Keyboard|Strg}} / {{Manual_Keyboard|Ctrl}}''': Select multiple devices. The order of selection is important.
*'''{{Manual_Keyboard|F}} (Fanning)''': By pressing and dragging the mouse, the devices are aligned linearly to each other.
*'''{{Manual_Keyboard|C}} (Circle -> Circle)''': By pressing and dragging the mouse, the devices are arranged in a circular pattern.
*'''{{Manual_Keyboard|M}} (Matrix)''': By pressing and dragging the mouse, a matrix is created from the selected devices.

== Cuelist ==
Individual cues can be copied with "'''{{Manual_Keyboard|Strg|C}}'''" and pasted into other positions (even in other cuelists) with "'''{{Manual_Keyboard|Strg|V}}'''" . The paste action always occurs '''above''' the selected cue. Note for version 3.0.1: The paste function only works if the cuelist already contains at least one cue! 

== Kernel ==
*'''{{Manual_Keyboard|Strg|C}}''': Shutdown Kernel

= Working Aids =
== Cuelist ==
In the tables of a cuelist, familiar actions from Excel can also be used. For the "Trigger Value" or "Fade" columns, it is possible to "copy down" a value. To do this, select the first cell to copy, then drag with the mouse down to the desired end position. By using the shortcut "Strg+U," the first value will be copied to all the other selected cells.

Cell selection can also be done via the keyboard. Click on the cell to copy, then hold down the Shift key and press the "down arrow" key.

The default settings for new cuelists can be configured in a project by right-clicking on "Cuelists" in the Project Explorer and selecting "Properties" at the bottom. This opens the "SceneList Project Default Configuration" window.

[[Category:Tips]]
[[Category:DMXControl 3]]

[[de: Tastenbelegung_und_Arbeitshilfen_DMXC3]]

Stream Deck DMXC3

2025-03-04T19:47:17Z

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} {{Picture_with_subtitle|Streamdeck.jpg||Stream Deck|right|320px}} Who doesn’t know this? You’re running lights at an event and notice that the stage is nicely lit, but the labeling on your MIDI controller or the DMX console you’re using is impossible to read in the dark. A solution for this are so-called macro boards like the Stream Deck from Elgato<ref>Official manufacturer website: https://www.elga..."

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

{{Picture_with_subtitle|Streamdeck.jpg||Stream Deck|right|320px}}
Who doesn’t know this? You’re running lights at an event and notice that the stage is nicely lit, but the labeling on your MIDI controller or the DMX console you’re using is impossible to read in the dark. A solution for this are so-called macro boards like the Stream Deck from Elgato<ref>Official manufacturer website: https://www.elgato.com/de/de</ref>. The following article describes the basic functions and their usage.

= General =
The Elgato Stream Deck is now available in various sizes and versions. While initially the versions only differed in the number of buttons, there are now versions with rotary encoders (knobs) and a touchbar. All devices share the feature that the buttons are equipped with a color display, so you can display custom text or symbols and change them dynamically. Technically, DMXControl 3 supports the following devices:

{| class="wikitable" style="text-align:center;"
|- class="hintergrundfarbe10"
! rowspan="2" style="width: 125px;" | Type !! rowspan="2" style="width: 75px;" | Revision !! rowspan="2" style="width: 125px;" | Buttons !! rowspan="2" style="width: 125px;" | Resolution !! colspan="2" | Support !! rowspan="2" | Notes
|- class="hintergrundfarbe10"
! style="width: 75px;" | Status !! style="width: 75px;" | DMXC- Version
|-
! rowspan="2" | StreamDeck Mini
| || rowspan="2" style="text-align:left;" | 2 x 3 Buttons || rowspan="2" | 72 x 72 Pixels || {{Yes}} || '''3.2.0''' ||
|-
| Rev. 2 || {{Yes}} || '''3.3.0''' || style="text-align:left;" |
|-
! rowspan="3" | StreamDeck (Standard)
| || rowspan="3" style="text-align:left;" | 3 x 5 Buttons || rowspan="3" | 72 x 72 Pixels || {{Yes}} || '''3.2.0'''
|-
| Rev. 2 || {{Yes}} || '''3.2.2''' ||
|-
| MK.2 || {{Yes}} || '''3.3.0''' ||
|-
! rowspan="2" | StreamDeck XL
| || rowspan="2" style="text-align:left;" | 4 x 8 Buttons || rowspan="2" | 96 x 96 Pixels || {{Yes}} || '''3.2.2'''
|-
| Rev. 2 || {{Yes}} || '''3.3.0''' || style="text-align:left;" |
|-
! Stream Deck +
| || style="text-align:left;" | 8 Buttons, 1 Touchbar, 4 Encoders || rowspan="2" | variable || rowspan="2" | {{No}} || rowspan="2" | || rowspan="2" style="text-align:left;" | More extensive changes and additions required for support
|-
! Stream Deck Neo
| || style="text-align:left;" | 8 Buttons, 1 Infobar, 2 Touchpoints
|}
{{Manual Box | en | Hint | New hardware revisions are generally always accompanied by an update to DMXControl 3.}}

The Stream Deck is connected to the PC via USB. It doesn’t matter whether the device is connected to the PC for the {{Manual Windowcaption|[[GUI DMXC3|Graphical User Interface (GUI)]]}} or for the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}}. This allows the Stream Deck to be used at a different location than the Front-of-House (FoH). The XL version requires a USB 3.0 connection due to the larger displays on the buttons. The smaller versions can also be connected via a USB 2.0 port.

DMXControl 3 can also work with multiple Stream Decks simultaneously. The unique assignment is done via the Stream Deck’s serial number. Once the device is connected and the project is saved, the Stream Deck remains visible in both the input tree (Input-Baum) and output tree (Output-Baum) in the {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignments]]}}. Alternatively, instead of a fixed assignment, you can work with so-called {{Manual Windowcaption|[[Macroboard DMXC3|Macroboard Profiles]]}}. This allows for more flexible assignment and enables the preparation of multiple pages that can be switched live.
{{Manual Box | en | Important | To ensure a clean display and visualization on the buttons, the software for the Stream Deck must be closed while working with DMXControl 3.}}

Info: This article shows an example of using a Stream Deck XL. The number of buttons in the following screenshots depends on the device version.

= Functionality =
== Inputs and Outputs ==
Once the Stream Deck is connected to the PC and DMXControl 3 is started, the device will appear in the input and output tree under Input Assignment:

{{Picture_with_subtitle|Stream Deck input outputs.jpg|1|Stream Deck Input Assignment|center|320px}}

On the input side, the 4x8 buttons and a {{Manual Commands|Connected}} input are displayed. The node {{Manual Commands|Button 1.1}} is set to "high" when the button is pressed. Once released, it returns to "low". The {{Manual Commands|Connected}} input always outputs "high" when the Stream Deck with the corresponding serial number is connected to DMXControl 3. Otherwise, it outputs "low".

Through the output {{Manual Commands|Brightness}}, it is possible to adjust the brightness of the Stream Deck. The range is from 0 to 100. Using the outputs {{Manual Commands|Button (Bitmap) X.Y}}, a graphic can be passed to the corresponding display, which will then show it.

== Display ==
To display something on a screen, a button output is added to a connection set along with a {{Manual Objectcaption|[[Draw Bitmap (Input Assignment) DMXC3|Draw Bitmap Node]]}}. The output {{Manual Commands|Bitmap}} of the node is connected to the input {{Manual Commands|O}} of the Stream Deck output. By default, text is displayed on the screen.

{{Picture_with_subtitle |Stream Deck Draw Bitmap.jpg|2|Stream Deck Draw Bitmap|center|600px}}

In the settings of the node, you can adjust the font, font color, and more. {{Manual Reference |arrow| For more information, see the article about the {{Manual Windowcaption|[[Draw Bitmap (Input Assignment) DMXC3|Draw Bitmap Node]]}}}}. These settings don't need to be static. Some properties can also be changed dynamically by other nodes. This is explained in more detail in the following examples.

= Examples =
With DMXControl 3 and {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}, it is possible to use a Stream Deck as another input and output device. Below are some examples of how you can assign the buttons and receive corresponding feedback.

== Start and stop cue list ==
The first example is likely to be needed frequently. Here, a {{Manual Windowcaption|[[Cuelist DMXC3|Cue List (Cuelist)]]}} is started by pressing the button, and stopped by pressing it again. Additionally, the display should show the name of the cue list and whether it is running, paused, or stopped.

{{Manual Box | en | Hint | This example only works as long as the cue list contains only one cue. If a chaser effect or something else is used, the example for "Cuelist Toggle Chaser" should be used.}}

{{Picture_with_subtitle |Stream Deck Cuelist Toggle IA.jpg|3|Cuelist Toggle Input Assignment|center|800px}}

Additionally, in the cue list "Full On," the option "Release at end mode" must be set to {{Manual Fields|With Go (With go)}}.

Explanation of how it works:

{{Manual Commands|Button 1.1}} is connected with {{Manual Commands|Go}} of the cue list "Full On." The {{Manual Commands|Name}} of the cue list is connected with the {{Manual Commands|Text}} input of the {{Manual Objectcaption|[[Draw Bitmap (Input Assignment) DMXC3|Draw Bitmap Node]]}}. If the name of the cue list is changed, the name on the display will also update. The {{Manual Commands|Status}} of the cue list goes to the input of the {{Manual Objectcaption|[[Input Selector (Input Assignment) DMXC3|Input Selector]]}}. Depending on the status of the cue list, a color is output at the exit.

{| class="wikitable centered" style="text-align:center; vertical-align:middle;"
|-
!style="width: 100px;" | Status
!style="width: 50px;" | Status Value
!style="width: 100px;" | Color
!style="width: 100px;" | RGB Value
|-
| Stopped || 0 || black || <code>0;0;0</code>
|-
| Paused || 1 || yellow || <code>130;130;0</code>
|-
| Running || 2 || green || <code>0;130;0</code>
|}

Each time the value changes at the input {{Manual Commands|O}} from the Bitmap output of the Stream Deck, the corresponding display will be updated. If the device is disconnected from the PC in between, it will only display something on the screen after the next cue list switch. In figure 3, you can see that the {{Manual Commands|Connected}} input is linked to the update of {{Manual Commands|Button (Bitmap) 1.1}}. This way, the display is updated each time it reconnects, showing the correct information.

The result on the Stream Deck display will look as follows:

== Start cue list only briefly ==
In the following example, a cue list should be active only as long as the button is pressed.

{{Picture_with_subtitle |Stream Deck Cuelist Flash IA.jpg|4|Cuelist Flash Input Assignment|center|800px}}

In contrast to the first example, a logic block with the function {{Manual Fields|Not}} must be placed behind the "Button 1.1." The output is connected to the {{Manual Commands|Stop}} of the {{Manual Objectcaption|[[Cuelist (Input Assignment) DMXC3|Cue List Node (Cuelist Node)]]}}.

== Devices or Device Groups ==
It is also possible to select devices or device groups with the buttons, for example {{Manual Windowcaption|[[Device DMXC3|Devices]]}} or {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}}. The corresponding connection set has the following structure:

{{Picture_with_subtitle |Stream Deck Device IA.jpg|5|Select device Input Assignment|center|800px}}

On the Stream Deck, not only the images of the respective devices appear, but also the background color visually indicates which device or device group is currently selected. It is also possible to display the device’s image. It is important that an image has been selected in the properties of the corresponding device group. The image should be saved as a <code>.png</code> file with a transparent background.

== Speed Master ==
In the following example, a button should trigger the tempo for a {{Manual Objectcaption|[[Speed Master (Master) DMXC3|Speed Master]]}} and display the current speed accordingly:

{{Picture_with_subtitle |Stream Deck Speedmaster IA.jpg|6|Speedmaster Input Assignment|center|800px}}

The button is connected to the {{Manual Commands|Learn}} input of the {{Manual Objectcaption|[[Speed Master (Input Assignment) DMXC3|Speed Master]]}} node. Then, the output {{Manual Commands|BPM}} of the Speed Master node is connected to the input {{Manual Commands|0}} of the {{Manual Objectcaption|[[Format (Input Assignment) DMXC3|Format Node]]}}. In the settings, the format field should contain {{Manual Fields|Speed: {0:0} BPM}}. The output of the Format Node is connected to the {{Manual Commands|Text}} input of the {{Manual Objectcaption|[[Draw Bitmap (Input Assignment) DMXC3|Draw Bitmap Node]]}}. The current speed of Speedmaster 1 will now be displayed on the screen.

To enhance the visual effect, the button should also blink in the current speed. To do this, a converter node {{Manual Objectcaption|[[Beat to Bool (Input Assignment) DMXC3|Beat to Bool]]}} is connected to the {{Manual Commands|Select}} input of the {{Manual Objectcaption|[[Input Selector (Input Assignment) DMXC3|Input Selector]]}}. In this, for input {{Manual Commands|0}}, the RGB value <code>0;0;0</code> is set, and for input {{Manual Commands|1}}, the RGB value <code>130;0;0</code> is set. The output is connected to the {{Manual Commands|Background Color}} of the {{Manual Objectcaption|Draw Bitmap Node}}.

At a speed of 300 BPM, the chaser stays red almost continuously. If such speeds are needed, the value in the {{Manual Objectcaption|Beat to Bool}} node under {{Manual Fields|On Time}} must be reduced.

{{Picture_with_subtitle |Stream Deck Speedmaster Draw Bitmap.jpg|7|Speedmaster Draw Bitmap Settings|center|350px}}



= Links and References =
== Links ==
<references/>

<noinclude>
[[Category: Manual DMXControl 3]]
</noinclude>

[[de: Stream_Deck_DMXC3]]

Change over from DMXControl 2 to DMXControl 3

2025-03-04T19:36:47Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0
| Content = x
}}

Switching from one software to another or upgrading to a newer version often presents several challenges. In the case of transitioning from DMXControl 2 to DMXControl 3, these challenges can be summarized as follows:
* DMXControl 3 operates differently in several areas compared to DMXControl 2, meaning you will need to start learning how to use it from scratch.
* You have a functioning system with DMXControl 2 that you are familiar with, but now you are faced with a new and seemingly complex system (simply because you are not yet accustomed to it).

This article aims to outline the main differences between DMXControl 2 and DMXControl 3 and to summarize and answer the frequently asked questions in the forum about transitioning from DMXControl 2 to DMXControl 3. By the end, you will hopefully feel more comfortable navigating DMXControl 3.

To address any concerns upfront: although DMXControl 3 may initially seem like a complete reinvention, there is no need to worry. Once you take a second look—perhaps after your first few attempts—you will realize that DMXControl 2 and DMXControl 3 share many similarities. Some features are just accessed differently or found in new locations.

{{Manual Box | en | Important | This article reflects the current implementation status of '''DMXControl 3.3.0'''. Technical changes due to ongoing development are possible at any time.}}

= Compatibility =
Projects from DMXControl 2 are not compatible with DMXControl 3. This also includes DDFs, which must be completely recreated due to the changed requirements. {{Manual Reference |arrow| More information on creating DDFs, including examples, can be found in the documentation section for {{Manual Windowcaption|[[DDF DMXC3|DDFs for DMXControl 3]]}}.}}

Extensive compatibility is not necessary because many improvements allow effects to be recreated in just a few minutes. In some areas, entirely new workflows have been introduced, based on and even surpassing the concepts of professional software. However, some tools from DMXControl 2, such as the audio player and the text book, have not yet been integrated into DMXControl 3. Furthermore, plugins (both output and regular plugins) are not compatible due to the modified interfaces.

= Migration Guide =
== General Recommendations ==
Every DMXControl 2 user should consider their own migration strategy based on the tables in the section [[Switching from DMXControl 2 to DMXControl 3#Version Comparison|Version Comparison]]:
* You can run DMXControl 2 and DMXControl 3 in parallel on the same PC, allowing you to gradually familiarize yourself with DMXControl 3.
* Gradually build a working setup in DMXControl 3. With parallel operation, you always have a fallback project that works as expected. However, don't overdo it at first—start slowly.
* If you are using a large number of devices, you will quickly benefit from features like {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} and the associated {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}} in DMXControl 3.
* Even if you still rely on DMXControl 2 for tools like the audio player, which is not yet available in DMXControl 3, start familiarizing yourself with DMXControl 3. This will help you understand the basic workflow and allow you to create small test shows. When the timecode player becomes available, you will only need to learn that specific tool.

{{Manual Box | en | Attention | As indicated in the system requirements, Windows 8.1 is the last officially supported operating system for DMXControl 2. While DMXControl 2 may still work on Windows 10 and Windows 11, this is at your own risk. Future updates to these operating systems may render DMXControl 2 unusable. Since DMXControl 2 is no longer being developed, no further updates will be provided if problems arise.}}

== Comparison of Key Features ==
A major difference to get used to: DMXControl 3 does not work with channels but rather with device functions and property values. This makes it crucial for DDFs (at least for required functions) to be accurately implemented. In DMXControl 2, you could manually adjust values via the channel overview. In DMXControl 3, this is no longer possible because the channel overview does not save values. However, the big advantage is that you can select and adjust multiple devices of any type simultaneously.

Another key difference: {{Manual Windowcaption|[[Effektsequencer DMXC2|Effects]]}} in DMXControl 2 are now called {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} in DMXControl 3. These combine the cuelists and effects you know from DMXControl 2. You use cuelists to store all your lighting effects, such as chases and movements. The workflow is quite similar to DMXControl 2. You configure your fixtures in the {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}, click {{Manual MenuText|Add Cue}}, select the device functions to save (similar to channel selection in DMXControl 2), and confirm with {{Manual Buttons|OK}} to insert a {{Manual Windowcaption|Cue}} into the {{Manual Windowcaption|Cuelist}}.

Additionally, DMXControl 3 includes {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}—mathematical functions like sine and sawtooth waves. These can be applied to almost any device property and adjusted live. Try dragging a {{Manual Objectcaption|1D Effect}} onto the dimmer of a {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}} to see how it responds.

== Initial Approach ==
For your first steps in DMXControl 3, start by adding some devices to your project. They don’t need to match your actual equipment. Ensure that device groups are automatically created during this process. Next, try creating some lighting moods by adjusting settings via the {{Manual Windowcaption|[[Control Panel DMXC3|Control Panel]]}} and {{Manual Windowcaption|[[Device Control DMXC3|Device Control]]}}. To reset, use the {{Manual Buttons|Clear}} button in the quick access bar.

After creating a few lighting moods, try saving them. In the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}}, create a new {{Manual Windowcaption|Cuelist}} and open it with a double-click. If a lighting mood exists in the {{Manual Windowcaption|Stage View}}, click {{Manual MenuText|Add Cue}} to save it. Clear the stage view and test playback using the {{Manual MenuText|Go}} button in the {{Manual Windowcaption|Cuelist editor}}.

{{Manual Box | en | Reference | ''A more detailed quick-start guide for DMXControl 3 is available in the '''[[Quickstart Guide DMXC3|Quickstart Guide]]'''.''}}

== Version Comparison ==
After describing the workflow in DMXControl 3, the following section provides a detailed comparison of DMXControl 2 and DMXControl 3.

== Environment ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Supported DMX Interfaces'''
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| Some DMX interfaces, such as output via Art-Net, offer additional features in DMXControl 3.
|-
| '''DDFs (Device Library)'''
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. Display of control elements in the DDF is configurable for each individual DDF. {{No|-}} DDFs must be downloaded manually.
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. DDFs are significantly simplified. They now only contain the pure device definition. The uniform display of the control elements is handled by DMXControl 3 itself, where all functions are displayed in real values. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF DMXC3|DDF Documentation for DMXC3]]}}.}} {{Yes|-}} DDFs from the DDFLibrary can be downloaded directly into DMXControl 3 and used in the project. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF Library DMXC3|DDF Library]]}}.}}
| In the {{DMXCWebLinks|DDFLib}}, fully functional DDFs can be provided for both DMXControl versions, each with different DMX modes. {{Manual Reference | warning |DDFs from DMXControl 2 cannot be used in DMXControl 3.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | System Requirements and Information}}

| '''Operating System'''
| '''Up to''' and including '''Windows 8.1'''.
| All Windows versions '''from Windows 7''' onwards.
| For detailed system requirements for DMXControl 3, see {{DMXCWebLinks|DMXC-HP|dmxcontrol-3/systemrequirements.html| Overview on DMXControl Homepage}}.
|-
| '''Program Language'''
| {{Yes|-}} German {{Yes|-}} English
| {{Yes|-}} German {{Yes|-}} English {{Yes|-}} French {{Yes|-}} Japanese
|
|-
| '''Documentation'''
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Handbuch_DMXControl_2 German Manual] {{Yes|-}} '''[[Manual_DMXControl_2|English manual in draft form]]''' {{Yes|-}} '''[[DDF DMXC2|DDF Documentation]]''' {{Yes|-}} Plugin interface
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Tutorials_DMXControl_3 German Tutorial] {{Yes|-}} '''[[Tutorials DMXControl 3|English tutorial]]''' {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Inhalts%C3%BCbersicht_Hauptprogramm_DMXC3 German Manual] {{Yes|-}} '''[[Manual_DMXControl_3|English Manual]]''' {{Yes|-}} '''{{DMXCWebLinks|YouTube|DMXC3 Playlists}}''' {{Yes|-}} '''[[DDF DMXC3|DDF Documentation]]''' including extensive examples and tutorials {{No|-}} Plugin interface
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Work Environment}}

| '''Hardware Environment'''
| {{Yes|-}} Single PC. {{No|-}} No distributed system.
| {{Yes|-}} Single PC. {{Yes|-}} Distributed system possible, where the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[Umbra DMXC3|Umbra]]}} can run separately from the {{Manual Windowcaption|[[GUI DMXC3|GUI]]}}.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Multi-User'''
| {{No|-}} Single user only.
| {{Yes|-}} Multiple GUIs in a multi-user environment. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Server-Client Concept DMXC3|Server-Client Concept]]}}.}}
| For effective work, do not use a WLAN connection between the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[GUI DMXC3|GUI]]}}.
|-
| '''Performance'''
| {{No|-}} Requires a CPU with a high clock rate on one core for using 2 DMX universes.
| {{Yes|-}} Due to efficient programming, even mid-range PCs can output multiple DMX universes. The separation of {{Manual Windowcaption|[[GUI DMXC3|GUI]]}} and {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} provides additional safety in case of an interface failure.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Project Management'''
| {{No|-}} Only manual, as required project data is stored "open" in a directory and DDFs are stored independently of the project in the installation directory. {{No|-}} Switching PCs requires manually sorting various files, including DDFs, DMX-In configuration, MIDI configuration. {{No|-}} Only simple automatic project backup without version history.
| {{Yes|-}} All data required for the project, including DDFs, is stored in a project file. {{Yes|-}} Only the project file is needed for switching PCs. {{Yes|-}} Automatic saving including storing a certain number of previous project versions.
| Project management in DMXControl 3 handles the complete organization of projects including the associated versions. Searching for storage locations is unnecessary. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Project Administration DMXC3|Project Management (Project Administration)]]}}.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | External Interfaces and Control}}

|-
| '''DMX Output'''
| {{Yes}}, maximum 2 DMX universes.
| {{Yes}}, up to 16 DMX universes, depending on PC/laptop performance.
|
|-
| '''DMX-In'''
| {{Yes}}, but a maximum of 1 DMX universe.
| {{Yes}}, 2 DMX universes.
|
|-
| '''Keyboard Control'''
| {{Yes}}, but only simple key assignments are possible.
| {{Yes}}, including support for multiple banks and key combinations.
|
|-
| '''MIDI Interface'''
| {{Yes}}, available.
| {{Yes}}, available, including native support for multiple MIDI controllers without additional tools.
|
|-
| '''Joystick Control'''
| {{Yes}}
| {{No}}, but an alternative control option is available via the 3Dconnexion plugin.
|
|-
| '''Macroboards'''
| {{No}}
| {{Yes}}, available, including support for multiple macroboards like Elgato Stream Deck. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stream Deck DMXC3|Stream Deck]]}}.}}
|
|-
| '''Timecode''' (Protocol)
| {{Yes}}
| {{No}}, but coming soon.
|
|-
| '''OSC Interface'''
| {{Yes}}, available via plugin.
| {{No}}
|
|-
| '''Terminal Interface'''
| {{Yes}}
| {{No}}, no replacement planned at this time.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Feature Extensions}}

| '''Plugins'''
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}}.
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}} or user plugins in the {{DMXCWebLinks|Forum|Board|161|Plugins and Addons}} section.
|
|-
| '''Plugin Interface'''
| {{Yes}}
| {{Yes}}
| The interface in DMXControl 3 is not compatible with DMXControl 2.
|}

== Functionality ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment

{{DMXC3 Manual-Tablesection | S1 | 4 | Prepare Project}}

| '''Personal Device Favorites'''
| {{No|-}} Selecting frequently used devices is not possible.
| {{Yes|-}} In the dialog {{Manual Windowcaption|[[Device Manager DMXC3|Add Device]]}}, you can select devices from the available list that are used frequently.
|
|-
| '''Groups (of Devices)'''
| {{Yes|-}} Supported in a simple form for quick selection of devices in the stage view.
| {{Yes|-}} {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} are a core concept of DMXControl 3 and are intelligently designed.
| Users with many devices performing the same lighting scenes have better tools with DMXControl 3.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Hardware Abstraction (HAL)'''
| {{No|-}} Limited abstraction of DMX values via DDFs.
| {{Yes|-}} {{Manual Windowcaption|[[Hardware Abstraction Layer (HAL) DMXC3|HAL]]}} is a core concept of DMXControl 3, providing complete abstraction of all device functions. Working directly with DMX values is no longer necessary.
| Users with similar (but not identical) devices can still program them uniformly in DMXControl 3.
|-
| '''Channel Overview'''
| {{Yes|-}} Available.
| {{Yes|-}} Available independently of DMX and includes highlighting of the selected device. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Channel Overview DMXC3|Channel Overview]]}}.}}
|
|-
| '''Graphical Stage View'''
| {{Yes|-}} Available as a rough orientation aid in the lighting setup.
| {{Yes|-}} Similar to DMXControl 2 but with extended animation possibilities like gobo projection. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}.}}
|
|-
| '''Visualizer'''
| {{Yes|-}} Supported via Magic 3D EasyView.
| {{Yes|-}} Supported via Magic 3D EasyView and other external visualizers accessible via Art-Net.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Saving Cues}}

| '''Cues'''
| {{Yes|-}} Supported.
| {{Yes|-}} Supported in an enhanced form, where there is no distinction by cue type anymore. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Cues are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Fanning'''
| {{No|-}} Only partially possible with a workaround using motion cues.
| {{Yes|-}} Explicit fanning support through special command syntax at various points like device functions, parameters in effects, fade times for cues, etc. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}}}}.
|
|-
| '''Relative Values'''
| {{No|}}
| {{Yes|-}} All numerical values for device functions such as dimmers, position, gobo rotation, etc., can be saved as relative and be calculated with other values during execution. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Absolute and Relative Values DMXC3|Absolute and Relative Values]]}}.}}
| The device function color is not included in the current version due to its complexity.
|-
| '''Motion Cues'''
| {{Yes|-}} Supported.
| {{Yes|-}} Motion cues are implicitly included in the "new" cues and effects and can be applied to all numerical device functions. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}}}.
| Motion cues from DMXControl 2 are not compatible with DMXControl 3.
|-
| '''Effects, Chasers'''
| {{Yes|-}} Supported, partially via tools like the running light generator or motion cue within the {{Manual Windowcaption|[[Chasers_tool_DMXC2|Chasers Tool]]}}.
| {{Yes|-}} Supported through the {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}} function with more effective definition options via various parameters, predefined effect library.
| Effects are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Dynamic Manipulation of Values'''
| {{No|}}
| {{Yes|-}} There are four types of {{Manual Windowcaption|[[Master DMXC3|Masters]]}} available, each of which can dynamically manipulate values of a function in a cue when the corresponding cuelist is executed. {{Manual Reference | arrow |For detailed explanations, see {{Manual Windowcaption|[[Master DMXC3|Master]]}}.}}. It does not matter whether it is a {{Manual Windowcaption|[[Cuelist DMXC3|Cue]]}} or an {{Manual Windowcaption|[[Effects and Filters DMXC3|Effect or Filter]]}}.
| All {{Manual Windowcaption|[[Master DMXC3|Masters]]}} can be addressed and modified live through various means like {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}, {{Manual Windowcaption|[[MIDI DMXC3|MIDI]]}}, and more using {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}.
|-
| '''Presets'''
| {{Yes|-}} Implicitly via the cue library.
| {{Yes|-}} Direct support as a programming element for advanced users. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Preset DMXC3|Preset]]}}}}.
| The preset concept is not compatible with DMXControl 2.
|-
| '''Command Concept'''
| {{Yes|-}} Only for simple dependencies, similar to an automated mouse click. {{No|-}} Logical, mathematical, or status-dependent commands cannot be executed.
| {{Yes|-}} In simple form within cuelists. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}}}. {{Yes|-}} Cross-linking of actions with various logical, mathematical, or status-dependent dependencies across all program functions using the Input Assignment. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}}}.
| Commands in DMXControl 2 are not compatible with DMXControl 3, as the capabilities in DMXControl 3 are much greater.
|-
| '''Command Line'''
| {{Yes}}
| {{No}}
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Execute Show}}

| '''Cuelists'''
| {{Yes|-}} Supported, multiple instances can be executed.
| {{Yes|-}} Supported including the possibility to execute multiple instances simultaneously. Additionally, extended trigger options for the execution in the cuelist are available. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Cuelists are the main control tool in DMXControl 3. The various "implicit" cuelists from different tools in DMXControl 2 are unified.
|-
| '''Value Mixing in Cuelists'''
| {{Yes|-}} HTP and LTP supported, but setting is global for the entire project.
| {{Yes|-}} Extended support with three modes (LTP, HTP, and LoTP). Definition of mixing behavior individually for each cuelist. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3|HTP-, LTP- and LoTP Mixing]]}}.}}
|
|-
| '''Command Box'''
| {{Yes|-}} Supported.
| {{Yes|-}} Developed further as Softdesk and offers completely customizable user interface with numerous control elements. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}}}.
| Softdesk is not compatible with the Command Box.
|-
| '''Master'''
| {{Yes|-}} Supported in simple form: two Grand Masters and one Speed Master for the entire project.
| {{Yes|-}} Available in an advanced form. In addition to the {{Manual Windowcaption|[[Grand Master (Master) DMXC3|Grand Master]]}}, you can create a {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Master]]}} for each {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}}. 
| By creating your own {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Masters]]}}, you can control the brightness of different groups of devices in a much more detailed manner.
|-
| '''Submaster'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available in an advanced form of the {{Manual Windowcaption|[[Executor DMXC3|Executors]]}}, for example, to control {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}. In a future version, the {{Manual Windowcaption|[[Master DMXC3|Masters]]}} will also be available in Executors.
| Direct control of DMX channels is no longer available due to the fundamentally different concept of DMXControl 3.
|-
| '''Audio Player'''
| {{Yes|-}} Supported.
| {{Yes|-}} Simple sound effects can be played within a {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}. For longer songs, the {{Manual Windowcaption|[[Timecode Player DMXC3|Timecode Player]]}} can be used.
| The Timecode Player in DMXC3 also allows playing excerpts of songs and fading them in and out.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Timecode Player'''
| {{Yes|-}} Supported, but only in simple form.
| {{Yes|-}} Offers the possibility to create complex music-synchronized light shows from multiple excerpts of songs with detailed and flexible display of audio frequencies. The light shows are built via the recording function of Executors or multiple parallel-played {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}.
|-
| '''Textbook'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available as a user plugin. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Textbook Plugin DMXC3|Textbook]]}}.}}
|
|
|-
| '''Manual Beat Control'''
| {{Yes|-}} Via BeatTool.
| {{Yes|-}} In an advanced form through the {{Manual Windowcaption|[[Speed Master (Master) DMXC3|Speed Master]]}}, which can be created in any number and specifically assigned to certain {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} or stored in {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}.
|
|-
| '''Automatic Beat Detection'''
| {{Yes|-}} Supported via Winamp plugin and external interfaces.
| {{Yes|-}} Supported via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}} and external interfaces.
|
|-
| '''Sound to Light'''
| {{Yes|-}} Via various plugins.
| {{Yes|-}} Via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}}.
|
|-
| '''Video Control'''
| {{Yes|-}} Via various plugins (Winamp, Beamertool) and Media Center.
| {{No|-}} Possibly via various plugins.
|
|-
| '''Scheduler (Task Scheduler)'''
| {{Yes|-}} Supported.
| {{No|-}} Not available as a separate module, but an alternative is available through cuelists with the trigger "Real Time Clock (RTC)".
|
|}

== Application Plugins ==
Some plugins are no longer required in DMXControl 3, as their functionality is already integrated. Others will not be available until updated by their authors. Plugins cannot be used without modification due to changes in the plugin interface and programming language.

{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Beamertool'''
| {{Yes}}, available.
| {{No}}
| The Beamertool for the Raspberry Pi can be used via Art-Net in both versions.
|-
| '''Matrix Control MadMaxOne'''
| {{Yes|-}} Available.
| {{No|-}} Will not be migrated.
| A new concept for matrix devices with corresponding effects is integrated into DMXControl 3. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Matrix DMXC3|Matrix]]}} and {{Manual Windowcaption|[[Radix DMXC3|Radial Matrix (Radix)]]}}.}}
|-
| '''PDA Control'''
| {{Yes}}, available.
| {{No}}
|
|}

[[Category: Tipps]]

[[de: Umstieg_von_DMXControl_2_zu_DMXControl_3]]

Change over from DMXControl 2 to DMXControl 3

2025-03-04T19:32:19Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0
| Content = x
}}

Switching from one software to another or upgrading to a newer version often presents several challenges. In the case of transitioning from DMXControl 2 to DMXControl 3, these challenges can be summarized as follows:
* DMXControl 3 operates differently in several areas compared to DMXControl 2, meaning you will need to start learning how to use it from scratch.
* You have a functioning system with DMXControl 2 that you are familiar with, but now you are faced with a new and seemingly complex system (simply because you are not yet accustomed to it).

This article aims to outline the main differences between DMXControl 2 and DMXControl 3 and to summarize and answer the frequently asked questions in the forum about transitioning from DMXControl 2 to DMXControl 3. By the end, you will hopefully feel more comfortable navigating DMXControl 3.

To address any concerns upfront: although DMXControl 3 may initially seem like a complete reinvention, there is no need to worry. Once you take a second look—perhaps after your first few attempts—you will realize that DMXControl 2 and DMXControl 3 share many similarities. Some features are just accessed differently or found in new locations.

{{Manual Box | en | Important | This article reflects the current implementation status of '''DMXControl 3.3.0'''. Technical changes due to ongoing development are possible at any time.}}

= Compatibility =
Projects from DMXControl 2 are not compatible with DMXControl 3. This also includes DDFs, which must be completely recreated due to the changed requirements. {{Manual Reference |arrow| More information on creating DDFs, including examples, can be found in the documentation section for {{Manual Windowcaption|[[DDF DMXC3|DDFs for DMXControl 3]]}}.}}

Extensive compatibility is not necessary because many improvements allow effects to be recreated in just a few minutes. In some areas, entirely new workflows have been introduced, based on and even surpassing the concepts of professional software. However, some tools from DMXControl 2, such as the audio player and the text book, have not yet been integrated into DMXControl 3. Furthermore, plugins (both output and regular plugins) are not compatible due to the modified interfaces.

= Migration Guide =
== General Recommendations ==
Every DMXControl 2 user should consider their own migration strategy based on the tables in the section [[Switching from DMXControl 2 to DMXControl 3#Version Comparison|Version Comparison]]:
* You can run DMXControl 2 and DMXControl 3 in parallel on the same PC, allowing you to gradually familiarize yourself with DMXControl 3.
* Gradually build a working setup in DMXControl 3. With parallel operation, you always have a fallback project that works as expected. However, don't overdo it at first—start slowly.
* If you are using a large number of devices, you will quickly benefit from features like {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} and the associated {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}} in DMXControl 3.
* Even if you still rely on DMXControl 2 for tools like the audio player, which is not yet available in DMXControl 3, start familiarizing yourself with DMXControl 3. This will help you understand the basic workflow and allow you to create small test shows. When the timecode player becomes available, you will only need to learn that specific tool.

{{Manual Box | en | Attention | As indicated in the system requirements, Windows 8.1 is the last officially supported operating system for DMXControl 2. While DMXControl 2 may still work on Windows 10 and Windows 11, this is at your own risk. Future updates to these operating systems may render DMXControl 2 unusable. Since DMXControl 2 is no longer being developed, no further updates will be provided if problems arise.}}

== Comparison of Key Features ==
A major difference to get used to: DMXControl 3 does not work with channels but rather with device functions and property values. This makes it crucial for DDFs (at least for required functions) to be accurately implemented. In DMXControl 2, you could manually adjust values via the channel overview. In DMXControl 3, this is no longer possible because the channel overview does not save values. However, the big advantage is that you can select and adjust multiple devices of any type simultaneously.

Another key difference: {{Manual Windowcaption|[[Effektsequencer DMXC2|Effects]]}} in DMXControl 2 are now called {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} in DMXControl 3. These combine the cuelists and effects you know from DMXControl 2. You use cuelists to store all your lighting effects, such as chases and movements. The workflow is quite similar to DMXControl 2. You configure your fixtures in the {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}, click {{Manual MenuText|Add Cue}}, select the device functions to save (similar to channel selection in DMXControl 2), and confirm with {{Manual Buttons|OK}} to insert a {{Manual Windowcaption|Cue}} into the {{Manual Windowcaption|Cuelist}}.

Additionally, DMXControl 3 includes {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}—mathematical functions like sine and sawtooth waves. These can be applied to almost any device property and adjusted live. Try dragging a {{Manual Objectcaption|1D Effect}} onto the dimmer of a {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}} to see how it responds.

== Initial Approach ==
For your first steps in DMXControl 3, start by adding some devices to your project. They don’t need to match your actual equipment. Ensure that device groups are automatically created during this process. Next, try creating some lighting moods by adjusting settings via the {{Manual Windowcaption|[[Control Panel DMXC3|Control Panel]]}} and {{Manual Windowcaption|[[Device Control DMXC3|Device Control]]}}. To reset, use the {{Manual Buttons|Clear}} button in the quick access bar.

After creating a few lighting moods, try saving them. In the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}}, create a new {{Manual Windowcaption|Cuelist}} and open it with a double-click. If a lighting mood exists in the {{Manual Windowcaption|Stage View}}, click {{Manual MenuText|Add Cue}} to save it. Clear the stage view and test playback using the {{Manual MenuText|Go}} button in the {{Manual Windowcaption|Cuelist editor}}.

{{Manual Box | en | Reference | ''A more detailed quick-start guide for DMXControl 3 is available in the '''[[Quickstart Guide DMXC3|Quickstart Guide]]'''.''}}

== Version Comparison ==
After describing the workflow in DMXControl 3, the following section provides a detailed comparison of DMXControl 2 and DMXControl 3.

== Environment ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Supported DMX Interfaces'''
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| Some DMX interfaces, such as output via Art-Net, offer additional features in DMXControl 3.
|-
| '''DDFs (Device Library)'''
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. Display of control elements in the DDF is configurable for each individual DDF. {{No|-}} DDFs must be downloaded manually.
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. DDFs are significantly simplified. They now only contain the pure device definition. The uniform display of the control elements is handled by DMXControl 3 itself, where all functions are displayed in real values. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF DMXC3|DDF Documentation for DMXC3]]}}.}} {{Yes|-}} DDFs from the DDFLibrary can be downloaded directly into DMXControl 3 and used in the project. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF Library DMXC3|DDF Library]]}}.}}
| In the {{DMXCWebLinks|DDFLib}}, fully functional DDFs can be provided for both DMXControl versions, each with different DMX modes. {{Manual Reference | warning |DDFs from DMXControl 2 cannot be used in DMXControl 3.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | System Requirements and Information}}

| '''Operating System'''
| '''Up to''' and including '''Windows 8.1'''.
| All Windows versions '''from Windows 7''' onwards.
| For detailed system requirements for DMXControl 3, see {{DMXCWebLinks|DMXC-HP|dmxcontrol-3/systemrequirements.html| Overview on DMXControl Homepage}}.
|-
| '''Program Language'''
| {{Yes|-}} German {{Yes|-}} English
| {{Yes|-}} German {{Yes|-}} English {{Yes|-}} French {{Yes|-}} Japanese
|
|-
| '''Documentation'''
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Handbuch_DMXControl_2 German Manual] {{Yes|-}} '''[[Manual_DMXControl_2|English manual in draft form]]''' {{Yes|-}} '''[[DDF DMXC2|DDF Documentation]]''' {{Yes|-}} Plugin interface
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Tutorials_DMXControl_3 German Tutorial] {{Yes|-}} '''[[Tutorials DMXControl 3|English tutorial]]''' {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Inhalts%C3%BCbersicht_Hauptprogramm_DMXC3 German Manual] {{Yes|-}} '''[[Manual_DMXControl_3|English Manual]]''' {{Yes|-}} '''{{DMXCWebLinks|YouTube|DMXC3 Playlists}}''' {{Yes|-}} '''[[DDF DMXC3|DDF Documentation]]''' including extensive examples and tutorials {{No|-}} Plugin interface
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Work Environment}}

| '''Hardware Environment'''
| {{Yes|-}} Single PC. {{No|-}} No distributed system.
| {{Yes|-}} Single PC. {{Yes|-}} Distributed system possible, where the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[Umbra DMXC3|Umbra]]}} can run separately from the {{Manual Windowcaption|[[GUI DMXC3|User Interface (GUI)]]}}.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Multi-User'''
| {{No|-}} Single user only.
| {{Yes|-}} Multiple GUIs in a multi-user environment. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Server-Client Concept DMXC3|Server-Client Concept]]}}.}}
| For effective work, do not use a WLAN connection between the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[GUI DMXC3|User Interface (GUI)]]}}.
|-
| '''Performance'''
| {{No|-}} Requires a CPU with a high clock rate on one core for using 2 DMX universes.
| {{Yes|-}} Due to efficient programming, even mid-range PCs can output multiple DMX universes. The separation of {{Manual Windowcaption|[[GUI DMXC3|User Interface (GUI)]]}} and {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} provides additional safety in case of an interface failure.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Project Management'''
| {{No|-}} Only manual, as required project data is stored "open" in a directory and DDFs are stored independently of the project in the installation directory. {{No|-}} Switching PCs requires manually sorting various files, including DDFs, DMX-In configuration, MIDI configuration. {{No|-}} Only simple automatic project backup without version history.
| {{Yes|-}} All data required for the project, including DDFs, is stored in a project file. {{Yes|-}} Only the project file is needed for switching PCs. {{Yes|-}} Automatic saving including storing a certain number of previous project versions.
| Project management in DMXControl 3 handles the complete organization of projects including the associated versions. Searching for storage locations is unnecessary. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Project Administration DMXC3|Project Management (Project Administration)]]}}.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | External Interfaces and Control}}

|-
| '''DMX Output'''
| {{Yes}}, maximum 2 DMX universes.
| {{Yes}}, up to 16 DMX universes, depending on PC/laptop performance.
|
|-
| '''DMX-In'''
| {{Yes}}, but a maximum of 1 DMX universe.
| {{Yes}}, 2 DMX universes.
|
|-
| '''Keyboard Control'''
| {{Yes}}, but only simple key assignments are possible.
| {{Yes}}, including support for multiple banks and key combinations.
|
|-
| '''MIDI Interface'''
| {{Yes}}, available.
| {{Yes}}, available, including native support for multiple MIDI controllers without additional tools.
|
|-
| '''Joystick Control'''
| {{Yes}}
| {{No}}, but an alternative control option is available via the 3Dconnexion plugin.
|
|-
| '''Macroboards'''
| {{No}}
| {{Yes}}, available, including support for multiple macroboards like Elgato Stream Deck. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stream Deck DMXC3|Stream Deck]]}}.}}
|
|-
| '''Timecode''' (Protocol)
| {{Yes}}
| {{No}}, but coming soon.
|
|-
| '''OSC Interface'''
| {{Yes}}, available via plugin.
| {{No}}
|
|-
| '''Terminal Interface'''
| {{Yes}}
| {{No}}, no replacement planned at this time.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Feature Extensions}}

| '''Plugins'''
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}}.
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}} or user plugins in the {{DMXCWebLinks|Forum|Board|161|Plugins and Addons}} section.
|
|-
| '''Plugin Interface'''
| {{Yes}}
| {{Yes}}
| The interface in DMXControl 3 is not compatible with DMXControl 2.
|}

== Functionality ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment

{{DMXC3 Manual-Tablesection | S1 | 4 | Prepare Project}}

| '''Personal Device Favorites'''
| {{No|-}} Selecting frequently used devices is not possible.
| {{Yes|-}} In the dialog {{Manual Windowcaption|[[Device Manager DMXC3|Add Device]]}}, you can select devices from the available list that are used frequently.
|
|-
| '''Groups (of Devices)'''
| {{Yes|-}} Supported in a simple form for quick selection of devices in the stage view.
| {{Yes|-}} {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} are a core concept of DMXControl 3 and are intelligently designed.
| Users with many devices performing the same lighting scenes have better tools with DMXControl 3.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Hardware Abstraction (HAL)'''
| {{No|-}} Limited abstraction of DMX values via DDFs.
| {{Yes|-}} {{Manual Windowcaption|[[Hardware Abstraction Layer (HAL) DMXC3|HAL]]}} is a core concept of DMXControl 3, providing complete abstraction of all device functions. Working directly with DMX values is no longer necessary.
| Users with similar (but not identical) devices can still program them uniformly in DMXControl 3.
|-
| '''Channel Overview'''
| {{Yes|-}} Available.
| {{Yes|-}} Available independently of DMX and includes highlighting of the selected device. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Channel Overview DMXC3|Channel Overview]]}}.}}
|
|-
| '''Graphical Stage View'''
| {{Yes|-}} Available as a rough orientation aid in the lighting setup.
| {{Yes|-}} Similar to DMXControl 2 but with extended animation possibilities like gobo projection. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}.}}
|
|-
| '''Visualizer'''
| {{Yes|-}} Supported via Magic 3D EasyView.
| {{Yes|-}} Supported via Magic 3D EasyView and other external visualizers accessible via Art-Net.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Saving Scenes}}

| '''Scenes'''
| {{Yes|-}} Supported.
| {{Yes|-}} Supported in an enhanced form, where there is no distinction by scene type anymore. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Scenes are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Fanning'''
| {{No|-}} Only partially possible with a workaround using motion scenes.
| {{Yes|-}} Explicit fanning support through special command syntax at various points like device functions, parameters in effects, fade times for scenes, etc. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}}}}.
|
|-
| '''Relative Values'''
| {{No|}}
| {{Yes|-}} All numerical values for device functions such as dimmers, position, gobo rotation, etc., can be saved as relative and be calculated with other values during execution. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Absolute and Relative Values DMXC3|Absolute and Relative Values]]}}.}}
| The device function color is not included in the current version due to its complexity.
|-
| '''Motion Scenes'''
| {{Yes|-}} Supported.
| {{Yes|-}} Motion scenes are implicitly included in the "new" scenes and effects and can be applied to all numerical device functions. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}}}.
| Motion scenes from DMXControl 2 are not compatible with DMXControl 3.
|-
| '''Effects, Chasers'''
| {{Yes|-}} Supported, partially via tools like the running light generator or motion scene within the {{Manual Windowcaption|[[Chasers_tool_DMXC2|Chasers Tool]]}}.
| {{Yes|-}} Supported through the {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}} function with more effective definition options via various parameters, predefined effect library.
| Effects are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Dynamic Manipulation of Values'''
| {{No|}}
| {{Yes|-}} There are four types of {{Manual Windowcaption|[[Master DMXC3|Masters]]}} available, each of which can dynamically manipulate values of a function in a scene when the corresponding cuelist is executed. {{Manual Reference | arrow |For detailed explanations, see {{Manual Windowcaption|[[Master DMXC3|Master]]}}.}}. It does not matter whether it is a {{Manual Windowcaption|[[Cuelist DMXC3|Scene (Cue)]]}} or an {{Manual Windowcaption|[[Effects and Filters DMXC3|Effect or Filter]]}}.
| All {{Manual Windowcaption|[[Master DMXC3|Masters]]}} can be addressed and modified live through various means like {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}, {{Manual Windowcaption|[[MIDI DMXC3|MIDI]]}}, and more using {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}.
|-
| '''Presets'''
| {{Yes|-}} Implicitly via the scene library.
| {{Yes|-}} Direct support as a programming element for advanced users. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Preset DMXC3|Preset]]}}}}.
| The preset concept is not compatible with DMXControl 2.
|-
| '''Command Concept'''
| {{Yes|-}} Only for simple dependencies, similar to an automated mouse click. {{No|-}} Logical, mathematical, or status-dependent commands cannot be executed.
| {{Yes|-}} In simple form within cuelists. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}}}. {{Yes|-}} Cross-linking of actions with various logical, mathematical, or status-dependent dependencies across all program functions using the Input Assignment. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}}}.
| Commands in DMXControl 2 are not compatible with DMXControl 3, as the capabilities in DMXControl 3 are much greater.
|-
| '''Command Line'''
| {{Yes}}
| {{No}}
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Execute Show}}

| '''Cuelists'''
| {{Yes|-}} Supported, multiple instances can be executed.
| {{Yes|-}} Supported including the possibility to execute multiple instances simultaneously. Additionally, extended trigger options for the execution in the cuelist are available. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Cuelists are the main control tool in DMXControl 3. The various "implicit" cuelists from different tools in DMXControl 2 are unified.
|-
| '''Value Mixing in Cuelists'''
| {{Yes|-}} HTP and LTP supported, but setting is global for the entire project.
| {{Yes|-}} Extended support with three modes (LTP, HTP, and LoTP). Definition of mixing behavior individually for each cuelist. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3|HTP-, LTP- and LoTP Mixing]]}}.}}
|
|-
| '''Command Box'''
| {{Yes|-}} Supported.
| {{Yes|-}} Developed further as Softdesk and offers completely customizable user interface with numerous control elements. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}}}.
| Softdesk is not compatible with the Command Box.
|-
| '''Master'''
| {{Yes|-}} Supported in simple form: two Grand Masters and one Speed Master for the entire project.
| {{Yes|-}} Available in an advanced form. In addition to the {{Manual Windowcaption|[[Grand Master (Master) DMXC3|Grand Master]]}}, you can create a {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Master]]}} for each {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}}. 
| By creating your own {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Masters]]}}, you can control the brightness of different groups of devices in a much more detailed manner.
|-
| '''Submaster'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available in an advanced form of the {{Manual Windowcaption|[[Executor DMXC3|Executors]]}}, for example, to control {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}. In a future version, the {{Manual Windowcaption|[[Master DMXC3|Masters]]}} will also be available in Executors.
| Direct control of DMX channels is no longer available due to the fundamentally different concept of DMXControl 3.
|-
| '''Audio Player'''
| {{Yes|-}} Supported.
| {{Yes|-}} Simple sound effects can be played within a {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}. For longer songs, the {{Manual Windowcaption|[[Timecode Player DMXC3|Timecode Player]]}} can be used.
| The Timecode Player in DMXC3 also allows playing excerpts of songs and fading them in and out.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Timecode Player'''
| {{Yes|-}} Supported, but only in simple form.
| {{Yes|-}} Offers the possibility to create complex music-synchronized light shows from multiple excerpts of songs with detailed and flexible display of audio frequencies. The light shows are built via the recording function of Executors or multiple parallel-played {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}.
|-
| '''Textbook'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available as a user plugin. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Textbook Plugin DMXC3|Textbook]]}}.}}
|
|
|-
| '''Manual Beat Control'''
| {{Yes|-}} Via BeatTool.
| {{Yes|-}} In an advanced form through the {{Manual Windowcaption|[[Speed Master (Master) DMXC3|Speed Master]]}}, which can be created in any number and specifically assigned to certain {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} or stored in {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}.
|
|-
| '''Automatic Beat Detection'''
| {{Yes|-}} Supported via Winamp plugin and external interfaces.
| {{Yes|-}} Supported via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}} and external interfaces.
|
|-
| '''Sound to Light'''
| {{Yes|-}} Via various plugins.
| {{Yes|-}} Via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}}.
|
|-
| '''Video Control'''
| {{Yes|-}} Via various plugins (Winamp, Beamertool) and Media Center.
| {{No|-}} Possibly via various plugins.
|
|-
| '''Scheduler (Task Scheduler)'''
| {{Yes|-}} Supported.
| {{No|-}} Not available as a separate module, but an alternative is available through cuelists with the trigger "Real Time Clock (RTC)".
|
|}

== Application Plugins ==
Some plugins are no longer required in DMXControl 3, as their functionality is already integrated. Others will not be available until updated by their authors. Plugins cannot be used without modification due to changes in the plugin interface and programming language.

{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Beamertool'''
| {{Yes}}, available.
| {{No}}
| The Beamertool for the Raspberry Pi can be used via Art-Net in both versions.
|-
| '''Matrix Control MadMaxOne'''
| {{Yes|-}} Available.
| {{No|-}} Will not be migrated.
| A new concept for matrix devices with corresponding effects is integrated into DMXControl 3. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Matrix DMXC3|Matrix]]}} and {{Manual Windowcaption|[[Radix DMXC3|Radial Matrix (Radix)]]}}.}}
|-
| '''PDA Control'''
| {{Yes}}, available.
| {{No}}
|
|}

[[Category: Tipps]]

[[de: Umstieg_von_DMXControl_2_zu_DMXControl_3]]

Change over from DMXControl 2 to DMXControl 3

2025-03-04T19:31:57Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0
| Content = x
}}

Switching from one software to another or upgrading to a newer version often presents several challenges. In the case of transitioning from DMXControl 2 to DMXControl 3, these challenges can be summarized as follows:
* DMXControl 3 operates differently in several areas compared to DMXControl 2, meaning you will need to start learning how to use it from scratch.
* You have a functioning system with DMXControl 2 that you are familiar with, but now you are faced with a new and seemingly complex system (simply because you are not yet accustomed to it).

This article aims to outline the main differences between DMXControl 2 and DMXControl 3 and to summarize and answer the frequently asked questions in the forum about transitioning from DMXControl 2 to DMXControl 3. By the end, you will hopefully feel more comfortable navigating DMXControl 3.

To address any concerns upfront: although DMXControl 3 may initially seem like a complete reinvention, there is no need to worry. Once you take a second look—perhaps after your first few attempts—you will realize that DMXControl 2 and DMXControl 3 share many similarities. Some features are just accessed differently or found in new locations.

{{Manual Box | en | Important | This article reflects the current implementation status of '''DMXControl 3.3.0'''. Technical changes due to ongoing development are possible at any time.}}

= Compatibility =
Projects from DMXControl 2 are not compatible with DMXControl 3. This also includes DDFs, which must be completely recreated due to the changed requirements. {{Manual Reference |arrow| More information on creating DDFs, including examples, can be found in the documentation section for {{Manual Windowcaption|[[DDF DMXC3|DDFs for DMXControl 3]]}}.}}

Extensive compatibility is not necessary because many improvements allow effects to be recreated in just a few minutes. In some areas, entirely new workflows have been introduced, based on and even surpassing the concepts of professional software. However, some tools from DMXControl 2, such as the audio player and the text book, have not yet been integrated into DMXControl 3. Furthermore, plugins (both output and regular plugins) are not compatible due to the modified interfaces.

= Migration Guide =
== General Recommendations ==
Every DMXControl 2 user should consider their own migration strategy based on the tables in the section [[Switching from DMXControl 2 to DMXControl 3#Version Comparison|Version Comparison]]:
* You can run DMXControl 2 and DMXControl 3 in parallel on the same PC, allowing you to gradually familiarize yourself with DMXControl 3.
* Gradually build a working setup in DMXControl 3. With parallel operation, you always have a fallback project that works as expected. However, don't overdo it at first—start slowly.
* If you are using a large number of devices, you will quickly benefit from features like {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} and the associated {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}} in DMXControl 3.
* Even if you still rely on DMXControl 2 for tools like the audio player, which is not yet available in DMXControl 3, start familiarizing yourself with DMXControl 3. This will help you understand the basic workflow and allow you to create small test shows. When the timecode player becomes available, you will only need to learn that specific tool.

{{Manual Box | en | Attention | As indicated in the system requirements, Windows 8.1 is the last officially supported operating system for DMXControl 2. While DMXControl 2 may still work on Windows 10 and Windows 11, this is at your own risk. Future updates to these operating systems may render DMXControl 2 unusable. Since DMXControl 2 is no longer being developed, no further updates will be provided if problems arise.}}

== Comparison of Key Features ==
A major difference to get used to: DMXControl 3 does not work with channels but rather with device functions and property values. This makes it crucial for DDFs (at least for required functions) to be accurately implemented. In DMXControl 2, you could manually adjust values via the channel overview. In DMXControl 3, this is no longer possible because the channel overview does not save values. However, the big advantage is that you can select and adjust multiple devices of any type simultaneously.

Another key difference: {{Manual Windowcaption|[[Effektsequencer DMXC2|Effects]]}} in DMXControl 2 are now called {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} in DMXControl 3. These combine the cuelists and effects you know from DMXControl 2. You use cuelists to store all your lighting effects, such as chases and movements. The workflow is quite similar to DMXControl 2. You configure your fixtures in the {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}, click {{Manual MenuText|Add Cue}}, select the device functions to save (similar to channel selection in DMXControl 2), and confirm with {{Manual Buttons|OK}} to insert a {{Manual Windowcaption|Cue}} into the {{Manual Windowcaption|Cuelist}}.

Additionally, DMXControl 3 includes {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}—mathematical functions like sine and sawtooth waves. These can be applied to almost any device property and adjusted live. Try dragging a {{Manual Objectcaption|1D Effect}} onto the dimmer of a {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}} to see how it responds.

== Initial Approach ==
For your first steps in DMXControl 3, start by adding some devices to your project. They don’t need to match your actual equipment. Ensure that device groups are automatically created during this process. Next, try creating some lighting moods by adjusting settings via the {{Manual Windowcaption|[[Control Panel DMXC3|Control Panel]]}} and {{Manual Windowcaption|[[Device Control DMXC3|Device Control]]}}. To reset, use the {{Manual Buttons|Clear}} button in the quick access bar.

After creating a few lighting moods, try saving them. In the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}}, create a new {{Manual Windowcaption|Cuelist}} and open it with a double-click. If a lighting mood exists in the {{Manual Windowcaption|Stage View}}, click {{Manual MenuText|Add Cue}} to save it. Clear the stage view and test playback using the {{Manual MenuText|Go}} button in the {{Manual Windowcaption|Cuelist editor}}.

{{Manual Box | en | Reference | ''A more detailed quick-start guide for DMXControl 3 is available in the '''[[Quickstart Guide DMXC3|Quickstart Guide]]'''.''}}

== Version Comparison ==
After describing the workflow in DMXControl 3, the following section provides a detailed comparison of DMXControl 2 and DMXControl 3.

== Environment ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Supported DMX Interfaces'''
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| {{Yes|-}} See article [[Supported_DMX_Interfaces|Supported DMX Interfaces]].
| Some DMX interfaces, such as output via Art-Net, offer additional features in DMXControl 3.
|-
| '''DDFs (Device Library)'''
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. Display of control elements in the DDF is configurable for each individual DDF. {{No|-}} DDFs must be downloaded manually.
| {{Yes|-}} See {{DMXCWebLinks|DDFLib}}. DDFs are significantly simplified. They now only contain the pure device definition. The uniform display of the control elements is handled by DMXControl 3 itself, where all functions are displayed in real values. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF DMXC3|DDF Documentation for DMXC3]]}}.}} {{Yes|-}} DDFs from the DDFLibrary can be downloaded directly into DMXControl 3 and used in the project. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[DDF Library DMXC3|DDF Library]]}}.}}
| In the {{DMXCWebLinks|DDFLib}}, fully functional DDFs can be provided for both DMXControl versions, each with different DMX modes. {{Manual Reference | warning |DDFs from DMXControl 2 cannot be used in DMXControl 3.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | System Requirements and Information}}

| '''Operating System'''
| '''Up to''' and including '''Windows 8.1'''.
| All Windows versions '''from Windows 7''' onwards.
| For detailed system requirements for DMXControl 3, see {{DMXCWebLinks|DMXC-HP|dmxcontrol-3/systemrequirements.html| Overview on DMXControl Homepage}}.
|-
| '''Program Language'''
| {{Yes|-}} German {{Yes|-}} English
| {{Yes|-}} German {{Yes|-}} English {{Yes|-}} French {{Yes|-}} Japanese
|
|-
| '''Documentation'''
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Handbuch_DMXControl_2 German Manual] {{Yes|-}} '''[[Manual_DMXControl_2|English manual in draft form]]''' {{Yes|-}} '''[[DDF DMXC2|DDF Documentation]]''' {{Yes|-}} Plugin interface
| {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Tutorials_DMXControl_3 German Tutorial] {{Yes|-}} '''[[Tutorials DMXControl 3|English tutorial]]''' {{Yes|-}} [https://wiki-de.dmxcontrol-projects.org/index.php?title=Inhalts%C3%BCbersicht_Hauptprogramm_DMXC3 German Manual] {{Yes|-}} '''[[Manual_DMXControl_3|English Manual]]''' {{Yes|-}} '''{{DMXCWebLinks|YouTube|DMXC3 Playlists}}''' {{Yes|-}} '''[[DDF DMXC3|DDF Documentation]]''' including extensive examples and tutorials {{No|-}} Plugin interface
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Work Environment}}

| '''Hardware Environment'''
| {{Yes|-}} Single PC. {{No|-}} No distributed system.
| {{Yes|-}} Single PC. {{Yes|-}} Distributed system possible, where the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[Umbra DMXC3|Umbra]]}} can run separately from the {{Manual Windowcaption|[[GUI DMXC3|User Interface (GUI)]]}}.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Multi-User'''
| {{No|-}} Single user only.
| {{Yes|-}} Multiple GUIs in a multi-user environment. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Server-Client Concept DMXC3|Server-Client Concept]]}}.}}
| For effective work, do not use a WLAN connection between the {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} and {{Manual Windowcaption|[[GUI DMXC3|User Interface (GUI)]]}}.
|-
| '''Performance'''
| {{No|-}} Requires a CPU with a high clock rate on one core for using 2 DMX universes.
| {{Yes|-}} Due to efficient programming, even mid-range PCs can output multiple DMX universes. The separation of {{Manual Windowcaption|[[GUI DMXC3|User Interface (GUI)]]}} and {{Manual Windowcaption|[[Kernel DMXC3|Kernel]]}} provides additional safety in case of an interface failure.
|
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Project Management'''
| {{No|-}} Only manual, as required project data is stored "open" in a directory and DDFs are stored independently of the project in the installation directory. {{No|-}} Switching PCs requires manually sorting various files, including DDFs, DMX-In configuration, MIDI configuration. {{No|-}} Only simple automatic project backup without version history.
| {{Yes|-}} All data required for the project, including DDFs, is stored in a project file. {{Yes|-}} Only the project file is needed for switching PCs. {{Yes|-}} Automatic saving including storing a certain number of previous project versions.
| Project management in DMXControl 3 handles the complete organization of projects including the associated versions. Searching for storage locations is unnecessary. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Project Administration DMXC3|Project Management (Project Administration)]]}}.}}

{{DMXC3 Manual-Tablesection | S1 | 4 | External Interfaces and Control}}

|-
| '''DMX Output'''
| {{Yes}}, maximum 2 DMX universes.
| {{Yes}}, up to 16 DMX universes, depending on PC/laptop performance.
|
|-
| '''DMX-In'''
| {{Yes}}, but a maximum of 1 DMX universe.
| {{Yes}}, 2 DMX universes.
|
|-
| '''Keyboard Control'''
| {{Yes}}, but only simple key assignments are possible.
| {{Yes}}, including support for multiple banks and key combinations.
|
|-
| '''MIDI Interface'''
| {{Yes}}, available.
| {{Yes}}, available, including native support for multiple MIDI controllers without additional tools.
|
|-
| '''Joystick Control'''
| {{Yes}}
| {{No}}, but an alternative control option is available via the 3Dconnexion plugin.
|
|-
| '''Macroboards'''
| {{No}}
| {{Yes}}, available, including support for multiple macroboards like Elgato Stream Deck. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stream Deck DMXC3|Stream Deck]]}}.}}
|
|-
| '''Timecode''' (Protocol)
| {{Yes}}
| {{No}}, but coming soon.
|
|-
| '''OSC Interface'''
| {{Yes}}, available via plugin.
| {{No}}
|
|-
| '''Terminal Interface'''
| {{Yes}}
| {{No}}, no replacement planned at this time.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Feature Extensions}}

| '''Plugins'''
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}}.
| {{Yes|-}} See {{DMXCWebLinks|DMXC-HP|downloads.html| Download area on the DMXControl homepage}} or user plugins in the {{DMXCWebLinks|Forum|Board|161|Plugins and Addons}} section.
|
|-
| '''Plugin Interface'''
| {{Yes}}
| {{Yes}}
| The interface in DMXControl 3 is not compatible with DMXControl 2.
|}

== Functionality ==
{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment

{{DMXC3 Manual-Tablesection | S1 | 4 | Prepare Project}}

| '''Personal Device Favorites'''
| {{No|-}} Selecting frequently used devices is not possible.
| {{Yes|-}} In the dialog {{Manual Windowcaption|[[Device Manager DMXC3|Add Device]]}}, you can select devices from the available list that are used frequently.
|
|-
| '''Groups (of Devices)'''
| {{Yes|-}} Supported in a simple form for quick selection of devices in the stage view.
| {{Yes|-}} {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} are a core concept of DMXControl 3 and are intelligently designed.
| Users with many devices performing the same lighting scenes have better tools with DMXControl 3.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Hardware Abstraction (HAL)'''
| {{No|-}} Limited abstraction of DMX values via DDFs.
| {{Yes|-}} {{Manual Windowcaption|[[Hardware Abstraction Layer (HAL) DMXC3|HAL]]}} is a core concept of DMXControl 3, providing complete abstraction of all device functions. Working directly with DMX values is no longer necessary.
| Users with similar (but not identical) devices can still program them uniformly in DMXControl 3.
|-
| '''Channel Overview'''
| {{Yes|-}} Available.
| {{Yes|-}} Available independently of DMX and includes highlighting of the selected device. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Channel Overview DMXC3|Channel Overview]]}}.}}
|
|-
| '''Graphical Stage View'''
| {{Yes|-}} Available as a rough orientation aid in the lighting setup.
| {{Yes|-}} Similar to DMXControl 2 but with extended animation possibilities like gobo projection. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}.}}
|
|-
| '''Visualizer'''
| {{Yes|-}} Supported via Magic 3D EasyView.
| {{Yes|-}} Supported via Magic 3D EasyView and other external visualizers accessible via Art-Net.
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Saving Scenes}}

| '''Scenes'''
| {{Yes|-}} Supported.
| {{Yes|-}} Supported in an enhanced form, where there is no distinction by scene type anymore. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Scenes are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Fanning'''
| {{No|-}} Only partially possible with a workaround using motion scenes.
| {{Yes|-}} Explicit fanning support through special command syntax at various points like device functions, parameters in effects, fade times for scenes, etc. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Fanning DMXC3|Fanning]]}}}}.
|
|-
| '''Relative Values'''
| {{No|}}
| {{Yes|-}} All numerical values for device functions such as dimmers, position, gobo rotation, etc., can be saved as relative and be calculated with other values during execution. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Absolute and Relative Values DMXC3|Absolute and Relative Values]]}}.}}
| The device function color is not included in the current version due to its complexity.
|-
| '''Motion Scenes'''
| {{Yes|-}} Supported.
| {{Yes|-}} Motion scenes are implicitly included in the "new" scenes and effects and can be applied to all numerical device functions. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}}}.
| Motion scenes from DMXControl 2 are not compatible with DMXControl 3.
|-
| '''Effects, Chasers'''
| {{Yes|-}} Supported, partially via tools like the running light generator or motion scene within the {{Manual Windowcaption|[[Chasers_tool_DMXC2|Chasers Tool]]}}.
| {{Yes|-}} Supported through the {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}} function with more effective definition options via various parameters, predefined effect library.
| Effects are not compatible.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Dynamic Manipulation of Values'''
| {{No|}}
| {{Yes|-}} There are four types of {{Manual Windowcaption|[[Master DMXC3|Masters]]}} available, each of which can dynamically manipulate values of a function in a scene when the corresponding cuelist is executed. {{Manual Reference | arrow |For detailed explanations, see {{Manual Windowcaption|[[Master DMXC3|Master]]}}.}}. It does not matter whether it is a {{Manual Windowcaption|[[Cuelist DMXC3|Scene (Cue)]]}} or an {{Manual Windowcaption|[[Effects and Filters DMXC3|Effect or Filter]]}}.
| All {{Manual Windowcaption|[[Master DMXC3|Masters]]}} can be addressed and modified live through various means like {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}, {{Manual Windowcaption|[[MIDI DMXC3|MIDI]]}}, and more using {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}.
|-
| '''Presets'''
| {{Yes|-}} Implicitly via the scene library.
| {{Yes|-}} Direct support as a programming element for advanced users. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Preset DMXC3|Preset]]}}}}.
| The preset concept is not compatible with DMXControl 2.
|-
| '''Command Concept'''
| {{Yes|-}} Only for simple dependencies, similar to an automated mouse click. {{No|-}} Logical, mathematical, or status-dependent commands cannot be executed.
| {{Yes|-}} In simple form within cuelists. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}}}. {{Yes|-}} Cross-linking of actions with various logical, mathematical, or status-dependent dependencies across all program functions using the Input Assignment. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}}}.
| Commands in DMXControl 2 are not compatible with DMXControl 3, as the capabilities in DMXControl 3 are much greater.
|-
| '''Command Line'''
| {{Yes}}
| {{No}}
|

{{DMXC3 Manual-Tablesection | S1 | 4 | Execute Show}}

| '''Scene Lists'''
| {{Yes|-}} Supported, multiple instances can be executed.
| {{Yes|-}} Supported including the possibility to execute multiple instances simultaneously. Additionally, extended trigger options for the execution in the cuelist are available. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.}}
| Cuelists are the main control tool in DMXControl 3. The various "implicit" cuelists from different tools in DMXControl 2 are unified.
|-
| '''Value Mixing in Cuelists'''
| {{Yes|-}} HTP and LTP supported, but setting is global for the entire project.
| {{Yes|-}} Extended support with three modes (LTP, HTP, and LoTP). Definition of mixing behavior individually for each cuelist. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[HTP-, LTP- and LoTP-Mixing (Cuelist) DMXC3|HTP-, LTP- and LoTP Mixing]]}}.}}
|
|-
| '''Command Box'''
| {{Yes|-}} Supported.
| {{Yes|-}} Developed further as Softdesk and offers completely customizable user interface with numerous control elements. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}}}.
| Softdesk is not compatible with the Command Box.
|-
| '''Master'''
| {{Yes|-}} Supported in simple form: two Grand Masters and one Speed Master for the entire project.
| {{Yes|-}} Available in an advanced form. In addition to the {{Manual Windowcaption|[[Grand Master (Master) DMXC3|Grand Master]]}}, you can create a {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Master]]}} for each {{Manual Windowcaption|[[Device Group DMXC3|Device Group]]}}. 
| By creating your own {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Masters]]}}, you can control the brightness of different groups of devices in a much more detailed manner.
|-
| '''Submaster'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available in an advanced form of the {{Manual Windowcaption|[[Executor DMXC3|Executors]]}}, for example, to control {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}. In a future version, the {{Manual Windowcaption|[[Master DMXC3|Masters]]}} will also be available in Executors.
| Direct control of DMX channels is no longer available due to the fundamentally different concept of DMXControl 3.
|-
| '''Audio Player'''
| {{Yes|-}} Supported.
| {{Yes|-}} Simple sound effects can be played within a {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}. For longer songs, the {{Manual Windowcaption|[[Timecode Player DMXC3|Timecode Player]]}} can be used.
| The Timecode Player in DMXC3 also allows playing excerpts of songs and fading them in and out.
|-
| {{Manual Icon inline |DMXC3 Icon V-Collection star yellow.png}} '''Timecode Player'''
| {{Yes|-}} Supported, but only in simple form.
| {{Yes|-}} Offers the possibility to create complex music-synchronized light shows from multiple excerpts of songs with detailed and flexible display of audio frequencies. The light shows are built via the recording function of Executors or multiple parallel-played {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}}.
|-
| '''Textbook'''
| {{Yes|-}} Supported.
| {{Yes|-}} Available as a user plugin. {{Manual Reference | arrow |See details {{Manual Windowcaption|[[Textbook Plugin DMXC3|Textbook]]}}.}}
|
|
|-
| '''Manual Beat Control'''
| {{Yes|-}} Via BeatTool.
| {{Yes|-}} In an advanced form through the {{Manual Windowcaption|[[Speed Master (Master) DMXC3|Speed Master]]}}, which can be created in any number and specifically assigned to certain {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} or stored in {{Manual Windowcaption|[[Effects and Filters DMXC3|Effects and Filters]]}}.
|
|-
| '''Automatic Beat Detection'''
| {{Yes|-}} Supported via Winamp plugin and external interfaces.
| {{Yes|-}} Supported via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}} and external interfaces.
|
|-
| '''Sound to Light'''
| {{Yes|-}} Via various plugins.
| {{Yes|-}} Via {{Manual Windowcaption|[[Audioanalyzer DMXC3|Audioanalyzer]]}}.
|
|-
| '''Video Control'''
| {{Yes|-}} Via various plugins (Winamp, Beamertool) and Media Center.
| {{No|-}} Possibly via various plugins.
|
|-
| '''Scheduler (Task Scheduler)'''
| {{Yes|-}} Supported.
| {{No|-}} Not available as a separate module, but an alternative is available through cuelists with the trigger "Real Time Clock (RTC)".
|
|}

== Application Plugins ==
Some plugins are no longer required in DMXControl 3, as their functionality is already integrated. Others will not be available until updated by their authors. Plugins cannot be used without modification due to changes in the plugin interface and programming language.

{| class="wikitable toptextcells"
|- class="hintergrundfarbe10"
! style="width: 10%;" | Feature !! style="width: 30%" | DMXControl 2 !! style="width: 30%" | DMXControl 3 !! style="width: 30%" | Comment
|-
| '''Beamertool'''
| {{Yes}}, available.
| {{No}}
| The Beamertool for the Raspberry Pi can be used via Art-Net in both versions.
|-
| '''Matrix Control MadMaxOne'''
| {{Yes|-}} Available.
| {{No|-}} Will not be migrated.
| A new concept for matrix devices with corresponding effects is integrated into DMXControl 3. {{Manual Reference | arrow |For details, see {{Manual Windowcaption|[[Matrix DMXC3|Matrix]]}} and {{Manual Windowcaption|[[Radix DMXC3|Radial Matrix (Radix)]]}}.}}
|-
| '''PDA Control'''
| {{Yes}}, available.
| {{No}}
|
|}

[[Category: Tipps]]

[[de: Umstieg_von_DMXControl_2_zu_DMXControl_3]]

Tutorials DMXControl 3

2025-03-04T19:00:29Z

Jkuehn:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0}}

=Tutorial for DMXControl 3.0=
If you are a user of DMXControl 2 and you want to test the beta version of DMXControl 3, you have to be willing to rethink some things. DMXControl 3 provides fantastic new features that did not fit into the framework of DMXControl 2. Therefore, we have prepared a tutorial as a guide to the new lighting control software DMXControl 3 for you.
 
During the transition from DMXControl2 to DMXControl 3 many new concepts have been introduced. A so-called HAL (Hardware Abstraction Layer) ensures that the program is independent from the DMX output, i.e. you work primarily with abstract properties such as color, position and beam instead of DMX values. Furthermore, there is now a separation in server and client, so that several people can work on one project at the same time. Great new opportunities in effect programming have been implemented, not inferior to professional DMX programs.

The basic differences between the releases of DMXControl 3 and 2 are described in the german article [http://www.dmxcontrol.de/wiki/Uebergang_von_DMXControl_2_zu_3 Übergang von DMXControl 2 zu 3 (german)]. It should be emphasized that DMXControl 2 will be maintained for some time and is provisionally proposed for usage as your main light control program.
 
Because of altered concepts the nature of the programming and operation has fundamentally changed. This requires that you start from the beginning again. We encourage you to study the following tutorial of the operating concepts of DMXControl 3 and to accept the changes. If you have understood the concepts, everything will be as common and simple as in DMXControl 2.
 
This tutorial is split into three parts:
* Lesson 1 to 7: Basic concepts, setup and configuration
* Lesson 8 to 14: Programming your cues and show
* Lesson 15 to 21: Execution of show and add-ons

If you find errrors anywhere or if you are not happy with some parts, please tell it to '''us''' by the bugtracker on the website, email or the betatest-thread on the homepage.
If you are convinced that the approach of DMXControl 3 is great, please tell it to '''others''' via facebook, feedback thread, etc.;)

Thanks to Arne, Dennis, Franky, Mark, Matthias, Stefan (and others) for all the work they have put into DMXControl 3. At this tutorial Carlo, Frank, Jens-Peter, Uwe and some alpha testers were involved. Also, this tutorial is obviously still in beta stage. Please notify the manual team with your suggestions. A 'proper' manual will be created in parallel to the beta phase.

Now have fun in learning DMXControl 3!

= Table of content =

{| width=100%
| width="50%" valign=top |
[[Lesson_1_Tut3|Lesson 1: Installation and configuration]] 
[[Lesson_2_Tut3|Lesson 2: The Panel concept of DMXControl 3 GUI]] 
[[Lesson_3_Tut3|Lesson 3: The Project Explorer]] 
[[Lesson_4_Tut3|Lesson 4: The Stage view ]] 
[[Lesson_5_Tut3|Lesson 5: Device properties and its control ]] 
[[Lesson_6_Tut3|Lesson 6: Configuration of output plugins ]] 
[[Lesson_7_Tut3|Lesson 7: Summary and some more details of setup ]] 
[[Lesson_8_Tut3|Lesson 8: Cues and cue lists ]] 
[[Lesson_9_Tut3|Lesson 9: Fanning, Chasers and other effects ]] 
[[Lesson_10_Tut3|Lesson 10: The Programmer view ]] 
[[Lesson_11_Tut3|Lesson 11: Triggers in cue lists ]] 
[[Lesson_12_Tut3|Lesson 12: Editing Cues and cue lists ]] 
[[Lesson_13_Tut3|Lesson 13: Presets ]] 
|valign=top |
[[Lesson_14_Tut3|Lesson 14: Summary and details - Programming ]] 
[[Lesson_15_Tut3|Lesson 15: Executors and use of cue lists ]] 
[[Lesson_16_Tut3|Lesson 16: SoftDesk ]] 
[[Lesson_17_Tut3|Lesson 17: Audio analyzer ]] 
[[Lesson_18_Tut3|Lesson 18: Beamer Tool ]] 
[[Lesson_19_Tut3|Lesson 19: Other DMX Clients ]] 
[[Lesson_20_Tut3|Lesson 20: Create new device definitions ]] 
[[Lesson_21_Tut3|Lesson 21: Summary and details for Execution ]] 
[[Lesson_22_Tut3|Lesson 22: Input Assignment ]] 
[[Lesson_23_Tut3|Lesson 23: Create a RGB Matrix]] 
[[Lesson_24_Tut3|Lesson 24: Transfer DMX values via ArtNet to DMXControl 2]] 
[[Appendix_1_Tut3|Appendix 1: Commands and Shortcuts]] 
[[Appendix_2_Tut3|Appendix 2: Tips for testing and behavior in case of error]] 
|}

= Links & References =
{| width=100%
| width="150px" valign=top | '''Videos:'''
| [http://www.dmxcontrol.de/wiki/DMXControl_3.0_-_Videos DMXControl 3.0 - Videos (german)]
|-
|'''FAQs:'''
| [http://www.dmxcontrol.de/wiki/DMXControl_3.0_%28FAQ%29 DMXControl 3.0 (FAQ) (german)]
|-
|'''more info:'''
| [http://www.dmxcontrol.de/wiki/Uebergang_von_DMXControl_2_zu_3 Übergang von DMXControl 2 zu 3 (german)]
|-
|
| [http://www.dmxcontrol.de/wiki/Getting_started_with_DMXControl_3_%28deutsch%29 Getting started with DMXControl 3 (german)]
|}

__NOTOC__
__NOTITLE__

[[Category: Tutorials DMXControl 3]]
[[de:Tutorials DMXControl 3]]