English DMXC-Wiki - User contributions [en]

Playground

2025-03-02T19:28:53Z

Jnoetzel:

{{Manual Box | en | Advanced | DMXControl 3 is in the beta phase. Therefore, there may be unforeseen responses or error messages. In addition, some features are not yet fully mature and DMXControl 3 still does not offer the functionality that provides DMXControl 2. Therefore DMXControl 3 is in its current state is '''not''' intended for productive use as long the beta test is running!
}}

Pack And Go DMXC2

2025-03-02T19:28:17Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Plugins_DMXC2
| TextBackwards = Plugins
| LinkForwards = DDF_DMXC2
| TextForwards = DDF basic
}}
{{Start-LaTeX}}
==Overview==

The Pack & go function is a great help when you have to change the PC for the show for some reason.
The function creates a ZIP file with the relevant files of a project.

==Description==
{{Picture_with_subtitle |DMXC2_Manual_pack_and_go_window.png|1|The « Pack And Go » configuration window}}

This file can E. g. via USB stick on another PC be transferred and there "' manual"' unpacked are. Target directory are the projects directory (<tt>C:\my documents\DMXControl...</tt>) from DMXControl and the application data directory (see below).

==Controls==

In the menu window, you can select which files "should be ZIPed" via the check boxes. Terms of default all are selected.

==Tip(s)== Special instructions for unpacking on the target machine

*We recommend you to create Pack & go file under Win7 not in the default installation directory, (XP: <tt>C:\Documents\[Username]\my documents\DMXControl Projecte</tt>; at Vista: <tt>C:\Users\[Username]\my documents\DMXControl Projecte</tt>) since there there writing and reading problems can give, if it does not work as an administrator.
* Some users have asked for a memo. You can use Notepad for example. As long as the file in the project directory is located and it is just named like the project (<tt><Projektname>.txt</tt>), so it will be packed to them by Pack & go.

{{Manual Box | en | Important | Special instructions for unpacking on the target machine 
"<tt>DMXInRemote.dat</tt>" and "<tt>MIDIRemote.dat</tt>": 
*Vista/Windows7: "<tt>%APPDATA%\PopSoft\DMXControl</tt>" (z.B. "<tt>C:\Users\[Username]\AppData\Roaming\PopSoft\DMXControl\</tt>") 
*WindowsXP: Im DMXControl-program directory (z.B. "<tt>C:\Documents\[Username]\application data\PopSoft\DMXControl\</tt>")
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Plugins_DMXC2
| TextBackwards = Plugins
| LinkForwards = DDF_DMXC2
| TextForwards = DDF basic
}}
[[de: Pack_And_Go_DMXC2]]
[[Category: DMXControl 2]]

Plugins DMXC2

2025-03-02T19:27:56Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Program_settings_DMXC2
| TextBackwards = Program settings
| LinkForwards = Pack_And_Go_DMXC2
| TextForwards = Pack And Go Function
}}
{{Start-LaTeX}}
==Overview==

The plugin interface makes it possible to extend DMXControl by additional functions by plugins. Plugins can be downloaded <ref>Plugin download http://www.dmxcontrol.de/downloads/plugins.html</ref> from the DMXControl main side. As special plugins, the beamer tool of Zoidberg and the MadMaxOne Plugin by Frank Brüggemann shall here be mentioned.
{{Manual Box | en | Important | These aren't same Plugins and output plugins and are stored in different lists. output plugins help merely the communication of DMXControl with the attached DMX interface.
plugins provide DMXControl with extended and additional functions.
}}

==Description==
Plugins are simply in the directory of plugins in the DMXControl program directory after the download unzip. Then, the plugin in the plugin administration can be configured and enabled after takeoff from DMXControl.

==Controls==
{{Picture_with_subtitle |DMXC2_Manual_plugin_plugin_administration.png|1|Window plugin administration|center}} 
At the opening of the plugin administration under « Configuration », « Plugins. . . » menu item menu opens the window of the « plugin administration » (see fig. 1).

All under DMXControl, in the plugin directory of installed plugins, are displayed in the plugin administration. The plugins are displayed in a list control, a checkbox enables or disables the plugin located in each plugin namen.

The button is below the list Provided that the plugin offers the possibility of a configuration, can here by choice « configure chosen plugin » the with the mouse and click on the badge the configuration window of the plugins be opened.

Below the button « configure chosen plugin » the button is Here users can release « Enable Plugins for users without administration privileges & raquo; these don't have any administration privileges at the PC, avoid this here.

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Program_settings_DMXC2
| TextBackwards = Program settings
| LinkForwards = Pack_And_Go_DMXC2
| TextForwards = Pack And Go Function
}}
[[de: Plugins_DMXC2]]
[[Category: DMXControl 2]]

Program settings DMXC2

2025-03-02T19:27:41Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = DMXIn_remote_control_DMXC2
| TextBackwards = DMXIn remote control
| LinkForwards = Plugins_DMXC2
| TextForwards = Plugins
}}
{{Start-LaTeX}}
==Overview==
Essential attitudes can be adapted regarding the unusual features of the computer and/or the light configuration in the window program configuration. 
The program configuration is divided up into 5 areas:

*General
*Graphical view
*Cues/Chasers
*Tools
*Output

==Description==
===Tabulator General===

{{Picture_with_subtitle |DMXC2_Manual_program_settings_general.png|1|Window program settings, tab general|center}} 

{| cellpadding="5" cellspacing="0" border="1"
|-
! style="text-align:left" | Setting
! style="text-align:left" | Meaning
! style="text-align:left" | Default
! style="text-align:left" | comment
|- style="vertical-align:top"
|colspan="4"|'''Performance'''
|- style="vertical-align:top"
| Refresh interval for spectrum analyzer
| Time interval after which new audio data are fetched by WinAmp
| 50 ms
| A larger interval can improve performance at weak computers
|- style="vertical-align:top"
| Disable automatic saving of cue library
| The cue library is stored periodically, by activation this storage can be put down.
| not enabled
| At great projects with outstandingly many cues, it can come to delays in the course of the chasers by the automatic storage of the cue library sometimes.
|- style="vertical-align:top"
|colspan="4"|'''View'''
|- style="vertical-align:top"
| Font size for zoomed views
| Type size in the graphical view at zoom
| 8
|
|- style="vertical-align:top"
| Indication of the DMX values %
| Rearrangement between absolute and percent indication
| not enabled
|
|- style="vertical-align:top"
|colspan="4"|'''Program startup'''
|- style="vertical-align:top"
| Execute command on programm start
| To the start of DMXControl an command which switches on e. g. the Grundlich is executed.
| no command defines
| The command can about the DMXControl usual commands are defined. (see chapter command overview)
|- style="vertical-align:top"
| Deactivating safety query at program end
| Deactivating query when ending DMXControl
| not enabled
|
|- style="vertical-align:top"
|colspan="4"|'''Other'''
|- style="vertical-align:top"
| Save color and gobo lists globally
| The color and gobo lists aren't stored in the project directrory, but in the DMXControl directrory .
| not enabled
| Farb and Gobolisten can be used in all projects
|- style="vertical-align:top"
| Flash "scroll lock" LED on beat
| Beat from the beat tool or sound analyzer flashes the "scroll lock" LED.
| not enabled
|
|}
 
{{Manual Box | en | Important | For large projects with above average many cues, it may cause ever automatic storing of cue library delays in the flow of the chasers. In this case, disable the automatic fuse is advisable at this point.}}

===Tabulator Graphical view===

{{Picture_with_subtitle|DMXC2_Manual_program_settings_graphical_view.png|2|Window program settings, tab graphical view|center}}
 
{| cellpadding="5" cellspacing="0" border="1"
|-
! style="text-align:left" | Setting
! style="text-align:left" | Meaning
! style="text-align:left" | Default
! style="text-align:left" | comment
|- style="vertical-align:top"
|colspan="4"|'''Device-popups'''
|- style="vertical-align:top"
| Open when hovering over the icon
| DDF devices popups, opens when you move the mouse over it.
| not enabled
|
|- style="vertical-align:top"
| Open after clicking the icon
| DDF devices popups, opens when clicking the device icon.
| enabled
|
|- style="vertical-align:top"
| Close after:        ms
| Time to close the DDF devices popups when the mouse leaves popup.
| 1 sec.
|
|- style="vertical-align:top"
|colspan="4"|'''Icons'''
|- style="vertical-align:top"
| Size
| Size of the icons in the graphical view in pixels
| 32 pixel.
|
|- style="vertical-align:top"
| Change size when zooming
| Information when zooming the graphical view also increase
| not enabled
|
|- style="vertical-align:top"
| Use presetation of color instead of graphic
| When enabled a programmed LED color is displayed in LED-RGB devices instead of the icons.
| not enabled
|
|- style="vertical-align:top"
| Show device name and adress
| The device names and addresses are displayed in addition to the icons in the graphical view of the stage
| not enabled
|
|}

===Tabulator Cues/Chasers===

{{Picture_with_subtitle|DMXC2_Manual_program_settings_cues-chasers.png|3|Window program settings, tab cues/chasers|center}} 
 
{| cellpadding="5" cellspacing="0" border="1"
|-
! style="text-align:left" | Setting
! style="text-align:left" | Meaning
! style="text-align:left" | Default
! style="text-align:left" | comment
|- style="vertical-align:top"
|colspan="4"|'''Cues'''
|- style="vertical-align:top"
| Default set points for non-fading channels
| About the slider can be set at what point the channel is switched on.
| 50%
|
|- style="vertical-align:top"
| No warning when all channels should be saved.
| When saving from all channels a warning carried DMXControl, since this database is also larger. Here, this warning can be turned off and be darurch more effectively worked.
| not enabled
|
|- style="vertical-align:top"
|colspan="4"|'''Chasers'''
|- style="vertical-align:top"
| Start chasers on double click
| It enables the start of a cue in the chaser by a double click.
| not enabled
|
|- style="vertical-align:top"
| Threat ungrouped chasers as separate group
| All of the chasers associated with any group form a distinct group activation.
| not enabled
|
|- style="vertical-align:top"
| Align group names right hand
| Sets the group names right in the chaser window from, rather than directly behind the chaser name.
| enabled
|
|}

===Tabulator Tools===

{{Picture_with_subtitle|DMXC2_Manual_program_settings_tools.png|4|Window program settings, tab tools|center}} 
 
{| cellpadding="5" cellspacing="0" border="1"
|-
! style="text-align:left" | Setting
! style="text-align:left" | Meaning
! style="text-align:left" | Default
! style="text-align:left" | comment
|- style="vertical-align:top"
|colspan="4"|'''Sound analyzer'''
|- style="vertical-align:top"
| Quelle VBVis-Plugin
| If the radio button VBVis plugin is enabled are imported the audio data for the BeatTool and the sound Analyzer via this plugin in Winamp after DMXControl.
| enabled
|
|- style="vertical-align:top"
| Quelle AVS-Plugin
| If the radio button AVS plugin import the audio data for the BeatTool and the sound Analyzer via this plugin in Winamp after DMXControl is enabled.
| not enabled
|
|}

===Tabulator Output===

{{Picture_with_subtitle|DMXC2_Manual_program_settings_output.png|5|Window program settings, tab output|center}} 
 
{| cellpadding="5" cellspacing="0" border="1"
|-
! style="text-align:left" | Setting
! style="text-align:left" | Meaning
! style="text-align:left" | Default
! style="text-align:left" | comment
|- style="vertical-align:top"
|colspan="4"|'''DMX mixer'''
|- style="vertical-align:top"
| Disable "Highest takes precendence" (HTP) mixing
| With this option, DMX mix can be switched between LTP and HTP.
| enabled
|
|- style="vertical-align:top"
| Use HTP for mixing RGB channels)
| If you enable this option, also the RGB channels in the HTP-mode are mixed.
| not enabled
|
|- style="vertical-align:top"
| Handle RGB channels as dimmer
| If you enable this option, RGB channels handled devices as dimmer by LED.
| not enabled
|
|- style="vertical-align:top"
| Let DDF's limit channel values (MinValue/MaxValue)
| If this option is enabled, which transferred values from the DDF's min and MaxValue and included for the output.
| not enabled
|
|- style="vertical-align:top"
| Apply values from all sources to selected device
| If this option is enabled, clustered devices perform the same processes in the graphical view of the stage at the end of cues.
| not enabled
|
|}

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = DMXIn_remote_control_DMXC2
| TextBackwards = DMXIn remote control
| LinkForwards = Plugins_DMXC2
| TextForwards = Plugins
}}
[[de: Programmkonfiguration_DMXC2]]
[[Category: DMXControl 2]]

Joystick control DMXC2

2025-03-02T19:27:25Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Keyboard_control_DMXC2
| TextBackwards = Keyboard control
| LinkForwards = MIDI_remote_control_DMXC2
| TextForwards = MIDI remote control
}}
{{Start-LaTeX}}
==Overview==
The joystick control gives you the possibility of steering DMXControl's functions with a joystick or gamepad.
{{Picture_with_subtitle |DMXC2_Manual_joystick_control_activate.png|1|Window for the activation of the joystick control|center}}
{{Manual Box | en | Important | The activation window of the joystick control must remain opened in DMXControl in the versions up to and including 2.11 so that the joystick control works. This is no longer necessary as of version 2.12.
}}

==Description==
{{Picture_with_subtitle |DMXC2_Manual_joystick_control_configuration.png|2|Window for the configuration of the joystick control|center}}
In the joystick control you can assign commands to the axes X, Y and Z and maximum 12 buttons each of four joysticks to thus e.g. steer scanner or hoving heads directly. The operation of dimmer channels and assignment of arbitrary commands to the axes or buttons is also possible. This happens just like the attitude at the other controls/remote controls keyboard control, MIDI remote control, DMXIn remote control.

The number of supported joysticks is limited on 4 at the moment, there exists the possibility, however, of not a solid device but the respectively select device influencing graphcal view in this one. About the group choice a fast change of the device to be steered is possible.

Modes
*Relativ (the deflection of the axes determines only the direction and speed of the movement, not her exact position relative)
*Absolut (the position of the axes determines the position of the cone of light (let off the ninepin snaps back))
per axis are adjustable..
In the relative mode this one can in addition « Area deactivated » at (useful to a bad provision of the joystick) and be the acceleration adjusted to to the edge.

==Module commands==

* Modul: '''Joystick control'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Control
|style="width: 200px" rowspan="3"| The next command (channel) is applied to the joystick control.
|style="width: 100px"| On/Off
|style="width: 200px"| The joystick control will be turned on or off (T-Flag).
|- style="vertical-align:top;"
|style="width: 100px"| Activate
|style="width: 200px"| The joystick control will be activate.
|- style="vertical-align:top;"
|style="width: 100px"| Deactivate
|style="width: 200px"| The joystick control will be deactivate.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Keyboard_control_DMXC2
| TextBackwards = Keyboard control
| LinkForwards = MIDI_remote_control_DMXC2
| TextForwards = MIDI remote control
}}
[[de: Joysticksteuerung_DMXC2]]
[[Category: DMXControl 2]]

DDFCreator DMXC2

2025-03-02T19:26:37Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = DDF_DMXC2
| TextBackwards = DDF basic
| LinkForwards = Beamertool_Plugin_DMXC2
| TextForwards = Beamertool Plugin
}}
{{Start-LaTeX}}
=Die Arbeit mit dem DDFCreator=
{{Manual Box | en | Attention | Im DDFCreator sind nicht alle möglichen Tags und Attribute zur DDF-Erstellung enthalten. Diese müssen bei Bedarf von Hand nachgetragen werden. (minvalue; maxvalue; virtual)
}}
==Overview==

===DDFCreator installing and setup===

Nachdem Sie die Installationsdatei des DDFCreators von der Homepage heruntergeladen haben, müssen Sie diese starten. Installieren Sie den DDFCreator in ein Verzeichnis ihrer Wahl. Anschließend starten Sie den DDFCreator über das Startmenü.

Der Editor benötigt zum Arbeiten den Ordner, in dem die Bilddaten für die DDFs abgelegt werden. Dieser wird automatisch bei der Installation von DMXControl mitgeliefert. Sie können zwar auch ohne Angabe des Ordners arbeiten, werden dann aber im DDF kein Deviceimage angezeigt bekommen. Nach einem Klick auf OK, öffnet sich das Einstellungsfenster des DDFCreators, in dem Sie Einstellungen am Programm vornehmen können:
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Einstellungen.png|1|Konfigurationsfenster des DDFCreators|center}}

In diesem Fenster können Sie das Raster An und Aus schalten, die Rasterung einstellen, die Sprachdatei

auswählen und den Images Ordner angeben. Dieser befindet sich im Installationsverzeichnis von DMXControl im

Unterverzeichnis Devices. Also z.B.: C:\Programme\DMXControl\Devices\Images.

Sie können den Ordner eintippen, oder über einen Auswahldialog angeben. Der Ordnerauswahldialog öffnet sich, wenn Sie die Browse Taste rechts neben dem Textfeld drücken. Sie können das Einstellungsfenster auch für spätere Einstellungen vom Arbeitsfenster aus aufrufen. Die Einstellungen werden über die Programmlaufzeit hinaus gespeichert, sie müssen Sie also nur einmal vornehmen, wenn sich der Ordner nicht ändert.

Nachdem Sie den Ordner angegeben haben bestätigen Sie ihre Eingabe mit einem Klick auf OK.

Daraufhin wird das Arbeitsfenster des DDFCreators angezeigt.

==Beschreibung==

===Das DDFCreator Arbeitsfenster===
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Fenster.png|2|Hauptfenster des DDFCreators|center|600px}}

Die einzelnen Menüpunkte werden in den folgenden Unterkapiteln beschrieben.
In der Abbildung werden fertige DDFs für komplexere Geräte als Beispiel gezeigt.

===Menu Datei:===

In diesem Menu finden Sie Auswahlmöglichkeiten um:

* Ein neues DDF zu erstellen
* Ein vorhandenes DDF zu laden
* Ein geöffnetes DDF zu speichern
* Ein geöffnetes DDF zu schließen
* DDFCreator zu beenden

===Menu DDF Eigenschaften:===

In diesem Menü können Sie die Basiseigenschaften eines DDFs einstellen. Dazu gehören:

* Die DMX Kanäle des DDFs
* Die DDF Informationen; also Hersteller, Name des Gerätes sowie den Autor und Version des DDFs
* Das Layout des DDF-Menüs, also die Größe des Popup-Fensters.
* Die DDF Procedures, also erweiterte Funktionen.
* Ein Hilfetext, der z.B: die Einstellung des benötigten Gerätemodes erklärt.

Mehr zu den einzelnen Untermenus im Verlauf dieses Dokumentes.

===Menu DDFCreator Einstellungen:===

Hier öffnen Sie das Einstellungsfenster vom DDFCreator.

===Menu Online:===

Hier stehen ihnen folgende Möglichkeiten zur Verfügung:

* DDFCreator Online Update

===Menu ?===

Hier erhalten Sie Informationen über DDFCreator.

=Überblick zur DDF-Erstellung=

In diesem Beispiel wird die Bedienung des DDFCreators erläutert. Als Beispiel dient ein DDF für einen Scheinwerfer. Dieser verfügt über einen DMX Kanal und soll stufenlos gedimmt werden.

==Ein neues DDF erstellen==
Um ein neues DDF zu erstellen klicken Sie im Menu Datei auf Neues DDF erstellen.
Daraufhin wird ein neues DDF generiert, welches Ihnen auf dem Bildschirm angezeigt wird.

Das Arbeitsfenster sieht dann wie folgt aus:
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_DDF.png|3|Ansicht eines leeren DDFs|center|600px}}

Es enthält:

*Platzhalter für '''Gerätenamen und DMX-Adresse'''. Die Werte werden durch DMXControl eingetragen, wenn das DDF in DMXControl verwendet wird.
*Das '''Deviceimage'''. Stellt ein Bild in der Grafischen Ansicht von DMXControl dar. Dieses Bild kann geändert werden.
*Das '''DDF'''. Der Bereich stellt die Größe des DDFs in DMXControl dar.

'''Alle Bedienelemente im DDFCreator sind mit einer ToolTip Funktion ausgestattet. '''

Wenn Sie also einmal nicht wissen, wozu ein Knopf da ist, halten Sie den Mauszeiger kurz darüber und sie können die Informationen des ToolTips lesen.

(Teilweise werden die ToolTips unten Links im Arbeitsfenster angezeigt)

==Ein vorhandenes DDF bearbeiten==

Das Bearbeiten eines vorhandenen DDFs funktioniert genauso, wie das Erstellen eines neuen DDFs.

Klicken Sie auf Datei -> DDF Laden und wählen Sie das zu ladende DDF aus.

Das DDF wird geprüft und erscheint dann auf der Arbeitsoberfläche.

Danach können Sie es ganz normal bearbeiten.

==Kontextmenüs==

Jedes Steuerelement, dass sich im DDF befindet verfügt über ein Kontextmenü. Dieses rufen Sie auf, indem Sie mit der rechten Maustaste auf das Steuerelement klicken.

Dieses sieht am Beispiel des Deviceimages wie folgt aus:
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_ImagePopupMenue.png|4|Kontextmenü des DeviceIcons|center}}

*Mit der '''Rückgängig Funktion''' können Sie einen Schritt rückgängig machen. Dabei zeigt die Zahl in der Klammer die Anzahl der gespeicherten Schritte an.

*Mit '''Einfügen''' können Sie neue Steuerelemente einfügen.

*Mit '''Löschen''' können Sie ein vorhandenes Steuerelement löschen.

*Mit '''Ausschneiden, Kopieren und Einfügen''' können Sie Steuerelemente wie in anderen Programmen bearbeiten.

*Über '''Eigenschaften''' rufen Sie das Eigenschaftsfenster des aktuellen Steuerelements auf.

==Grafische Elemente definieren==

===Das Deviceimage ändern===

Um das Deviceimage oder dessen Position zu ändern müssen Sie als erstes das Eigenschaftsfenster des Deviceimage aufrufen. Dies geschieht entweder, indem Sie doppelt auf das Deviceimage klicken, oder über '''rechte Maustaste -> Eigenschaften'''. Sie können die Eigenschaftsfenster für andere Steuerelemente auf die gleiche Art und Weise aufrufen. DeviceName und DMX-Adresse haben allerdings kein Eigenschaftsfenster. Eine Abbildung des Deviceimage Fensters finden Sie [[DDF_Creator_DMXC2#Das_Eigenschaftsfenster_des_Deviceimages|hier]].

In diesem Fenster können Sie alle Einstellungen des Deviceimage vornehmen. Auf der rechten Seite können Sie die Position und die Größe des Deviceimage enstellen. Sollten keine Werte für '''height und width''' eingetragen sein, wird jeweils der Standardwert von 32 verwendet.

Im Linken Teil befindet sich das aktuelle Deviceimage. Mit einem Doppelklick auf dieses öffnet sich ein weiteres Fenster indem sich eine Auflistung aller im Images Ordner enthaltenen Bilder befindet. Sie können das Bild durch markieren auswählen. Dabei wird immer das zuletzt angeklickte Bild übernommen wenn Sie auf OK klicken.

In diesem Beispiel wollen wir einen blauen Scheinwerfer steuern. Die Position und die Größe des Images wollen wir nicht ändern. Markieren Sie '''BLUE.gif''' in der Bildauswahl und klicken Sie sowohl in der Bildauswahl als auch im Deviceimage Eigenschaftsfenster auf OK. Die Fenster schließen sich und sie sehen wie das ausgewählte Deviceimage übernommen wurde.

===Ein Steuerelement einfügen===

Um den Scheinwerfer nun dimmen zu können fügen wir einen Schieberegler, auch Slider genannt ein. Dazu klicken Sie rechts auf eine freie Stelle im DDF und im Kontextmenü auf '''Einfügen -> Slider'''.

Daraufhin wird an der Stelle an der Sie rechts geklickt haben ein neuer Slider eingefügt.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_PopupMenue.png|5|Kontextmenü mit verschiedenen Optionen|center}}

Ihr DDF sollte nun ungefähr wiefolgt dargestellt werden:
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Sliderhinzugefuegt.png|6|DDF mit einem hinzugefügten Slider|center}}

===Ein Steuerelement verschieben===

Wahrscheinlich sitzt der Slider nicht genau dort wo er sitzen soll, deshalb verschieben wir ihn. Das Verschieben funktioniert bei allen anderen Steuerelementen genau gleich. Klicken Sie auf das Steuerelement. Es wird von einem Rahmen umzogen. Ziehen Sie das Steuerelement mit gedrückter Maustaste an die gewünschte Stelle.

Nachdem Sie den Slider an die richtige Stelle geschoben haben können Sie ihn noch in seiner Größe ändern.
===Die Größe eines Steuerelementes ändern===
Hierbei gibt es die gleichen Möglichkeiten wie beim Verschieben. Das Skalieren funktioniert bei allen Steuerelementen gleich.

Die Steuerelemente Options und Label können aber nicht skaliert werden.

===Ein Steuerelement löschen===

Falls Sie ein Steuerelement löschen wollten, gibt es zwei Möglichkeiten.

*'''Per Maus löschen''': Dazu klicken Sie rechts auf das Steuerelement und im Kontext Menu auf Löschen. Anschließend werden Sie gefragt, ob Sie wirklich löschen wollen. Bestätigen Sie die Frage mit JA. Das Steuerelement wird gelöscht.
*'''Per Tastatur löschen''': Klicken Sie dazu auf das Steuerelement, sodass er markiert ist. Drücken Sie nun auf der Tastatur die ENTF Taste. Das Steuerelement ist gelöscht.

===Die Größe des Layouts ändern===

Da wir nur den Slider als Bedienelement benötigen, ist das DDF viel zu groß. Gehen Sie über das Menu '''DDF-Eigenschaften''' in das Layout Fenster. Dort können Sie die Größe beliebig einstellen. Per druck auf OK werden die Einstellungen übernommen.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Menue-Layout.png|7|Menüeintrag DDF Eigenschaften|center}}

{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Layout.png|8|Einstellungen für das DDF-Layout|center}}

Alternativ können Sie auch einfach den Rahmen, der um das DDF gezogen ist mit der Maus anklicken und skalieren.

Nachdem Sie das alles gemacht haben, ist die Darstellung des DDFs schon fertig. Als nächstes müssen wir uns um die DMX-Eigenschaften kümmern.

== DMX Kanäle festlegen ==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Kanaele.png|9|Übersicht über die vom DDF verwendeten Kanäle|center|600px}}

Jedes DMX Gerät hat eine bestimmte Anzahl von belegten DMX Kanälen. Diese müssen in das DDF eingetragen werden. Der Scheinwerfer in diesem Beispiel hat nur einen Kanal. Hochwertige Geräte können 16 oder mehr Kanäle haben.

Über das Menü DDF Eigenschaften kommen Sie in das Untermenu DMX Kanäle (siehe Abbildung 9). Öffnen Sie dieses Fenster. Wie Sie sehen ist bereits ein DMX Kanal angelegt. Für dieses Beispiel benötigen wir keine zusätzlichen Kanäle. Falls Sie für ein anderes zusätzliche DDF DMX-Kanäle anlegen müssen, klicken Sie auf '''Neu''' und legen dadurch neue Kanäle an. Klicken Sie doppelt in die Spalten und tragen Sie ihre Werte ein. '''Achten Sie darauf, dass Sie die Kanäle in der richtigen Reihenfolge eintragen. Dabei verschiebt sich alles um eine Zahl.''' Das bedeutet, der erste Kanal des Gerätes ist im DDF als Kanal 0 vorgegeben, der siebte ist demnach Kanal 6, usw. DDFCreator kontrolliert beim Druck auf OK die eingetragenen Werte auf ihre Korrektheit, wobei ein korrekter Wert natürlich nicht immer für das entsprechende DDF richtig ist. Sollten Sie aus versehen einen falschen Wert eingetragen haben, werden Sie bei Druck auf OK, auf den Fehler hingewiesen, und die fehlerhafte Zelle wird markiert. Wenn Sie einen Kanal löschen wollen, markieren Sie die Kanalnummer in der '''channel''' Spalte und drücken Sie auf Löschen. Dabei werden die Kanalnummern automatisch neu durchnummeriert.

=== TYPE Konfiguration ===

Unter "type" kann man dem Kanal bestimmte Funtionen zuordnen! '''Alle "types" müssen klein geschrieben werden!!!''' 

*1. pan ---> Pankanal
*2. tilt --->  Tiltkanal
*3. panfine ---> 2ter Pankanal, erforderlich bei Geräten mit 16bit.
*4. tiltfine ---> 2ter Tiltkanal, erforderlich bei Geräten mit 16bit.
*5. gobo ---> Gobokanal, erforderlich bei globalen Gobolisten.
*6. color ---> Colorkanal, erforderlich bei globalen Colorlisten.
*7. dimmer ---> Dimmer-, Shutter-, ON/OFF-Kanal. mit Hilfe dieses Kanals ist es möglich die "blackout-Funktion" in DMXC zu nutzen.
*8. r ---> Rot - Wichtig für "HAL" ab 2.11 (darstellung der Farbe in der Grafischen Bühnenansicht)
*9. g ---> Grün - Wichtig für "HAL" ab 2.11 (darstellung der Farbe in der Grafischen Bühnenansicht)
*10. b ---> Blau - Wichtig für "HAL" ab 2.11 (darstellung der Farbe in der Grafischen Bühnenansicht)

Folgende types machen Sinn haben aber bis jetzt keine zugeordnete Funktion
# w ---> Weiß
# a ---> Amber
# c ---> Cyan
# m ---> Magenta
# y ---> Gelb

Da kein weiterer Kanal als der bereits vorhandene benötigt wird, schliessen wir das Fenster.

==Informationen über das DDF eintragen==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_DDFInformation.png|10|Einstellungsfenster für das DDF|center}}

Als nächstes sollten Sie im Informationsbereich des DDFs Daten über den Autor und das Gerät hinterlegen. Dazu öffnen Sie bitte das Fenster '''DDF Informationen''' (siehe Abbildung 10). Im darauffolgenden Fenster können Sie alle Informationen eingeben. Dabei ist '''name''' der Name des Gerätes, author sind Sie, und '''vendor''' ist der Hersteller des Gerätes.

Als nächstes muss der Slider eingestellt werden. Öffnen Sie dazu wie unter 5.3 beschrieben das Eigenschaftsfenster des Sliders (per Doppelklick oder über Kontext Menu). Es öffnet sich das Eigenschaftsfenster (siehe Abbildung 12).

Um das DDF fertig zu machen, müssen wir nun dem Slider noch einen Kanal zuweisen. Dazu tragen Sie unter '''channel''' eine 0 ein, weil der Slider sich auf Kanal 0 beziehen soll. Danach noch den '''endvalue''' auf 255 anheben und fertig. Nachdem Sie auf OK gedrückt haben, ist das DDF fertig. Über '''Datei -> DDF Speichern''' können Sie das DDF in einem Ordner ihrer Wahl speichern.

Das fertige DDF sollte ungefähr so aussehen:
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_DDFFertig.png|11|Fertiges DDF|center}}

=Die Eigenschaftsfenster=

Jedes Steuerelement (bis auf DeviceName und DMX-Adresse) verfügen über ein Eigenschaftsfenster. In diesem Fenster können alle Eigenschaften des Elementes eingestellt werden. Dabei verfügt DDFCreator über eine Fehlererkennung, welche die meisten Fehler findet und durch eine Meldung anzeigt. Im Folgenden werden die Eigenschaftsfenster der einzelnen Steuerelemente dargestellt und auf Besonderheiten hingewiesen.

==Allgemeine Eigenschaften==

Die Eigenschaften top, left, height und width beschreiben die Positionierung und Größe des Elementes.
Alle Bedienelemente in DDFCreator sind mit einer ToolTip Funktion ausgestattet.
Wenn Sie also einmal nicht wissen, wozu ein Attribut da ist, halten Sie den Mauszeiger kurz darüber, und sie können die Informationen des ToolTips lesen.

==Das Eigenschaftsfenster des Sliders==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_SliderEigenschaften.png|12|Eigenschaften des Sliders|center}}

Das Eigenschaftsfenster ist sehr einfach aufgebaut. Für jede Eigenschaft des Sliders gibt es ein Textfeld, in das Sie Zahlenwerte oder Zeichenketten (Strings) eintragen können.

==Das Eigenschaftsfenster des Commands==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_CommandEigenschaften.png|13|Eigenschaften des Commands|center}}

Im Commandfenster können Sie wie beim Slider die gewünschten Werte einfach eintragen. Eine Besonderheit ist, dass Sie die Sequenz Felder auch mit einem Wert aus der in DDFCreator enthaltenen Bibliothek füllen können. Klicken Sie dazu rechts auf das Sequenzfeld, und dann auf Code aus der Bibliothek einfügen oder auf den Button neben dem Feld. Mehr über die Codebibliothek von DDFCreator unter 6.2. Zusätzlich kann der Button noch gefärbt und mit einem Icon versehen werden. Um die Farbe oder ein Icon auszuwählen einfach doppelt auf die entsprechende Fläche klicken. Zum entfernen der Farbe bzw. des Icons einfach doppelt Rechts auf die Fläche klicken.

==Das Eigenschaftsfenster des Deviceimages==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_ImageEigenschaften.png|14|Eigenschaften des DeviceImages|center}}

In diesem Fenster können Sie das Deviceimage auswählen. Um das Bild zu ändern, einfach doppelt darauf klicken und im folgenden Fenster das neue Bild auswählen. Im Auswahlfenster werden alle GIFs angezeigt, die im Images Ordner vorhanden sind. Sie können also einfach neue GIFs mit den Maßen 32 x 32 Pixel in den Ordner kopieren, und diese werden von DDFCreator beim nächsten Aufruf automatisch erkannt.

==Das Eigenschaftsfenster des OnOff==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_OnOffEigenschaften.png|15|Eigenschaften des OnOff|center}}

Das OnOff Fenster ist sehr intuitiv gehalten. Sequenzen können über die Bibliothek eingefügt werden, dazu rechts auf das Textfeld klicken oder den Button benutzen. Mehr über die Codebibliothek von DDFCreator unter 6.2. Beim OnOff ist es nicht erlaubt, dass sowohl in on- und offvalue etwas steht, sowie in on und offsequence. Deshalb werden die jeweils anderen Textfelder deaktiviert, sobald in die anderen etwas eingetragen wird. Das Hinzufügen und Entfernen von Farbe und Icon ist identisch zum Command.

==Das Eigenschaftsfenster des Dropdown==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_DropdownEigenschaften.png|16|Eigenschaften des Dropdowns|center}}

In der Liste auf der linken Seite können Sie die einzelnen Items des Dropdowns mit den dazugehörigen Werten eintragen. Über die Taste Neu können sie neue Items anlegen. Klicken Sie auf einen Namen oder einen Wert um diesen zu ändern. Mit Löschen können sie einen Eintrag aus der Liste löschen. Über Hoch und Runter können Sie die Reihenfolge der Einträge verändern. Jedes Item kann mit einer Farbe oder einem Icon versehen werden. Dies funktioniert analog zum Command. Sollte wie in diesem Beispiel eine Farbe und ein Icon vergeben sein, wird nur das Icon angezeigt.

==Das Eigenschaftsfenster des Label==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_LabelEigenschaften.png|17|Eigenschaften des Labels|center}}

Das Eigenschaftsfenster des Labels ist sehr übersichtlich. Für jede Eigenschaft gibt es ein Textfeld zum Eintragen. Die Breite des Labels wird automatisch durch die Textlänge ermittelt.

==Das Eigenschaftsfenster des Options==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_OptionsEigenschaften.png|18|Eigenschaften der Options|center}}

Das Options Fenster ist zweigeteilt, in einen allgemeinen Bereich, und in einen spezifischen Bereich, weil das Options aus zwei Teilen besteht:

*einem Container in dem sich alle Radiobuttons befinden, und
*die Radiobuttons selber.

Deshalb ist der linke Teil auch immer der gleiche, egal auf welchen Radiobutton geklickt wurde, da sich alle auf den gleichen Container beziehen. Der rechte Teil hingegen beschreibt den Radiobutton, der gerade ausgewählt wurde. Die Position des spezifischen Buttons ist relativ zum Container. Das bedeutet, die Koordinaten des Buttons im DDF wären in diesem Beispiel top=173 und Left=108. Mehr zu der Besonderheit der Options und deren Bearbeitung unter 5 .

==Das Eigenschaftsfenster des Position==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_PositionEigenschaften.png|19|Eigenschaften des Position-Elements|center}}

Das Eigenschaftsfenster des Positions ist selbsterklärend.

''Hinweis:'' Das Position-Element ist automatisch an die Kanäle Pan und Tilt gekoppelt. Daher muß hier kein "channel" zugewiesen werden.

==Das Eigenschaftsfenster des Colorpickers==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_ColorpickerEigenschaften.png|20|Eigenschaften des Colorpickers|center}}

Das Colorpicker Steuerelement ermöglicht es über drei DMX Kanäle bei RGB Geräten jede beliebige Farbe einzustellen. Diese drei Kanäle werden in den Feldern channel 1 – 3 hinterlegt. Mode kann entweder den Wert „rgb“ oder „cmy“ haben, je nach dem ob das Gerät RGB oder CMY Farbmischung hat. Die Eingabefelder für Position und Größe sind in ihrer Funktion identisch mit den anderen Controls.

==Das Line Steuerelement==

Das Line Element wird als Linie angezeigt, und kann ganz normal skaliert werden. Ein Doppelklick auf die Linie dreht diese um 90°.

=Was Sie über das Bearbeiten von Options Elementen wissen sollten=

Options Elemente verhalten sich anders als andere Elemente. Deshalb wird in diesem Teil besonders auf die spezifischen Eigenschaften eingegangen. Dabei bezeichnet das Options das gesamte Element, mit allen Symbolen und dem Container. Ein Option ist ein einzelnes Element im Container.

==Das Einfügen von Options==

Options Elemente bestehen immer aus mehr als einem Symbol. Deshalb wird mit dem Erstellen des ersten Elementes immer ein Container mit angelegt. In diesen werden die Elemente eingefügt. In Abbildung 24 ist gezeigt, wie ein Option neu eingefügt wurde. Um nun ein weiteres Option zu diesem hinzuzufügen, klicken Sie rechts auf das erstellte und auf Einfügen -> Options, daraufhin wird zu dem einen, ein zweites hinzugefügt. Für ein drittes und viertes usw. funktioniert es genau gleich. Die Containergröße passt sich automatisch an die Anzahl und die Position der Option an.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Options1.png|21|Ein Options-Steuerelement|center}}
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Options2.png|22|Options mit zwei Elementen|center}}

Wenn sie anstelle von dem erstellten Options auf eine leere Stelle im DDF klicken, und dort ein Options einfügen, erstellen Sie ein zweites komplett unabhängiges (siehe Abbildung 26).
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Options3.png|23|Ansicht mit zwei Options|center}}

==Die Sache mit dem Container==

Das Options Element besteht aus einem Container und den einzelnen Option Elementen.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Options4.png|24|Options mit mehreren Elementen|center}}

Der Container ist normalerweise unsichtbar, aber nicht transparent, das bedeutet, dass andere Steuerelemente durch den Container verdeckt werden. Deshalb ist es wichtig darauf zu achten, dass der Container nur so klein wie möglich ist. In Abbildung 28 ist zu sehen, das obwohl nur drei Option Elemente enthalten sind, der Container eine große Fläche einnimmt.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Options5.png|25|Ein Options-Menü verdeckt ein anderes|center}}

In Abbildung 25 sehen sie, wie das Label durch den Container verdeckt wird. In DMXControl ist das genauso.

==Options bearbeiten==

Da ein Options Element aus einem Container und den einzelnen Option Elementen besteht, gibt es zwei Möglichkeiten ein Options zu bearbeiten.

* Der gesamte Container mit allen Elementen wird bearbeitet
* Ein einzelnes Option wird bearbeitet.

Da Option Elemente sich nicht skalieren lassen, und sich die Größe des Containers automatisch auf den kleinst möglichen Wert einstellt, ist ein Skalieren nicht möglich. Daher stehen nur Verschieben und Löschen als Bearbeitungsmöglichkeiten zur Verfügung.

Normalerweise markieren Sie beim Anklicken eines einzelnen Option den gesamten Container. Um nun ein einzelnes Option im Container anzuwählen, drücken sie die # Taste. In der Statusleiste von DDFCreator wird ihnen angezeigt, dass nun EINZELNES OPTION BEARBEITEN AKTIVIERT ist.
Mit einem erneuten Druck auf # wechseln Sie wieder in den globalen Modus. Die Aktivierung der # Option hat keinen Einfluss auf die Bearbeitung von anderen Steuerelementen.

===Das gesamte Options verschieben===
Das ist die Standardeinstellung. Klicken sie auf ein beliebiges Option, wird der komplette Container markiert wird. Verschieben sie nun wie in 3.4.3 beschrieben das Element. Sie werden sehen, dass sich der gesamte Container mit allen enthaltenen Option Elementen verschiebt.

===Ein einzelnes Option verschieben===
Drücken Sie # um den Bearbeitungsmodus umzuschalten. Markieren Sie wie gewohnt das zu bearbeitende Element, und verschieben Sie es wie in 3.4.3 beschrieben. Der Container passt sich automatisch an.

===Das gesamte Options löschen===
Markieren Sie den gesamten Container, falls erforderlich vorher # drücken, um wieder in den normalen Bearbeitungsmodus zu schalten. Löschen Sie das Element wie unter 3.4.5 beschrieben.

===Ein einzelnes Option löschen===
Schalten Sie per # den Bearbeitungsmodus um. Markieren Sie das zu löschende Option Element. Löschen Sie es wie in 3.4.5 beschrieben. Sollte das Option Element das letzte im Container enthaltene Element sein wird der Container automatisch mitgelöscht.

=Code und Initsequence im DDF eintragen=

==Überblick==

Um komplexere Funktionen im DDF zu realisieren, besteht die Möglichkeit sog. Procedures zu programmieren, die beim Verändern eines DMX Kanals oder eines Steuerelementes aufgerufen werden. Eine Beschreibung der Programmiersprache finden Sie im DDF-Tutorial auf der Homepage.
Um diese Procedures im Editor zu hinterlegen, gibt es das DDF Procedures Fenster. In diesem Fenster kann auch die Initsequence eingegeben werden. Öffnen Sie das Fenster über DDF-Eigenschaften -> DDF Procedures.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_Procedures.png|26|Ansicht des Proceduren-Fensters|center|600px}}

Auf der linken Seite sehen Sie eine Liste der vorhandenen Procedures. Mit Neu fügen Sie ein neues Procedure hinzu. Mit Löschen entfernen Sie ein vorhandenes. Auf der rechten Seite können Sie im Codefenster den Procedurecode eintragen, oder über Rechtsklick auf das Fenster aus der Codebibliothek holen. Wenn Sie Änderungen im Code vornehmen, werden diese zwischen gespeichert. Sie können also ein Procedure bearbeiten und dann ein anderes auswählen und dieses ändern. Erst wenn Sie auf OK drücken werden die Änderungen für alle Procedures ins DDF geschrieben. Genauso ist es mit der Initsequence. Sie können diese Manuell eintragen oder per Rechtsklick über die Bibliothek holen. Mehr über die Bibliothek in 6.2.

==Die Codebibliothek==
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_CodeBibliothek.png|27|Die Code-Bibliothek|center|600px}}

Ein sehr nützliches Feature in DDFCreator ist eine vorhandene leicht erweiterbare Codebibliothek. Diese ermöglicht es Sequences und Procedures auf Abruf schnell einzufügen, und sich so die Programmierung und Fehler zu vermeiden. Die Elemente aus der Bibliothek sind allgemeine Codebausteine, die auf jeden Fall noch an das entsprechende DDF angepasst werden müssen. Die Bibliothek enthält verschiedenen Procedures, die oft in ähnlicher Art und Weise verwendet werden, und von daher leicht anzupassen sind. Genauso ermöglicht es die Bibliothek eigenen Code einzuspeichern, um diesen zukünftig bei DDFs zu nutzen.

===Die Codebibliothek aufrufen===

Sie können die Codebibliothek von jedem Textfeld aus aufrufen, in das Sie eine Sequence oder ein Procedure einfügen können, indem Sie rechts auf das Feld klicken und dann im folgenden Kontextmenu auf '''Code aus der Bibliotek einfügen'''.

===Eigene Bausteine einfügen===

Die Bausteine werden in der Datei code.xcq im DDFCreator Verzeichnis gespeichert. Diese Datei kann von ihnen nach belieben geändert werden, um neue Codebausteine hinzuzufügen. Die Bibliothek unterstützt mehrsprachige Kommentare. Dazu wird einfach für jede Sprache ein eigener <description> Block angelegt. Das Attribut '''lang''' entscheidet welche Sprache es ist. Dabei ist der Aufbau wie folgt:

<library>
<procedure name=“Hier steht der Name des Procedures“>
<code>
Hier kommt der Code rein, auch Mehrzeilig
</code>
<description lang=“german“>
Hier kommt der Kommentar oder die Beschreibung des Bausteins rein
</description>
</procedure>
<sequence name=“Hier steht der Name der Sequenz“>
<code>
Hier kommt der Code rein, auch Mehrzeilig
</code>
<description lang=“german“>
Hier kommt der Kommentar oder die Beschreibung des Bausteins rein
</description>
<description lang=“english“>
Here is the English description stored.
</description>
</sequence>
</library>

Ein Baustein besteht immer aus einem äußeren Tag (procedure oder sequence) der beschreibt, ob es sich bei dem Baustein um ein Procedure oder um eine Sequence handelt. Der äußere Tag enthält dann zwei innere Tags, einen für den Code, den anderen für die Beschreibung. Die Reihenfolge der Bausteine ist egal, DDFCreator wählt je nachdem, ob ein Procedure oder eine Sequence eingefügt werden soll die entsprechenden Elemente aus. Natürlich muss erst ein Baustein abgeschlossen sein, bevor der nächste anfangen darf, wie folgendes '''falsche Beispiel''' zeigt:

<library>
<procedure name=“Hier steht der Name des Procedures“>
<code>
Hier kommt der Code rein, auch Mehrzeilig
</code>
<sequence name=“Hier steht der Name der Sequenz“>
<code>
Hier kommt der Code rein, auch Mehrzeilig
</code>
<description lang=“german“>
Hier kommt der Kommentar oder die Beschreibung des Bausteins rein
</description>
</sequence>
<description lang=“german“>
Hier kommt der Kommentar oder die Beschreibung des Bausteins rein
</description>
</procedure>
</library>

Nach einer Änderung von code.xcq steht nach einem Neustart von DDFCreator der Baustein ganz normal zur Verfügung. Achten Sie darauf, vor einer Aktualisierung von DDFCreator ihre code.xcq zu sichern, da diese sonst überschrieben werden kann.

=Online Funktionen=

==DDF-Upload Funktion==

Mit dieser Funktion wird das aktuell angewählte DDF an den DMXControl Server geschickt. Es wird direkt auf die Homepage geladen und steht der Nutzergemeinde sofort zur Verfügung. Sollte ein DDF von ihrem Gerät bereits verfügbar sein, werden Sie darauf hingewiesen.

==Online Update Funktion==

Seit Version 1.1 steht eine Online Update Funktion zur Verfügung. Mit dieser Funktion aktualisiert sich DDFCreator automatisch über das Internet. Wenn Sie auf Online Update klicken, testet DDF-Editor die Verbindung zum DMXControl Server. Danach werden die lokalen Dateien mit denen auf dem Server verglichen. Sollten neue Dateien gefunden worden sein, wird ihnen der Download angeboten. Mit den Haken in den Checkboxen vor den Dateinamen können Sie anwählen, welche Dateien sie herunterladen wollen. Die lokalen Dateien werden ohne weiteres Nachfragen überschrieben. Seien sie also vorsichtig, wenn Sie der Codebibliothek eigenen Code hinzugefügt haben, da dieser beim Updaten überschrieben wird. Sichern Sie ihre eigene Code Datei deshalb vor dem Update. In Version 1.2 von DDFCreator ist eine Merge Funktion geplant, welche die neue Code Bibliothek und die eigene auf der Festplatte vereint, dadurch entfällt das sichern.

=Sprache=

==Die Sprachdateien==

Im Unterordner Language von DDFCreator gibt es Sprachdateien für DDFCreator, für jede Sprache eine. Dabei ist der Dateiname gleichzeitig die Sprache. Falls Sie uns helfen möchten und den Editor in eine neue Sprache übersetzen wollen gehen Sie wie folgt vor.

*Kopieren Sie die Ausgangsdatei (also z.B. german.xcl) und benennen Sie die neue Datei in den Namen der Sprache (z.B. spanisch.xcl)

*Öffnen Sie die neue Datei. Die Sprachdatei selber ist wieder ein XML File. Zwischen zwei Tags steht immer der Text. Übersetzten Sie einfach alle angegebenen Strings in die neue Sprache. Ändern Sie den Namen der Sprache ganz oben im File ab. Speichern Sie die Datei.

*Nun können Sie die neue Sprache in DDFCreator einstellen. Nach einem Neustart arbeitet DDFCreator mit der neuen Spracheinstellung.

*Bitte schicken Sie uns die neue Sprachdatei, damit wir diese der ganzen Nutzergemeinde zugänglich machen können.

=Tipps/Support Funktionen=

==Die Tastaturkürzel==

===Taste #===

# Schaltet den Bearbeitungsmodus für das Options Element um. Mit dieser Taste bestimmen Sie, ob Sie das gesamte Options oder nur ein einzelnes Option bearbeiten wollen.

===STRG + Z===

Mit dieser Tastenkombination machen Sie den letzten Schritt rückgängig. Dies wird über die Rückgängigfunktion von DDFCreator durchgeführt. Mehr über die Rückgängigfunktion in 3.8.

===Taste Umschalt, auch Shift oder Großschreibtaste===

Mit dieser Taste aktivieren Sie die Mehrfachauswahl, Sie können nun wie im Windows Explorer mehrere Elemente markieren und diese gleichzeitig verschieben, löschen, ausschneiden und kopieren.

===Taste ENTF===

Über die ENTF Taste können Sie das markierte Element, bzw. die markierten Elemente löschen.

===STRG + C===

Kopiert die markierten Steuerelemente in die Zwischenablage.

===STRG + X===

Kopiert die markierten Steuerelemente in die Zwischenablage, und entfernt diese aus dem DDF.

===STRG + V===

Fügt kopierte oder ausgeschnittene Steuerelemente wieder ein.

==Die Rückgängig Funktion==

Die Rückgängig Funktion erlaubt es ihnen eine Aktion rückgängig zu machen. Aktionen sind:

*Ein neues Steuerelement erstellen
*Ein vorhandenes Steuerelement verschieben (auch mehrere)
*Ein Steuerelement skalieren
*Ein Steuerelement löschen

Nicht rückgängig gemacht werden Änderungen die über die Eigenschaftsfenster vorgenommen wurden. Wenn Sie also die Kanalnummer für einen Slider über das Eigenschaftsfenster ändern wird dies durch die Rückgängig Funktion nicht wieder zurückgesetzt.

==Die automatische DDF Überprüfung==

Wenn Sie ein neues DDF laden wird in einem Ladebalken angezeigt, dass das DDF überprüft wird. In diesem Balken erhalten Sie Informationen, welcher Knoten gerade überprüft wird. Nach der Überprüfung wird ihnen ein Fenster angezeigt, in welchem die gefundenen Fehler dargestellt werden. Hier können Sie auswählen, welche Fehler behoben werden sollen.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_DDFPruefen.png|28|Prüfung des DDFs auf Fehler|center}}

Dabei werden in einer Baumansicht die Knoten angezeigt, und welche Attribute fehlerhaft sind. Sollten keine Attribute angezeigt werden, ist der Knoten selber falsch. Im rechten Bereich wird der Fehler beschrieben, und der XML Code angezeigt. Im unteren Bereich kann ausgewählt werden, wie die Reparatur durchgeführt werden soll.
{{Picture_with_subtitle |DMXC2_Manual_DDFCreator_DDFFehler.png|29|Fehler in DDF gefunden|center}}

==Links and references==
<references/>

Tutorial: [[DDF mit DDFCreator erzeugen]]

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = DDF_DMXC2
| TextBackwards = DDF basic
| LinkForwards = Beamertool_Plugin_DMXC2
| TextForwards = Beamertool Plugin
}}
[[de: DDF_Creator_DMXC2]]
[[Category: DMXControl 2]]

Textbook DMXC2

2025-03-02T19:26:07Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Timecode_player_DMXC2
| TextBackwards = Timecode player
| LinkForwards = Command_line_DMXC2
| TextForwards = Command line
}}
{{Start-LaTeX}}
==Overview==
At theater and musical events it is imperative that light atmospheres and effects are activated exactly on a particular keyword. For this, the script module has been integrated into DMXControl. With this you can control lights, movement scenes and also sound effects (such as thunder, barking of dogs or similar) as well as start commands at the precise moment of a cue in a theater or musical piece. The field of application of the script module doesn't remain restricted to theater and musicals because this module is suitable for other types of production with synchronised actions, such as choral or carnival productions.

{{Picture_with_subtitle |DMXC2_Manual_textbook_window.png|1|The textbook module|center}}

==Description==

The window of the textbook module is divided into three areas:

* the text field area with text editor functions in the upper part of the module
* the control area with buttons for the control of the performance in the middle part of the module
* the direction area with a cue overview and cue processing functions in the lower part of the module
 

===Text field area===

The text field area contains a text editor with which you can scroll through the textbook (described) as a script without influencing the cue timing. In addition, you can add simple customizations with the editor, such as changing the color or the size of the script text. The editor is sufficient for underlining keywords or placing notes to oneself in different colors. However, the editor of the module isn't designed for making major changes to the script. A third-party dedicated text editor is more suitable for this purpose.
 

To open script files in DMXControl, they must be formatted using '''Rich Text Format'''<ref>Wikipedia: http://de.wikipedia.org/wiki/Rich_Text_Format</ref> (file extension '''.rtf'''). In the text field the text not too extensively becomes, if the script should be divided up into several parts, preferably every break so that a subdivision. The part script arisen so can correspondingly, explained still more exactly in the article below, options display be loaded separately in the breaks about one. In addition, the text structure of the script isn't provided in the script module. This means you can adapt the script to her requirements individually and don't have to adapt themselves to a DMXControl-specific text structure.

A small progress bar is under the text field. This shows the current Fortschitt in the script using which one can assess approximately how long the current piece already is on and how much text follows still until the next break or the end of the play.

So that DMXControl recognizes at which ones scenes corresponding to places in the script are, scene references are made with references to the corresponding scenes. These reprimands are always inserted by DMXControl at the beginning of a new line in the Textskript. One leaves one line each the best above and below the reference freely so that the script remains as open as possible.

{{Manual Box | en | Important | The string '''# # #''' mustn't happen in the normal text of the script since DMXControl uses this character string as a marking for the prepared reference entries. If this character string is used, it can come to serious faults!}}

===Cue references===
Cue references are stressed by DMXControl so that these are readable better. You have format always following:

### <Cue-ID> - <Cue name> ### <Director comment>

The cue ID is a four-digit reference number produced by DMXControl automatically. This number is needed so that DMXControl finds the right cue in the internal database for the cue reference. The scene name corresponds to the cue name allocated in DMXControl and can be chosen individually at the construction of the cue. Here it should be taken care of on this to use apt names so that at a search the corresponding cues can be found fast again. Additional information, like the way of the light atmosphere, can stand as a management comment at the end of a cue reference. E.g. a cue reference can look as follows:

###0002 – thunder storm ### thunder(audio)

All cue types like ''simple cue'' or ''audio cue'' supported by DMXControl can be used in the script. Since the made cue references are also only character strings, these can be processed with an external editor exactly like the remaining text of the script. DMXControl leads therefore a consistency check through, whether at every start all scenes indicated in the script are available in the internal database. If a cue was found in the database, then a green rhombus is shown to the corresponding scene besides the name in the management area. If a scene entry doesn't refer to any existing scene, then the rhombus is colored red besides the name.

{{Manual Box | en | Attention | It should absolutely be taken care of on this that the scene references aren't changed when working with an external text editor since scene references can be lost through this and it can come to inconsistencies}}

==Controls==

===Control area===

{{Picture_with_subtitle |DMXC2_Manual_textbook_control_area_normal.png|2|The control area|center}}
Four button are in the control area. This one is the greatest of them « GO » button. He starts the select cue and selects the following cue automatically. So the will on by clicking repeatedly « GO » button the row after all cues started in the script.

Two navigation buttons are on the left besides it « Prev » and « Next ». With them one can navigate between the cues without executing her. So one can skip single cue references if a keyword was missed and the next scene shall be selected now.

On the right besides the « GO » button this one is « AutoScroll » button. With this the AutoScroll function of the script can be activated or deactivated. At the AutoScroll function a red harvest line is shown and the harvest line and the script always scrolls the script up to the next scene reference. The scrolling up speed is derived from the indicated delta time to the next scene in the management area, as a rule, through what a manual customization is required.

{{Picture_with_subtitle |DMXC2_Manual_textbook_control_area_search.png|3|The control area in search mode|center}}

The control block also contains a small search function since DMXControl's version 2.11. With the help of the key combination ''ctrl' '+' 'f'' the search function is activated. Sie durchsucht das Skript bei einem Klick auf « Next hit » as of the current cursor position after the entered search text. If the search text is found in the script, then the script jumps to this position and marks the corresponding passage. The left button in the search view closes the search function and shows the control view again.

===Direction area===

The management area contains a script administration in the upper section. With the drop down menu the different Teilskripte can be selected and can with the button « Managing » being laid out, copied, renamed or deleted. With « Open » the fitting text file can be opened to every part script.

A list is in the lower part with all scenes contained in the script which are sorted after her appearance in the script. In this list different parameters get shown every single scene, the partial ones by clicking slowly, twice (no-one double-click) you can process:

{{Picture_with_subtitle |DMXC2_Manual_textbook_cue_list.png|4|Part from the cue list of the text book|center}}

{| class="wikitable centered"
|- style="vertical-align:top;"
!
! Function
! Description
! Workable
|- style="vertical-align:top;"
|style="width: 10px"| 1
|style="width: 100px"| Cue aktiv
|style="width: 500px"| Here you can select, whether the scene is taken into account or left out in the expiry
|style="width: 100px"| Yes
|- style="vertical-align:top;"
|style="width: 10px"| 2
|style="width: 100px"| green / red diamond
|style="width: 500px"| If cue reference and cue agree on the database, the diamond is green, otherwise red
|style="width: 100px"| No
|- style="vertical-align:top;"
|style="width: 10px"| 3
|style="width: 100px"| Name
|style="width: 500px"| Name of the corresponding cue entry
|style="width: 100px"| Yes
|- style="vertical-align:top;"
|style="width: 10px"| 4
|style="width: 100px"| Line
|style="width: 500px"| The line number is shown to the cue reference here
|style="width: 100px"| No
|- style="vertical-align:top;"
|style="width: 10px"| 5
|style="width: 100px"| Delta-T
|style="width: 500px"| Time between the last and the current cue. The value indicated here has influence on the scrolling up speed of the AutoScroll function
|style="width: 100px"| Yes
|- style="vertical-align:top;"
|style="width: 10px"| 6
|style="width: 100px"| catchword
|style="width: 500px"| As small help a passage at which the cue shall be started can be indicated here
|style="width: 100px"| Yes
|- style="vertical-align:top;"
|style="width: 10px"| 7
|style="width: 100px"| Comment
|style="width: 500px"| A note can be indicated with additional information about the cue which appears in the script at the end of the corresponding cue reference here
|style="width: 100px"| Yes
|- style="vertical-align:top;"
|style="width: 10px"| 8
|style="width: 100px"| Fade time
|style="width: 500px"| The fade time determines how long the fade of the last cue shall last to the current cue
|style="width: 100px"| Yes
|}

 

Single cue entries are on the left of the cue list these confessed button for making, working and deleting from other modules. You find details for her operation control center DMXC2 in the article to the [[Control_center_DMXC2|Control center]].
The cue progress bar is below the cue list. This shows graphically how long the current cue is already displayed in proportion to her one fade duration.

{{Manual Box | en | Important | If several cues which contain the same devices are started at the same time, then the DMX version starts to jump and the light begins to flicker. In addition, scene injections cannot be broken off. It must therefore be taken care of on this that the fade times aren't chosen too greatly!}}

==Module commands==

* Modul: '''Textbook'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| Go button
|style="width: 200px"| The further command is applied to the go button.
|style="width: 100px"| Select
|style="width: 200px"| The button is operated when executing the command.
|- style="vertical-align:top;"
|style="width: 100px"| Previous button
|style="width: 200px"| The further command is applied to the previous button.
|style="width: 100px"| Select
|style="width: 200px"| The button is operated when executing the command.
|- style="vertical-align:top;"
|style="width: 100px"| Next button
|style="width: 200px"| The further command is applied to the next button.
|style="width: 100px"| Select
|style="width: 200px"| The button is operated when executing the command.
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Select script
|style="width: 200px" rowspan="3"| The further command selects the corresponding script.
|style="width: 100px"| Next
|style="width: 200px"| Select the next script.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| Select the previous script.
|- style="vertical-align:top;"
|style="width: 100px"| Textbook name
|style="width: 200px"| The script chooses from the drop down list with the name.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Timecode_player_DMXC2
| TextBackwards = Timecode player
| LinkForwards = Command_line_DMXC2
| TextForwards = Command line
}}
[[de: Textbuch_DMXC2]]
[[Category: DMXControl 2]]

Submaster DMXC2

2025-03-02T19:25:22Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Chasers_tool_DMXC2
| TextBackwards = Chasers Tool
| LinkForwards = Master_DMXC2
| TextForwards = Master
}}
{{Start-LaTeX}}
{{Manual Box | en | Attention | First time you open a DMXC 2.11 Project with DMXC 2.12, are the fader combinations shown on the sub-master no longer correctly due to an internal reorganization. Therefore all sub-master combinations must be updated once.}}

==Overview==
The sub-master reflects exactly the tool in DMXControl again which every Light jockey already knows from his hardware desk. The 12 sub-masters can be enlarged by arbitrarily many benches. In addition, the possibility, every sub-master channel, several DMX channels insists to select simultaneously or to assign an orders or also single cues.

If a midi controller shall come to use (see MIDI remote tool) for a better handling, it is also very advisable to familiarize itself with this module.
{{Picture_with_subtitle |DMXC2_Manual_submaster_window.png|1|Submaster window|center|600px}}

==Description==
{{Picture_with_subtitle |DMXC2_Manual_Submaster_ModulIcon.png|2|Modulicon im Steuerzentrum|right}}
The module can under the menu « Window » menu item « Submaster » as well as being found and started under the icon in control center (see figure 2).

The submaster window apears at the first start in the « simple view » (see figure 1). Apart from the simple view there is also a view in which two real submaster benches pass « ''A'' and ''B'' Crossfade &lraquo. Here you can fade over, this means to Crossfaders between the two benches ''A'' and ''B''.

==Controls==
You'll find in the upper left corner a dropdown, with this dropdown you can change the look to « Simple view » or « Crossfade view ». The view after installation of DMXControl per default stands on this one « Simple view ».

The area is in the left window side below the Dropdownbox for the choice of the view to the administration of the submaster benches. As long as no submaster bank was laid out yet, no faders are in the fader area at the disposal.
A new submaster bank is laid out by a click on the button « add » the ''New submaster bank'' then seems in the listing window and in the entry field. This name can now overwritten by a meaningful name in the entry field. Deleting a submaster bank is made by selecting in the listing window and a click on the button « Delete ». With the button « Arrow up/down » the entries can be sorted in the listing window.

{{Picture_with_subtitle |DMXC2_Manual_submaster_context_menu.png|3|Context menu|right}}
As soon as a bank has been laid out, every fader can one or more DMX channels, an order or a cue are assigned to. The regulator opens a contex menu a click with this one with mouse button on the point below (see figure 3).
The fader lets himself one in or also several device channels, the fader can also aply an command or a cue.
If an assignment has been carried out, a slider over the respective joist as well as the name of the select channel, the order or the cue name appear besides this. By a click with the left mouse button, the name can be changed in a meaningful name. As of now the assigned channels, orders or cues, can be adjusted with the fader of 0-255. The current putting value stands directly under the badge « Flash » below the fader with the corresponding submaster number (1-12).

Channels became voted, the one already in other modules manipulated/set got, the levels can be in the submaster similarly as watched in the channel overview.

{{Manual Box | en | Important | The sub-master overlays other manipulators. Another assignment of the channels used here consists, such as which (Sound2Light), in another module [[Sound_analyzer_DMXC2|sound analyzer]] it should be taken care of on this that the '''other''' value was suppressed after the change of the slider.
Only a click on the button « Reset » this one lifts over spelling of the submaster the S2L (in the context of flash mode) (here: deactivate and activate again or the adjust the other module renewed) again.
}}

===Flash mode===
If one liked to take one of the 12 regulators to another value very fast, then the button « Flash & raquo; offers himself at. He takes care that the respective regulator jumps on the value adjusted under master module (flash).
The area is in the sub-master window below on the left « Flash mode » different modes be able to here be adjusted for the flash buttons:

* « Normal » deadman's control; The value only remains as long as got, as you push.
* « ON/OFF » alteration wiring; The value is held to pressures up to the renewed one.
* « Only one enable » same as ON/OFF, the flash mode, however, becomes regulator deactivated at the same time at all others (moved back).

In addition, the button are here still « Reset » and the button flash « Space ».

===Crossfade (view)===
Becomes in the dropdown « Crossfade » the view of the submaster selectly enlarges himself so around another 12 faders (bank B). However, only 12 different channel groups still can be hired. It, however, is possible now to assign to every channel group of 2 values between which can be changed abruptly, manually or automatically by fading over time (1-30 sec. ).
If there was in the « simple view » only the bank A shown, so it is availably still a bank B in the crossfade.
{{Picture_with_subtitle |DMXC2_Manual_submaster_crossfade.png|4|Submasters crossfade view|center|600px}}

Apart from the controls this one in also the « Simple view » are available, the area is in the left window area still « fading over automatically ». Be able to times be adjusted for the automatic fade for 0 to 30 seconds as fading over time in the area with the slider.

On the right side you find the area « Fade » with the following controls:

* Button « Copy A to B » the fader settigs of the bank A can here be copied to bank B.
* Button « A » B immediately switches over of bank to bank A.
* Button « Auto A » fade with predefine automatic fading over time from bank B to bank A.
* Überblend « Fader » with the fader you can also fade over by the mouse.
* Button « Auto B » fade with predefine automatic fading over time from bank A to bank B.
* Button « B » A immediately switches over of bank to bank B.
* Button « Copy B to A » the fader settigs of the bank B can here be copied to bank A.

==Module commands==

* Modul: '''Submaster'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Set value
|style="width: 195px" rowspan="2"| The select channel is put on the corresponding value in the column value. (O flag must be set)
|style="width: 105px"| 1-12
|style="width: 195px"| Subbmaster 1-12 corresponds to it in the select bank. The command is applied to the corresponding submaster
|- style="vertical-align:top;"
|style="width: 105px"| ''Bank name'': 1-12
|style="width: 195px"| Bank name corresponds to the subbmaster 1-12 in the bank. The commandis applied to the corresponding submaster.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Flash
|style="width: 195px" rowspan="2"| With this command any or the channel chosen can become flash by command.
|style="width: 105px"| All
|style="width: 195px"| The command is applied to all 12 submasters.
|- style="vertical-align:top;"
|style="width: 105px"| 1-12 ''Bank name'': 1-12
|style="width: 195px"| The command is applied to the select submaster. (see also above)
|- style="vertical-align:top;"
|style="width: 105px"| Increase value Decrease value
|style="width: 195px"| The select channel is increased by the value 5 or decreased .
|style="width: 105px"| 1-12 ''Bank name'': 1-12
|style="width: 195px"| see above
|- style="vertical-align:top;"
|style="width: 105px"| Select Bank
|style="width: 195px"| With the command one of the made bank can be selected in the submaster.
|style="width: 105px"| ''Bank namen''
|style="width: 195px"| The corresponding bank name which is then selected can be selected here.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Chasers_tool_DMXC2
| TextBackwards = Chasers Tool
| LinkForwards = Master_DMXC2
| TextForwards = Master
}}
[[de: Submaster_DMXC2]]
[[Category: DMXControl 2]]

Command overview DMXC2

2025-03-02T19:24:01Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Glossary_DMXC2
| TextBackwards = Glossary
}}
{{TOCright}}
{{Start-LaTeX}}
=Command overview=

Commands are a powerful concept in DMXControl. Originally develops it turned out to trigger certain actions by external input devices (MIDI controller, computer keyboard) that the internal communication also profits from the command concept between modules.

Some examples of commands:
*Fade in a cue
*Causing a blackout
*Start a [[Chasers_tool_DMXC2|chaser tool]]
*Flash a [[Submaster_DMXC2|Submasters]]

Typical appearance of commands:
*in a cue expiry of the [[Cue_list_DMXC2|cue list]]
*assignt to the buttons of the commabd box
*started in the audio player or in the text book module
*used into chasers
*assigned into movement cues to the individual figure points
*the original purpose: the integration of hardware operating devices

Almost every module in DMXControl offers commands of its own that otherwise keyboard or mouse intensive processes can much be automated now which means. The commands available are explained in the command overview.

Certain processes need a parameter value (for example "factor of the acceleration" etc. ) in addition to the command, either this one definitely agrees in the command authority or (if the flag ''ask for value'' is set) is questioned by dialog box.

{{Picture_with_subtitle |DMXC2_Manual_command_overview_edit_command.png|1|Window for creating a command}}

The flag ''toggle'' has influence on the behavior of puh buttons (on external controllers) or buttons (e.g. in the commando box). The Control which means a click switches on the Control either or turns off is put into a so-called ''Toggle mode'' depending on previous condition.
One can hereby button at a MIDI keyboard an effect be assigned, for example, either this one runs either as long as the button is held (''Toggle-Flag'' '''off''') or as long as another time is pushed to the button (''Toggle-Flag'' '''on''').

Being able to become certain functions with commands within DMXControl triggered. This chapter delivers a survey of all commands.

==General==

An order has the basic structure:
<Module> - <Device/Functions> - <Channel> - <Flag> -<Value>

* <Module> the mentioned object (ageneral a tool) which shall execute this one is
* <Funktionen> the provided methods/actions or "sub-objects" of the module are, of course they are different depending on a select module
* <Kanal> either an attribute or the operation at sub-objects is
* <Flag> describe the attitudes of the command
* <Wert> submits a parameter to the attribute or the operation

The command entry is supported at the petition by the GUI surface by only the possible values turning up for the choice always.

===Flag===
4 flags can be put parallel here:

* '''Toggle mode''' - This flag has influence on the instruction execution. Commands are usually executed by buttons when pushing and relase (respectively with corresponding value). The toggle mode suppresses the execution when letting off so that e.g. an active effect remains switched on up to the next keystroke.
* '''Use specified value''' - This flag is, whether this one specified instead of the real (e.g. of DMXIn) shown off with fed value shall be used.
* '''Ask for value''' - A dialog box appears to enter the value to the running time. E.g. this can make sense at the call of commands over the keyboard or command box to avoid many uniform commands which are different only by a value.
* '''Ignore value 0''' - With this parameter the function of "letting off" can be stopped if the value 0 results from it. An command with this flag only can be concluded by another command or be overwritten by other values at times. For example: Unlike the toggle mode the active effect also remains after let off active the button and another keystroke cannot be switching off again either.

===Device/Functions===

Defaults with the following generic meaning methods appear at objects, also which offers a register, lists or drop down choice of elements (e. g. audio player -> track, scene list -> list, chasers-> chase) here besides the dynamic ones:

* '''Selected''' - das gerade aktuelle Element wird angesprochen
* '''Next''' - das folgende Element in der Liste wird angesprochen
* '''Previous''' - das vorige Element in der Liste wird angesprochen
* '''---''' (Separator) - no function

===Channel===

If '''start/stop''' is chosen, the respectively complementary operation is carried out for the action just executed.
===Value===

{{Manual Box | en | Attention | The values are expected standardizedly from 0. 000 to 100. 000, so one must imagine the petition in per cent values. It is supported for finer dissolvings up to three fractional digits.
}}

==Module Command==

As described above, every module supports different orders.

===Audio cue===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="4"| Kanal 1-16
|style="width: 200px" rowspan="4"| The further command is used select of one of the 16 audio channels on this one.
|style="width: 100px"| Pause
|style="width: 200px"| Regards the channel selected under equipment/function as renewed call at, after the channel output is continued.
|- style="vertical-align:top;"
|style="width: 100px"| Rewind
|style="width: 200px"| Rewinds the audio file to start.
|- style="vertical-align:top;"
|style="width: 100px"| Stop
|style="width: 200px"| Stopped the audio file.
|- style="vertical-align:top;"
|style="width: 100px"| Set volume
|style="width: 200px"| Set the volume by take-over the indicated value.
|}

===Audio player===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="4"| Select
|style="width: 195px" rowspan="4"| The further command is applied to the currently select audio track. (Command selects at this function the makes sense to none)
|style="width: 105px"| Start/Stopp
|style="width: 195px"| The command ''start/stop'' starts and stops the select Audiotrack for playback. (The order should be used in connection with the T flag. )
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command ''start'' starts the select Audiotrack for playback.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The order ''stop'' stops the select Audiotrack at playback.
|- style="vertical-align:top;"
|style="width: 105px"| Rewind
|style="width: 195px"| The audio cursor jumps to the beginning of the sound file by the command''Rewind'' again.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next previous Other entries
|style="width: 195px" rowspan="2"| The further command is on the near, previous or into audio track named dropdown the used.
|style="width: 105px"| Select
|style="width: 195px"| Or this one selects the next, previous into audio track named dropdown ''Device/Function''.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop Rewind
|style="width: 195px"| see above
|}

===BeatTool===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| Tap button
|style="width: 200px"| The command (channel) is applied to the Tap button in the beat tool.
|style="width: 100px"| Select
|style="width: 200px"| The Tap button is selected (selected).
|- style="vertical-align:top;"
|style="width: 100px"| Sync button
|style="width: 200px"| The command (channel) is applied to the Sync button in the beat tool.
|style="width: 100px"| Select
|style="width: 200px"| The Sync button is selected (selected).
|- style="vertical-align:top;"
|style="width: 100px"| Reset button
|style="width: 200px"| The command (channel) is applied to the Reset button in the beat tool.
|style="width: 100px"| Select
|style="width: 200px"| The Reset button is selected (selected).
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Factor
|style="width: 200px" rowspan="3"| The function factor has an effect on the multiplier for the BPM..
|style="width: 100px; text-align: center"| 2
|style="width: 200px"| Multiplier two for BPM.
|- style="vertical-align:top;"
|style="width: 100px; text-align: center"| 1
|style="width: 200px"| Multiplier one for BPM.
|- style="vertical-align:top;"
|style="width: 100px; text-align: center"| 1/2
|style="width: 200px"| Multiplier half for BPM.
|- style="vertical-align:top;"
|style="width: 100px"| BPM value
|style="width: 200px"| With the function BPM value the BPM value can be influenced directly.
|style="width: 100px"| Set
|style="width: 200px"| BPM value entered transfers this one the command (channel) set to.
|- style="vertical-align:top;"
|style="width: 100px"| From sound analyzer
|style="width: 200px"| This function has an effect on the checking box in the sound analyzer.
|style="width: 100px"| On/OFF
|style="width: 200px"| In connection with the T flag the function can one and be turned off.
|}

===DMX-Output===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Blackout
|style="width: 200px" rowspan="3"| The ''Blackout'' command refers to the ''Blackout'' icon in the control center and in the graphical view.
|style="width: 100px"| Toggle
|style="width: 200px"| The command ''Toggle'' inverted the momentary behaviour of the ''Blackout''-Funktion.
|- style="vertical-align:top;"
|style="width: 100px"| On
|style="width: 200px"| The command ''On'' activate the ''Blackout''-Funktion.
|- style="vertical-align:top;"
|style="width: 100px"| Off
|style="width: 200px"| The command ''Off'' deactivate the ''Blackout''-Funktion.
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Freeze
|style="width: 200px" rowspan="3"| The ''Freeze'' command refers to the ''Freeze'' icon in the control center and in the graphical view.
|style="width: 100px"| Toggle
|style="width: 200px"| The command ''Toggle'' invertst the momentary behaviour of the ''Freeze''-funktion.
|- style="vertical-align:top;"
|style="width: 100px"| On
|style="width: 200px"| The command ''On'' activate the ''Freeze''-funktion.
|- style="vertical-align:top;"
|style="width: 100px"| Off
|style="width: 200px"| The command ''Off'' deactivate the ''Freeze''-funktion.
|}

===DMXIn remote===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the DMX remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

===Chasers tool===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px"| All
|style="width: 195px"| The command will apply on all chasers.
|style="width: 105px"| Stop
|style="width: 195px"| All running chasers will be stoped.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="11"| Selected
|style="width: 195px" rowspan="11"| The further command will applied to the current effect. Stand above an effect category, if got categories used, the corresponding category amens. These although can be selected, however, cannot be assigned to any order.
|style="width: 105px"| Start/Stop
|style="width: 195px"| The comand start/stop starts and stopt the select chaser for an automatic expiry. (The command should be used in connection with the T flag.).
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command start starts the selected chaser in the chaser tool for an automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The command stop stops the selected chaser in the chaser tool for an automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Set acceleration
|style="width: 195px"| With this command the chaser acceleration can be backed the percent value entered in value.
|- style="vertical-align:top;"
|style="width: 105px"| Set intensity
|style="width: 195px"| With this command the chaser intensity can be backed the percent value entered in value.
|- style="vertical-align:top;"
|style="width: 105px"| Next stept
|style="width: 195px"| Lead the next step out at stock exchange securities which are prepared for account mode ''only a step''.
|- style="vertical-align:top;"
|style="width: 105px"| Repeat on/off
|style="width: 195px"| Turns off the option ''repeat'' for the chosen effect. See note (use T flag)
|- style="vertical-align:top;"
|style="width: 105px"| Audio triggered on/off
|style="width: 195px"| The option ''music control'' for the chosen chaser switches turns on/off. See note (use T flag)
|- style="vertical-align:top;"
|style="width: 105px"| Next play mode
|style="width: 195px"| Select the ''next account mode'' for the chosen effect.
|- style="vertical-align:top;"
|style="width: 105px"| Play mode: * Manual * Normal * Reverse * Bounce * Random * Only one step
|style="width: 195px"| Select the corresponding play mode for the chosen chaser.
|- style="vertical-align:top;"
|style="width: 105px"| Intens. with Start/Stop
|style="width: 195px"| The command starts ''Intens. with start/stop'' and stoped a percent value can the select chaser submit for the brightness for automatic expiry, simultaneous about the value column.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next Previous Several entries
|style="width: 195px" rowspan="2"| The further order is on the currently near, previous or into the drop down named effect used.
|style="width: 105px"| Select
|style="width: 195px"| Or this one selects the near, previous the dropdown equipment/function named chaser into.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop Set acceleration Set intensity Next step Repeat on/off Audio triggered on/off Play mode Intens. with Start/Stop
|style="width: 195px"| see above
|}

{{Manual Box | en | Hint | If the option ''repeat'' or ''audio triggered'' is used in the chaser tool, this must without use the T flags are carried out. The following command sequence must be indicated for switching on here: 
'''Modul:''' Chaser 
'''Device/Function:''' Chaser name, next, previous, current 
'''Channel:''' Repeat on/off, Audio triggered on/off 
'''Flag:''' O-Flag (Used specified value) 
'''Value:''' 100 
Turning off is correspondingly with the '''value:''' 0.
}}

===Devices===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Selected
|style="width: 195px" rowspan="2"| The broader parameters are/the select device(s) in the graphical view used only on this.
|style="width: 105px"| Dimmer, Pan, Tilt Channel 1 - 32
|style="width: 195px"| For the select device a corresponding value can the appropriate channel be selected and be assigned in the column ''value''.
|- style="vertical-align:top;"
|style="width: 105px"| Pan invert Tilt invert Pan & Tilt invert.
|style="width: 195px"| There is here the possibility at scanners and movingheads to inverting the axes by command.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="5"| Other entries
|style="width: 195px" rowspan="5"| All device which was added to the current project is below of ''select device''. Here you can direct select a device on which the broader parameters are used.
|style="width: 105px"| Select
|style="width: 195px"| The corresponding device is selected in the graphical view.
|- style="vertical-align:top;"
|style="width: 105px"| Deselect
|style="width: 195px"| The selection for the corresponding device is deselected in the graphical view.
|- style="vertical-align:top;"
|style="width: 105px"| Switch selection
|style="width: 195px"| The selection for the corresponding device is inverted in the graphical view.
|- style="vertical-align:top;"
|style="width: 105px"| Other channel items
|style="width: 195px"| For the select device the appropriate channel can be selected. These are, indicated in the DDF, shown to names of the channels.
|- style="vertical-align:top;"
|style="width: 105px"| Pan invert Tilt invert Pan & Tilt invert.
|style="width: 195px"| There is here the possibility at scanners and movingheads to inverting the axes by command.
|}

===Group selection===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| <Remove selection>
|style="width: 200px"| A before select grouping will be resetted.
|style="width: 100px"| Select
|style="width: 200px"| The group standing under device/function will selected.
|- style="vertical-align:top;"
|style="width: 100px"| Group name
|style="width: 200px"| The group mit dem group name will selected fom the grouping.
|style="width: 100px"| Select
|style="width: 200px"| The group standing under device/function will selected.
|}

===Joystick control===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Control
|style="width: 200px" rowspan="3"| The next command (channel) is applied to the joystick control.
|style="width: 100px"| On/Off
|style="width: 200px"| The joystick control will be turned on or off (T-Flag).
|- style="vertical-align:top;"
|style="width: 100px"| Activate
|style="width: 200px"| The joystick control will be activate.
|- style="vertical-align:top;"
|style="width: 100px"| Deactivate
|style="width: 200px"| The joystick control will be deactivate.
|}

===Command box===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| A choice of this function there is the possibility of accessing the different banks (1-10) about the order in the command box.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank 1 to 10
|style="width: 200px"| Direct choice of one of the ten banks.
|- style="vertical-align:top;"
|style="width: 100px"| Button
|style="width: 200px"| With the function button orders already made can be cloned in the command box or used in other modules.
|style="width: 100px"| Button name
|style="width: 200px"| Name of the button which shall be used.
|}

===Command line===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| 0-9,.,+,-,Thru @,Full,Enter, Del,/,Slider
|style="width: 200px"| The following command is applied to the individual control elements in the command line with the slider.
|style="width: 100px"| Set
|style="width: 200px"| Selects the appropriate control, or set the slider to a value.
|}

===Master===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 50px"| Channel
!style="width: 250px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| Grandmaster
|style="width: 200px"| The broader parameter is applied to the grand master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the grand master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|- style="vertical-align:top;"
|style="width: 100px"| Sek. Grandmaster
|style="width: 200px"| The broader parameter is applied to the secondary grand master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the secondary grand master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|- style="vertical-align:top;"
|style="width: 100px"| Speedmaster
|style="width: 200px"| The broader parameter is applied to the speed master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the speed master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|- style="vertical-align:top;"
|style="width: 100px"| Flashmaster
|style="width: 200px"| The broader parameter is applied to the flash master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the flash master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|}

===MIDI remote===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the MIDI remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

===Sound Analyzer===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Sound2Light
|style="width: 200px" rowspan="3"| The further orders (channel) only are applied to the Sound2Light function.
|style="width: 100px"| On/Off
|style="width: 200px"| The function can the T flags under use and be turned off one.
|- style="vertical-align:top;"
|style="width: 100px"| Activate
|style="width: 200px"| With the command the Sound2Light function is activated.
|- style="vertical-align:top;"
|style="width: 100px"| Deactivate
|style="width: 200px"| With the command the Sound2Light function is deactivated.
|- style="vertical-align:top;"
|style="width: 100px"| Bank
|style="width: 200px"| With the function bank the appropriate bank from this can drop down be selected in the sound analyzer.
|style="width: 100px"| Bank name
|style="width: 200px"| The bank names laid out correspondingly stand drop down in the sound Analyzer under channel from this.
|}

===Submaster===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Set value
|style="width: 195px" rowspan="2"| The select channel is put on the corresponding value in the column value. (O flag must be set)
|style="width: 105px"| 1-12
|style="width: 195px"| Subbmaster 1-12 corresponds to it in the select bank. The command is applied to the corresponding submaster
|- style="vertical-align:top;"
|style="width: 105px"| ''Bank name'': 1-12
|style="width: 195px"| Bank name corresponds to the subbmaster 1-12 in the bank. The commandis applied to the corresponding submaster.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Flash
|style="width: 195px" rowspan="2"| With this command any or the channel chosen can become flash by command.
|style="width: 105px"| All
|style="width: 195px"| The command is applied to all 12 submasters.
|- style="vertical-align:top;"
|style="width: 105px"| 1-12 ''Bank name'': 1-12
|style="width: 195px"| The command is applied to the select submaster. (see also above)
|- style="vertical-align:top;"
|style="width: 105px"| Increase value Decrease value
|style="width: 195px"| The select channel is increased by the value 5 or decreased .
|style="width: 105px"| 1-12 ''Bank name'': 1-12
|style="width: 195px"| see above
|- style="vertical-align:top;"
|style="width: 105px"| Select Bank
|style="width: 195px"| With the command one of the made bank can be selected in the submaster.
|style="width: 105px"| ''Bank namen''
|style="width: 195px"| The corresponding bank name which is then selected can be selected here.
|}

===Cue libary===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="2"| All entries
|style="width: 200px" rowspan="2"| All cues are the entries the dropdown ''device/function'' within the cue library in. At select of an entry the command can in the dropdown ''channel'' be applied to the scene.
|style="width: 100px"| Execute
|style="width: 200px"| Execute the chosen cue directly.
|- style="vertical-align:top;"
|style="width: 100px"| Fade in
|style="width: 200px"| Executes the chosen cue, with the fade in time stored in the cue.
|}

===Cue list===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="5"| Select
|style="width: 195px" rowspan="5"| The further order is applied to the currently select cue list. (The Command selects at this function the makes no sense)
|style="width: 105px"| Start/Stop
|style="width: 195px"| The command ''Start/Stop'' starts/stops the select cue list at automatic expiry. (The command should be used in connection with the T flag.)
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command ''Start'' starts the select cue list at automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The command ''Stop'' stops the select cue list at automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| G O !
|style="width: 195px"| The command ''G O!'' executes the next cue from the Szeneliste.
|- style="vertical-align:top;"
|style="width: 105px"| Scroll to current cue
|style="width: 195px"| The command '' scroll to current cue'', forces the current cue to scroll to the visible window area.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next Previous Other entries
|style="width: 200px" rowspan="2"| The further command is or into the dropdown named cue list used on the currently next or previous cue.
|style="width: 105px"| Select
|style="width: 195px"| Selects the next (previous) cue list or the one selected in the dropdown ''device/function''.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop G O ! Scroll to current cue
|style="width: 195px"| see above
|}

===Textbook===

{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| Go button
|style="width: 200px"| The further command is applied to the go button.
|style="width: 100px"| Select
|style="width: 200px"| The button is operated when executing the command.
|- style="vertical-align:top;"
|style="width: 100px"| Previous button
|style="width: 200px"| The further command is applied to the previous button.
|style="width: 100px"| Select
|style="width: 200px"| The button is operated when executing the command.
|- style="vertical-align:top;"
|style="width: 100px"| Next button
|style="width: 200px"| The further command is applied to the next button.
|style="width: 100px"| Select
|style="width: 200px"| The button is operated when executing the command.
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Select script
|style="width: 200px" rowspan="3"| The further command selects the corresponding script.
|style="width: 100px"| Next
|style="width: 200px"| Select the next script.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| Select the previous script.
|- style="vertical-align:top;"
|style="width: 100px"| Textbook name
|style="width: 200px"| The script chooses from the drop down list with the name.
|}

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Glossary_DMXC2
| TextBackwards = Glossary
}}
[[de: Befehlsübersicht_DMXC2]]
[[Category: DMXControl 2]]

Glossary DMXC2

2025-03-02T19:22:57Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Magic_3D_Easy_View_Plugin_DMXC2
| TextBackwards = Magic 3D Easy View Plugin
| LinkForwards = Command_overview_DMXC2
| TextForwards = Command overview
}}

{| border="0" class="hintergrundfarbe1 rahmenfarbe1" style="margin: 0 auto; border-style: solid; padding:5px;" align="center"
| '''Inhaltsverzeichnis''' [[#A|A]] [[#B|B]] [[#C|C]] [[#D|D]] E [[#F|F]] [[#G|G]] [[#H|H]] I J K [[#L|L]] [[#M|M]] N [[#O|O]] [[#P|P]] Q R [[#S|S]] [[#T|T]] U V W X Y Z
|}
{{TOCright}}
{{Start-LaTeX}}

== A ==
=== ArtNet ===
ArtNet (or Art-Net) is an IP based protocol for the assignment of large quantities of DMX information about LANs or WANs under use of the default network topology. The present ArtNet uses UDP about IP. The specification was made by the company "Artistic Licence" and is freely available in version 3 at the moment ([http://www.artisticlicence.com/WebSiteMaster/User%20Guides/art-net.pdf Download]). She was appreciated by bigger manufacturers.<ref>
[http://www.martin.com/product/product.asp?product=Ether2DMX8&Words=artnet Martin Ether2DMX8™]. Abgerufen am 12. März 2013.</ref><ref>
[http://www.jb-lighting.de/index.php?S=3_3&P=41#fragment-2 JB Lightning Licon 2X]. Abgerufen am 12. März 2013.</ref><ref>
Einbindung in die [http://www.opendmx.net/index.php/OLA Open Lighting Architecture]. Abgerufen am 12. März 2013.</ref> The advantage of ArtNet consists that the DMX cables are replaced by Ethernetkabel in parts of the transmission path. One needs no more classic DMX transmitter at the PC with that since the signals are sent about a mostly per default available network interface. A complete show can theoretically be steered over the Internet with that. WLAN ways are more practice relevant so that the wiring can be dropped on unfavorable ways or even for the most part. Another advantage is the bi direktionale communication for re-registrations by means of RDM which, however, isn't supported of DMXControl yet. Also proprietary protocols are conceivable since the UPD protocol bi direktional is interpreted.
Since the steered equipment has DMX interfaces for the most part by means of 5-pole XLR sockets furthermore, one needs another one or several so-called ArtNet knots which one, the ArtNet information in standard DMX 512 signals zurückverwandeln. So an ArtNet knot gets the signals about a network interface for one and or more DMX university verses distributes the DMX signals separated according to university verses about XLR. These Nodes even can be built themselves: [[Art-Net-Node für 25 Euro]].

=== Audio cue ===
Audio cues permit playing an audio file in a definable length. You are usable for cues in various modules equally. The light technician also can synchronously steer audio sequences to the light with that. E.g. there is an important application for this at the theater control by means of script.
{{Picture_with_subtitle |DMXC2_Manual_edit_cues_audio_cue.png|1|Create a audio cue}}
To other cues an audio cue analogously gets an eloquent name so that these are re-traceable also in the cue library. As a wave file WAVE, MP3, MP2, MP1 and OGG-Vorbis files can be used. Like other cues also can the audio cue a duration be assigned to control the temporal sequence of the cues and with that the length of the wave file as of the beginning. Has suitably to be broken off around the audio input after the adjusted time the option "after passed duration stop account". The duration also can on be limited manually to carry out the control over the "GO" button. Audio cues can be assigned to one by 16 (audio-)channels. About the channel number audio cues can be broken off by command. Siehe auch [[#Audio manager|Audio manager]]

=== Audio manager ===
The audio manager as a drop down menu hides behind the "audio stop" button or courage button in the control center (loudspeaker with a red point). An overview has active audio streams (channels) opened out for itself there. The left symbol says to the statuses of the respective audio cue the audio stream can be manipulated with the respectively right symbol group with the usual functions break, rewinding, stop. The channels can be changed in the volume one by one and switched dumbly about orders. Several audio cues also can be on a channel.
{{Picture_with_subtitle |DMXC2_Manual_glossary_audioManager.png|2|View of the audio manager in the control center|600px}}

== B ==
=== Bank ===
Banks which serve for the ready attitude of different attitudes of the same module can be laid out within certain modules. By means of commands you can change between the Banks. Banks can be made in the following modules:
; DMXIn remote control: Different assignment of DMX channels
; Command box (Pages): Choice of different pages (at most 10)
; Midi Fernsteuerung: Different assignment of MIDI channels
; Sound Analyzer: Different assignment of settings
; Submaster: Assignment of the 12 sub-masters. It is for " possible to order groups of equipment logically front ", "Audience" "hall light" for example bench parse.

=== Blackout ===
A blackout describes turning off immediately ( or in the lighting engineering. Darken ) all light sources. Transferred to the DMX protocol this means that all dimmer channels are immediately put on 0%. A "blackout" buttone is in DMXControl in the control center. If this is activated, all channels defined as dimmer channels are backed 0% and the version closed on these channels until the blackout is lifted again.

== C ==
===Color filter===
A color filter is a firm intention for a lamp which shall ink her light. Color filters are usually colored plastic films. Besides that there is also dichroic filter, which consist of glass and make a considerably better filtration possible at a higher price.

===Color wheel===
A color wheel is often found in moving heads and other multifunction headlights. It is a plate on which glass color filters are arranged circularly and reach to the course of ray. Discreet light colors or half colors are produced by the color wheel be able to into been different.

=== Command ===
see [[Command_overview_DMXC2|Command overview]]

=== Cue ===
A show consists of various cues. A cue is an instantaneous adjustment of all connected devices (DMX values). A fade and hold time can be specified for each scene, which remain within it comes to fruition [[#Scene_list|scene list]] or [#Chaser|chaser]. Values of a cue to remain active on the issue, until they are explicitly overridden, for example by a different cue.
{{Picture_with_subtitle |DMXC2_Manual_cue_list_newcue.png|3|Create a new cue|400px}}
In addition to the "simple cue" can [[#Command|commands]], motion or [[#audio_cue|audio cue]] can be used. All cues can be managed in the cue library and can be selected and reused from there. Composition cues can combine any types of cues.

{{Manual Box | en | Hint | The concept of '''cue''' from DMXControl corresponds to the '''scene''' from various other light control programs.
}}

=== Cue list ===
One or more cues form a cue list. The maximum number of cues per cue list is limited only by the resources of your computer. Playing a cue list indicates the sequential execution of all individual cues taking into account its duration and fade. The cues can also be forwarded manually. Multiple lists can run in parallel cue at a time.

== D ==
=== DDF ===
DDF is the abbreviation of "''DEVICE definition file''". DDFs are used by DMXControl to describe information about the used equipment in the XML format. Among other things the channel occupancy of the device, the layout of the control window as well as further information are contained in a DDF. The DDFs are in the sub-folder "DEVICEs" of the DMXControl contents directory. The accompanying device image files which are shown on the graphical view lie name in another sub-folder „Images“. A DDF library is installed per default. For the construction of DDFs see [[DDF_DMXC2|DDF basics]].

===Device===
In DMXControl the term device refers to a point in the DMX chain, where the signal is evaluated. This can happen, for example by:
* an dimmer
* an fog machine
* an multi-function spotlight as moving head or scanner
* an [[#DMXC plugin|Application plugin]]
* everything DMX can process
A device is usually (but not necessarily) physically present and responsive to the transmitted signals DMX. Devices are described by DDF, containing all the necessary information for control. In the graphical view of the Stage devices can be created, deleted, and moved in front of the background image. A click on the device icon opens the Control Panel. Devices always need a [[#Start address|Start address]].

=== DMX512 ===
The DMX512 protocol 1986 of the USITT, an American organization was defined, which deals among others with theater technology (short DMX). With various improvements it is also standardized in Germany since 1994 (DIN 56930/Teil2). DMX stands '''for D 'igital', 'M '''ultiple'' 'X''', which means that the signals are transferred digitally over a line to the dimmers and other devices'''. Unlike this the earlier ones had systems one analogous line each for every single device. Since the equipment is switched at DMX behind each other, one also talks about a DMX chain (engl. daisychain). In a plain verse attached equipment has a clear start address between 1 and 512 everybody. However, at most 32 equipment only should be attached at a DMX rope since otherwise the burden on the line gets too big. Remedial action then can be taken with amplifiers or splinters. A value between 0 and 255 sent can weden over the DMX protocol on every channel in a cycle. The meaning of the value isn't defined in the DMX protocol but depends on the device individually. Protected two wire lines shall be used for DMX with 5-pole XLR plugs. However, in the practice one finds 3-pole XLR verb Indians at a favorable equipment particularly in front of - these aren't then, however, standard-compliant and mustn't bear the name ''DMX512''.

=== DMXC plugin ===
DMXControl defines two kinds of Plugins for the expansion of the functionality:
* Outout plugins to the support of different new DMX interfaces
* Application plugins for inserting new modules and functions in DMXControl

=== DMX interface ===
A "DMX interface" (also frequently called "DMX transmitter") represents the hardware interface between PC and the DMX universe. There are the values produced by DMXControl on the DMX chain. The transmitters can parallel or about USB serially internally be attached at the PC. One needs a DMX interface for productive use of DMXControl or the real drive of a DMX-capable device, in principle the program works completely (primarily for exercise purposes) also without interface. DMXControl uses output plugins to mention different DMX transmitters with a uniform interface. A complete list of the DMX interfaces supported by DMXControl is found on our [[http://www. dmxcontrol. de/unterstuetzte-interfaces. html|Website]]. The DMXControl interface specification is available so that you your self can make an output plugin. At the program start DMXControl is looking for files in his contents directory with the ending "*.out.dll" which the output plugins represent. One then can activate and configure the required plugins over the menu item of output plugins.

=== Dimmer channel ===
Channels which function as dimmers become in the DDF of the respective device by means of type=dimmer when such defines. Using this information DMXControl only can apply certain functions to channels which also steer the brightness of a device. Among other things these are:
* [[Master_DMXC2|Grandmaster]]
* [[#Blackout|Blackout]]
* Automatic [[#HTP|HTP]]
* Joist below the device icon in the [[Graphical_view_DMXC2|Graphical view]]

== F ==
=== Fade in time ===
One can define a one dazzling time in DMXControl for every cue around gentle fadeing to realize between cues. Be the DMX values brought closer to the stored values continuously and finally put on these during this period of time (engl. [[#Fader|fading]]). The contrast to this is a sudden change of the values at a one dazzling time of 0 seconds. Which not faded are (e.g. Gobo wheels) one can fading point do for channels be defined.

=== Fader ===
A fader is a mechanical slider more classically wisely which changes an electrical resistance and is found at audio or light sound mixers, for example. The English verb to fade expresses a fluent, continuous transition between two values. This is primarily confessed dull one and dull out as volume change at the beginning and end of a piece of music. (Software-)faders are used in DMXControl mainly in the [[#Submaster|submaster]]. You serve to adjust exact DMX values or to realize gentle transitions between cues. Also in much DDFs faders are defined and make the attitude possible there among other things of trick and strobe speed or colors.

=== Flash button ===
Flash buttons set their assigned channels temporarily (for the duration of the operation) to the maximum allowable value. This is in DMXControl by the maximum values in the DDF and the [[Master_DMXC2|Flash master]] defined

== G ==
=== Gobo / Gobo wheel ===
A gobo (Graphical optical blackout) alters the beam of a spotlight. It is a mask that can be cut out of geometric shapes, texts or images. The light beam then assumes this shape. Gobos are constructed of metal stamped from thin sheet metal or glass gobos more expensive than in combination with [[#color filter|dichroic filters.]]
In the headlamps often even more screens sit on a circular gobo. Depending on the rotation of the gobo wheel, there is a certain gobo in the beam, the beam then becomes the subject. Also there is the possibility to have gobos rotate around itself.

== H ==
=== HTP ===
HTP stands for "highest takes precedence" (the highest value prevails ) and is usually used for dimmer channels ,e.g. To prevent flicker by parallel changes from several sources.
DMXControl HTP can be applied to all channels that are marked as type="dimmer" in DDF. Thus, the highest value is always output on one channel, for example we can the sound analyzer and run at the same time can also create an chaser. Would be possible that a preheat , because the value "10" would be compared to the "0" as by setting an ongoing chaser. By default, the HTP mode is disabled, but can be switched to the application configuration easy.
HTP / LTP processed per channel - channels in the DDF as a " dimmer type = '' ''" are registered HTP are mixed , the rest of LTP . But if you completely shut down the program configuration HTP , then dimmer channels are mixed LTP . If you have problems with "hanging " channels , which probably has to do with the HTP mode. In the channel list is displayed which channel of which was last modified mixer channel . If for example a fully wound channel of a cue, it can only be set by the next cue, or by closing the cue module back to a lower value . When a cue fades into another , the old values should also be reduced .

== L ==
=== LTP ===
LTP stands for "latest takes precedence" (the last value prevails) and is automatically used when DMXControl for all channels that are not marked as "Dimmer". The last channel change is passed directly to the output system. If the mixer channel is closed, the state before the first change by the just closed mixer channel will be restored on each DMX channel.

=== Line termination ===
To ensure a low-loss and trouble-free transmission of the DMX signal DMX512 protocol requires a terminating resistor of 120 ohms at the end of the DMX chain between Data + and Data-(pin 2 and 3). So that feedback and to prevent signal reflections that could distort further transmitted values. There are to buy commercial terminators (5-7 €), but you can be prepared in a DMX connector such a device itself also through the incorporation of an appropriate resistor.

== M ==
=== Master ===
A master is the load Which authority has influence on the signal before it reaches the output. Changes to a master controller act synchronously on all channels and give maximum values for them before in DMXControl there is the module [[Master_DMXC2|Master]], where grand master (dimmer), secondary master (dimmer), flash master and Speedmaster (speed of chasers and fading times) maximum value for.

=== Mixer channel ===
DMXControl internally uses a mixer that collects the DMX outputs of the various active modules and generates the output values, which are then displayed on the respective DMX transmitter. The different sources (ie mostly modules) are referred to as "Mixer channels", not to be confused with DMX channels. A mixer channel usually covers the entire DMX channel space that the respective DMXControl version is available (256 or 512 channels). If a mixer channel "'' closed'' ', are also calculates the new output values. The blender system of DMXControl always the module that was operated by the user as a last resort reserves the Controlle until:
* the module is closed,
* another module is operated
* the module is reset.
Some modules such as the audio player example provide a button with which you can reset the module (small red circle with a slash through). '' 'Example:'''
If one uses a channel with the flash button on the submaster, the submaster is the last module, which accesses the channel. Thus, another chaser of this DMX channel acts again, you can do 3 things:
* close the submaster window,
* start the chaser again and
* reset the Submaster.

=== Mixer mode ===
The channel of the internal mixer can be mixed to 2 standards, these are [[#LTP|LTP]] and [[#HTP|HTP]].

== O ==
===Output plugins ===
The union on the side of the software which processes the generated DMX data represents a version Plugin between DMXControl and a hard or software. This mainly is DMX interfaces (transmitters) which pass the data (mostly cable-bound) on to a DMX-capable device. The union to a visualisierer or by ArtNet is but also taken by output plugins. See also [[Output_plugins_DMXC2|Output plugins]].

== P ==
=== Preheat ===
The preheat (also Pre Heat) serves to increase the life of your bulbs. The lamps are not switched off completely, but always operated slightly dimmed, so that the lamp is not currently visible. In DMXControl can reach a preheat by
* activate the HTP mode (in the program settings)
* save a cue that contains the desired channel values for the preheating and
* this cue a [[#Command|command]] call at startup can (also program settings).

=== Project ===
You can generate various projects (shows), and save (one at a time just a project) load. DMXControl in a project contains all project data that are relevant for a show. Such data include which DMX devices are used, created scenes and effects, input and output configurations and more. However, they are stored by the individual modules of DMXC in a shared folder with different file extensions.

In addition, there are also so called ''global'' data, the DMXControl across projects in a separate directory (<tt> "%appdata%/PopSoft /" </tt>) stores. These global data including settings of the MIDI and DMX remote controls. Therefore, these data must be copied when copying a project to another computer. How this works easiest, may be found in [[Pack_And_Go_DMXC2|Chapter 31 Pack and Go]].

== S ==
=== Spectrum===
Decomposition of the frequency band of an audio file in different intervals. All intervals together form the spectrum. DMXControl in the intervals can be assigned to channels.

=== Start adresse ===
Each physical device in a DMX chain has a so called starting or base address. This is set on the device itself, ideally it is identical with the start ardress the [[#Device|device]] in DMXControl. This address refers to the lowest, but not necessarily the only one channel from a device processes the DMX values. A 4-channel dimmer with the start address 5 evaluates the channels 5,6,7 and 8, a moving head can prove quite 15 or more channels for its functions. It is also possible to assign the same start address multiple devices. This can lead to unwanted results, but are also deliberately used in the same headlights for synchronous outputs.
As the start address is set, depends on the device, please note here the manufacturer's instructions.

{{Manual Box | en | Hint | In the Device Configuration dialog box, the positions of DIP switches own piano are displayed to the selected start address.
}}

=== Submaster ===
A submaster is a [[#Fader|fader]] can control the values of different channels together. The submaster concept in DMXControl by realized, each consisting of a submaster fader and flash button [[Submaster_DMXC2|Submaster module.]] Using a submaster, for example, the same functions are bundled, so all channels of 10 red LED headlights.

== T ==
===Termination resistor===
To ensure of a loss and trouble-free assignment of the DMX signals the DMX512 protocol requires RS485 standard a terminating resistor of 120 Ohm at the end of the DMX chain between the signal leads (exact this). Feedbacks and signal reflections which could distort further sent values are prevented with that. €Zhowever, one gets her aurochs guarantee of a loss and trouble-free also by the installation of a corresponding resistance into a DMX plug between datas+ and data ), (Pin 1 and 2) produce themselves.

=== Transition point ===
The "'' use point''" is used when blending between two cues. While the channels with the attribute "''fade = yes''" (dimmer) are soft fade, the other channels (shutter, gobo wheel) must be set at a point abruptly to a new value. The insertion point is the location on the timeline represents (between 0 and 100% of the fade), the switching happens. In this way, gobos can be changed either at the beginning or at the end of the fade.

== Referenzen ==
<references />
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Magic_3D_Easy_View_Plugin_DMXC2
| TextBackwards = Magic 3D Easy View Plugin
| LinkForwards = Command_overview_DMXC2
| TextForwards = Command overview
}}
[[de: Glossar_DMXC2]]
[[Category: DMXControl 2]]

DDF DMXC2

2025-03-02T19:22:23Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Pack_And_Go_DMXC2
| TextBackwards = Pack And Go Function
| LinkForwards = DDFCreator_DMXC2
| TextForwards = DDFCreator
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_DDF_graphical_view.png|1|Graphical view with DDF icon|right|250px}}

{{Picture_with_subtitle |DMXC2_Manual_DDF_example.png|2|Opened DDF window with control elements|right|250px}}

DDF is the abbreviation of ''Device Definition File''. The DDF are the device description (Fixtures) in DMXControl, they serve to inform DMXControl about the functions of the attached DMX device to this. In the DDF the number becomes this one how channels of the DMX device defined and as well these use possible control elements:
*Position input control element e.g. at Movingheads and Scanners.
*RGB or CMY color choice control element to the color mixture at e.g. LED headlight or color mixed units at Movingheads.
*Dropdown control elements
*Button control elements.

Become the DDF in the « graphical view » with an icon of the device shown (see figure 1), then also can here be accessed the icon, the DDF window by a click with the control elements (see figure 2). XML format which is translated by DMXControl into the internal device description is carried out the description the DMX equipment in one. The DDF are found the DMXControl main directory in the sub-folder <tt>DEVICEs</tt>. The accompanying icon pictures, which one in the & laquo; Graphic stage view & raquo; be, lie in another sub-folder named shown <tt>images</tt>.

You get prefabricated DDFs, which weren't enclosed at the installation, can you perhaps of the DMXControl home page in the device library<ref name="GB">Link Gerätebibliothek:http://www.DMXControl.de/Geraetedefinitionen/Geraetebibliothek.html</ref>. DDF can be made in a simple way with a XML editor (e. g. PSPad<ref>Link XML-Editor PSPad:http://www.PSPad.de</ref>) or also with the [[DDF_Creator_DMXC2|DDFCreator]]. There are advantages and disadvantages with the DDFCreator as also the construction of a DDF with a XML editor. With a XML editor, paraphrasing an existing DDF can be managed considerably faster than with the DDFCreator, against this one is fundamentally faster with the DDFCreator at the construction of a new DDF surface with slidern, button etc. 

''At both one needs a corresponding knowledge to make an operating DDF no matter whether one now the DDFCreator preferred or the XML editor. Shall the following chapters be conveyed for you, this knowledge among other things the language reference serves as a reference book''

==Description==
A very common language syntax which e.g. is also used in the other dialects at web pages or WAP in the Internet sides is XML (e''X''tensible ''M''arkup ''L''anguage). But you don't have to be an expert to make a new device description too manually. The following simple notes suffice:

Please take care that your editor doesn't store any (invisible) control characters. There won't be any problems at the Windows editor or PSPad. If you want to use Word or similar software, you should save the file in the raw document format (*.txt).

* The DMXControl dialect of XML requires for every opening tag always one (<tt><tag></tt>) closing (<tt></tag></tt>) tag. Only this one gets the last level completed just by implication day (e. g. <tt><item caption= "white" value="0" /></tt>).
* The final signs <tt>/></tt> and <tt></tag></tt> are semantically equivalent, also <tt><item caption="white" value="0" > </item></tt> is valid in this case.
* Every day can have attributes which you find professed in the table below. Every attribute value is started with an equals sign and the value must always be included in double apostrophes.
* All day and attribute identifiers are noted down at DMXControl in a small letter.
* The day has to be defined hierarchically. They also should make this recognizable about corresponding indents.
* As a rule, not cares about the order of the attributes of a day. Where it for once depends on the order anyway, you describe below explicitly.
* Comment are noted down in the form <tt><!- This is a comment —></tt>.
* E.g. you can have a look at xml files (therefore also the DMX DEVICEs files) in open form with the Internet Explorer.
 
So it was already this - we have a look at a simple example.

===Example: dimmed spotlight===
Every device should get an apt icon to receive an adapted representation in stage representation. This icon will be find in the subdirectory Images (<tt>Root:\Programme\DMXControl\Devices\Images</tt>).

{{Manual Box | en | Hint | The icons afterwards still can be changed in DMXControl. (In the context menu of the graphical view).
}}

The preceding line numbers of the following XML example file cannot be inserted; they serve only the description of the example:
<source lang=xml>
1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <device image="light.gif" initsequence=“set 0 128“ >
3 <channels>
4 <function channel="0" minvalue="0" maxvalue="255" name="Intensity" fade="yes" />
5 </channels>
6 <form width="177" height="85">
7 <deviceimage top="0" left="0" />
8 <devicename top="0" left="40" />
9 <deviceadress top="16" left="40" />
10 <slider channel="0" startvalue="0" endvalue="255" top="40" left="0" height="41" width="176" default="0" />
11 </form>
12 </device>
</source>

 

{| cellpadding="5" style="width: 100%;"
|- style="vertical-align:top;"
|style="width: 50px; margin: 5px;"|'''Row   1'''
|
|the Parser will informed about the used XML version.
|- style="vertical-align:top;"
|valign="top" style="width: 50px; valign: top; margin: 5px;"|'''Row   2'''
|
|the global description of the new type of device defines inclusive reference to the icon to be put and one ( initialization of the device the optional initsequence was demonstrated here, is but at a headlight only conditionally appropriately. The dimmer channel is (50%) ) put on DMX value 128 at the initialization here.
|- style="vertical-align:top;"
|valign="top" style="width: 50px; valign: top; margin: 5px;"|'''Row   3'''
|
|the DMX channels of the device are defined between line 3 and 5.
|- style="vertical-align:top;"
|valign="top" style="width: 50px; valign: top; margin: 5px;"|'''Row   4'''
|
|the channel description of the first channel is. This is always the channel numbers at zero important begin, i. e. the first channel is <tt>channel="0"</tt>. In addition, other parameters as well as the channel name are still put here.
|- style="vertical-align:top;"
|valign="top" style="width: 50px; valign: top; margin: 5px;"|'''Row   6'''
|
|the lines 6-9 describe the form, that is this one, to graphic coordinates in the context menu for the device picture, names and start address in the unity „Pixel“.
|- style="vertical-align:top;"
|valign="top" style="width: 50px; valign: top; margin: 5px;"|'''Row 10'''
|
|here the operating devices follow a slider with his graphic coordinates and the assignment to the channel in question with her qualities, in this example now. Operating devices like radio badges also could, drop down or badges are declared for other types of device here.
|}

{{Picture_with_subtitle |DMXC2_Manual_DDF_dimmer.png|3|Dimmer-DDF|center|200px}}

Three button become Pinup button, Move button, Close button will be generatedly per default generatedly on the top right side (see figure 3).

===Create a DDF===
Before you make a new DDF, please have a look on our webside in the device library whether a suitable or similar already give it to definitions for your device. To make a new DDF, you modify an existing DDF of a similar device best. This goes text been based change considerably faster than with the DDF Creator just with this. If you have completed your work, you simply put the xml file in the subdirectory in the DMXControl list „DEVICEs“himself has in your DMX installation as of and store the corresponding gif picture (in the format 32 x32 pixels, the transparency fashion proves itself) in the subdirectory „images“in this „DEVICE“List-. The device should be visible at the next start of DMXControl so.

===Syntax overview===
Every description contains four main parts (see figure 4):
*Description of global qualities <tt>device</tt> (in the example dimmed spotlight line 1-2)
*Description of the individual DMX channels <tt>channels</tt> (in the example dimmed spotlight line 3-5)
*Description of the graphic context menu <tt>form</tt> (in the example dimmed spotlight line 6-11)
*Prozedure code (not contained, optionally in the example)
{{Picture_with_subtitle |DMXC2_Manual_DDF-structure1.png|4|Basic structure of a DDF|center|500px}}

All form elements must on the will provide DDF form with graphic coordinates to the positioning. The elements „Label“ and „Line“ are passive and serve only the design of the surface. The remaining active elements of the form (also control element mentioned, e.g. on/off) can be used for the active control of the DMX device.

====Graphical elements====
The figure 5 shows a survey of all supported graphic elements. An assignment to the required syntax elements is carried out in the explanation texts.
{{Picture_with_subtitle |DMXC2_Manual_DDF-structure2.png|5|Graphic elements|center|500px}}

The following figure 6 illustrates the meaning of the graphic coordinates of the control elements:
{{Picture_with_subtitle |DMXC2_Manual_DDF-structure3.png|6|Graphic coordinates of the control elements|center|600px}}

====Functional elements====
The active control elements interact in 3 possible concepts with DMXControl or the device in which exactly one concept is selected at the definition of a concrete control element:

{| class="wikitable centered"
|- style="vertical-align:top;"
!
! Konzept
! Beschreibung
! Beispiel
|- style="vertical-align:top;"
|style="width: 10px"| 1
|style="width: 150px"| Channel/Value concept
|style="width: 200px"| The control element is assigned via the channel attribute to a concrete channel. Concrete values or ranges of values which are put at the activity of the control element are defined in the control element.
|style="width: 200px"| - option list   caption="Star sky" value="165" - Value range of the slider   startvalue="0" endvalue="255"
|- style="vertical-align:top;"
|style="width: 10px"| 2
|style="width: 150px"| Sequences
|style="width: 200px"| An instruction consequence which is executed when operating is defined in the control element as a string.
|style="width: 200px"| clicksequence= “set 1 75; set 2 100“
|- style="vertical-align:top;"
|style="width: 10px"| 3
|style="width: 150px"| Action/Procedures
|style="width: 200px"| A separately defined procedure contains more complex program instructions. The procedure is operate assigned via the action attribute and at everybody the control element executed.
|style="width: 200px"| action="SetGobo"
|}

This which Channel attribute and the action attribute can want to use alternatively in the control elements particularly means.

{{Manual Box | en | Hint | For many applications the first two concepts are sufficient.
}}

Like the complexity and cardinality of the 3 concepts grows, the running time requirements also increase. The simplest variant on the solution of a task should therefore always be chosen. Also at the channel description an action attribute can be used. This means that the procedure is called at every change of the channel value. In figure 7 an example is shown how different control elements can interact with the channels. „So like the complexity and channel_n“address and can over the 3 mentioned above concepts be put. The current value, obliged to it for a control element are, are addressed more than one name freely eligible for office (reference) assigned to the control element here „control_n“bezeichnet. Im following example is for three control elements „Actionses“and additional „Reference names“assigned. And therefore should, as a rule these Actionses be able to do one or '''put''' several Channel values „'''set''' name“being described. Furthermore there is one „action“ assigned to the channel_3. This is intended to read and to inform about to the control elements the current channel values „assigned to the channel_3. Scheduled, this one are '''Get''' name this for this“get since she must '''read''' current channel values.
{{Picture_with_subtitle |DMXC2_Manual_DDF-structure4.png|7|Interaction of control elements|center|600px}}

{{Manual Box | en | Hint | The markings of the buttons don't have a meaning here.
}}

===Syntax===
This chapter describes the syntax of the device and form configuration files of DMXControl.

====Generic attributs====
{{Manual Box | en | Hint | Attributes often recurring are described to it globally once for the shortening with the same meaning after the following tables here.
}}

{| class="wikitable centered"
|- style="vertical-align:top;"
! Reference
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|style="width: 50px"| GP1
|style="width: 75px"| value
|style="width: 200px"| Assigned DMX value
|style="width: 100px"| byte
|style="width: 100px"| 0, 128, 255
|- style="vertical-align:top;"
|style="width: 50px"| GP2
|style="width: 75px"| caption
|style="width: 200px"| Descriptive enumeration value. Explanatory name for an attitude.
|style="width: 100px"| string
|style="width: 100px"| Dimmer, Strobe, usw.
|- style="vertical-align:top;"
|style="width: 50px"| GP3
|style="width: 75px"| top
|style="width: 200px"| Relative x-coordinate of the element of the left upper corner
|style="width: 100px"| integer
|style="width: 100px"| top=“150“
|- style="vertical-align:top;"
|style="width: 50px"| GP4
|style="width: 75px"| left
|style="width: 200px"| Relative x-coordinate of the element of the left upper corner.
|style="width: 100px"| integer
|style="width: 100px"| left=“100“
|- style="vertical-align:top;"
|style="width: 50px"| GP5
|style="width: 75px"| width
|style="width: 200px"| Width of the element
|style="width: 100px"| integer
|style="width: 100px"| width=“80“
|- style="vertical-align:top;"
|style="width: 50px"| GP6
|style="width: 75px"| height
|style="width: 200px"| Height of the element
|style="width: 100px"| integer
|style="width: 100px"| height=“30“
|}

{{Manual Box | en | Hint | All coordinate details (top, left, width, height) are indicated in pixel.
}}

====Device description====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|style="width: 100px"| <device>
|style="width: 75px"|
|style="width: 200px"| '''Level 1'''
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| image
|style="width: 200px"| Icon filename.
|style="width: 100px"| string, Filename.gif
|style="width: 100px"| Moon.gif
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| initsequence
|style="width: 200px"| Sets initial values for the individual DMX channels of the device
|style="width: 100px"| Optional use e.g. for scanner/moving head's start position
|style="width: 100px"| set 0 15; set 7 128;
|- style="vertical-align:top;"
|style="width: 100px"| <information>
|style="width: 75px"|
|style="width: 200px"| '''Level 2''' Supplementary comment.
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <name>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Arbitrary text.
|style="width: 100px"|
|style="width: 100px"| Custom Scanner
|- style="vertical-align:top;"
|style="width: 100px"| <vendor>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Arbitrary text (manufacturer).
|style="width: 100px"| optional
|style="width: 100px"| Showtec
|- style="vertical-align:top;"
|style="width: 100px"| <deviceidentifier>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Arbitrary text (manufacturer identifier.
|style="width: 100px"| optional
|style="width: 100px"| TG-3
|- style="vertical-align:top;"
|style="width: 100px"| <author>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Arbitrary text (originator).
|style="width: 100px"| optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <comment>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Arbitrary text (comment).
|style="width: 100px"| optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <help>
|style="width: 75px"|
|style="width: 200px"| '''Level 2''' Help text (ASCII).
|style="width: 100px"| optional
|style="width: 100px"|
|}

====Channel description====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|style="width: 100px"| <channels>
|style="width: 75px"|
|style="width: 200px"| '''Level 2''' For every DMX channel is one “<function>”-part to define
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <function>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<channels>“
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel
|style="width: 200px"| Internal DMX channel number channel no. must always of 0 climbing without interruption be defined for the individual channels
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| minvalue
|style="width: 200px"| Minimal DMX value
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| maxvalue
|style="width: 200px"| Maximal DMX value
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Descripting name for the channel.
|style="width: 100px"| string
|style="width: 100px"| Intensity
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| fade
|style="width: 200px"| Channel fading
|style="width: 100px"| string
|style="width: 100px"| yes,no
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| type
|style="width: 200px"| Channel typ Important for the internal data handling
|style="width: 100px"| string
|style="width: 100px"| dimmer, r,g,b, pan, panfine, tilt, tiltfine, color, gobo
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at change of the channel value
|style="width: 100px"| string optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <virtual>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<channels>“
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <channel>
|style="width: 75px"|
|style="width: 200px"| '''Level 4''' Subtag from “<virtual>“
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel
|style="width: 200px"| Internal DMX channel number The three rgb channels assigned to the virtual dimmer
|style="width: 100px"| integer
|style="width: 100px"|
|}

{{Manual Box | en | Hint | The channel type (type) also should allocate channel for everybody
become provided that this channel to the type matches. E.g. it doesn't make sense to describe every channel as a dimmer.
}}

{|
|- style="vertical-align:top;"
|style="width: 100px"| dimmer
|style="width: *"| reserved for channels these regulate the intensity
|- style="vertical-align:top;"
|style="width: 100px"| r,g,b
|style="width: *"| reserve for channels of RGB LED equipment, <tt>r</tt> for the red channel, <tt>g</tt> for the green channel, <tt>b</tt> for the blue channel. On the one hand, <tt>r, g, b</tt> are for the type it HAL needs in DMXControl. This also means, this in the graphical view the colors of the spotlights be shown. One can one racks use this in the program configuration under « graphical view » and then at « symbol » « representation of the colors instead of graphic ». On the other hand, the type also for the one into the 2.12 new one LED's run light generator required becomes.
|- style="vertical-align:top;"
|style="width: 100px"| a,w
|style="width: *"| reserve for channels of (RGB)A as and (RGB)W LED devices, <tt>a</tt> for the amber channel, <tt>W</tt> for the white channel. The type <tt>a</tt> and <tt>w</tt> aren't supported by DMXControl yet the device, however, is appropriately since amber or white channel make a bigger and bigger contribution to the market and therefore perhaps are supported by DMXControl soon, too with additional.
|- style="vertical-align:top;"
|style="width: 100px"| pan, panfine
|style="width: *"| reserve for the Pan channels of scanners, moving heads or similar equipment. How pan is and panfine assigned to the channel for the rough control the channel for the fine control at 16 bits of device.
|- style="vertical-align:top;"
|style="width: 100px"| tilt, tiltfine
|style="width: *"| as in the case of pan and panfine but for the tilt axis.
|- style="vertical-align:top;"
|style="width: 100px"| color, gobo
|style="width: *"| The appropriate Farb and Goborad channels can be assigned to (importantly to color & gobo lists)
|- style="vertical-align:top;"
|style="width: 100px"| c, m, y
|style="width: *"| reserviert für Kanäle von CMY-Geräten, <tt>c</tt> für den Cyan Kanal, <tt>m</tt> für den magenta Kanal und <tt>y</tt> für den gelben Kanal. Die types <tt>c, m, y</tt> werden noch nicht von DMXControl unterstützt sind aber sinnvoll.
reserved for CMY devices, <tt>c</tt> for the cyan channel, <tt>m</tt> for the magenta channel, <tt>y</tt> for the yellow channel. The type <tt>c, m, y</tt> aren't supported by DMXControl make sense, however, yet.
|- style="vertical-align:top;"
|style="width: 100px"| other
|style="width: *"| all other channels don't need a type description
|}

{{Manual Box | en | Hint | The ones for RGB devices reserved type's are important the HAL (Hardware Abstraction Layer) since version 2. 11 in which then be able to the adjusted colors of the spotlight, be represented in the graphical view too. Also for version 2.12, here they also are needed for the RGB running light generator.}}

====Menue description====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|style="width: 100px"| <form>
|style="width: 75px"|
|style="width: 200px"| '''Level 2''' Subtag from “<device>“
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| width height
|style="width: 200px"| See generic attribute GP5; GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <deviceimage>
|style="width: 75px"|
|style="width: 200px"| '''Level 3'' Subtag from “<form>“; Absolute position of the shown picture
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <devicename>
|style="width: 75px"|
|style="width: 200px"| '''Level 3'' Subtag from “<form>“; Absolute position of the shown name
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <deviceaddress>
|style="width: 75px"|
|style="width: 200px"| '''Level 3'' Subtag von “<form>“; Absolute position of the shown base address
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|}

====Control elements====
=====Position control=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_Manual_DDF_position_field_cartesian.png]]  [[file:DMXC2_Manual_DDF_position_field_polar.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<position>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Creates a positioning field for positioning from scanners or moving heads.
|colspan="2" style="width: 100px"| By a click on the button down on the right in the DDF you can switch between a cartesian and polar positioning.
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|}

{{Manual Box | en | Hint | The position pointer can be placed by initsequenz
}}

=====Slider=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_manual_DDF_slider.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<slider>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Creates a slider
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel
|style="width: 200px"| assigned channel alternative for action
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| startvalue
|style="width: 200px"| Value range of the Slider (lower value)
|style="width: 100px"| integer
|style="width: 100px"| startvalue="0"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| endvalue
|style="width: 200px"| Value range of the Slider (uper value)
|style="width: 100px"| integer
|style="width: 100px"| endvalue="255"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| tickfreq
|style="width: 200px"| Scaling, distance of the scale subdivision
|style="width: 100px"| integer
|style="width: 100px"| tickfreq="32"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| smallchange
|style="width: 200px"| Change rate e.g. at the up down keys
|style="width: 100px"| integer (VB-properties)
|style="width: 100px"| smallchange="20"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| largechange
|style="width: 200px"| Change rate e.g. at the mouse click (not draged)
|style="width: 100px"| integer (VB-properties)
|style="width: 100px"| largechange="50"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Referenz name for procedure code (variable name)
|style="width: 100px"| string optional
|style="width: 100px"| StrobeSpeed
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at change at the Slider alternative channel
|style="width: 100px"| string optional
|style="width: 100px"| SetSpeed
|}

=====Dropdown=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_manual_DDF_dropdown.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<dropdown>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from“<form>“; Creates a dropdown menu.
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width
|style="width: 200px"| See generic attribute GP3 bis GP5
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel
|style="width: 200px"| Assigned channel alternative for action
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Referenz name for procedure code (variable name)
|style="width: 100px"| string optional
|style="width: 100px"| Gobo
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at change of a dropdown entries, alternative for channel
|style="width: 100px"| string optional
|style="width: 100px"| SetGobo
|- style="vertical-align:top;"
|style="width: 100px"| <item>
|style="width: 75px"|
|style="width: 200px"| '''Level 4''' Subtag from “<dropdown>“
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| caption
|style="width: 200px"| Explanatory name
|style="width: 100px"| string
|style="width: 100px"| Clear
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| value
|style="width: 200px"| DMX value for caption
|style="width: 100px"| integer
|style="width: 100px"| value="0"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| minvalue maxvalue
|style="width: 200px"| Value range for caption for the diplayed of the dropdown entry.
|style="width: 100px"| integer
|style="width: 100px"| minvalue="10" maxvalue="26"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| color
|style="width: 200px"| Show a square with the assigned color before caption.
|style="width: 100px"| hex
|style="width: 100px"| color="#ff0000" Color Red
|- style="vertical-align:top;"
|style="width: 100px"| <colorlist>
|style="width: 75px"|
|style="width: 200px"| '''Level 4''' Subtag from “<dropdown>“ All entries of the in color list assigned to the device insert.
|style="width: 100px"| optional a substitute/ addition for Item
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <gobolist>
|style="width: 75px"|
|style="width: 200px"| '''Level 4''' Subtag from“<dropdown>“ All entries of the in gobo list assigned to the device insert.
|style="width: 100px"| optional a substitute/ addition for Item
|style="width: 100px"|
|}

=====Options=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_manual_DDF_options.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<options>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Creates a radio button field
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left
|style="width: 200px"| See generic attribute GP3 & GP4
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel
|style="width: 200px"| Assigned channel alternative foraction
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at change of a radio buttons, alternative for channel
|style="width: 100px"| optional
|style="width: 100px"| SetGoboSpeed
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Referenz name for procedure code (variable name)
|style="width: 100px"| string optional
|style="width: 100px"| GoboSpeed
|- style="vertical-align:top;"
|style="width: 100px"| <option>
|style="width: 75px"|
|style="width: 200px"| '''Level 4''' Subtag from “<options>“
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| caption
|style="width: 200px"| See generic attribute GP2
|style="width: 100px"| string
|style="width: 100px"| off
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| value
|style="width: 200px"| DMX value for caption
|style="width: 100px"| integer
|style="width: 100px"| 0
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left
|style="width: 200px"| See generic attribute GP3 & GP4, relativ position for positioning from “<options>“
|style="width: 100px"| integer
|style="width: 100px"| left="0" top="0"
|}

=====On/Off-Button=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_Manual_DDF_onoff.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<onoff>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Creates a button as switch
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel
|style="width: 200px"| Assigned channel alternative for action
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at pushing the buttons alternative for channel
|style="width: 100px"| string optional
|style="width: 100px"| SetLampOnOff
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Referenz name for procedure code (variable name)
|style="width: 100px"| string optional
|style="width: 100px"| LampOnOff
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| caption
|style="width: 200px"| Explanatory name
|style="width: 100px"| string
|style="width: 100px"| On/Off
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| color
|style="width: 200px"| Hex RGB color value of the button
|style="width: 100px"| hex
|style="width: 100px"| color="#00ff00" color green
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| onvalue
|style="width: 200px"| DMX value for button ON
|style="width: 100px"| integer
|style="width: 100px"| onvalue="150"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| offvalue
|style="width: 200px"| DMX value for button OFF
|style="width: 100px"| integer
|style="width: 100px"| offvalue="0"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| onsequence
|style="width: 200px"| Execute a Sequence, by switching to ON
|style="width: 100px"| string
|style="width: 100px"| "set 0 230; set 1 25"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| offsequence
|style="width: 200px"| Execute a Sequence, by switching to OFF
|style="width: 100px"| string
|style="width: 100px"| "set 0 0; set 1 0"
|}

=====Command-Button=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_manual_DDF_command.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<command>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag for “<form>“; Creates a button as push button.
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at pushing the button.
|style="width: 100px"| string optional
|style="width: 100px"| SetReset
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Referenz name for procedure code (variable name)
|style="width: 100px"| string optional
|style="width: 100px"| Reset
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| caption
|style="width: 200px"| Explanatory name
|style="width: 100px"| string
|style="width: 100px"| Reset
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| color
|style="width: 200px"| Hex RGB color value of the button
|style="width: 100px"| string
|style="width: 100px"| color="#0000ff" color blue
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| clicksequence
|style="width: 200px"| Activity to be started at the button click is specified in the attribute
|style="width: 100px"| string
|style="width: 100px"| "save 0; set 0 230; hold 5500; restore 0"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| downsequence
|style="width: 200px"| Activity to be started at push down the button is specified in the attribute
|style="width: 100px"| string
|style="width: 100px"| "save 0; set 0 230; hold 5500; restore 0"
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| upsequence
|style="width: 200px"| Activity to be started at relase the button is specified in the attribute
|style="width: 100px"| string
|style="width: 100px"| "save 0; set 0 230; hold 5500; restore 0"
|}

=====Colorpicker=====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_manual_DDF_colorpicker.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<colorpicker>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Creates a colorpicker.
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel1
|style="width: 200px"| Assignment to 1. channel red oder cyan, alternative for action
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel2
|style="width: 200px"| Assignment to 2. channel green or magenta, alternative for action
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| channel3
|style="width: 200px"| Assignment to 3. channel blue oder yellow, alternative for action
|style="width: 100px"| integer optional
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Referenz name for procedure code (variable name)
|style="width: 100px"| string optional
|style="width: 100px"| ColRGB
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| action
|style="width: 200px"| Call of a procedure at changing a color, alternative for channel1-3
|style="width: 100px"| string optional
|style="width: 100px"| SetColRGB
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| mode
|style="width: 200px"| Choice of the two modes RGB or CMY
|style="width: 100px"| string
|style="width: 100px"| mode=“cmy“
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| layout
|style="width: 200px"| Choice of two different layouts from the Colorpickers
|style="width: 100px"| integer
|style="width: 100px"| layout="1"
|}

'''Beispiel:'''
<source lang=xml>
<colorpicker mode="rgb" channel1="0" channel2="1" channel3="2" layout="2" top="40"
left="0" height="75" width="177"/>
</source>

{{Manual Box | en | Hint | Please keep the mouse button pushed down if you want to change the setting in the color bar over the drop down menu. A direct input of the numeric value is also possible.
Become the color values in procedures about name:colorchannel provided with references ({ColRGB:1}; {ColRGB:2}; {ColRGB:3})
}}

====Passive design elements====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierachie and properties
! Notice
! Example
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_Manual_DDF_line.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<line>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Design element; Creates a line.
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| x1; y1
|style="width: 200px"| Start coordinate of the line
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| x2; y2
|style="width: 200px"| End coordinate of the line
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|colspan="5" style="text-align:center"| [[file:DMXC2_Manual_DDF_label.png]]
|- style="vertical-align:top;"
|style="width: 100px"| '''<nowiki><label></nowiki>'''
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from “<form>“; Design element; additional description of an operating device.
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| top left width height
|style="width: 200px"| See generic attribute GP3 bis GP6
|style="width: 100px"| integer
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| caption
|style="width: 200px"| Text to be shown
|style="width: 100px"| string
|style="width: 100px"| CMY Mischung
|}

'''Example:'''
[[file:DMXC2_Manual_DDF_Giotto-Spot.png|miniatur|center|600px|Bild 8: DDF Giotto Spot 400]]

{{Manual Box | en | Advanced | You find this DDF in the [http://www.dmxcontrol.de/Geraetedefinitionen/Geraetebibliothek.html#SGM device libary (at the moment not online)] on the DMXControl Website.
}}

====Help====
In fig. 9 shows an example of a help menu, help menus are optional. It is recommended to announce the DMX occupancy of the device here. The help description is carried out in the ASCII format. Please increase the clarity by formatting with tabulator signs or underlinings. The help can one by click on the question mark button (next to the Pin badge) and be turned off.

[[Bild:DMXC2_Manual_DDF_help.png|miniatur|center|600px|Bild 9: Hilfemenü eines DDF's]]

====Sequences====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Operation
! Meaning
! Example
|- style="vertical-align:top;"
|style="width: 150px"| save >channel<
|style="width: 250px"| Storing the current channel value of the DMX channel intermediately >channel<
|style="width: 200px"| "save 0; set 0 230; hold 5500; restore 0"
|- style="vertical-align:top;"
|style="width: 150px"| set >channel< >value<
|style="width: 250px"| Set the channel >channel< to value >value<
|style="width: 200px"| "save 0; set 0 230; hold 5500; restore 0"
|- style="vertical-align:top;"
|style="width: 150px"| hold >time<
|style="width: 250px"| Timer (wait >time< in ms)
|style="width: 200px"| "save 0; set 0 230; hold 5500; restore 0"
|- style="vertical-align:top;"
|style="width: 150px"| restore >channel<
|style="width: 250px"| Move the value of the DMX channel stored intermediately >channel< back again.
|style="width: 200px"| "save 0; set 0 230; hold 5500; restore 0"
|}

===Procedurs (advanced programming options)===
The device and form configuration of DMXControl also permits the programming of algorithmic changes of the DMX signals which are executed automatically with the operation of control elements like onoff button, dropdown menu or slider.

So you can set conditions and formulae the values which are assigned to the control elements about logical. E.g. the procedures serve to be able to treat multiple occupations of a channel (e.g. gobo rotation lies on the same channel as the gobo selection) so that the value can be calculated differently depending on rotational speed.

These procedures also permit you the programming of dependences of the channels or operating devices of a device, any colors e.g. you connect certain colors with gobos in a firm or algorithmic assignment or you organize certain speeds.

Also can at devices with two color wheels, the colors then select more than one drop down or predefined colors have drop down at RGB or CMY devices assigned to one for themselves so.

====General principles====
The procedures become this one as an action attribute <tt><function></tt> tags (channels) or the control elements e.g. <tt><onoff></tt>, <tt><slider></tt> or <tt><dropdown></tt> assigned.
With operation of corresponding control elements the code of the procedure is interpreted and executed automatically.
The action attribute is against this into assigned, a channel the <tt><function></tt> tag she is executed so at every change of the belonging channel value.
Using the procedures „References“on the values of the control elements which are declared by the <tt>Name</tt> attribute within the form definition of the control elements e.g.

<source lang=xml>
<dropdown top="16" left="207" width="113" name="color_color" action="SetColor">
</source>

This means: The procedure SetColor is executed with operation of the drop down menu and the value of the drop down menu is submitted to the called procedure <tt>SetColor</tt> as a variable <tt>color_color</tt>.

Furthermore implicit references as a default assignment to the channels exist. E.g. that way is <tt>channel_2</tt> with the channel (<tt>function</tt>) with <tt>channel=2</tt> binded, also the action <tt>GetColor</tt> assigned.

<source lang=xml>
<function channel="2" minvalue="0" maxvalue="255" name="Color" fade="no"
action="GetColor" colorchannel="yes"/>
</source>

Till now, variables in the real meaning as freely verifiable loft values aren't defined.

====Basic syntax elements and conventions====
While the references are marked by her name ('''"color_color"'''), the current value is addressed by curly brackets of the assigned control element ('''"{color_color}"''').

To simplify the interpretation of the procedure code by a Parser, some conventions you unfortunately must observe although they seem not very user friendly are agreed on in the present program release. For comparison purposes and the following tables on this one always provide a generic language variant to right sides on the easier to learn.

The following signs serve as sync separators:
{| class="wikitable centered"
|- style="vertical-align:top;"
! Operation
! Meaning
|- style="vertical-align:top;"
|style="width: 75px"| !
|style="width: 300px"| start with an command
|- style="vertical-align:top;"
|style="width: 75px"|  |
|style="width: 300px"| separate the individual components
|- style="vertical-align:top;"
|style="width: 75px"|  $
|style="width: 300px"| conclude an order
|}

The following arithmetical operations are supported:
{| class="wikitable centered"
|- style="vertical-align:top;"
! Operation
! Meaning
|- style="vertical-align:top;"
|style="width: 75px"|  +
|style="width: 300px"| addition
|- style="vertical-align:top;"
|style="width: 75px"|  -
|style="width: 300px"| subtraction
|- style="vertical-align:top;"
|style="width: 75px"|  *
|style="width: 300px"| multiplication
|- style="vertical-align:top;"
|style="width: 75px"|  /
|style="width: 300px"| division
|- style="vertical-align:top;"
|style="width: 75px"|  mod
|style="width: 300px"| modulo-Operation (issues the remainder of the mod division in the form of result)
|}

Every expression must be surrounded by a bracket to be calculated.
The following examples illustrate the use of arithmetical operations:
{| class="wikitable centered"
|- style="vertical-align:top;"
! DMXControl code
! Generic language variant
|- style="vertical-align:top;"
|style="width: 280px"| !set_channel|2|(227+{color_speed})$
|style="width: 280px"| channel_2 := 227 + color_speed
|- style="vertical-align:top;"
|style="width: 280px"| !set_channel|3|((({gobos_gobo}-1)*51)+25)$
|style="width: 280px"| channel_3 := (gobos_gobo-1)*51+25
|- style="vertical-align:top;"
|style="width: 280px"| !set_control|gobos_speed|((({channel_3}-1) mod 51)-26)$
|style="width: 280px"| gobos_speed := ((channel_3 -1) mod 51)-26
|}

The used standard operators have the following semantics:
{| class="wikitable centered"
|- style="vertical-align:top;"
! Operation
! Meaning
|- style="vertical-align:top;"
|style="width: 160px"| set_control | >cntr< | >val<
|style="width: 400px"| the control element puts >val< on the value of the expression with the given name >cntr<
|- style="vertical-align:top;"
|style="width: 160px"| set_channel | >ch< | >val<
|style="width: 400px"| >Val< submits the value to the indicated channel >ch<
|}

The following relational operators can be used:
{| class="wikitable centered"
|- style="vertical-align:top;"
! Operation
! Alternative notation
! Meaning
|- style="vertical-align:top;"
|style="width: 185px"| >
|style="width: 185px"| > - &gt; - |gt|
|style="width: 185px"| greater
|- style="vertical-align:top;"
|style="width: 185px"| <
|style="width: 185px"| < - &lt; - |lt|
|style="width: 185px"| smaller
|- style="vertical-align:top;"
|style="width: 185px"| =
|style="width: 185px"| = - &eq; - |eq|
|style="width: 185px"| eaqual
|}

With the help of the comparing operations conditions can be formulated since DMXControl supports the if instruction.
{| class="wikitable centered"
|- style="vertical-align:top;"
! DMXControl code
! Generic language variant
|- style="vertical-align:top;"
|style="width: 280px"| !if|{channel_3} < 1|
|style="width: 280px"| if channel_3 < 1 then
|}

{{Manual Box | en | Hint | The procedure “INITCONTROLS”do you execute when opening the form around which Controls put toward the values which are provided by the current DMX values. Into this, so only "Get" functions should be called! However, it is recommended Initcontrols doesn't have to be defined so that the Controls always show the current condition of the device.
}}

====XML syntax of the procedure code====
{| class="wikitable centered"
|- style="vertical-align:top;"
! Tag
! Attribute
! Hierarchy and properties
! Meaning
! Example
|- style="vertical-align:top;"
|style="width: 100px"| '''<code>''' 
|style="width: 75px"|
|style="width: 200px"| '''Level 2''' Subtag from "<device>" includes all procedures
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"| <procedure>
|style="width: 75px"|
|style="width: 200px"| '''Level 3''' Subtag from "<code>" includes the code of the procedures
|style="width: 100px"|
|style="width: 100px"|
|- style="vertical-align:top;"
|style="width: 100px"|
|style="width: 75px"| name
|style="width: 200px"| Name of the procedures
|style="width: 100px"| string
|style="width: 100px"| SetGobo
|}

====An example prozedure====
This example shows a procedure that sets the values of the control elements "color_color" and "color_speed" a moving heads in relation to the current DMX-value of channel 2 (color changer). The Mac 250 + has 4 options for the color wheel:

* Solid color (first If in the example below),
* Turn clockwise (2. If in the example below),
* Turn counter clockwise (3 if in the example below), as well as
* random colors with different speeds (4. If in the example below).

Here, the declarations in the configuration file, the relevant variables are highlighted in bold:

<source lang=xml>
<function channel="2" minvalue="0" maxvalue="255" name="Color" fade="no"
action="GetColor"/>
</source>

“color_color” is the reference to the value of the dropdown menu for selecting a color.

<source lang=xml>
<dropdown top="16" left="207" width="113" name="color_color" action="SetColor">
</source>

“color_speed” is the reference to the value of the slider to the speed:

<source lang=xml>
<slider top="16" left="320" height="25" width="65" startvalue="0" endvalue="18"
tickfreq="9" smallchange="1" largechange="5" name="color_speed" action="SetColor"/>
</source>

The procedure split the DMX_Werte of the channel 2 in 4 intervals and performs different assignments. The current value is checked so and the controls are adjusted accordingly.

{| class="wikitable centered"
|- style="vertical-align:top;"
! DMXControl code
! Generic language variant
|- style="vertical-align:top;"
|style="width: 280px"| <source lang=XML><procedure name='GetColor'></source>
|style="width: 280px"| <source lang=C>Procedure GetColor( )</source>
|- style="vertical-align:top;"
|style="width: 280px"| 
<source lang=xml>
!if|{channel_2} < 208|
!set_control|color_color|
{channel_2}$
!set_control|color_speed|0$
|
!if|({channel_2} > 207) and
({channel_2} < 227)|
!set_control|color_color|-1$
!set_control|color_speed|
(226-{channel_2})$
$
!if|({channel_2} > 226) and
({channel_2} < 246)|
!set_control|color_color|-2$
!set_control|color_speed|
({channel_2}-227)$
$
!if|({channel_2} > 245) and
({channel_2} < 256)|
!set_control|color_color|-3$
!set_control|color_speed|
((255-{channel_2}) * 2)$
$
$</source>
|style="width: 280px"| <source lang=C>
begin
if channel_2 < 208 then
color_color := channel_2;

color_speed := 0;
(else)
if (channel_2 > 207) and
(channel_2 < 227) then
color_color := -1;
color_speed := 226-channel_2;

(else)
if (channel_2 > 226) and
(channel_2 < 246) then
color_color := -2;
color_speed :=channel_2-227

(else)
if (channel_2 > 245) and
(channel_2 < 256) then
color_color := -3;
color_speed := (255-channel_2) * 2;

;</source>
|- style="vertical-align:top;"
|style="width: 280px"| <source lang=XML></procedure></source>
|style="width: 280px"| <source lang=C>end</source>
|}

==Tip(s)==

'Minvalue' and 'maxvalue' the control attributes are new in DMXControl 2.12 drop. By setting these attributes also the right double down entry is displayed if the current DMX value of value is different, but still in the range min/max value is.

==Links and references==
Links
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Pack_And_Go_DMXC2
| TextBackwards = Pack And Go Function
| LinkForwards = DDFCreator_DMXC2
| TextForwards = DDFCreator
}}
[[de: DDF_DMXC2]]
[[Category: DMXControl 2]]

DMXIn remote control DMXC2

2025-03-02T19:19:56Z

Jnoetzel: /* Configuring the command assignment */

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = MIDI_remote_control_DMXC2
| TextBackwards = MIDI remote control
| LinkForwards = Program_settings_DMXC2
| TextForwards = Program settings
}}
{{Start-LaTeX}}
==Overview==

DMXControl offers the possibility of using the DMX receipt of suitable interfaces.
One gets through ''remote control'' of DMXControl by e.g. another light desk nothing more in the way with that. 
The configuration is quite similar to be able send the full range of values 0-255 to the MIDI remote control with the advantage at DMX and not as in the case of midi only 0-127. 
 
With the DMXIn remote control DMXControl can in all modules by external steer DMX desk. So e.g. being able to channels in DMXControl by faders change, effects start, masters and sub-masters steer, attitudes of the Soundanalyzers change etc. 
Through this one programming of the single ones weds DMXIn channel can be made an external operation adapted to the claims of one's own for DMXControl. This is primarily advisable at events because one can access corresponding actions with respect to hardwares. Also at the use of DMXControl in the theater area one can proceed with the DMXIn remote control by Softpatch or sub-master directly over a desk. 

By use of banks values are different attitudes e. g. different Locations, set etc. possible for the assignment the different command to the individual DMX channels or DMX. 
 
Apart from the assignment to the commands there also is the possibility of the Softpatches. Every initial channel is put directly on an internal DMXControl channel. Through this the device lying at this channel can be headed directly. The disadvantage is if the device is moved in the universe, also must be assigned to the Softpatch newly. 
The better way is to assign the appropriate DMXIn channel to the channel of the device directly even if it is a little more effort. The assignment remains unchanged also after moving the device. 
 
The configuration window should be used in the way that the DMX channels to which DMXControl commands shall be assigned are represented. The defined control elements have to be understood therefore as such rather virtually, they correspond taken exactly to a DMX channel. 
 

==Description and configuration.==
You configure correctly, you can check at the channel overview whether your interface for DMX into. If you have switched this to the in mode on the left below. Here version these are shown to DMX in values instead of the current ones now, the corresponding values in the table see this means you at channel changes at the desk. 
 
{{Manual Box | en | Hint | In the DMXIn view the equipment assigned to the channels is also shown on the view, however, a change of the values doesn't have any effect on the device.}} 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_channel_overview.png|1|Channel overview DMX-In|center}} 
 

===The configuration window===
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_Menue.png|2|Open the configuration window|right|300px}}
For the configuration of the DMXIn remote control you must the DMXIn remote control configuration window over the menu « Configuration « Menu item « DMXIn remote control » calling first (see figure 2). 
Since DMXControl 2.12 the configuration window is divided up on two register riders. On the one hand the register pus for the control elements (see figure 3) and the register rider for the command assignment to the control elements (see figure 4).
In the two choices as well as the Softpatchbereich is visible for it. The table is the DMXIn channels behind the rider control elements for the DMX channel configuration, to the appropriate DMX channel. Here every channel can into the table openings' control element a name of its own be assigned. DMX channel can be assigned so that one can subdivide a channel into several areas in which different actions are executed the corresponding in the wider range of values. E.g. the assignment of different color configurations of one would be LED headlight a possible application’s to a fader.
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_control_elements.png|3|Configuration window DMXIn remote control - control elements - |center}} 
The table is behind the rider command assignment (see figure 4) with the assignment of the commands to the corresponding channel configurations, all commands can be applied to the different DMXControl modules here.
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_command_assignment.png|4|Configuration window DMXIn remote control - command assignment - |center}} 
External DMX channels can directly be assigned by e.g. a desk to the internal DMXControl channels in the Softpatch area. The external channel number and on right can on the left into this one two inputs is typed in by a click on the button &laquo do this one internal channel number « Add « is the assignment written down on the list. 
Highlighted assignments in the list can by a click on the button « Delete » being deleted again.

===Configuring the DMX channel configuration===
By a click on the button « Add » below the DMX channel configuration you produce a new control element (see figure 5). The name « new control element » an informative name can be changing now. The button « Delete » the straight highlighted control element deletes with the button « Arrow up/down » the entries can be moved and therefore sorted (see figure 6). 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_control_element.png|5|Added new control element|center}} 
This is an opportunity for the clear naming one indicates the channel and the DMX value area as names. At « DMX channel » the corresponding channel is indicated and at now « Min. » or « Max. » the corresponding range of values. 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_configuration.png|6|Configuration of four control elements for 2 DMX channels|center}} 
The channel 1 with the range of values 0 – 255 e.g. one could use for the master or a sub-master so that at movement of the fader the master or sub-master follows the fader movement. For the channel 2 the range of values is subdividedly, here areas in four e.g. one could deposit four different effects or also four colors of LED headlights. 
 
{{Manual Box | en | Hint | The control elements of the DMX channel configuration are not project-related stored. You can find it in <tt>application data/pop soft/DMXControl/DMXInRemote.dat</tt>.}} 
 

===Configuring the command assignment===
The command assignment is, carried out in the lower table window control elements dip the names of the control elements defined in the upper window under the table head here. 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_configuration2.png|7|Tab of the command assignment, add to a new order bank|center}} 
 
To assign commandsto the corresponding control elements now, must once by the badge « Add » a new bank being laid out. By laying out different banks different assignments can be made to the control elements 
 
{{Manual Box | en | Hint | The command assignment is, stored project-relatedly this one unlike the DMX channel configuration
File name in the project list is: <tt>PROJEKTNAME.DMXInRemote</tt>}} 
E.g. with the name ''Show1'' then passes the possibility of assigning a corresponding command to the individual control elements by production of a new bank, under module then becomes at all control elements « &raquo deactivates » shown. 
The individual table columns have following meaning and functions:
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{Manual Box | en | Hint | Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

==Controls==

{{Picture_with_subtitle |DMXC2_Manual_DMXIn_activation.png|8|DMXIn activation window|right|200px}}
The configuration of the control elements is carried out this one [[MIDI_control_DMXC2|MIDI control]] elements almost analogously to this one. Every control element corresponds to a DMX channel whose value is used for the configured command.
Another this one lets himself on the right side « Softpatch » configuring. Values of the DMX can into be distributed on arbitrary other DMX out channels with that. This is useful to e.g. only steer a certain equipment with an external light desk.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

 

==Module commands==

* Modul: '''DMX remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the DMX remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the command of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some commands to ensure a correct function.
|}

==Tipp(s)==

{{Manual Box | en | Attention | It is valid for DMXControl 2.11 and smaller:So that these attitudes also are realized, the window must « DMXIn remote control » open and there the checking box « DMXIn remote control » is active being active. For DMXControl 2. 12 is no longer required.
}}
 
Here short instructions to proceed for the DMX4All interface as in the case of the facilities are:
{{Picture_with_subtitle |DMXC2_Manual_output_plugin_administration.png|9|Output plugin administration at the choice of the DMX4All-Plugins|center}}

Open the Output plugin administration (menu Settings > Output plugins). There you click this is responsible for her interface on the Plugin. Click on the button « Configure selected plugin » around for the individual attitudes hers. Here exemplary the dialog of the ''DMX4All'' plugin:
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_DMX4All_configuration.png|10|Activation of the DMXIn function of the DMX4All-plugin|center}}

Here you carry out the attitudes, hers to activate interfaces around the DMX entrance now. In the example this is the checking box « DMX-in » active.
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = MIDI_remote_control_DMXC2
| TextBackwards = MIDI remote control
| LinkForwards = Program_settings_DMXC2
| TextForwards = Program settings
}}
[[de: DMXIn-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

DMXIn remote control DMXC2

2025-03-02T19:19:14Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = MIDI_remote_control_DMXC2
| TextBackwards = MIDI remote control
| LinkForwards = Program_settings_DMXC2
| TextForwards = Program settings
}}
{{Start-LaTeX}}
==Overview==

DMXControl offers the possibility of using the DMX receipt of suitable interfaces.
One gets through ''remote control'' of DMXControl by e.g. another light desk nothing more in the way with that. 
The configuration is quite similar to be able send the full range of values 0-255 to the MIDI remote control with the advantage at DMX and not as in the case of midi only 0-127. 
 
With the DMXIn remote control DMXControl can in all modules by external steer DMX desk. So e.g. being able to channels in DMXControl by faders change, effects start, masters and sub-masters steer, attitudes of the Soundanalyzers change etc. 
Through this one programming of the single ones weds DMXIn channel can be made an external operation adapted to the claims of one's own for DMXControl. This is primarily advisable at events because one can access corresponding actions with respect to hardwares. Also at the use of DMXControl in the theater area one can proceed with the DMXIn remote control by Softpatch or sub-master directly over a desk. 

By use of banks values are different attitudes e. g. different Locations, set etc. possible for the assignment the different command to the individual DMX channels or DMX. 
 
Apart from the assignment to the commands there also is the possibility of the Softpatches. Every initial channel is put directly on an internal DMXControl channel. Through this the device lying at this channel can be headed directly. The disadvantage is if the device is moved in the universe, also must be assigned to the Softpatch newly. 
The better way is to assign the appropriate DMXIn channel to the channel of the device directly even if it is a little more effort. The assignment remains unchanged also after moving the device. 
 
The configuration window should be used in the way that the DMX channels to which DMXControl commands shall be assigned are represented. The defined control elements have to be understood therefore as such rather virtually, they correspond taken exactly to a DMX channel. 
 

==Description and configuration.==
You configure correctly, you can check at the channel overview whether your interface for DMX into. If you have switched this to the in mode on the left below. Here version these are shown to DMX in values instead of the current ones now, the corresponding values in the table see this means you at channel changes at the desk. 
 
{{Manual Box | en | Hint | In the DMXIn view the equipment assigned to the channels is also shown on the view, however, a change of the values doesn't have any effect on the device.}} 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_channel_overview.png|1|Channel overview DMX-In|center}} 
 

===The configuration window===
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_Menue.png|2|Open the configuration window|right|300px}}
For the configuration of the DMXIn remote control you must the DMXIn remote control configuration window over the menu « Configuration « Menu item « DMXIn remote control » calling first (see figure 2). 
Since DMXControl 2.12 the configuration window is divided up on two register riders. On the one hand the register pus for the control elements (see figure 3) and the register rider for the command assignment to the control elements (see figure 4).
In the two choices as well as the Softpatchbereich is visible for it. The table is the DMXIn channels behind the rider control elements for the DMX channel configuration, to the appropriate DMX channel. Here every channel can into the table openings' control element a name of its own be assigned. DMX channel can be assigned so that one can subdivide a channel into several areas in which different actions are executed the corresponding in the wider range of values. E.g. the assignment of different color configurations of one would be LED headlight a possible application’s to a fader.
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_control_elements.png|3|Configuration window DMXIn remote control - control elements - |center}} 
The table is behind the rider command assignment (see figure 4) with the assignment of the commands to the corresponding channel configurations, all commands can be applied to the different DMXControl modules here.
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_command_assignment.png|4|Configuration window DMXIn remote control - command assignment - |center}} 
External DMX channels can directly be assigned by e.g. a desk to the internal DMXControl channels in the Softpatch area. The external channel number and on right can on the left into this one two inputs is typed in by a click on the button &laquo do this one internal channel number « Add « is the assignment written down on the list. 
Highlighted assignments in the list can by a click on the button « Delete » being deleted again.

===Configuring the DMX channel configuration===
By a click on the button « Add » below the DMX channel configuration you produce a new control element (see figure 5). The name « new control element » an informative name can be changing now. The button « Delete » the straight highlighted control element deletes with the button « Arrow up/down » the entries can be moved and therefore sorted (see figure 6). 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_control_element.png|5|Added new control element|center}} 
This is an opportunity for the clear naming one indicates the channel and the DMX value area as names. At « DMX channel » the corresponding channel is indicated and at now « Min. » or « Max. » the corresponding range of values. 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_configuration.png|6|Configuration of four control elements for 2 DMX channels|center}} 
The channel 1 with the range of values 0 – 255 e.g. one could use for the master or a sub-master so that at movement of the fader the master or sub-master follows the fader movement. For the channel 2 the range of values is subdividedly, here areas in four e.g. one could deposit four different effects or also four colors of LED headlights. 
 
{{Manual Box | en | Hint | The control elements of the DMX channel configuration are not project-related stored. You can find it in <tt>application data/pop soft/DMXControl/DMXInRemote.dat</tt>.}} 
 

===Configuring the command assignment===
The command assignment is, carried out in the lower table window control elements dip the names of the control elements defined in the upper window under the table head here. 
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_configuration2.png|7|Tab of the command assignment, add to a new order bank|center}} 
 
To assign commandsto the corresponding control elements now, must once by the badge « Add » a new bank being laid out. By laying out different banks different assignments can be made to the control elements 
 
{{Manual Box | en | Hint | The command assignment is, stored project-relatedly this one unlike the DMX channel configuration
File name in the project list is: <tt>PROJEKTNAME.DMXInRemote</tt>}} 
E.g. with the name ''Show1'' then passes the possibility of assigning a corresponding command to the individual control elements by production of a new bank, under module then becomes at all control elements « &raquo deactivates » shown. 
The individual table columns have following meaning and functions:
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

==Controls==

{{Picture_with_subtitle |DMXC2_Manual_DMXIn_activation.png|8|DMXIn activation window|right|200px}}
The configuration of the control elements is carried out this one [[MIDI_control_DMXC2|MIDI control]] elements almost analogously to this one. Every control element corresponds to a DMX channel whose value is used for the configured command.
Another this one lets himself on the right side « Softpatch » configuring. Values of the DMX can into be distributed on arbitrary other DMX out channels with that. This is useful to e.g. only steer a certain equipment with an external light desk.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

 

==Module commands==

* Modul: '''DMX remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the DMX remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the command of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some commands to ensure a correct function.
|}

==Tipp(s)==

{{Manual Box | en | Attention | It is valid for DMXControl 2.11 and smaller:So that these attitudes also are realized, the window must « DMXIn remote control » open and there the checking box « DMXIn remote control » is active being active. For DMXControl 2. 12 is no longer required.
}}
 
Here short instructions to proceed for the DMX4All interface as in the case of the facilities are:
{{Picture_with_subtitle |DMXC2_Manual_output_plugin_administration.png|9|Output plugin administration at the choice of the DMX4All-Plugins|center}}

Open the Output plugin administration (menu Settings > Output plugins). There you click this is responsible for her interface on the Plugin. Click on the button « Configure selected plugin » around for the individual attitudes hers. Here exemplary the dialog of the ''DMX4All'' plugin:
{{Picture_with_subtitle |DMXC2_Manual_DMXIn_DMX4All_configuration.png|10|Activation of the DMXIn function of the DMX4All-plugin|center}}

Here you carry out the attitudes, hers to activate interfaces around the DMX entrance now. In the example this is the checking box « DMX-in » active.
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = MIDI_remote_control_DMXC2
| TextBackwards = MIDI remote control
| LinkForwards = Program_settings_DMXC2
| TextForwards = Program settings
}}
[[de: DMXIn-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

Keyboard control DMXC2

2025-03-02T19:18:14Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = PDA_remote_control_DMXC2
| TextBackwards = PDA remote control
| LinkForwards = Joystick_control_DMXC2
| TextForwards = Joystick control
}}
{{Start-LaTeX}}
==Overview==

With keyboard control DMXControl has steered modules in everyone by keyboard for itself, e.g. DMX channels can be put, started effects/stopped, the audio player start/stop, changed etc. attitudes of the Soundanalyzers on predefined values of devices so.
By the free programming of the individual buttons lets themselves, one to the claims of one's own make conformist keyboard operation for DMXControl.
This is primarily because one can access corresponding actions with respect to hardwares over single buttons advisable at events. E.g. the command line can be used or also assigned different chasers to the individual buttons by the connection of an external USB numeric keypad very comfortably.
Till now, is for the banks concept at the keyboard control, not implemented yet unlike the command box, DMXIn and midi remote control.

==Description and configuration==
===Configuring keyboard control===
{{Picture_with_subtitle |DMXC2_Manual_keyboard_control_menue.png|1|Opens the configuration window|right|300px}}
For the configuration of keyboard control you have to open the keyboard control configuration window over the menu « Configuration » Menu item « Keyboard control » first (see figure 1).
All buttons are listed on the left side, the control elements in the configuration window. Since DMXC 2.12 the F1 button also can be covered with orders. This wasn't possible at earlier versions.
{{Picture_with_subtitle |DMXC2_Manual_keyboard_control_configuration.png|2|The Configuration_window|right|530px}}
 
{{Manual Box | en | Hint | You store project-relatedly, the order assignment the file name is in the project list: <tt>PROJECTNAME.keyboard</tt>
}}

The other table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{Manual Box | en | Hint | Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

 
You find the administration part in the menu « Window » in the menu item « Keyboard control».

In the administration part you can adjust, whether keyboard control is active the depressed buttons are intercepted and whether keyboard control also works if exactly another program has the focus.

==Controls==

{{Picture_with_subtitle |DMXC2_Manual_keyboard_control_aktivate.png|3|Keyboard control aktivating window|right|250px}}
The configuration of the control elements is carried out this one elements almost analogously to the [[MIDI_Fernsteuerung_DMXC2|MIDI control]]. Every control element corresponds to a DMX channel whose value is used for the configured command.
Another this one lets himself on the right side « Softpatch » configuring. Values of the DMX can into be distributed on arbitrary other DMX out channels with that. This is useful to e.g. only steer a certain devices with an external light desk.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}
 
{{Manual Box | en | Attention | Programs can no longer globally question or intercept on button petitions by the new safety policy of Microsoft since Windows sight at an active user accounts control system (UAC). This speaks in it that at the activation this one « Global ». A fault appears attitude in the administration part. It therefore isn't possible in sight and Windows 7 with an active user accounts control system to steer DMXControl about keyboard control if exactly another program has the focus.
}}

==Tip(s)==

{{Manual Box | en | Important | It is valid for DMXControl 2.11 and more smally:So that these attitudes also are realized, the window must « DMXIn remote control » open and there the checking box « DMXIn remote control active » being active. For DMXControl 2.12 is no longer required.
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = PDA_remote_control_DMXC2
| TextBackwards = PDA remote control
| LinkForwards = Joystick_control_DMXC2
| TextForwards = Joystick control
}}
[[de: Tastatursteuerung_DMXC2]]
[[Category: DMXControl 2]]

Keyboard control DMXC2

2025-03-02T19:17:57Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = PDA_remote_control_DMXC2
| TextBackwards = PDA remote control
| LinkForwards = Joystick_control_DMXC2
| TextForwards = Joystick control
}}
{{Start-LaTeX}}
==Overview==

With keyboard control DMXControl has steered modules in everyone by keyboard for itself, e.g. DMX channels can be put, started effects/stopped, the audio player start/stop, changed etc. attitudes of the Soundanalyzers on predefined values of devices so.
By the free programming of the individual buttons lets themselves, one to the claims of one's own make conformist keyboard operation for DMXControl.
This is primarily because one can access corresponding actions with respect to hardwares over single buttons advisable at events. E.g. the command line can be used or also assigned different chasers to the individual buttons by the connection of an external USB numeric keypad very comfortably.
Till now, is for the banks concept at the keyboard control, not implemented yet unlike the command box, DMXIn and midi remote control.

==Description and configuration==
===Configuring keyboard control===
{{Picture_with_subtitle |DMXC2_Manual_keyboard_control_menue.png|1|Opens the configuration window|right|300px}}
For the configuration of keyboard control you have to open the keyboard control configuration window over the menu « Configuration » Menu item « Keyboard control » first (see figure 1).
All buttons are listed on the left side, the control elements in the configuration window. Since DMXC 2.12 the F1 button also can be covered with orders. This wasn't possible at earlier versions.
{{Picture_with_subtitle |DMXC2_Manual_keyboard_control_configuration.png|2|The Configuration_window|right|530px}}
 
{{Manual Box | en | Hint | You store project-relatedly, the order assignment the file name is in the project list: <tt>PROJECTNAME.keyboard</tt>
}}

The other table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

 
You find the administration part in the menu « Window » in the menu item « Keyboard control».

In the administration part you can adjust, whether keyboard control is active the depressed buttons are intercepted and whether keyboard control also works if exactly another program has the focus.

==Controls==

{{Picture_with_subtitle |DMXC2_Manual_keyboard_control_aktivate.png|3|Keyboard control aktivating window|right|250px}}
The configuration of the control elements is carried out this one elements almost analogously to the [[MIDI_Fernsteuerung_DMXC2|MIDI control]]. Every control element corresponds to a DMX channel whose value is used for the configured command.
Another this one lets himself on the right side « Softpatch » configuring. Values of the DMX can into be distributed on arbitrary other DMX out channels with that. This is useful to e.g. only steer a certain devices with an external light desk.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}
 
{{Manual Box | en | Attention | Programs can no longer globally question or intercept on button petitions by the new safety policy of Microsoft since Windows sight at an active user accounts control system (UAC). This speaks in it that at the activation this one « Global ». A fault appears attitude in the administration part. It therefore isn't possible in sight and Windows 7 with an active user accounts control system to steer DMXControl about keyboard control if exactly another program has the focus.
}}

==Tip(s)==

{{Manual Box | en | Important | It is valid for DMXControl 2.11 and more smally:So that these attitudes also are realized, the window must « DMXIn remote control » open and there the checking box « DMXIn remote control active » being active. For DMXControl 2.12 is no longer required.
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = PDA_remote_control_DMXC2
| TextBackwards = PDA remote control
| LinkForwards = Joystick_control_DMXC2
| TextForwards = Joystick control
}}
[[de: Tastatursteuerung_DMXC2]]
[[Category: DMXControl 2]]

MIDI remote control DMXC2

2025-03-02T19:17:16Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_activate.png|1|MIDI-Fernsteuerung|right}}
The MIDI remote control enables DMXControl to use MIDI protocol. Unlike the DMXIn remote control the MIDI remote control only uses a word size of 7 bits so that only values of 0 to 127 over the protocol are transferred.
Apart from little MIDI keyboards, there is the Behringer BCF2000 or BCR2000 as well as Korg nanoKONTROL 2 or Pioneer CDJ 350 also.
It is advisable to review the reference documentation here: Wikipedia <ref> MIDI on Wikipedia http://de.wikipedia.org/wiki/Musical_Instrument_Digital_Interface </ref>
 
 
 

==Description and configuration==

Some of the best known midi controllers are well:
* BCF2000/BCR2000 von Behringer <ref>BCF2000 http://www.behringer.com/de/Products/BCF2000.aspx </ref>
* Korg nanoKONTROL 2
* Pioneer CDJ-350

But also almost every keyboard (instrument) can be used with a MIDI input, or usb to midi interface.
MIDI devices which connect via USB also work.

The configuration files of the BCF2000 are shown in the pictures.

===The configuration window===
DMXControl needs to know about new MIDI interfaces. If your interface or device was not recognized on launch, you should enable it now.

Under the menu « Settings » choose configuration and choice of the corresponding MIDI device are carried out « MIDI remote control » here. If your device does not appear in the MIDI in/out port list then you should try reinstalling your device drivers.

After choosing the MIDI in device, you will be able to see incoming MIDI message appear in the bottom of this window.

{{Manual Box | en | Hint | It should be respected, however, on this that the subsequent configuration with « MIDI Learn » only work when the MIDI remote control is deactivated in between (see picture ''active voice'').
Furthermore a simultaneous use of the MIDI port of (a device) works together with another program (e. g. Winamp control about Xor MIDI Control) only the original (not Windows) drivers of the manufacturer (here: Fame).
}}

===Config of MIDI channel configuration===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_control_elements.png|2|MIDI remote control configuration, control element|center}}
Since the first configuration at the simplest one with this one « MIDI Learn ». It is, is come in to the configuration here preferably in this way to make function. Changes can be carried out by hand later any time.
To the better overview one should which one give the control elements the name of the assigned control element as long as one still knows « New control element » which button heard. (One most simply leaves renaming, « enter key », with this one).
E.g. sensible Nammen would be fader 1, fader 2 etc. or button C, button C sharp etc. or Poti 1, Poti 2 etc.
The names one are subject to alteration, should, however, be chosen correspondingly so that it is known also after quite a long time still around which control elements.

===Configuring the command assignment===

{{Picture_with_subtitle |DMXC2_Manual_MIDI_remote_control_command_assignment.png|3|MIDI remote control configuration, command assignment|center}}

After the controller was included in the upper list and named completely, you can do this one order corresponding to control elements in the register rider command assignment assign now.

For the individual control elements every functionality can be chosen, it already is used of the keyboard control or the command box like you.

E. g. with the name ''Show1'' then passes the possibility of assigning a corresponding order to the individual control elements by production of a new bank, under module then becomes at all control elements « deactivates » shown. 
The individual table columns have following meaning and functions.
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''                 Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{Manual Box | en | Hint | Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

==Controls==
The configuration of the control elements is carried out this one elements almost analogously [[DMXIn-Fernsteuerung_DMXC2|DMXIn control]] to this one. Every control element corresponds to a midi channel whose value is used for the configured order.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

==Module commands==

* Modul: '''MIDI remote'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| At choice of this function, there is the possibility of accessing the different benches about the command in the MIDI remote control.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank name
|style="width: 200px"| Direct choice of the defined benches about bank namens.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==

'''Flags:''' You click in this column, you a context menu is shown if two option in which or one can turn off: 
– Receive: Switch on this option if the MIDI order shall be processed at reception. 
– Send: Switch on this option if the MIDI order shall be sent if the corresponding value changes in the program. 

The banks are, stored the control elements however global in the project folder. You therefore should at a bill of exchange on another computer with the pile And go function provide it best this also gets this file changed on the new computer.

Be recommended can, the software midi OX, since one can test hereby whether the device also is attached also correctly and signals arrive in the PC. One can find the program here: of course one can http://www.midiox.com/zip/midioxse.exe test the function ability of the interface also with MIDI Sequencer programs.

One uses one a normal midi keyboard ("piano buttons") should so the buttons mark themselves with stickers best behind the buttons to know what one hides. The buttons should be covered structuredly, to this a small example:
One puts himself the first 4 sub-masters (e. g. ) headlights on the first 4 white buttons of the keyboard of the left. Perhaps one has effects run light (or the like) with these sub-masters (headlights) programmed, these effects are then put on the black buttons more than the first four white buttons. So one has the headlights manually in the handle and also can if necessary start a run light fast.
At all applications it is useful a button to cover himself with a proper blackout at least because sometimes this button is "gold worth" because one can thus immediately turn all headlights/scanners off. One should put the blackout on a button for example on the outermost right white button which one can remember well (or black button, because everything gets dark).

==Links and references==
<references/>
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Joystick_control_DMXC2
| TextBackwards = Joystick control
| LinkForwards = DMXIn_remote_control_DMXC2
| TextForwards = DMXIn remote control
}}
[[de: MIDI-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

PDA remote control DMXC2

2025-03-02T19:16:33Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Shape_editor_DMXC2
| TextBackwards = Shape editor
| LinkForwards = Keyboard_control_DMXC2
| TextForwards = Keyboard control
}}
{{Start-LaTeX}}
==Overview==
The PDA remote control has developed from the terminal interface of DMXControl over the serial remote control. By the « PDA remote control » DMXControl can ( telnet, COM interface, Bluetooth or about WLAN ) head with PDA and other serial interfaces.

{{Manual Box | en | Important | The window of the PDA remote control must remain open as in the case of all other remote controls/controls in DMXControl. No communication takes place at closed window.}}

==Description==
This one « Serial remote control » did you implement in DMXControl to make the access about a serial interface or network (Ethernet) to the program possible. DMXControl expects a connection in the Netwerk on port 2145. This one can this port in the window « PDA remote control » being changed. Any program which can send character strings (strings) out is able to radioguide DMXControl with that.
This one « Serial remote control » among other things android is (e.g. ) uses of the PDA control [[PDA_2_DMXC]] and of the web interface or the PHP class as well as different other controls.
Since the protocol of the interface is open, it is possible for everybody to access DMXControl about a program of one's own.

The interface works bidirectionally, i. e. data can be sent and made an enquiry about. A table of the possible orders can be found below. Some orders don't return a value other after executing as a confirmation.

To DMXControl every order is sent to it, n must with a line break (in Java and C # "") be completed.

==Port==
A list of the commands and answers are listed by DMXControl into table following this one. Developers who would like to write an external program for DMXControl's control can make first experiences the best with a terminal program like telnet or Putty. This goes with the order at local work: '''telnet 127. 0. 0. 1 2145'''. One then immediately recognizes what the answers look. All commands are interpreted by great/use of small initial letters independently of DMXControl.

{{Manual Box | en | Hint | Instead of '''SetChannel''', so '''sEtChAnNeL''' also can be written to.
}}

The abbreviation '''CV''' stands '''for ChannelValueChanged''' for '''ChannelValue''' and '''CVC'''

{|cellpadding="5" cellspacing="0" border="1"
|'''Enquiry to DMXC'''
|'''Answer from DMXC'''
|'''Description'''
|'''Example'''
|- style="vertical-align:top;"
|SetChannel ''Channel value''
|CV ''Channel value''
|Set the '''''Channel''''' on the '''''Wert'''''.
|'''SetChannel 1 200''' -> '''CV 1 200'''
|- style="vertical-align:top;"
|SC ''Channel Wert''
|CV ''Channel Wert''
|Short notation for SetChannel.
|'''SC 1 200''' -> '''CV 1 200'''
|- style="vertical-align:top;"
|GetChannel ''Channel''
|CV ''Channel value''
|Ask the value of the channel '''''Channel'''''.
|'''GetChannel 1''' -> '''CV 1 200'''
|- style="vertical-align:top;"
|GC ''Channel''
|CV ''Channel value''
|Short notation for GetChannel.
|'''GC 1''' -> '''CV 1 200'''
|- style="vertical-align:top;"
|GetAllDevices
|''List of Devices''
|Question on all devices available in DMXControl.
|'''GetAllDevices''' ->
'''1. PAR-1'''
'''2. PAR-2'''
'''...'''
'''10. Botex SP-1500 Stroboskop'''
|- style="vertical-align:top;"
|GetDeviceInfo ''DeviceID''
|''Device information''
|Asks for more exact information about the device with the number '''''DeviceID'''''. Three possibilities exist for PanTilt: '''No, Coarse, Fine'''. With Coarse or Fine, so the channels follow of Pan Tilt, at a scanner: '''''PanTilt: Coarse 0 1''''' on a 16 bit Scanner '''''PanTilt: Fine 0 1 14 15'''''. The order is there '''Pan Tilt PanFine TiltFine'''. After '''''Channels: quantity''''' is a list appended with all names of the channels as they are deposited in the DDF.
|'''GetDeviceInfo 10''' ->
'''Name: Botex SP-1500 Stroboskop'''
'''StartAddress: 257'''
'''PanTilt: No'''
'''Channels: 2'''
'''Channel1: frequenz'''
'''Channel2: intensity'''
|- style="vertical-align:top;"
|StartChannelNotification ''StartChannel EndChannel''
|None
|The asynchronous information about channel changes activates. In DMXControl if himself a channel '''''StartChannel''''' and '''''EndChannel''''' change, DMXControl sends a message with the new value. Of StartChannelNotification overwrites the old area send a further.
|'''StartChannelNotification 1 10'''. After value change of channel 5 on 255: -> '''CVC 5 255'''
|- style="vertical-align:top;"
|StopChannelNotification
|None
|The notification deactivates about channel changes.
|'''StopChannelNotification'''
|- style="vertical-align:top;"
|GetCommandPossibilities ''Dropdown Index, Predecessor index''
|''List of the possibilities''
|An command consists of single parts. ''Module'', ''Device/Function'', ''Channel'', ''...''. Since the following choice is based on the previous one, must the row after be questioned from the front. With ''GetCommandPossibilities 1'' one receives a list of the module possibilities. Every possibility has one ID. With ''GetCommandPossibilities 2 3'' one receives the choice for Device/Function, based on module 3.
|'''GetCommandPossibilities 1''' ->
'''1. Deaktivate'''
'''2. Audio'''
'''3. Audiotrack'''
'''...'''
|- style="vertical-align:top;"
|RunCommand ''Index1 Index2 Index3 Flags Value''
|None
|With this command one executes the command. '''''Index1, Index2''''' and '''''Index3''''' the indices are there of GetCommandPossibilities.
'''''Flags''''' is one binarily more codedly uprightly. Bit 0 stands for ''using indicated value'' for ''Toggle mode'' and bits 1.
'''''Value''''' a DMX value is in per cent of 0,000 to 100,000 (for future 16 bits of values).
|'''RunCommand 2 5 3 0 0.000'''
|}
 

== GetCommandPossibilities und RunCommand ==
To execute a specific order with '''rush command''', one must know which ID the order has. One very simply can find out this ID with the call '''GetCommandPossibilities'''. One works himself at this step by step down from the topmost level (1) up to the required level (e.g. 3). The first number behind the call represents the level on which one just is. The following numbers stand for the IDs of the results of the queries of the previous levels. It is therefore very important that the level of the row will pass after.
 
To start e.g. an effect this way, this could look as follows: A call of the order '''GetCommandPossibilities 1''' delivers the following table in which there isn't a second number since we are on the highest level (level 1).
Installed Plugins join the list if available.

1. Deaktivate
2. Audio
3. Audio track
4. BeatTool
5. DMX outpute
6. DMXIn remote
'''7. Chasers'''
8. External Action (Plugin)
9. Devices
10. Group selection
11. Joystick
12. Command box
13. Command line
14. Master
15. MIDI remote
16. OSC receiver (Plugin)
17. Sound analyzer
18. Submaster
19. Cue libary
20. Cue list
21. Textbook

We question on the options '''for the ID 7 chasers''' for the level '''2''' now: '''GetCommandPossibilities 2 7''' provides the ID, the options which can be accessed, to us. In this case 1-4 would be choice and jumps of the chasers possibly about the IDs. The pro-even grief rents chasers have the IDs as of 6:

1. All
2. Selected
3. Next
4. Previous
5. ----
'''6. [CHASER 1]'''
7. [CHASER 2]
8. [CHASER 3]
9. ...

The call following now for the 3rd level '''GetCommandPossibilities 3 6''' shows the functions possible for this effect in our example ''[CHASER 1]''. DMXControl gives the following list back:

1. Select
2. Start/Stop
'''3. Start'''
4. Stop
5. Set acceleration
6. Set intensity
7. Next step
8. Repeat on/off

With '''RunCommand 7 6 3''' the chaser has 1 to start or to stop with '''RunCommand 7 6 4''' for itself. For the chaser 3 these would be the calls '''RunCommand 7 8 3''' and '''RunCommand 7 8 4'''. If values still must be transferred, these are appended behind: '''RunCommand 7 6 3 0 0,000'''. Other calls work according to the same principle.

{{Manual Box | en | Hint | Perhaps it helps at the understanding to look at the programming of the command box. The columns at the button programming '''module''', '''device/function''', '''channel''', '''flags''' and '''value''' correspond to the levels, IDs and values of the '''RunCommand''' command.
}}

==Links and references==
Links
#PDA-Fernbedienung Software: http://www.dmxcontrol.de/files/pda-2-dmxc/PDA-2-DMXC_1.0_Setup.exe

Tutorials
#[[PDA-2-DMXC|PDA-2-DMXC Tutorial]] ''''Not yet translated''''
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Shape_editor_DMXC2
| TextBackwards = Shape editor
| LinkForwards = Keyboard_control_DMXC2
| TextForwards = Keyboard control
}}
[[de: PDA-Fernsteuerung_DMXC2]]
[[Category: DMXControl 2]]

Motion cue DMXC2

2025-03-02T19:15:57Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Scheduler_DMXC2
| TextBackwards = Scheduler
| LinkForwards = Shape_editor_DMXC2
| TextForwards = Shape editor
}}
{{Start-LaTeX}}
==Overview==
Scenes of the motion editor is a pure submodule in DMXControl 2 and thus only cue module or chaser module to find, is when there using the button « Add » a new step « Motion cue » inserted or edited.
The motion cue itself is ultimately only the assignment of different devices (with pan + tilt feature) to the previously created characters and its configuration. (See figure editor).
(Each motion cue includes thus always just exactly a figure at the time, but access to all previously created characters and can manage.)
{{Picture_with_subtitle |DMXC2_Manual_motion_cue_editor_window.png|1|The motion cue editor|center}}

==Description==

As soon as a figure has been selected and at least a device was added to the list, the one with the button can « Cue test » being looked right below. During this test cycle this one can live « Duration » « Repetitions » and « Wait time » you adjust, these are then played exactly again and again in this order. (In our example the 4 scanners turn 3 x the spiral all and then 10. 8 sec. wait on the final position at the same time for 5. 1 sec.)
The function beat triggered cannot become live and is visible first playing the scene. (Duration is by the beat replaces, the waiting time remains unchanged nevertheless.)
We would become the attitude of now « Absolute » on « Relative » alter, the next spiral pass would go exactly in bulk in that place so where the commercial just is. (Caution is, however, required here since himself scanning constructions then reconcile the debit positions outside the mirror be rich far at and it therefore comes to a modified form of the figure this one.)

{{Manual Box | en | Hint | Selecting always only Pan+Tilt of the device to avoid ungewünschte side-effects.
}}
Some correction attitudes are under the device list for the Bewegungszene still. The figure can be scaled and/or moved for any listed device here. Authorities of the figure graphically are overlaid in color separated in the black preview pane. So the changes (here 4 different scalings of the spiral) can be recognized well in relation to each other.

===Offset===
The offset only can be recognized when at least 2 equipment is available in the same motion cue and has adjusted a different offset. The device carries away the figure deferred (unity in steps).

{{Manual Box | en | Hint | The figure is changed at an active offset, is that way to respect stehts that aren't more greatly the offset of all equipment than the available steps of a figure.
}}

If « sequential offset » is activated, all other equipment waits with a lower offset for the completion of the figure of the device with a higher offset. Is the function is deactivated without the figure carried away once more to waiting.

==Color and pattern==
If with a motion cue not only Pan and Tilt of a device shall be changed, then this is also possible. For this the list offers « Assigned cues » the possibility of assigning an order to every step of the figure on hand. Here can change orders like Gobo or color in the simplest case insertedly be. For performance reasons this possibility which allows also arbitrary nestings in the theory should, however, be handled very thriftily.

==Controls==

All control elements can both be held tight and drawn with the mouse and be changed with the arrow keys (at a previous selection). Offers one's services for a fine justification particularly if the slider tends to the jumping second.
All equipment can individually be adjusted for the scene. So a scaling, moving, negation of all X (Pan) and Y (Tilt) is independently of each other possibly values and can vary from scene to scene. Two of identical figures is possible also a run counter-same, since per equipment the checking box « Play in reverse » can set be.

{{Manual Box | en | Hint | With motion cues also slow color transitions can be realized by one assigning one color channel each to the parameters X and Y. Furthermore further effects like a controlled Gobo choice etc. are possible.}}

==Tip(s)==

To clarify the difference, recommends it 4-6 scanners put themselves together close together very much (these even can be slid into each other with Easy view) and let all scanners carry away a circle with very few steps. All commercials can permanently be recognized one by one at non-sequential offset. These otherwise overlap at the beginning and end of the figure like grading.

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Scheduler_DMXC2
| TextBackwards = Scheduler
| LinkForwards = Shape_editor_DMXC2
| TextForwards = Shape editor
}}
[[de: Effektsequencer_DMXC2]]
[[Category: DMXControl 2]]

Scheduler DMXC2

2025-03-02T19:15:27Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Command_line_DMXC2
| TextBackwards = Command line
| LinkForwards = Motion_cue_DMXC2
| TextForwards = Motion Cue Editor
}}
{{Start-LaTeX}}
==Overview==

With the Scheduler tool (also known as Scheduler) to perform time-controlled since version 2. 11 shows, E. g. daily, weekly, any periodic or one-time tasks\/dates.

==Description==

There are several tasks parallel programmable. The assignment of tasks to the dates is made using commands, how it is used by other tools.

{{Manual Box | en | Hint | In the version 2.11 was the Scheduler still in the experimental stage, so the point had to be under the menu item «Configuration» «Experimental parts of the program» selected. Since release 2.12, this is no longer necessary, because the Scheduler since this version belongs to the standard modules.
}}

{{Picture_with_subtitle |DMXC2_Manual_scheduler_window.png|1|The Task Scheduler|center}}
 

==Controls==

It adds a new task with the button « Add ». The window « planned execution » consists of four self explanatory:
* Name of the execution
* Date - here also periodic appointments can be selected
* Zeit - fixed, random or recurring dates
* Befehl - here the DMXControl activity command is mapped to

{{Picture_with_subtitle |DMXC2_Manual_scheduler_planned_execution.png|2|How to create a new execution|center}}

{{Manual Box | en | Hint | To run the appointments the Scheduler must be started, but minimized.
}}

Tasks can be activated via the check box at the bottom of the window « Active » or the check box in the list before the name, or it can be disabled. Disabled tasks but are retained. The checkbox « execute retroactively » causes a task then later runs if the actual date DMXControl or the Scheduler was not started.
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Command_line_DMXC2
| TextBackwards = Command line
| LinkForwards = Motion_cue_DMXC2
| TextForwards = Motion Cue Editor
}}
[[de: Zeitplaner_DMXC2]]
[[Category: DMXControl 2]]

Command line DMXC2

2025-03-02T19:15:00Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Textbook_DMXC2
| TextBackwards = Textbook
| LinkForwards = Scheduler_DMXC2
| TextForwards = Scheduler
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_Kommandozeile_Fenster.png|1|Die Kommandozeile|right}}
The Command line module is a useful little tool to add fast DMX values of single or also more DMX channels. This quality adds it on to the be clear attractive particularly if single lamps or whole light groups-or you must turn off at. Also at the programming of light atmospheres the module is very useful because it is hereby quite simply possible to put several lamps on the same brightness value which e.g. time would more much take up with several faders.
 

==Description==

With the buttons simple commands are written down on the lower input line of the module. The DMX value of every channel can be put by means of special instruction chains. Only DMX values can, however, be put at the moment. More complex orders, like displaying time-dependently on a DMX value defined before or the control of other program modules, aren't possible with DMXControl's current version.
 

==Controls==

The command buttons take up the largest portion of the window. The exact significance of every badge is listed in the following table:

{| class="wikitable centered"
|- style="vertical-align:top;"
! Button
! Description
! Example
|-
|style="text-align:center; vertical-align:middle"|
Digit
| Input of a number. This can be both a channel number and a channel value, depending on at which place she is in the instruction chain.
| 27 <Enter>
|-
|style="text-align:center; vertical-align:middle"| THRU
| Choose a coherent area of channels.
| 1 THRU 5 corresponds to the input 1+2+3+4+5
|-
|style="text-align:center; vertical-align:middle"| + / -
| Adding or remove of channels etc.
| 1 THRU 50 - 20
|-
|style="text-align:center; vertical-align:middle"| @
| This symbol stands before the channel value order.
| 20+21+25@128 (Put the channel values of the channels 20, 21 and 25 on the DMX value 128)
|-
|style="text-align:center; vertical-align:middle"| DEL
| Deletes the last entry.
|
|-
|style="text-align:center; vertical-align:middle"| FULL
| Sets the channel values of the specified channels to their maximum value.
| 255 (or as specified in the DDF)
|-
|style="text-align:center; vertical-align:middle"| Enter
| Send down the chain of command, which clears the entry field.
| The current chain of command appears in the gray area of the input line.
|-
|}

 

The input field is located at the bottom of the window. It consists of two parts, the actual input box (white background) and a display of the last command (grey background).

Right next to the buttons a fader is located. With this you can channel the appropriate channels, much like in the [[Submaster_DMXC2|Submaster]]. Once entered the numbers of one or more channels in the input field and the chain of command was confirmed with, you can adjust fader as the channel value of the channels with this.

 

Valid command chain can look like this:

{| class="wikitable centered"
|- style="vertical-align:top;"
! Command
! Description
|- style="text-align: left;"
| 2 @ 134 <Enter>
| Set the channel value of the second DMX channel on the value of 134.
|- style="text-align: left;"
| 2 + 3 FULL
| Sets the channel values of the channels 2 and 3 to its maximum value
|- style="text-align: left;"
| 3 THRU 8 - 6 @ 57 <Enter>
| Sets all the channels the channel values 3-8 without the channel 6 on the value of 57
|-
| 1 + 4 <Enter> @ 82 <Enter>
| Also an input in two steps: 1 Select the channels 1 and 4 off 2. Sets the channel values of the previously selected channels (here 1 and 4) to the value of 82
|}

==Module commands==

* Modul: '''Command line'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| 0-9,.,+,-,Thru @,Full,Enter, Del,/,Slider
|style="width: 200px"| The following command is applied to the individual control elements in the command line with the slider.
|style="width: 100px"| Set
|style="width: 200px"| Selects the appropriate control, or set the slider to a value.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

{{Manual Box | en | Hint | The operation of the command line module is even easier if you are buttons using the [[Keyboard_control_DMXC2|Keyboard control]] sets on the number block of the keyboard («THRU» you can e.g. on "'\/ ' ' and «@»"'* "' set). Thus, the chain of command can be entered even faster and easier.
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Textbook_DMXC2
| TextBackwards = Textbook
| LinkForwards = Scheduler_DMXC2
| TextForwards = Scheduler
}}
[[de: Kommandozeile_DMXC2]]
[[Category: DMXControl 2]]

Audioplayer DMXC2

2025-03-02T19:14:18Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Command_Box_DMXC2
| TextBackwards = Command box
| LinkForwards = Timecode_player_DMXC2
| TextForwards = Timecode player
}}
{{Start-LaTeX}}
==Overview==

With the audio player audio tracks can be accompanied by cues, chasers and commands. The audio player in principle only offers another surface that for a [[Cuelist_DMXC2|cue list]], like the script and the time code player the possibility is here establishing the cues for the course of the song point exactly. Through this individual Lightshows can be made for some songs.

==Description==

The two audio traces are, the stereo traces of a music track present which a striking feature of the audio player (left channel: green, right channel: red). In this the temporal course with the corresponding amplitudes of the song and the sedate cues are shown to window area. At inefficient computers it recommends himself not to load the waveform graphic with the checking box to suppress the indication of the amplitude course, through what CPU performance is saved.
{{Picture_with_subtitle |DMXC2_Manual_Audioplayer_Fenster.png|1|The Audio player|center|600px}}
{{Manual Box | en | Important | The audio player serves the crown transparency of wave files. If it is merely about playing wave files, the audio cue has to be preferred. Several also can play audio channels (up to 16 pieces) parallel there.
}}

==Controls==
{| class="wikitable centered"
|- style="vertical-align:top;"
! Icon
! Bezeichnung
! Beschreibung
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_DMXControl.png]]
|style="width: 170px; vertical-align:middle"| DMXControl
|style="width: 380px"| With the button DMXControl in the audio player you adjust, that the sound file and the audio cue list are started and played about DMXControl.
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_WinAmp.png]]
|style="width: 170px; vertical-align:middle"| WinAmp
|style="width: 380px"| With the button WinAmp in the audio player you adjust, that the sound file and the audio cue list are started and played about the external program WinAmp. (Synchronization with WinAmp)
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_play.png]]
|style="width: 170px; vertical-align:middle"| Play
|style="width: 380px"| The play button starts the sound file and the audio cue list if the DMXControl button is operated.
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_rewind.png]]
|style="width: 170px; vertical-align:middle"| Rewind
|style="width: 380px"| With this button the audio cursor is placed again on the beginning of the song. (This works also when playing the sound file)
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_repeat.png]]
|style="width: 170px; vertical-align:middle"| Repeat
|style="width: 380px"| If this button is operated, then the sound file is played from the front after ending again.
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_prefade_listening.png]]
|style="width: 170px; vertical-align:middle"| Prefade listening
|style="width: 380px"| With the pre-hearing button the sound file becomes audio cursor position wornly as of the current one. At a renewed click on the button the player stops and the audio cursor returns into his starting point.
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_zoom.png]]
|style="width: 170px; vertical-align:middle"| Zoom
|style="width: 380px"| With the zoom lens drop down the audio trace can be extended.
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_do_not_load_waveform.png]]
|style="width: 170px; vertical-align:middle"| Do not load waveform
|style="width: 380px"| If the checking box is highlighted, the audio trace graphic isn't loaded. Through this the performance can be increased at slow computers.
|- style="vertical-align:top;"
|style="width: 50px; text-align:center; vertical-align:middle"| [[File:DMXC2_Manual_audio_player_button_clock.png]]
|style="width: 170px; vertical-align:middle"| Clock
|style="width: 380px"| With the clock badge the straight highlighted cue is moved on the current audio cursor position in the audio cue list.
|}

The remaining buttons are standard buttons.
===Audio track===
*A '''yellow''' vertical line in the audio trace represents the current position marking of the audio cursor.
*A '''white''' vertical line in the audio trace shows the cue marking with positions already assigned.
*Line '''blue''' more vertically is shown on the audio trace this one if the audio cursor stands on an assigned cue marking.

If one is with the mouse cursor on a cue marking, the mouse pointer converts himself to a double arrow. In addition, a tool tip is shown to the cue with the name. The cue marking can be placed by clicking and hold tight this one con mouse button.

{{Manual Box | en | Hint | The mouse pointer is on the audio trace and not on a cue marking, a tool tip which contains merely a hyphen is then shown. This tool tip is without broader meaning.
}}

===Manage audio project===
*Button « Add »: By this button a new lets himself make Audiotrack project.
*Button « Open »: With this Button one assigns an audio file to the audio track project. Possible audio files must be for mp3, mp2, mp1, wav or ogg of the type.
*Button « Manage »: The menu items hide: behind this Button « Add », « Copy », « Rename », « Delete » and « Manage ». The audio lists can be also managed with them.

{{Manual Box | en | Important | There are problems ''with a certain skew'' at wave files with a variable bit rate (VBR). 
It is therefore the best to use wave files with a constant bit rate (e. g. 128 Kbit or 320 Kbit).
}}

===Serve===
At the click with the mouse button into the audio window the audio cursor (yellow line) appears in this place. E.g. the lets himself in with that « Play » mode (click of the play button) jumps to an arbitrary place to hear these.
A double click into the audio window starts this one « Play »-mode in the appropriate place. A renewed double click stops this one « Play »-mode.

New cues can be assigned as follows:

*Hear the title and think highly of you in the graphic on prominent places in the song where you want to place cues, effects or commands. This action is exactly like in other DMXControl tools made by clicking the button « Add ».
*Particularly quick users even create this in the « Play »-mode. Usually one, however, stops the title and places the cursor exactly in the desired place. There are two possibilities, there got quite exactly therefore:
**One extends the audio player window or about the breadth of the complete screen
**one can adjust a zoom lens factor for the graphic representation of the amplitudes.
*Make a new cue, choose one from the cue library or you define an order.
*You can change the position of an cue in the audio track by the way by moving the assigned blue joist with the mouse (double arrow cursor). The new position is updated in the instruction list. By a click on the table head « Position » are the cues sorted climbing or getting off.
*The fade in time can be adapted the dull by selecting the appropriate cell in the table.
*If you turn the hooklets off with the cue names, the corresponding cue is deactivated, however, remains in the Trackdefinition. One can use this in the construction phase to test the interaction of single effects until one has found the right combination.

==Module commands==

* Modul: '''Audio player'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="4"| Select
|style="width: 195px" rowspan="4"| The further command is applied to the currently select audio track. (Command selects at this function the makes sense to none)
|style="width: 105px"| Start/Stopp
|style="width: 195px"| The command ''start/stop'' starts and stops the select Audiotrack for playback. (The order should be used in connection with the T flag. )
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command ''start'' starts the select Audiotrack for playback.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The order ''stop'' stops the select Audiotrack at playback.
|- style="vertical-align:top;"
|style="width: 105px"| Rewind
|style="width: 195px"| The audio cursor jumps to the beginning of the sound file by the command''Rewind'' again.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next previous Other entries
|style="width: 195px" rowspan="2"| The further command is on the near, previous or into audio track named dropdown the used.
|style="width: 105px"| Select
|style="width: 195px"| Or this one selects the next, previous into audio track named dropdown ''Device/Function''.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop Rewind
|style="width: 195px"| see above
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==

====Synchronization of the audio player with Winamp====

The audio player can be synchronized also with a play cunning of the Wimamp player:

*This one « DMXControl » audio player mode adjusts the normal button.
*The audio player can synchronize himself with the play list of the Winamp player if you activate the '''Winamp''' button. In this case the audio player searches, whether the straight song also an audio player track played in the play cunning is and then starts the corresponding scenes and effects. The music control (e.g. also the jumping to certain places) is then incumbent Winamp.

The advantage of this concept lies in it that of the beat trigger which music controlled effects triggern can do one gets of course synchronous beat then. To this the Winamp AVS plugin must be installed. The Trackliste and the Winamp play cunning synchronize himself over the title announced at Winamp, most the mp3-ID3 day the song. E.g. one can ''file -> view file.info...'' do this in Winamp in the menu seeing and also changing ' (see the following picture) '. Of course this goes also with other mp3 editors. The announced title is in Winamp changeable at ''attitudes/title/extended title formatting''.
{{Picture_with_subtitle |DMXC2_Manual_audio_player_track_information.png|2|Track informationen in Winamp|center|400px}}

To start this mode, the '''Winamp button''' must be active (see item 1 in the following picture). It is '''quite important''' that the Trackname agrees with the announced title of the song (see Punkt2 in the picture). One recognizes whether the synchronization is successful by this, whether in the field wave file (where the song file name is given) ''(-)'' one ''(X)'' for successful or one seems for not found (see item 3 in the picture).
{{Picture_with_subtitle |DMXC2_Manual_audio_player_Winamp_control.png|3|Synchronisisation of the audio player with Winamp|center|750px}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Command_Box_DMXC2
| TextBackwards = Command box
| LinkForwards = Timecode_player_DMXC2
| TextForwards = Timecode player
}}
[[de: Audioplayer_DMXC2]]
[[Category: DMXControl 2]]

Command Box DMXC2

2025-03-02T19:13:13Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = BeatTool_DMXC2
| TextBackwards = BeatTool
| LinkForwards = Audioplayer_DMXC2
| TextForwards = Audioplayer
}}
{{Start-LaTeX}}
==Overview==
The command box delivers a simple, open surface for the live business. With the command box DMXControl can be controled in all modules by button. So e.g. DMX channels can be set on predefined values of devices, start/stop effects, the audio player start/stop, changed attitudes of the sound Analyzer etc.

In addition, the command box can be started with a second screen and/or touch screen ideally to have direct control over DMXControl.

==Description==

By the free programming of the individual buttons one, operation environment which is adapted to the claims of one's own and graphic can be made for DMXControl. This makes sense primarily on events because one must have opened only a window (command box window) and can control all actions from there openly. By use of banks up to 1000 buttons are possible for 20 at a matrix of 10 x 10 or 4000 buttons at a matrix of 20 x 20. The number of buttons is variably adjustable. With the mouse or about a direct input about the keyboard the number of buttons can be adjusted.

{{Manual Box | en | Attention | Adjusting the buttons with the mouse is limitedly on a matrix of 20 x 20. By a direct input also higher values can be entered. That it makes no more sense depending on monitor as of a certain size it can do at considerably higher values also to falls refrained come.
}}

The variable command box window can be adapted to the corresponding requirements in his size. The button are scaled so that they are distributed evenly on the window. Through this window has space also for other made on the monitor to itself ( e.g. Graphical view ). A text, a color, an icon and a corresponding order can be assigned to every badge (see fig. 1).

{{Picture_with_subtitle |DMXC2_Manual_commando_box_window.png|1|Design example of the command box|center|600px}}

 

==Controls==

The checking box is located in the upper part of the command box window « Programming mode & raquo; (see) fig. 2, you can change with which between the programming mode and the User mode.
{{Picture_with_subtitle |DMXC2_Manual_commando_box_programming_mode.png|2|Checkbox to serve between Programming mode and User mode|right}}

To cover button with commands, the command box must be switched over into the programming mode. By clicking on the checking box the input mask appears in the upper area (see fig. 3).
{{Picture_with_subtitle |DMXC2_Manual_commando_box_button_programming.png|3|The input mask|center|600px}}

{{Manual Box | en | Attention | In the live business the programming mode must be turned off, i.e. the using mode must be active!
}}

The matrix size of the command box can be adjusted in the input mask in the upper area, i. e. the number of button per line as well as the number of lines per bank.

A changing the matrix size additionally is possible. Changing the line count is relatively easy, only when changing the column number the button are thrown in a mess.

Since the button can be moved in the programming mode by ''Drag and Drop'', one can the buttons then sort themselves again. When moving the buttons the button in front of which a black vertical line is is taken in the old place and inserted in the place before the button. All buttons between this move themselves, what is requiring habituation at the beginning of something. But if one has seen through the system, it gets simpler. 
(To move the button, you have to move him up or down, to the left or right, it's sometimes a little bit sticky)

With the button on right above « Reset button » an occupied command box button can be reseted (deleted), it is for this the corresponding button to select and then the button « Reset button » operating.

The occupancy of the corresponding button is announced at the table after choice of a button. If the button isn't occupied yet, seems under button name becomes the corresponding button with his index number as well as the standard color gray and at module ''Deactivate'' shown .

{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''Button name:''' ||     || A name of one's own can be listed in the field button name by a click on the field for the button which then appears on the button afterward, too.
|- style="vertical-align:top;"
| style="text-align:right" | '''Color:''' ||     || By a click to the field color the color palette window in which one can select the color of the button opens.
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" | '''Icon:''' ||     || At a click on the icon field a file browser in which one can select and load a corresponding graphic for the button opens. The file format is restricted to the following graphics: bmp; dib; gif; jpg. The size of the picture should amount to 64 x 64 pixels therefore be square.
|- style="vertical-align:top;"
| style="text-align:right" | '''Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{Manual Box | en | Hint | Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

==Module commands==

* Modul: '''Command box'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| A choice of this function there is the possibility of accessing the different banks (1-10) about the order in the command box.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank 1 to 10
|style="width: 200px"| Direct choice of one of the ten banks.
|- style="vertical-align:top;"
|style="width: 100px"| Button
|style="width: 200px"| With the function button orders already made can be cloned in the command box or used in other modules.
|style="width: 100px"| Button name
|style="width: 200px"| Name of the button which shall be used.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==

* Chasers can be put on command box buttons by Drag & Drop.
* An on/off mode of the buttons is coupled to the flag toggle mode of the command. The buttons seem visually depressed until the next click here durably, too.
* In the programming mode the buttons can be moved by Drag & Drop. To this the button must be let off exactly between two buttons (there where the line appears).

You shall go exemplarily using the effect module into the possible attitude for select effect in this place. « Channel », is come in to « flags » and « value » only on the entry fields « module », « devices/function » since the entry fields « button name », « color», and « icon » are individual input fields. You find a list of all possible attitudes above.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

 
{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Set acceleration of chaser !!colspan="2" style="text-align:center"| Set intensity of chaser !!colspan="2" style="text-align:center"| Chaser next step
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Set acceleration ||style="text-align:right"| '''Channel:''' || Set intenstity ||style="text-align:right"| '''Channel:''' || Next step
|-
| style="text-align:right" | '''Flags:''' || -,O,-,I ||style="text-align:right"| '''Flags:''' || -,O,A,- ||style="text-align:right"| '''Flags:''' || -,-,-,-
|-
| style="text-align:right" | '''Value:''' || 50 ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}
 

{{Manual Box | en | Hint | The following points have to be taken into account at the above examples: 
* A firm value of 50% is at the example command taken on '' set acceleration ''. 
* The value is at the example command questioned by the user '' Set intensity '' over the query window. If the query flag (A flag) isn't shown, this is due to the column width of the openings « Flags ». 
* The acceleration the flag if at » ''Ignor value 0'' « value isn't, set the acceleration remains only as long as indicated on this, how the button is pushed. 
* The corresponding chaser must have been started before a '' chaser next step ''.}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = BeatTool_DMXC2
| TextBackwards = BeatTool
| LinkForwards = Audioplayer_DMXC2
| TextForwards = Audioplayer
}}
[[de: Kommandobox_DMXC2]]
[[Category: DMXControl 2]]

Command Box DMXC2

2025-03-02T19:12:08Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = BeatTool_DMXC2
| TextBackwards = BeatTool
| LinkForwards = Audioplayer_DMXC2
| TextForwards = Audioplayer
}}
{{Start-LaTeX}}
==Overview==
The command box delivers a simple, open surface for the live business. With the command box DMXControl can be controled in all modules by button. So e.g. DMX channels can be set on predefined values of devices, start/stop effects, the audio player start/stop, changed attitudes of the sound Analyzer etc.

In addition, the command box can be started with a second screen and/or touch screen ideally to have direct control over DMXControl.

==Description==

By the free programming of the individual buttons one, operation environment which is adapted to the claims of one's own and graphic can be made for DMXControl. This makes sense primarily on events because one must have opened only a window (command box window) and can control all actions from there openly. By use of banks up to 1000 buttons are possible for 20 at a matrix of 10 x 10 or 4000 buttons at a matrix of 20 x 20. The number of buttons is variably adjustable. With the mouse or about a direct input about the keyboard the number of buttons can be adjusted.

{{Manual Box | en | Attention | Adjusting the buttons with the mouse is limitedly on a matrix of 20 x 20. By a direct input also higher values can be entered. That it makes no more sense depending on monitor as of a certain size it can do at considerably higher values also to falls refrained come.
}}

The variable command box window can be adapted to the corresponding requirements in his size. The button are scaled so that they are distributed evenly on the window. Through this window has space also for other made on the monitor to itself ( e.g. Graphical view ). A text, a color, an icon and a corresponding order can be assigned to every badge (see fig. 1).

{{Picture_with_subtitle |DMXC2_Manual_commando_box_window.png|1|Design example of the command box|center|600px}}

 

==Controls==

The checking box is located in the upper part of the command box window « Programming mode & raquo; (see) fig. 2, you can change with which between the programming mode and the User mode.
{{Picture_with_subtitle |DMXC2_Manual_commando_box_programming_mode.png|2|Checkbox to serve between Programming mode and User mode|right}}

To cover button with commands, the command box must be switched over into the programming mode. By clicking on the checking box the input mask appears in the upper area (see fig. 3).
{{Picture_with_subtitle |DMXC2_Manual_commando_box_button_programming.png|3|The input mask|center|600px}}

{{Manual Box | en | Attention | In the live business the programming mode must be turned off, i.e. the using mode must be active!
}}

The matrix size of the command box can be adjusted in the input mask in the upper area, i. e. the number of button per line as well as the number of lines per bank.

A changing the matrix size additionally is possible. Changing the line count is relatively easy, only when changing the column number the button are thrown in a mess.

Since the button can be moved in the programming mode by ''Drag and Drop'', one can the buttons then sort themselves again. When moving the buttons the button in front of which a black vertical line is is taken in the old place and inserted in the place before the button. All buttons between this move themselves, what is requiring habituation at the beginning of something. But if one has seen through the system, it gets simpler. 
(To move the button, you have to move him up or down, to the left or right, it's sometimes a little bit sticky)

With the button on right above « Reset button » an occupied command box button can be reseted (deleted), it is for this the corresponding button to select and then the button « Reset button » operating.

The occupancy of the corresponding button is announced at the table after choice of a button. If the button isn't occupied yet, seems under button name becomes the corresponding button with his index number as well as the standard color gray and at module ''Deactivate'' shown .

{|style="padding:20px;"
|- style="vertical-align:top;"
| style="text-align:right" | '''Button name:''' ||     || A name of one's own can be listed in the field button name by a click on the field for the button which then appears on the button afterward, too.
|- style="vertical-align:top;"
| style="text-align:right" | '''Color:''' ||     || By a click to the field color the color palette window in which one can select the color of the button opens.
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" | '''Icon:''' ||     || At a click on the icon field a file browser in which one can select and load a corresponding graphic for the button opens. The file format is restricted to the following graphics: bmp; dib; gif; jpg. The size of the picture should amount to 64 x 64 pixels therefore be square.
|- style="vertical-align:top;"
| style="text-align:right" | '''Module:''' ||     || At the click to the field module a drop down list from which one can select one of the modules available in DMXControl opens.
''The following modules can be selected:''

'''Disabled:''' no module selected.

'''Audio:''' Using command on the module audio.

'''Audiotrack:''' Using command on the module Audio track player.

'''BeatTool:''' Using command on the module Beat Tool.

'''Chasers:''' Using command on the module Chaser.

'''Command line:''' Using command on the module Command line.

'''Command box:''' Using command on the module Command box.

'''Cue libary:''' Using command on the module Cue libary.

'''Cue list:''' Using command on the module Cue list.

'''Devices:''' Using command on the module Devices in the graphical view.

'''DMX output:''' Using command on the module DMX output.

'''DMXIn remote:''' Using command on the module DMXIn remote.

'''Group selection:''' Using command on the module Group selection.

'''Joystick:''' Using command on the module Joystick control.

'''Master:''' Using command on the module Master.

'''Midi Remote:''' Using command on the module Midi remote.

'''OSC receiver:''' Using command on the module OSC receiver.

'''Sound Analyzer:''' Using command on the module Sound analyzer.

'''Submaster:''' Using command on the module Submaster.

'''Textbook:''' Using command on the module Textbook.
|}
{{Manual Box | en | Hint | Plugins which support a control by the command box also seem additional here. This shall exemplarily be called MadMaxOne plugin here.
}}
{|style="padding:20px;"
|- style="vertical-align:top;"
| style="width: 110px; text-align:right" |   ||     || '''MadMaxOne Plug-In:''' Using command on the plugin MadMaxOne. 
|- style="vertical-align:top;"
| style="text-align:right" |'''Device/Function:''' ||     || The corresponding functions of the module are selected by a click in this field be able to depending on select module, or the device to be mentioned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Channel:''' ||     || By a click in this field an appropriate channel for a device can be adjusted or depending on module and function a corresponding action can be assigned.
|- style="vertical-align:top;"
| style="text-align:right" | '''Flags:''' ||     || At a click on the field flags a dropdown list with which the corresponding flags can be put or deleted opens.

''The following flags can be selected:''

'''Toggle mode (T):''' With the T flag a button can be configured as on/off switch button.

'''Use specified value (O):''' With the O flag lets himself in, written down on the field, apply per cent value to the module/device.

'''Ask for value (A):''' With the A flag a value written down more petition tightly on it can be applied to the module/device. At the click on the configured button an input window in which the value can be entered opens.

'''Ignore value 0 (I):''' The handing over of a value of zero at not depressed button is ignored.
|- style="vertical-align:top;"
| style="text-align:right" | '''Value:''' ||     || By a click in this field a corresponding value can be deposited quickly for a device or a function.
|}
{{BoxHint
|Text = Both at ' '“Using indicated value“''and''“Questioning on value“the entered value is a per cent value in the area of 0. 000% to 100. 000% ' '. A input of values 0 to 255 or 0 to 65535 isn't possible here.
}}

==Module commands==

* Modul: '''Command box'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Bank
|style="width: 200px" rowspan="3"| A choice of this function there is the possibility of accessing the different banks (1-10) about the order in the command box.
|style="width: 100px"| Next
|style="width: 200px"| The next bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Previous
|style="width: 200px"| The previous bank selects.
|- style="vertical-align:top;"
|style="width: 100px"| Bank 1 to 10
|style="width: 200px"| Direct choice of one of the ten banks.
|- style="vertical-align:top;"
|style="width: 100px"| Button
|style="width: 200px"| With the function button orders already made can be cloned in the command box or used in other modules.
|style="width: 100px"| Button name
|style="width: 200px"| Name of the button which shall be used.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==

* Chasers can be put on command box buttons by Drag & Drop.
* An on/off mode of the buttons is coupled to the flag toggle mode of the command. The buttons seem visually depressed until the next click here durably, too.
* In the programming mode the buttons can be moved by Drag & Drop. To this the button must be let off exactly between two buttons (there where the line appears).

You shall go exemplarily using the effect module into the possible attitude for select effect in this place. « Channel », is come in to « flags » and « value » only on the entry fields « module », « devices/function » since the entry fields « button name », « color», and « icon » are individual input fields. You find a list of all possible attitudes above.

{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Start the chaser !!colspan="2" style="text-align:center"| Stop the chaser !!colspan="2" style="text-align:center"| Start/Stop the chaser
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Start ||style="text-align:right"| '''Channel:''' || Stop ||style="text-align:right"| '''Channel:''' || Start/Stop
|-
| style="text-align:right" | '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || -,-,-,- ||style="text-align:right"| '''Flags:''' || T,-,-,-
|-
| style="text-align:right" | '''Value:''' || - ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}

 
{| style="width:100%"
|-
!colspan="2" style="text-align:center"| Set acceleration of chaser !!colspan="2" style="text-align:center"| Set intensity of chaser !!colspan="2" style="text-align:center"| Chaser next step
|-
| style="text-align:right" | '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers ||style="text-align:right"| '''Module:''' || Chasers
|-
| style="text-align:right" | '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected ||style="text-align:right"| '''Device/Function:''' || Selected
|-
| style="text-align:right" | '''Channel:''' || Set acceleration ||style="text-align:right"| '''Channel:''' || Set intenstity ||style="text-align:right"| '''Channel:''' || Next step
|-
| style="text-align:right" | '''Flags:''' || -,O,-,I ||style="text-align:right"| '''Flags:''' || -,O,A,- ||style="text-align:right"| '''Flags:''' || -,-,-,-
|-
| style="text-align:right" | '''Value:''' || 50 ||style="text-align:right"| '''Value:''' || - ||style="text-align:right"| '''Value:''' || -
|}
 

{{Manual Box | en | Hint | The following points have to be taken into account at the above examples: 
* A firm value of 50% is at the example command taken on '' set acceleration ''. 
* The value is at the example command questioned by the user '' Set intensity '' over the query window. If the query flag (A flag) isn't shown, this is due to the column width of the openings « Flags ». 
* The acceleration the flag if at » ''Ignor value 0'' « value isn't, set the acceleration remains only as long as indicated on this, how the button is pushed. 
* The corresponding chaser must have been started before a '' chaser next step ''.}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = BeatTool_DMXC2
| TextBackwards = BeatTool
| LinkForwards = Audioplayer_DMXC2
| TextForwards = Audioplayer
}}
[[de: Kommandobox_DMXC2]]
[[Category: DMXControl 2]]

BeatTool DMXC2

2025-03-02T19:10:31Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Sound_analyzer_DMXC2
| TextBackwards = Sound analyzer
| LinkForwards = Command_Box_DMXC2
| TextForwards = CommandBox
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_beattool_window.png|1|The beat module|right|200px}}
For the music controlled light show you also should have a look at the '''beat module'''.

It offers the possibility, '''beat''' so-called produce BPM studio <ref>http://www.alcatech.de/html/rebuild.php?src=products_private.html </ref> and therefore steer effects live and completely self-sufficiently ''by hand'' or with help of external sources like the free Winamp <ref> http://www.winamp.com/media-player/de (freeware)</ref> or this.
It is therefore another module besides the sound Analyzer to analyze music outside DMXControl.

{{Manual Box | en | Hint | The programs [ http://numark. de/index. php?option = com_content [http://www. virtualdj. com/ VirtualDJ] & amp & task = view & ID = 203 & Itemid = 278 NumarkCue ]; http://www. native-instruments. com/index. php [?ID = traktor3 NI TraktorDjStudio ], with help are the [http://www. dmxcontrol. de/wiki/OSC _to_MIDI OSC to MIDI tools] supports.
}}

==Description==
{{Picture_with_subtitle |DMXC2_Manual_beattool_module_Icon.png|2|The module icon|right}}
So that this « Beat module » the window accomplishes his tasks, permanently must remain opened. It is under the menu item « Window » find, as well as directly about the icon callable. 

The beat module can be used to this that a special event-or you switch further. Cue module or effect module must the corresponding checking box be marked to this in the modules « bopping triggered » (« music steered ») being put. E.g. a single light/strobe in time for the music therefore can be activated or the position increases at a run light at every beat.
At first beat should in the mode around a feeling for desired or unwanted to get « Manual » cues being tested.

The red joist flashes every time if the beat module has generated time. Under this the temporal distance and the value in BPM get shown, by means of same (beat per minute) double-click which one can be edited, to provide a BPM value manually (e.g. of a beat counter at the DJ mixer).
{{Manual Box | en | Hint | This only is, taken, however, if you in the mode « Manual » are.
}}

 

==Installation notes==
'''You can skip the following section, if you only want to use the mode ''manually''. ''' 

The following steps are needed, around in the mode « WinAmp AVS plug-in » achieving first successes. This is the simplest way how you get the beat of an arbitrary (mp3-)song or a microphone in DMXControl.
{{Manual Box | en | Hint | The mode « WinAmp AVS plug-in » the one who least shows delay between actual audible beat and visible lightning of the joist also is.
}}
{{Picture_with_subtitle |DMXC2_Manual_beattool_AVS_installation.png|3|Selection by Winamp installation|right|200px}}
You load himself down first the free player of the home page indicated above and take care at the installation that the AVS-Plugin is select. (All other hooklets can be removed) 

{{Manual Box | en | Attention | At some operating systems it can happen that Winamp must be executed with administrator rights before the player passes data on to other programs. (This is e. g. the case at Windows 7 in the test mode or Windows 8)
}}
{{Picture_with_subtitle |DMXC2_Manual_beattool_winamp_configuration.png|4|Aktivate the AVS Visualizers in Winamp|right|200px}}
If the player and DMXControl have started, the Plugin can be selected by means of right click on the spectrum (or Ctrl+ K).
The DMXControl-Ausgabeplugin can be selected in the AVS window then opening with a right click in turn.
The Winamp-DMXControl effect is only one in AVS after an installation of Winamp of many, why still recommends to remove the random case in the AVS editor to himself.
 

==Controls==

*The Beat module supports three modes:
*« Manuell » 
*« WinAmp AVS-Plugin » 
*« BPM-Studio » 

===Manuell===
{{Picture_with_subtitle |DMXC2_Manual_beattool_AVS_selection.png|5|Aktivate DMXControl in the AVS plugin|right|200px}}
In this mode most functionalities of the beat module are utilizable. With help the « Tap button » a single beat can be produced. Two are at least used this so that the beat can be continued automatically beat. Directly under this « Tap button » the time can beat between the last ones be read in ms. The advertisement is limited on five beat intervals and reflects the current formula again for the mean average value which is issued in the form of beat ongoingly now.
The three values under the beat lightning reflect exactly this value again. the value just calculated is at second place (x/x/x). In first place this one arising from it beat-per-minute and the maximum deviation in last place of this time to the other tab badge petitions.
With « Reset » the determined values can be deleted any time. 
 
With the buttons « 2 », « 1 » and « 1/2 » the multiplier with which the beat is distributed can be chosen. Has to be taken into account that this one « Tap button » in everybody case only the factor « 1 » changed.
You click together, at himself, that is a beat of 60 BPM, become « 2 » always 120 BPM and at « 1/2 » 30 BPM appear. Quite different at the manual overwriting of time. This stands « 2 », and we enter 60,0 becomes at « 1/2 & raquo; calculated down and turned around on 15 BPM. 

If the function « from sound analyzer » is checked the beat after each other of time of the sound analyzer overwritten very simply becomes all 5, activated. 
{{Picture_with_subtitle |DMXC2_Manual_beattool_AVS_editor.png|6|random change deactivate|right|200px}}
There we us but still in the mode « Manual » is, these can by hand by button any time « Tap « and being overwritten the other way round. 

If the beat has come once from time, the can with help « Sync button » being helped. The becomes unlike « Tap button » no new (beat-)distance calculated but available time when pushing on the button synchronizes (started newly). The ''phase relationship'' is corrected short around.

===Winamp AVS plugin===
If you have followed the installation notes completely above, a beat should immediately be recognizable at choice of this mode. You can adjust a BPM maximum value with the regulator which comes to the application however only for an active checking box. The button « Reset » and the button « Tap » don't have any functionality for this mode, are, however, accessible furthermore so that a liquid change to the mode « Manual » possible without break is. 

===BPM-Studio===
The BPM studio runs on any computer in the network, the beat also can be fetched by this player under input of the name so. At installation on the same computer ''localhost'' can be kept for ordinary. The interval query also should be left for 2000 ms.
Little values can lead to instability at slow computers. 

==Module commands==

* Modul: '''BeatTool'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| Tap button
|style="width: 200px"| The command (channel) is applied to the Tap button in the beat tool.
|style="width: 100px"| Select
|style="width: 200px"| The Tap button is selected (selected).
|- style="vertical-align:top;"
|style="width: 100px"| Sync button
|style="width: 200px"| The command (channel) is applied to the Sync button in the beat tool.
|style="width: 100px"| Select
|style="width: 200px"| The Sync button is selected (selected).
|- style="vertical-align:top;"
|style="width: 100px"| Reset button
|style="width: 200px"| The command (channel) is applied to the Reset button in the beat tool.
|style="width: 100px"| Select
|style="width: 200px"| The Reset button is selected (selected).
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Factor
|style="width: 200px" rowspan="3"| The function factor has an effect on the multiplier for the BPM..
|style="width: 100px; text-align: center"| 2
|style="width: 200px"| Multiplier two for BPM.
|- style="vertical-align:top;"
|style="width: 100px; text-align: center"| 1
|style="width: 200px"| Multiplier one for BPM.
|- style="vertical-align:top;"
|style="width: 100px; text-align: center"| 1/2
|style="width: 200px"| Multiplier half for BPM.
|- style="vertical-align:top;"
|style="width: 100px"| BPM value
|style="width: 200px"| With the function BPM value the BPM value can be influenced directly.
|style="width: 100px"| Set
|style="width: 200px"| BPM value entered transfers this one the command (channel) set to.
|- style="vertical-align:top;"
|style="width: 100px"| From sound analyzer
|style="width: 200px"| This function has an effect on the checking box in the sound analyzer.
|style="width: 100px"| On/OFF
|style="width: 200px"| In connection with the T flag the function can one and be turned off.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==

*With the button « Sync » the beat can as a side effect single produce even if no BPM value was gone falteringly.
*With the badge & laquo; Reset & raquo; can you synchronize time on the music if a phase shift has arisen. Be able to hire you next to this badge, whether you double or would like to halve time.

== Links and references==
Links
<references/>
Tutorials
*Tutorial BPM-Studio: http://dmxcontrol.de/wiki/BPM-Studio_(Tutorial)
*BPM-Studio-Plugin: http://dmxcontrol.de/wiki/BPM-Studio_Plugin
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Sound_analyzer_DMXC2
| TextBackwards = Sound analyzer
| LinkForwards = Command_Box_DMXC2
| TextForwards = CommandBox
}}
[[de: BeatTool_DMXC2]]
[[Category: DMXControl 2]]

Sound analyzer DMXC2

2025-03-02T19:09:45Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Master_DMXC2
| TextBackwards = Master
| LinkForwards = BeatTool_DMXC2
| TextForwards = BeatTool
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_sound_analyzer_window.png|1|The sound analyzer|left|190px}}
The Soundanalyzer makes it possible that the light control adapts to the music to time and the level automatically. This almost can draw without operator for one party business be used very well.

This module offers a detailed spectrum analysis in which the 24 detail steps can be manipulated and assigned to a channel directly. Next to the beat module another possibility is here, offered beat to extract from an external music source.

==Description==
So that the sound analyzer can accomplish his tasks, the window permanently must remain opened. The sound analyzer lets himself over the menu « Window » Menu item « Sound analyzer » call as well as directly about the symbol. {{Picture_with_subtitle |DMXC2_Manual_sound_analyzer_module_icon.png|2|Module icon|right}} 
It is necessary at the sound Analyzer to understand three concepts which overlap and agree on the complete module generally:

* The source and its manipulation
* The beat generation
* The Sound2Light function and its restrictions

{{Manual Box | en | Hint | The '''source in BLUE''' , the '''beats in RED''' und '''Sound2Light in GREEN'''.
}}

===Sources===
Till now, the two Winamp sources (VbVis or AVS) exclusively can be selected for the sound Analyzer (also see program configuration, rider tools).

<gallery>
File:DMXC2_Manual_sound_analyzer_configuration.png|Pic. 3: Tools
File:DMXC2_Manual_sound_analyzer_winamp_configuration.png|Pic. 4: Winamp-Plug-In
File:DMXC2_Manual_sound_analyzer_VBLink.png|Pic. 5: VBlink
File:DMXC2_Manual_sound_analyzer_AVS_selection.png|Pic. 6: AVS
</gallery>

Both are in the program configuration and the former is activated by specification. Thanks to the possibility, with Winamp also '''linein://''' (at the need of also the same sound card = line out) and line of the sound card be of use possible, every other player for which to play by additional audio drivers or a simple interconnecting cable between the sound source.
It that both VbVis and AVS distribute the changes at the Winamp equalizer has to be taken care, however the volume of Winamp, itself influence on the version not has.
Check in the choice of '''linein://''' the input levels of her sound card/the Windows mixer.

As soon as you have set up a proper source, you, joists permanently changing in '''BLUES''', should be able to see.

===Beat===
The beat is symbolized by the '''red''' small box which should flash regularly. All (two) attitudes for the beat also are represented by limits in '''RED'''.
The version of the beat is always active. Merely wrong threshold values can cause that the field remains dark for the beat. If a control of stock exchange securities or sequences is planned, then the hooklet must correspondingly be activated for beat triggered (music controlled) at the modules cue list module or chaser module.

===Sound2Light===
If the hooklet is put in the corresponding box here, the S2L control is activated. One, however, doesn't immediately see an effect at the very first use since a channel (of a device) must be assigned to one of the 24 spectrum joists at least. To be able to adjust this, it requires, however, a '''bank''' besides the existence of at least a device (see Devices),

{{Picture_with_subtitle |DMXC2_Manual_sound_analyzer_bank_selection.png|7|Bank selection}}

The attitudes being stored in this one. So more configurations can be stored per project. Only the channels of the spectrum joists, however, become stored and not the values of the other regulators in the sound Analyzer. If a channel is assigned, the joist '''GREEN''' changes color exactly like the switching threshold if this is active.
The values of the levels are, converted and distributed directly on DMX values of 0-255 with what classic '''clavilux effects''' with 24 detail steps 1:1 nachbauen can.

==Controls==
One can manipulate the '''source''' directly and therefore influence both beat and S2L with the element ''spectrum increase''. The value can be varied between 0 and 255 in which no change is carried out in the middle at about 128. This attitude can a little finer over the button « Edit channel settings » being adjusted.
{{Picture_with_subtitle |DMXC2_Manual_sound_analyzer_correction_curve.png|8|The correction curve of the sound analyzers|center|300px}}

===Beat settings===
The beat can be found out from a source on two different ways. With the first one over the Spectrum-Analyzer (short '''Analyzer''') and with the second over the VU meter ( short '''VU''' ).
The Analyzer can be configured with the '''red''' rectangle (in the upper area). Whenever one of the spectrum joists rises into this rectangle, a beat is recognized. The rectangle is adjusted by the 4 regulators around the spectrum indication.

The VU meter method is a simplified method of the level analysis <ref> Wikipedia http://en.wikipedia.org/wiki/VU_meter </ref>. The '''red''' marking into the joist below the spectrum indication puts a threshold value there which can be changed with the mouse. A beat is recognized if the VU advertisement exceeds the threshold value.
« AutoGain » can here with a click actively/deactivated (-) and shows the multiplier found out automatically.
{{Picture_with_subtitle |DMXC2_Manual_sound_analyzer_autogain.png|9|The AudioGain display}}

===Sound2Light settings===
If one of the 24 spectrum joists is assigned to one or several channels (click on one of the joists), then this gets '''GREEN''' and you can store in a bank.
The S2L function can be activated/deactivated about the corresponding hooklet now.

There are another four attitudes which concern ONLY the S2L:

* Switch threshold at X%:
* Ignore trigger level (see button ''Edit channel settings'')
* Set to X% when above threshold:
* VU-meter

The switching threshold is the lower value which must be exceeded so that a S2L version is carried out. The values above the switching value are NOT distributed newly on all 255 values but merely all values put on 0 below the threshold. The threshold is therefore e.g. only values of 26-255 therefore arrive at 10% at the DMX device (> 25. 5).
This global attitude can with a hooklet under « Edit channel settings » be lifted for some spectra again (checking box « Ignore trigger level »).

One still would like (that is only 0, or value on X) can so to receive a binary version in addition, under « Set to X% when above threshold » a DMX value 'X' which is always submitted to the version as soon as the threshold value was exceeded being adjusted. This attitude doesn't have any effect as soon as « Set to X% when above threshold » you deactivated.

This « VU meter » is the easiest to understand if one sees it. A spectrum joist therefore should for test purposes, instead of device, the dimmer channels are assigned to one by 4-8 devices.
The choice is radio button « All similar » the behavior is same at all '''lamps''', put. The choice is radio buton , though « VU meter » the rash splits up (since possible for 2. 11), on all 4-8 joists so. Watch ideal in the graphic stage view (at positioning of Generic dimmers besides each other. )

==Module commands==

* Modul: '''Sound Analyzer'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 100px"| Channel
!style="width: 200px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="3"| Sound2Light
|style="width: 200px" rowspan="3"| The further orders (channel) only are applied to the Sound2Light function.
|style="width: 100px"| On/Off
|style="width: 200px"| The function can the T flags under use and be turned off one.
|- style="vertical-align:top;"
|style="width: 100px"| Activate
|style="width: 200px"| With the command the Sound2Light function is activated.
|- style="vertical-align:top;"
|style="width: 100px"| Deactivate
|style="width: 200px"| With the command the Sound2Light function is deactivated.
|- style="vertical-align:top;"
|style="width: 100px"| Bank
|style="width: 200px"| With the function bank the appropriate bank from this can drop down be selected in the sound analyzer.
|style="width: 100px"| Bank name
|style="width: 200px"| The bank names laid out correspondingly stand drop down in the sound Analyzer under channel from this.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Links and references==
<references/>

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Master_DMXC2
| TextBackwards = Master
| LinkForwards = BeatTool_DMXC2
| TextForwards = BeatTool
}}
[[de: Sound_analyzer_DMXC2]]
[[Category: DMXControl 2]]

Master DMXC2

2025-03-02T19:09:02Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Submaster_DMXC2
| TextBackwards = Submaster
| LinkForwards = Sound_analyzer_DMXC2
| TextForwards = Sound analyzer
}}
{{Start-LaTeX}}
==Overview==
{{Picture_with_subtitle |DMXC2_Manual_Master_Fenster.png|1|Der Master in DMXControl 2|right|200px}}
Being able to control primarily all dimmbaren channels with the master.
This module proceeds globally and provides the DMX values of all channels, which have been defined in the DDF as '''dimmer''' with a multiplier of 0-100%.
There are 2 global dimmer groups realized as well as the flash values and the speed of all effects overwritten. 
 
 
 
 
 
 
 
 
 
 
 
 
 

==Description==
{{Picture_with_subtitle |DMXC2_Manual_Master_module_icon.png|2|Module icon|right}}
The most frequent field of application for the master module is the Dimmen of all illuminants/light sources. Become all equipment by presetting which has a dimmer channel about this one & laquo; Grand & raquo; dimmed down.
The module can under the menu item « Window » as well as being found under the icon in the tax center.
 

{{Manual Box | en | Hint | It recommends this to himself [[Submaster_DMXC2|submaster]] module for testing the master module also open and cover with 2-4 different equipment.
}}

===Grand vs. Grand2===
{{Picture_with_subtitle |DMXC2_Manual_devices_configure_device.png|3|Device configuration|right|250px}}
If one liked to stop this dimming at some device or subject to a second self-contained dimming, this happens about this one « Grand2 ».
A small change is, however, in the for this at every device « Device configuration » necessary. There which master is, to then fixed the device is assigned.
The checking box is located in the device configuration which can be reached about the device list or the graphical view « Dimmer: Secondary grand master ».
If this checking box is active, this one is as of now « Grand2 » responsible for this device. (The function should be dawned from, this device doesn't have any dimmer channel.)
 

===Flash===
At this « Flashmaster » is the DMX value fixed for the flash effect. The value of a certain channel which was selected in the submaster module or in the command box is overwritten temporarily.
If a higher DMX value than this one caused effects by others currently is adjusted now, we get a '''flash''' (lightning). A very little value is, however, (near by zero) voted, we get another possibility of a blackout (see control center).
 
===Speed===
This one « Speed master » influence not the individual device but the effects in which device has already been used.
The speed master concrete accesses the speed values of all chasers.
The multiplier can be adjusted of 1-200 %. 

==Controls==

All faders can be used with the mouse. You can click drawn or directly to the position of the set point. If the regulator is activated (dotted small box), a change can be carried out also with the arrow keys. The regulators are busy so arrow corresponds to a movement of the regulator up to down understanding and therefore invertedly as mufflers.
==Module commands==

* Modul: '''Master'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 100px"| Device/Function
!style="width: 200px"| Description
!style="width: 50px"| Channel
!style="width: 250px"| Description
|- style="vertical-align:top;"
|style="width: 100px"| Grandmaster
|style="width: 200px"| The broader parameter is applied to the grand master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the grand master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|- style="vertical-align:top;"
|style="width: 100px"| Sek. Grandmaster
|style="width: 200px"| The broader parameter is applied to the secondary grand master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the secondary grand master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|- style="vertical-align:top;"
|style="width: 100px"| Speedmaster
|style="width: 200px"| The broader parameter is applied to the speed master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the speed master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|- style="vertical-align:top;"
|style="width: 100px"| Flashmaster
|style="width: 200px"| The broader parameter is applied to the flash master.
|style="width: 50px"| set
|style="width: 250px"| The value is applied to the flash master. (Submaster, midi, DMXIn or the percent value indicated to the O flag)
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Submaster_DMXC2
| TextBackwards = Submaster
| LinkForwards = Sound_analyzer_DMXC2
| TextForwards = Sound analyzer
}}
[[de: Master_DMXC2]]
[[Category: DMXControl 2]]

Chasers tool DMXC2

2025-03-02T19:08:15Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Cue_list_DMXC2
| TextBackwards = Cue list
| LinkForwards = Submaster_DMXC2
| TextForwards = Submaster
}}
{{Start-LaTeX}}
==Overview==
One can have with this tool to make chasers and to go off. An chaser represents an expiry of cues which can be changed in the order, speed, Sound2Light etc. , though. An chaser also stands for

* a coherent light game of a different devices (e. g. interplay two color change machines),
* a functional expiry of a device (the course of the DMX values) describes a function
* particularly concise activities (e. g. stroboscope chaser)

Several chasers can be started parallel.

{{Manual Box | en | Hint | An chaser in DMXControl corresponds to the concept '''Chaser''' from other programs. An chaser of the chaser of one is similar, [cue_list_DMXC2|cue list]] at long last, however, offers extended functions.
}}

==Description==

All chasers of a project are represented by a tree structure in DMXControl. Every chaser contains arbitrarily many steps (single scenes).
{{Picture_with_subtitle |DMXC2_Manual_Effektsequenzer_Fenster.png|1|Der Effektsequencer|center|500px}}

Chasers and steps can arbitrarily be copied or deleted, moved, hinzugefügtt. Of course the individual scenes also can be chosen from the scene library. Steps can be defined also as an order, audio scene or movement scene.

==Controls==

The view is in the left upper part of the Effektsequencer window with the tree structure of all chasers. The individual steps can be (see figure 1) one or hiddenly with the '''+/-''' node.

===Effect management===
{| style="float:right"
|-
| {{Picture_with_subtitle |DMXC2_Manual_chaser_tool_effect_management.png|2|Effect management|right|200px}}
|-
| {{Picture_with_subtitle |DMXC2_Manual_chaser_tool_effect_effect.png|3|Effect configuration|right|200px}}
|}
On the one hand, in the area of effect management (see figure 2) can by the button « Add » new effects made, existing effects with the button « Copy » copyed or with the button « Delete » being deleted. Furthermore the possibility passes the effects by means of the button « arrow high » and « arrow down « moving in the list.

Apart from the effect construction, the cues contained in the stock exchange securities (''steps'') also can be made, processed or deleted here. In addition, the cues can be moved within the effect. (see figure 2)

====Effect====
If a new effect is made, he can in the area « Effect » being configured. The effect should be assigned to here in the area of ''effect name'', a meaningful name. The account mode also can be adjusted as well as the Sound2Light mode activated in this area. Effects can as well here by input of a group name ''(group name in brackets)'' be grouped in a full bracket (see figure 3).

{{Manual Box | en | Important | No blanks may happen in the Gruppennamenklammer since otherwise DMXControl doesn't recognize the group names. An underscore can be used as a substitute for the blank. 
Effect names and group names must be a blank, otherwise the group isn't recognized.
}}

=====Effect-grouping=====
With the effect grouping, similar effects can be grouped together, whereby an effect can also be in several groups at the same time. To do this, all group names are written with a semicolon separated into the parenthesis.
<Effectname>(<Group1>;<Group2>;<Group3>;...)
With several groups assigned to an effect the effect speed with the first group and the intensity is connected with the second group.
<Effectname>(<SpeedGRP>;<IntensityGRP>)
Shall an effect be assigned to several groups, the speed and the intensity, however, be assigned to the same group so the effect name must be typed in twice.
<Effectname>(<SpeedIntensGRP>;<SpeedIntensGRP>;<OtherGRP>;...)
Through this extended functions offer themselves at the effect control. With the option « Execute always only one chaser per group » you can reach that the active effect is ended in a group as soon as a new effect is started from the group. However, this action doesn't have influence on effects of other groups. With this function it can be prevented that several effects which influence the same equipment channels are active at the same time. Otherwise e. g. it can come to an unchecked version of the DMX values of the individual effects what at headlights to one flicker leads.

A typical application case is the separation from movement stock exchange securities and normal headlight stock exchange securities. The list of the effects then can for example look so:

Running_Light1(Speed;PAR)
Change_Indicator(Speed;PAR)
Everyone_Flash(Speed;PAR)
Scanner_In_Circle(Speed;Scanner)
Wild_Swivel(Speed;Scanner)
Quiet_Atmosphere(Speed;Scanner)

{{Manual Box | en | Important | The following points serve the attitude or the syntax of groupings
* The advertisement of the effect groups can [[Program_settings_DMXC2|program configuration]] in the [[be adjusted right justified.
* Behind the group name no broader signs should be entered. Blanks appended inadvertently make the grouping ineffectively or similar.
}}

=====Effect play mode=====
The dropdown « Play mode » if influences the account of the effect, gives this one to six modes selectly can be.

{| class="wikitable centered"
|- style="vertical-align:top; text-align:left;"
!style="width: 150px; text-align:center"| Play mode
!style="width: 450px;"| Description
|- style="vertical-align:top;"
|style="text-align:center"| ''Manual''
| The respectively next cue must be manually ''the next step'' actively at choice of manual, over the Button.
|- style="vertical-align:top;"
|style="text-align:center"| ''Normal''
| Become the cues of the row at choice of regular after worked off from above down. Is the checking box ''repeat'' actively, then is after processing of the last cue you start with the first one again.
|- style="vertical-align:top;"
|style="text-align:center"| ''Reverse''
| At choice of backward the scenes of the row are after worked off up from below. Is the checking box ''repeat'' actively, then is after processing of the first scene you start with the last one again.
|- style="vertical-align:top;"
|style="text-align:center"| ''Bounce''
| At choice of bounce the cues of the row are after worked off from above down. Is the checking box ''repeat'' actively, then is after processing of the last cue you work off from below up.
|- style="vertical-align:top;"
|style="text-align:center"| ''Random''
| At choice of random, be the cues worked off in a random order.
|- style="vertical-align:top;"
|style="text-align:center"| ''Only one step''
| The checking box ''Repeat'' is not actively if is a cue is executed at the effect list by chance and the effect deactivated after that.
|}

* The checking box & laquo; '''repeating''' & raquo; effect has started after expiry once more.

* The checking box « '''music controlled''' » [[BeatTool_DMXC2|beat tool]] lets the cues in the effect depending of or of the Tap button.

====Effect (extended settings)====
{{Picture_with_subtitle |DMXC2_Manual_chaser_tool_effect_extended_settings.png|4|Effect extended settings|right|200px}}
At the click on the button « Extended settings » does the extended effect configuration field get visible. (see figure 4)

This configuration field offers extended attitudes towards the configuration of the effect.

* This provides at activation for it the checking box '''ignore global speed master''' the effect isn't influenced by the speed master in the module [[Master_DMXC2|master]].

*An entry field also is the dropdown button '''category'''. A new page tab can be produced (see figure 1 page tab LED) by the input of a new category namen here. When producing the first page tab, the page tab default also is produced per default. This page tab cannot be deleted. By the assignment the effects can be divided up on different page tabs. By assignment of an effect of category amen existing to one, this is assigned to the corresponding page tab and, later, also still can be changed or moved. If no more effect is assigned to a page tab, then the page tab is deleted automatically.

* A priority can be fixed in the entry field '''priority'''. Effects with a higher priority end effects with a lower priority. It the checking box "'''only a effect per group'''" was activated presupposed. Of zero the effect means this a priority no priority has.

* n the entry field '''repetitions''' one can repetitions determine after how many the effect shall be ended. Zero stands the value for an infinite repetition.

* With the two buttons '''Command define''', one can call module-related orders at the start and when ending the scene '''on start''' and '''on stop'''.

{{Manual Box | en | Hint | The advertisement of the effect groups can in the [[Program_settings_DMXC2|program stettings]] be adjusted right justified.
}}

===Cue konfiguration===
{{Picture_with_subtitle |DMXC2_Manual_chaser_tool_step.png|5|Step setting|right|200px}}
If a new step towards an effect was made, then this can be configured in the entry field "'''step'''". (see figure 5)

Die Erstellung von Szenen wird ausführlich im [[Szenen_DMXC2|Kapitel 9 Szenen]] erklärt.
The construction of cues is explained in detail in the [[Szenen_DMXC2|chapter 9 cues]].

* The meaningful name of the step can be described in the entry field "'''step name'''" or afterwards also at selected step be changed.
* With the checking box "'''active voice'''" one can decide worked off in the effect whether the step is.
* The one fade time of the select cue can be determined in the entry field "'''one fade time'''".
* In the entry field "'''hold time'''" (in the scene list as a duration described) the time can, the scene lasts before be this one is switched to the next step adjusted.

{{Manual Box | en | Hint | The entry fields at the one fade time and hold time (duration) stand for on the right to the left for seconds, seconds and minutes.
}}

===Play===
{{Picture_with_subtitle |DMXC2_Manual_chaser_tool_play_all.png|6|Play configuration|right|200px}}
Settings for the playback can be made in the chaser tool window in 2 areas.

====Play (all)====
Under '''Play (all)''' finds himself to be, the button on the other hand is here to stop all regular effects ('the configuration setting for the account at all stock exchange securities (see figure 6) (« ''Stop all chasers''' & raquo;).
* Checking box 'execute ''only an effect per group''': Depending on attitude the chosen effect is started in addition or he replaces all regular effects (which then are ended). This quality refers to all effects.

* Checking box ''' Start fade from last values ''': Default gets after an effect is worn out, this one existed changed to the light atmosphere before the start of the effect. This university verses verifies by old values means at the change, between 2 effects the old effect is changed into the new one but ending is this. If the checking box is highlighted, the last values are left on the universe. Important: This concerns effects only grouped in which equipment is here overwritten of course again if new to it, too started effect also uses this equipment.

* Checking box '''Start only if no other is running''': Active is only selecting cash if the checking box also '''execute only an effect per group'''. An effect is already going on in a group, it isn't that way possibly to start another one from this group. For this, at first the regular effect must be ended.

{{Manual Box | en | Important | DNot means that after ending the effect (or another effect of the group), furthermore the last values are distributed '''only start the function when no-one runs'''! All equipment returns before to the stand the first effect was started. To realize this, this one recommends himself the use [[Cue_list_DMXC2|cue list]].
}}

====Play (selected chaser)====
{{Picture_with_subtitle |DMXC2_Manual_chaser_tool_play_play_selected_chaser.png|7|Play (selected chaser)|right|300px}}
The attitudes under ''' Play (selected chaser) ''' apply to the respectively highlighted effect in the list and be stored for every effect.
* Button « Play » With this button the effect selected in the list can be started or stopped. The button functions alternatingly as start/stop button.
* Button « Execute next step » With this button an effect can: this one has ''manually'' the account mode further switched be.
* Fader « Intensity » One adjusts the brightness of the dialed effect with this fader kan in the list: provided that himself in the effect a channel with this type: ''dimmer'' be. (Type: Dimmer see [[DDF_DMXC2|Chapter 32 DDF basics]])
* Checking box « Intensity grouped » One can group the intensity: for the select effects within the group by the checking box. D. h, all the select effects of a group react to the change of the intensity at activation.
* Fader « Speed boost » Here the speed of the effect can be influenced: at the play. All steps of an effect are accelerated or slowed down in the same relationship.
* Checking box « Speed boost grouped » One can group the acceleration: for the select effects within the group by the checking box. D. h, all the select effects of a group react to the change of the acceleration at activation.

=== Use of Effects ===
Effects can either be started directly manually from the chaser tool or be embedded in any forms of cue lists (also audioplayer and textbook). One must the the menu item to this from the context menu « Command » selecting. E.g. a single effect is activated with the command ''start'' and ''stop'', e.g. there also is an command to stop all regular effects. Example: One can tie effects by one going on adding and then the menu item in the audioplayer « Command » selects.

Under '''module''' then '''chasers''''. One then has made this one under '''function''' choose the effect before. Where the effect shall put then the first Marker '''start''' down and make order '''stop''' there where the effect shall stop start there.
Which one can be executed by stock exchange securities per one Init or Finalizer order at the start and end, under « extended effect settings » can defined be.

{{Manual Box | en | Hint | Please always assure before that the chaser/step to be renamed also really is selected. Sometimes it can happen that by opening/closeing of the tree the marking node switchts. Also causing an effect this isn't automatically marked yet.
}}

==Module commands==

* Modul: '''Chasers tool'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px"| All
|style="width: 195px"| The command will apply on all chasers.
|style="width: 105px"| Stop
|style="width: 195px"| All running chasers will be stoped.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="11"| Selected
|style="width: 195px" rowspan="11"| The further command will applied to the current effect. Stand above an effect category, if got categories used, the corresponding category amens. These although can be selected, however, cannot be assigned to any order.
|style="width: 105px"| Start/Stop
|style="width: 195px"| The comand start/stop starts and stopt the select chaser for an automatic expiry. (The command should be used in connection with the T flag.).
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command start starts the selected chaser in the chaser tool for an automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The command stop stops the selected chaser in the chaser tool for an automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Set acceleration
|style="width: 195px"| With this command the chaser acceleration can be backed the percent value entered in value.
|- style="vertical-align:top;"
|style="width: 105px"| Set intensity
|style="width: 195px"| With this command the chaser intensity can be backed the percent value entered in value.
|- style="vertical-align:top;"
|style="width: 105px"| Next stept
|style="width: 195px"| Lead the next step out at stock exchange securities which are prepared for account mode ''only a step''.
|- style="vertical-align:top;"
|style="width: 105px"| Repeat on/off
|style="width: 195px"| Turns off the option ''repeat'' for the chosen effect. See note (use T flag)
|- style="vertical-align:top;"
|style="width: 105px"| Audio triggered on/off
|style="width: 195px"| The option ''music control'' for the chosen chaser switches turns on/off. See note (use T flag)
|- style="vertical-align:top;"
|style="width: 105px"| Next play mode
|style="width: 195px"| Select the ''next account mode'' for the chosen effect.
|- style="vertical-align:top;"
|style="width: 105px"| Play mode: * Manual * Normal * Reverse * Bounce * Random * Only one step
|style="width: 195px"| Select the corresponding play mode for the chosen chaser.
|- style="vertical-align:top;"
|style="width: 105px"| Intens. with Start/Stop
|style="width: 195px"| The command starts ''Intens. with start/stop'' and stoped a percent value can the select chaser submit for the brightness for automatic expiry, simultaneous about the value column.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next Previous Several entries
|style="width: 195px" rowspan="2"| The further order is on the currently near, previous or into the drop down named effect used.
|style="width: 105px"| Select
|style="width: 195px"| Or this one selects the near, previous the dropdown equipment/function named chaser into.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop Set acceleration Set intensity Next step Repeat on/off Audio triggered on/off Play mode Intens. with Start/Stop
|style="width: 195px"| see above
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

{{Manual Box | en | Hint | If the option ''repeat'' or ''audio triggered'' is used in the chaser tool, this must without use the T flags are carried out. The following command sequence must be indicated for switching on here: 
'''Modul:''' Chaser 
'''Device/Function:''' Chaser name, next, previous, current 
'''Channel:''' Repeat on/off, Audio triggered on/off 
'''Flag:''' O-Flag (Used specified value) 
'''Value:''' 100 
Turning off is correspondingly with the '''value:''' 0.
}}

==Tip(s)==

With effect grouping, e.g. you can use the following trick:

Just make 3 different scanner movements. ONLY the position is stored in every scene (to this make hooks) and no brightness, color, Gobo etc. Then one makes exactly the opposite and programs 3 effects you can again only with color-cycling. When required then you can again 3 only with gobo changing. And one already can arrange a gigantic combination from these 3x3 chasers. For this one then takes '''starter effects''' contain the nothing else as the orders '''start movment1, start colorchange3, start gobochange2'''. With corresponding hold times a sequence is programmed by '''automatic''' changes so quite fast.

==Links and references==
Tutorials
*[[Manuelle Erstellung eines Lauflichtes]] '''Not yet, wait until translation'''
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Cue_list_DMXC2
| TextBackwards = Cue list
| LinkForwards = Submaster_DMXC2
| TextForwards = Submaster
}}
[[de: Effektsequencer_DMXC2]]
[[Category: DMXControl 2]]

Cue list DMXC2

2025-03-02T19:06:51Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Scenes_DMXC2
| TextBackwards = Scenes
| LinkForwards = Chasers_tool_DMXC2
| TextForwards = Chasers tool
}}
{{Start-LaTeX}}
==Overview==
With the cue list several cues can be sequenced. This offers you the possibility of organizing the individual cues at an event with predefined expiration time. This module is similarly suitable for theater events and comparable events.

{{Picture_with_subtitle |DMXC2_Manual_cue_list_new_cue.png|1|Create a new cue|center}}

Per cue which takes effect however only within the cue list or an effect a one dazzling time as well as a duration you (describe in the Chasers tool) as hold time can be indicated.
Values of a cue remain active on the version until they are overwritten explicitly, for example by another cue.

All cues are managed in the cue library and can be chosen and reused from there.

==Description==

One or several cues form a cue list. The maximum number of cues per cue list is only limited by the resources of your computer. Playing a cue list means the sequential execution of all individual cues under consideration of the the one dazzling time and duration (hold time). The cues can also manually be further switched. Several cue lists can expire at the same time (parallel operation).

E. g. you use the cue tool at theater applications and everywhere there where it suffices, simple cues after a particular duration (hold time) further add-on. The cue tool works resource loading substantially less than the [[chaser_tool_DMXC2|chaser tool]]. The cue list is always worked off sequentially and to be more precise as of the cue which is just highlighted. For the beginning of the play, so the first entry must be highlighted.

==Controls==

{{Picture_with_subtitle |DMXC2_Manual_cue_list_window.png|2|The cue list|center}}

So that the button « GO & raquo; the manual further wiring can work, the following conditions must be filled for:

*The cue list must be represented (Button » play « is clicked).
*The respective cue must have '''manually''' as a duration (hold time) (adjust time to zero and one then still reduce tenths). If a duration (hold time) is adjusted, this is taken into account which yes also can be quite practical (to let e.g. a sequence of light atmospheres go with firm times and switch to the next cue manually only later again).
*The cues must be marked with the checking box (hook), they otherwise are deactivated. 

At a right click on the cue name opens himself a context menu with the menu item « Set color . . . « a color palette window opens where a color can be selected for the cue name.

{{Manual Box | en | Hint | If HTP is not necessary, so HTP turn it off in the [[Program_settings_DMXC2|program settings]] (depends on the cue definition).
}}

==Module commands==

* Modul: '''Cue list'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 105px" rowspan="5"| Select
|style="width: 195px" rowspan="5"| The further order is applied to the currently select cue list. (The Command selects at this function the makes no sense)
|style="width: 105px"| Start/Stop
|style="width: 195px"| The command ''Start/Stop'' starts/stops the select cue list at automatic expiry. (The command should be used in connection with the T flag.)
|- style="vertical-align:top;"
|style="width: 105px"| Start
|style="width: 195px"| The command ''Start'' starts the select cue list at automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| Stop
|style="width: 195px"| The command ''Stop'' stops the select cue list at automatic expiry.
|- style="vertical-align:top;"
|style="width: 105px"| G O !
|style="width: 195px"| The command ''G O!'' executes the next cue from the Szeneliste.
|- style="vertical-align:top;"
|style="width: 105px"| Scroll to current cue
|style="width: 195px"| The command '' scroll to current cue'', forces the current cue to scroll to the visible window area.
|- style="vertical-align:top;"
|style="width: 105px" rowspan="2"| Next Previous Other entries
|style="width: 195px" rowspan="2"| The further command is or into the dropdown named cue list used on the currently next or previous cue.
|style="width: 105px"| Select
|style="width: 195px"| Selects the next (previous) cue list or the one selected in the dropdown ''device/function''.
|- style="vertical-align:top;"
|style="width: 105px"| Start/Stop Start Stop G O ! Scroll to current cue
|style="width: 195px"| see above
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==

*As follows one can configure cue lists so that the following one is activated and started when reaching the end of a list: An command cue is with the order at the end of every cue list ''' cue list > Next & gt; Start ''' to insert.
*There is an accumulation of the fade and permanent times to synchronize the list with a time code for longer scene lists since the version 2. 12.
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Scenes_DMXC2
| TextBackwards = Scenes
| LinkForwards = Chasers_tool_DMXC2
| TextForwards = Chasers tool
}}
[[de: Effektsequencer_DMXC2]]
[[Category: DMXControl 2]]

Channel view DMXC2

2025-03-02T19:06:32Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = output_plugins_DMXC2
| TextBackwards = Output Plugins
| LinkForwards = Scenes_DMXC2
| TextForwards = Scenes
}}
{{Start-LaTeX}}
==Overview==
The channel overview displays a general overview of the current channel status of DMX signals. Information about the current channel values, the channel assignment, and the source of the channel value are represented here.

==Description==
You can see and adjust directly the channel value of every single DMX channel in the channel overview. This module serves in the disco area to analyze to test ticks or around an unknown device configuration mainly. The channel overview is primarily the individual light atmospheres helpfully in the theater area at being clear to it and the generation. E.g. you also can test the effect of procedures into the DDFs with this window since the DMX values of the individual channels are shown.

{{Picture_with_subtitle |DMXC2_Manual_channel_overview_window.png|1|The channel overview|center}}

The individual channels are represented in the middle part of the channel overview into tabular form. Every cell represents one of the altogether 1024 of DMXControl supported DMX channels. In turn each of these cells is subdivided into several areas which contain different information.

{{Manual Box | en | Hint | Channel representation style="text-align: left;"{{!}}The channel number which gives the address of the appropriate channel is in the left upper corner of the cell. An advertisement for the channel value which shows the intensity of the appropriate channel from 0 to 255 is on the right side. A joist represents the channel intensity graphically besides that on the left.

Directly you show under this, to which function the channel in the assigned device heard or which equipment function he heads. The name of the corresponding device is a line in a gray field represented below. If a device has several channels, the gray field reaches to all appropriate channels.

A colored marking which announces the source of the channel value is shown on the lower part of the cell. The assignment of the color to the source has to be taken from the lower part of the channel overview.

{{!}}
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_channel_representation.png|2|Description of the channel information|250px|center}}
}}

{|
|-
| The channel chosen currently is marked by a red frame. Click in one of the cells to select another channel. The value of the chosen channel can be changed by the Slider on the left window edge. However, a multiple selection of channels is also possible with the help of the Shift and Ctrl buttons. ||
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_channel_multiple_selection.png|3|multiple selectionof channels in the channel overview|500px|center}}
|}

==Controls==
====Button Out/In====
With the button « Out » or « In » in the lower left corner you adjust, whether the DMX-out or DMX in values is shown. Channel values are, only then shown case the active version Plugins DMX into support in the DMX in view.

====Slider====
A Slider which is used to adjust the value of the select channels is directly over this button.
The scrolling up joist on the right side serves to scroll by the indication of the channels merely.

====Double-click on channel====
Double-click through one an input window in which new DMX value can one want to enter for the select channel by keyboard opens on a channel (cell in the channel overview).

====Marking several channels====
Buttons ''''Shift'''' and ''''Ctrl'''' can with the Windows typical channel areas are selected which have changed by the Slider or the scrolling up wheel on a value at the same time for themselves.

====Changing channel value with mouse wheel====
With a mouse with scrolling up wheel the values of the active highlighted channel can get high or scrolled down in 10s steps.

====Channel On/Off with Space-button====
With the Space button you can switch one or several highlighted on (DMX value 255) or turn (DMX value 0) off.

====Source overview====
In the lower area of the channel overview everyone is shown to sources possible for the version and provided with a colored marking, through what one can identify the source for the channel value version of a channel. Every source has his own mixer channel.
{{Picture_with_subtitle |DMXC2_Manual_channel_overview_source.png|4|Details of all possible DMX value sources.|center|650px}}
The entry '''unknown source''' puts the public mixer channel, which all program parts of DMXControl which don't have a mixer channel of their own use. The sources are unknown because the mixer channel cannot be assigned to any tool by DMXControl directly.

==Tip(s)==

The window '''channel overview''' also can be used to test a new equipment. Any DMX channel (even without a Device Definition) may be set here. Simply select channel and use the Slider on the left. Of course the start address of the device has to be taken into account.

{{Manual Box | en | Hint | With the space bar you can toggle between the channel values '''0''' and '''255'''.
}}
{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = output_plugins_DMXC2
| TextBackwards = Output Plugins
| LinkForwards = Scenes_DMXC2
| TextForwards = Scenes
}}
[[de: Szenen_DMXC2]]
[[Category: DMXControl 2]]

Scenes DMXC2

2025-03-02T19:04:41Z

Jnoetzel:

{{Manual Header
| Type = DMXC2 Main-Software
| Version = 2.12.2
| LinkBackwards = Channel_view_DMXC2
| TextBackwards = Channel overview
| LinkForwards = Cue_list_DMXC2
| TextForwards = Cue list
}}
{{Start-LaTeX}}
==Overview ==
In the lighting engineering scenes are basic elements. A scene represents a light atmosphere, that is both the brightness values of headlights, like also the positioning, colors or motives (so-called Gobos) etc. , of Moving Heads or scanners. Scenes save information about DMX values, audio files or scanner or Moving Head movements, in DMXControl. Every project is built up from a combination from different self-definable scenes and scene combinations. 

== Working with cues ==
(Except for the commands) DMXControl 2 has a name of his own every scene in DMXContol 2 which can be chosen individually. Empty and special signs are also permitted in the scene name. However, it should be taken care of on this that this name is self-explanatory such as '''song X''', '''solo song share''' or '''LED PAR1 red'''. On the one hand, this ensures that the function of a scene still can be recognized after quite a long time, too. On the other hand, a scene so also can be found quite simple (see below) in the cue library if one liked to reuse her in another place.

In the textbook, scenes behave a little differently than in DMXControl's rest. Although scenes also have a one dazzling time but no length in the script. Scenes cannot be further switched or ended after a certain time either through this.

Scenes become in every module about the button « Add » added to a project. By a click on the button « Add » a menu (see figure 1) about the one in the individual scene ways, orders, the cue library or on which opens « Submenu produced automatically » can grasped it be.

{{Picture_with_subtitle |DMXC2_Manual_cues_add-menue.png|1|Menue add for cues|center}}

{{Manual Box | en | Hint | For the faster scene construction do the button « Add & raquo; by simultaneous hold of the button « Shift » being accessed the menu item you selected in the last time.
}}

==Cue types==
There are altogether five scene types, the '''simple scene''', '''the order''', the '''audio scene''', the '''movement scene''' and the '''composition scene''', in DMXControl. Depending on task another scene type offers its services for the use. You find a short explanation as well as some examples of the respective use in the following fast overview to every scene type. 

===Quick overview===
{| class="wikitable centered"
|- style="vertical-align:top;"
! Type
! Description
|- style="vertical-align:top;"
|style="width: 150px"| Simple cue
|style="width: 600px"| Store the DMX values of several eligible equipment channels. So light atmospheres quite simply can be stored, e.g. the color and dimmer values of LED PAR cans.
|- style="vertical-align:top;"
|style="width: 150px"| Command
|style="width: 600px"| Serve for the control of certain parameters in the project, such as starting or stopping an effect by another cue, the handing over of a value to a device or the control of the grand master.
|- style="vertical-align:top;"
|style="width: 150px"| Audio cue
|style="width: 600px"| Audio files can be tied and played with her in a simple way in the project.
|- style="vertical-align:top;"
|style="width: 150px"| Moving cue
|style="width: 600px"| Store movement processes for scanners and movingheads, such as the circle figure of a movingheads.
|- style="vertical-align:top;"
|style="width: 150px"| Composition cue
|style="width: 600px"| Combine several scenes to a complete scene. E.g. several orders can be started with her at the same time.
|}

===Simple cue===
One represents light atmosphere also described as a CUE one '''simple cue''' in DMXControl in the lighting engineering. A user-defined choice of channel values of the devices available in the project is stored in her. Every scene ever has an fade in and a hold time (duration). The one dazzling time takes effect when starting a scene. DMXControl dazzles about into the started scene in the indicated one dazzling time of the current light atmosphere. The duration which services DMXControl before the following cue is displayed, e. g. in the chaser tool can be adjusted with the hold time. 

First, to make a new '''simple scene''' in a module, e. g. one adjusts the desired light atmosphere about the channel overview or the sub-master. One then clicks in the corresponding module on the button « Add « and vote in the following pop-up menu « Simple cue » from. The dialog appears « Save cue » (fig. 1)
{{Picture_with_subtitle |DMXC2_Manual_Szenenliste_SzeneSpeichern.png|2|Dialog zum Speichern einer Szene|center}}

All DMX values changed since the last scene storage get pre-select on the left side automatically. You can change these attitudes after the requirements of the scene. Only those channel values are stored which are provided with a hooklet. If a hook is black, the DMX value is stored newly so, the hook is gray, the value stored before in this scene is kept and not replaced by an amended value.

{{Manual Box | en | Important | The choice should be well-considered. If several scenes shall go off at the same time, channels only may into at most be select for one of the corresponding scenes. On the other side should for theater applications if possible all dimmer channels be stored so that every scene can be started independently of other scenes. For this the function is « Save all (not recommended) ».}}

Channels can be looked for by names in the search window. Three button with which the tree of the scenes can be opened up differently are next to the search window:
*« - » close all device nodes
*« + » open all device nodes
*« / » only display channels, witch having values are different from 0

The buttons under the search window permit a simpler marking of the channels. With « Clear » is the channel choice deleted, « all » channels will be marked « Store » and stores the current choice intermediately « Recall » the one with the button « Store » stored choice. Exactly this one last two button simplify the choice at channel assignments always returning.

{{Manual Box | en | Hint | To ensure work a faster when making scenes, one can himself by hold of the button '''SHIFT''' and a simultaneous click on the button « OK » the previous click on the button « Recall » economizing.
}}

{{Picture_with_subtitle |DMXC2_Manual_cues_save_cue_search.png|3|The search in the dialog « Save cue «. |center}}

One dials a channel in the left window (including hooklets set), one can change the DMX value to be stored also with the two entry fields ''value [byte]'' (as a numerical value between 0 and 255) or with equal rights with ''value [percent]'' (in an integer percent detail) in the lower part of the window.
{{Picture_with_subtitle |DMXC2_Manual_cues_save_cue_input_value.png|4|Manual input of a channel value|center}}

The choice attitudes towards the advertisement are temporary and aren't stored when leaving the dialog. 

On this one raked side the window be able to she give a name to the light atmosphere adjusted before and the one dazzling time as well as her duration define. You can do the duration on also by adjusting the time to zero and reduction by another step « manual » putting. E.g. DMXControl runs the next scene through it in the scene list first if the button « GO « you push. Furthermore can you adjust the fading over point therefore display, switch channels be switched over, save a comment on the scene and divide up the scene into a self-definable category to this the time. To this one simply writes down the name of the category on the appropriate field. This doesn't exist yet, a new category is laid out so automatically.

{{Manual Box | en | Hint | The legend box is only a legend in the dialogue window for the explanation on the right down side. One can change nothing in her even if it has the appearance.
}}

===Commands===
Commands offer extensive and versatile control possibilities in DMXControl. Functions or parameters (values) of single modules or devices can specifically be changed or put with them. This is possible also over module limits so that a module also can steer a function of another module. So for example an order can start an effect in the chaser tool or adjust the expiry speed in the audio player. A nesting of stock exchange securities also quite simply can realize be ordered, effects started or stopped the in turn other one with orders.
{{Picture_with_subtitle |DMXC2_Manual_cues_edit_commands.png|5|Dialog for saving of a command|center}}
In the dialog « edit commands » they can arrange the corresponding command. A command has the basic structur:

<Modul> - <Function> - <Attribute> - <Flag> - <Value>

{| class="wikitable centered"
|- style="vertical-align:top;"
! Type
! Description
! Button
|- style="vertical-align:top;"
|style="width: 150px"| <Modul>
|style="width: 600px"| Aim module in which the order shall carry out an attitude
|style="width: 150px"| left dropdown
|- style="vertical-align:top;"
|style="width: 150px"| <Funktion>
|style="width: 600px"| Methods, actions or objects provided by the select module. Choice is dependent on the chosen module.
|style="width: 150px"| middle dropdown
|- style="vertical-align:top;"
|style="width: 150px"| <Attribute>
|style="width: 600px"| Either an attribute or the operation at sub-objects. Choice is dependent on the chosen function.
|style="width: 150px"| right dropdown
|}

Only these will support functions of the corresponding module shown through which the choice of the correct order is quite simple. 

In addition under three drop down different flags with which one can influence the order can be put. You think in the corresponding module articles an exact overview, which orders and flags a corresponding supports module and what they cause. You find orders a general survey about everyone in DMXControl in the appendix in this one possible [[Command_overview_DMXC2|Command overview]].

===Audio cue===
Audio cues are used to e.g. carry out sounds and pieces of music in theater projects. The audio cue confines itself to the account of the audio files purely. To provide a soundtrack for a piece of music with lighting effects placed from the point of view of time exactly, the audio player is suitable better.
{{Picture_with_subtitle |DMXC2_Manual_cues_edit_audio_cue.png|6|Dialog for configuration of a Audio cue|center}}
In the dialog « Audio cue » they can make a new audio cue. The path of the audio file is listed in the field '''audio file'''. with the button &laquo Open » on the right next to the input field the audio file is loaded and can with the button « Play » being pre-heard. You adjust the time over the duration until the following scene becomes execute in a scene expiry. Moreover, can vote for you, whether the account is concluded after expiry of the period.

{{Manual Box | en | Important | Since a scene doesn't have any duration in the script by definition, a wave file cannot here be broken off after a certain period either but is immediately ended. To be able to carry out a time controlled demolition of the audio playback nevertheless, they must insert the audio scene in an effect with predefined period and active demolition option. You then start this from the script by order.
}}

Furthermore audio scenes can be assigned to one by altogether 16 sound channels. These channels can respectively be completed by order out of other modules. Several audio cues also can lie on a channel. The audio cue will '''repeat account''' with the option in an endless loop represented.

{{Manual Box | en | Hint | To be able to see a listing of all active audio cues, you must in the control center on the arrow besides the icon « Audio playback » clicking.
}}

===Moving cue===
With moving cues, it is possible to create complex motion patterns for scanners and moving heads and put into a cue together. Other uses are possible such as a targeted control of the colour or gobo channels of a device are available, can be used so the movement control, versatile.
{{Picture_with_subtitle |DMXC2_Manual_Moving cue_editor_window.png|7|Dialog for creating an motion cue|center|600px}}
For information about creating a motion scene, see the article for more [[Motion_cue_DMXC2|Motion cue]]

===Composition cue===
Composition cues offer the possibility to combine multiple scenes into one. This is intended mainly for commands and several scenes with the same pop-up time and length. Scenes with different pop-up duration and stop time (duration) can not be summarized in this way.
{{Picture_with_subtitle |DMXC2_Manual_cues_edit_composition_cue.png|8|Dialog for configuration of a composition cue|center}}
A list with all cues in the cue list is located on the left side of the window. You can edit this list using the buttons «Add», «Edit» and «Delete». On the right side can customize the name of the composition scene, the fade-in - and holding time (duration) select settings and the transition point for all cues existing in the composition cue, when cues without pop-up time like for example commands are enabled. Among them, you can write a brief description of the composition scene even after a long time yet to know what the scene is.

==Cue libary==
Into the cue library, all of the cues used in the project are listed and globally in many modules available. A scene is newly created, a new entry into the cue library is created automatically. Existing cues can easily be inserted via the button «Add» of the appropriate modules using the menu entry «cue library». The now opening cue library represents the cues structured according to their type and according to the above-mentioned categorization.
{{Picture_with_subtitle |DMXC2_Manual_cues_cue_libary.png|9|The cue libary|center}}
The search and two option buttons located in the upper part of the window to affect the viewer into the cue library. On the right side, four buttons are located to manage individual cues. You can add new cues, as well as existing cues, edit, or delete. In addition, the cue library offers you also the possibility to copy individual cues. This is particularly important against the background of the cues when inserting from the cue list are not copied, but himself, described as input, refer to the appropriate instance of the scene in the cue library.

Cues from the cue library in a module are added to these are '' copied '', but it creates a link to the corresponding cue in the cue library. This ensures that a change this cue (E. g. for correction or improvement) together with global effect on all used parts. Therefore, you should only then repeatedly use a cue if the cue at all points must be the same. Otherwise, it is appropriate to create a new cue.

== Cue and chaser generator ==
In version 2. 12, DMXControl contains four scenes - and running light generators. These wizards allow you to create scenes and run lights automatically in three steps. Everywhere, where a scene using the button «Add» can be generated, you can «Created» create the wizard from the submenu. Independent scenes are created with all generated scenes in the scene library appear.
{{Picture_with_subtitle |DMXC2_Manual_cues_automatic_cue.png|10|Automatic cue creation|center}}
Step by step instructions, how to create scenes, with the respective Wizard, find one in the tutorial [[Automatic creation of a Chaser|Automatic creation of a Chaser (DMXControl 2)'''Not yet, wait until translation''']]

== Cue import from CSV==
Another way of the scene creation the sub-menu «Import from CSV» offers Here you can make at once several scenes in Excel or similar programs, which offer a CSV export, by entering the channels and the channel values

This writing table in the top row of the required channel address and in the rows below the dedicated channels channel values in an Excel table. The following table shows a 4 dimmer channel running light consisting of 4 generic dimmers.
The first column is for convenience only and is not to be entered.

{| class="wikitable centered"
|-
!Channel adress
!   1  
!   2  
!   3  
!   4  
|-
|Cue 1
|style="text-align:center;"|255
|style="text-align:center;"|0
|style="text-align:center;"|0
|style="text-align:center;"|0
|-
|Cue 2
|style="text-align:center;"|0
|style="text-align:;"|255
|style="text-align:center;"|0
|style="text-align:center;"|0
|-
|Cue 3
|style="text-align:center;"|0
|style="text-align:center;"|0
|style="text-align:center;"|255
|style="text-align:center;"|0
|-
|Cue 4
|style="text-align:center;"|0
|style="text-align:center;"|0
|style="text-align:center;"|0
|style="text-align:center;"|255
|}

Call the menu «Imoprt from CSV» of «Import wizard scenes from CSV» pops up here is the button «Open file» import the CSV file into DMXControl (see fig. 11).

{{Picture_with_subtitle |DMXC2_Manual_cues_import_from_CSV-1.png|11|Import from CSV: Step 1|center}}

Depending on the what CSV delimiter was used, can it be that as shown in Fig. 12 an error message appears. Anyway to get a correct display, you can select in the upper part between four CSV separator (comma, semicolon, space, tab).

{{Picture_with_subtitle |DMXC2_Manual_cues_import_from_CSV-2.png|12|Import from CSV: Step 2 with mistake|center}}

In our case the imported table is displayed after you select of the CSV separator (tab) correctly (see Figure 13).

{{Picture_with_subtitle |DMXC2_Manual_cues_import_from_CSV-3.png|13|Import from CSV: Step 2 without mistake|center}}

By clicking on the check box ''' channel number is first line''' the channel numbers in the first row are applied (see Figure 14).

{{Picture_with_subtitle |DMXC2_Manual_cues_import_from_CSV-4.png|14|Import from CSV: Step 2 (import channel numbers)|center}}

The fade-in - and hold-time (duration) for all scenes can be set in step 3 now, besides a name can be given the scenes which is consecutively numbered.

{{Picture_with_subtitle |DMXC2_Manual_cues_import_from_CSV--5.png|15|Import from CSV: Step 3|center}}

By a click on the button «Completing» are the scenes made and into the corresponding module taken from this this one «Import from CSV» you called.

==Module commands==
* Module: '''Audio cue'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="4"| Kanal 1-16
|style="width: 200px" rowspan="4"| The further command is used select of one of the 16 audio channels on this one.
|style="width: 100px"| Pause
|style="width: 200px"| Regards the channel selected under equipment/function as renewed call at, after the channel output is continued.
|- style="vertical-align:top;"
|style="width: 100px"| Rewind
|style="width: 200px"| Rewinds the audio file to start.
|- style="vertical-align:top;"
|style="width: 100px"| Stop
|style="width: 200px"| Stopped the audio file.
|- style="vertical-align:top;"
|style="width: 100px"| Set volume
|style="width: 200px"| Set the volume by take-over the indicated value.
|}

* Module: '''Cue libary'''

* Meaning from ''device/function'' and ''channel''
{| class="wikitable centered"
|- style="vertical-align:top;"
!style="width: 105px"| Device/Function
!style="width: 195px"| Description
!style="width: 105px"| Channel
!style="width: 195px"| Description
|- style="vertical-align:top;"
|style="width: 100px" rowspan="2"| All entries
|style="width: 200px" rowspan="2"| All cues are the entries the dropdown ''device/function'' within the cue library in. At select of an entry the command can in the dropdown ''channel'' be applied to the scene.
|style="width: 100px"| Execute
|style="width: 200px"| Execute the chosen cue directly.
|- style="vertical-align:top;"
|style="width: 100px"| Fade in
|style="width: 200px"| Executes the chosen cue, with the fade in time stored in the cue.
|}

Meaning of the ''Flags'':
{| class="wikitable centered"
|- style="vertical-align:top;"
! style="width: 35px"| Flag
! style="width: 105px"| Meaning
! style="width: 460px"| Description
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| T
| style="width: 105px"| Toggle mode
| style="width: 460px"| The Flag »''Toggle mode''« result in the function's being set by the first call and being reset by the second call.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| O
| style="width: 105px"| Used specified value
| style="width: 460px"| The Flag »''Used specified value''« result in the being assigned to the appropriate channel of the value in the openings' value. This value isn't DMX value 0 to 255 but a per cent value 0. 000 to 100. 000%
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| A
| style="width: 105px"| Ask for value
| style="width: 460px"| The Flag »''Ask for value''« result in the opening at call of the order of an input window in which the per cent value can be entered.
|- style="vertical-align:top;"
| style="width: 35px; text-align:center"| I
| style="width: 105px"| Ignore value 0
| style="width: 460px"| The Flag »''Ignore value 0''« result in the being ignored of a value of zero. Do you need at some orders to ensure a correct function.
|}

==Tip(s)==
Cues can usually double-click called be, i.e. the corresponding settings are then called and played.

==Links und Referenzen==
Tutorials
*[[Manuelle Erstellung eines Lauflichtes|Manuelle Erstellung eines Lauflichtes (DMXControl 2) '''Not yet, wait until translation''']]
*[[Automatische Erstellung eines Lauflichtes|Automatische Erstellung eines Lauflichtes (DMXControl 2) '''Not yet, wait until translation''']]

{{End-LaTeX}}
{{NavigationTop-Man2
| LinkBackwards = Channel_view_DMXC2
| TextBackwards = Channel overview
| LinkForwards = Cue_list_DMXC2
| TextForwards = Cue list
}}
[[de: Szenen_DMXC2]]
[[Category: DMXControl 2]]

Lesson 9 Tut3

2025-03-02T19:02:22Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_8_Tut3
| TextBackwards = Lesson 8
| LinkForwards = Lesson_10_Tut3
| TextForwards = Lesson 10
}}
==Overview==
The previous lession introduced simple cues. In this lesson we explain some more sophisticated features of scenes, e.g. the fanning feature. With fanning you can create impressive effects with groups of lamps, e.g. rainbow effects or waves.
DMXControl 3 provides an effect library.

==Lecture 9: Fanning, chasers and other effects==
DMXControl 3 extends the scope of scenes so that dynamic effects can be included, and you can apply certain algorithms for the attributes (e.g. DMX values) of included devices or groups. This allows you to create highly complex cues with a few mouse clicks. Don't believe it? Let's demonstrate how it works!

===Fanning===
The first mechanism is fanning. Just as you can open an ornate oriental fan, and created a colorful beautiful picture, you can create beautiful color palettes or beam spreads.

From technical point of view fanning means to split a value to a group of devices. We distinguish between linear and alternate fanning. See the following tables explaining the syntax element.

====linear fanning====
{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || Linear interpolation
|-
| <> || 50 <> 100 || Linear interpolation: marginal devices: 100, central devices 50 (mnemonic trick: In the symbol both signs are directed outside; in these positions the first value is applied; the second value is applied in the center.)
|-
| >< || 50 >< 100 || Contrary: marginal devices: 50, central devices 100 (mnemonic trick: In the symbol both signs are directed inside; there the first value is applied (in the center); the second value is applied at the edge.)
|}

=== alternate fanning ===
{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| # || 50 # 100 || Alternate values 100/50/100/50 ...
|-
| # # || 100 # 50 # 0 || Alternate values 100/50/0/100/50/0 ...
|}
 
How does it work?

Lets assume we want to have a cue where the 8 RGB Pars have to be faded from red in the middle to blue at the edges.
{{Picture_with_subtitle|DMXC3L09 Fanning pink.JPG|1|Linear color fanning example|center|600px}}

How many actions are needed for programming? 8? 16? 32?
The answer is: '''Three!''' 
We will apply linear fanning by "><" where we separate the marginal devices from central devices. The actions:
* select the group "RGB pars"
* go to property grid panel and type in for red color "0<>255"
* type for blue color "255<>0"

Here is the amazing result in property grid:
{{Picture_with_subtitle|DMXC3L09 Fanning pink programmer.JPG|2|Settings for linear fanning|center}}

Let's make another exercise with alternate fanning. The task is switching on each second lamp (i.e. setting dimmer to 100%).
{{Picture_with_subtitle|DMXC3L09 Fanning alternate.JPG|3|Alternate color fanning example|center|600px}}

There is a simple solution: Insert "0#100" into the dimmer value text field.
{{Picture_with_subtitle|DMXC3L09 Fanning alternate programmer.JPG|4|Settings for alternate fanning|center}}

=== Effects and filters ===
With fanning you can create static cues. The "effects and filters" panels provides some additional effects that can be used for dynamic changes within a cue (e.g. swinging, flashing, running lights, etc.). Of course that's done fast and easy with DMXControl 3, or did you expect something else? ;)

Let's have an example: You want to have a blinking effect with all front light lamps.

In "'''Effects and filters'''" panel (accessed via '''Windows-> Effects and Filters''') some super effects are offered, which you can use to create a dynamic change within the cues such as "sine", "trapezoid", "Sawtooth". Using drag&drop you can easily attach the sine effect to the dimmer in the '''Property Grid'''.
Now this attribute behaves as it is expected by the symbol or name of the effect. You can change specific effect parameters in the '''Property Grid''' for example to affect the amplitude or frequency of the effect. For examples and details see the table below.
{{Picture_with_subtitle|DMXC3L09 Fanning with Sinus effect.JPG|5|Setting for flash effects|center|600px}}

Try it! You'll love it! 

Tip: Use the chaser effect to implement running lights within our RGB pars:
*Select the RGB group
*Drag the chaser effect to the dimmer in '''Property Grid'''

{{Manual Box | en | Hint | Effects (attachables) will be summed to the values that are manually adjusted. (If the device has a dimmer set at 30%, and you add a sinus with amplitude of 20%, the brightness minimum value will be 30%, the maximum value 50%)}}
 
Hint: Press the '''Del''' key (or delete symbol) in '''Property Grid''' to remove the effect from the attribute.

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribute
! Example
! Description
|-
| Amplitude
| 50 > 100
| Value interval for selected attribute; Can be set to negative value also.
|-
| Phase
| [0..100]
| Offset between group elements.
|-
| Frequency
| [0..1]
| Cycle speed.
|}
 
{{Manual Box | en | Hint | By fanning the offset, you get interesting chasers.
}}

In order to illustrate the power of this concept we have listed following use cases for you:

{| class="wikitable FCK__ShowTableBorders"
|-
! Use case
! How-to
! Amplitude
|-
|Jump effect: Dimmer should slowly fade to 0, and then will jump to full value
|Srag "Sawtooth" to dimmer property
| -100
|-
|Running light: One changing element of a group has 100% dimmer
|Drag "Chaser" to dimmer property
| 100
|-
|Gobo change:
|Drag "ListSwitch" to gobo property
|
|-
|Fade-in-effect with waiting time: Dimmer fades to 70, waits, Dimmer fades to 0, waits.
|Drag "Trapezoid" to dimmer property
| 70
|-
|Pattern of 8: Moving lights follow the "8" shape.
|Drag "Lissajous" to position property
| 270
|-
|On/off-effect: Lamps are switched on/off
|Drag "Rectangle" to dimmer property
| 100
|-
|Harmonic fade: Lamps dim in a harmonic way to 100% and back to 0.
|Drag "Sinus" to dimmer property
| 100
|-
|Color change: Lamps change sequentially to all possible colors.
|Drag "Sawtooth" to color property
| 100
|-
|}

==Exercise==
1) Try to apply fanning to pan/tilt of your moving lights. That rocks! ;)
 
2) Implement a running light with chaser effect

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

Lesson 24 Tut3

2025-03-02T19:00:26Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_23_Tut3
| TextBackwards = Lesson 23
| LinkForwards = Appendix_1_Tut3
| TextForwards = Appendix 1
}}
==Overview==
In this lesson we look at how we can combine the advantages of DMXControl release 3, with those of release 2, by connecting the tools via ArtNet.

== Lesson24: Transferring DMX values over Artnet to DMXControl 2 ==
{{Manual Box | en | Hint | This lesson works in if you are using Win 7. Win 8 has more problems, but it is possible to make it work.
}}

Since DMXControl 3 still is in an early stage, some functions of the series 2 do not yet exist. This will be improved in the future, but it will take some time before all the functions of the series 2 are present. Nevertheless, we do not want to miss the advantages when using release 3. This section shows how a connection can be made from DMXControl 3 to DMXControl 2 via ArtNet.

We start with the configuration of DMXControl 2 for receiving ArtNet data. For this, we choose in the taskbar of DMXControl 2 '''Configuration -> Output Plugins ...'''. We go to the output plugin dialog in which we configure the "ArtNet Plugin" by clicking "Configure Selected Plugin":

{{Picture_with_subtitle |2.12_Ausgabeplugin_Konfiguration.PNG|1|ArtNet-plugin configuration in DMXControl 2|center|400px}}

Important here are the settings '''SubNet''' and for '''input node''' the '''Universe'''. We will configure DMXControl 3 in this way, so that it transmits our desired values in the subnet 0 in the universe 0.

The setting'' 'Universe''' in '''output node''' does not matter, and can (if required) be freely selected. But it must differ from the'' 'Universe''' of the input node, otherwise we get (in this configuration), a feedback loop, and DMXControl is no longer operable. In our configuration, the universe 8 is the next free universe.

Close the window by clicking OK and activate the output plugin by checking the box in front of the name of the interface:
{{Picture_with_subtitle |2.12_Ausgabeplugin.PNG|2|Output plugins window in DMXControl 2|center|400px}}

DMXControl 2 is now ready to receive ArtNet data. In the next step we need to configure DMXControl 3 to send its DMX output via Artnet. At '''Settings--> DMX Interfaces''' we find the output plugins of DMXControl 3:

{{Picture_with_subtitle |3.0_Ausgabeplugin.PNG‎|3|Interface Panel DMXControl 3|center|600px}}

With '''Add Interface ...'''we now select the ArtNet plugin:
{{Picture_with_subtitle |Art-Net_auswählen.PNG‎|4|Adding the ArtNet Interface DMXControl 3|center|350px}}

In simple configurations the ArtNet transmitter is now running. But to be sure, configure the ArtNet plugin still on the correct network interface. By clicking on '''Advanced Interface Settings ...''' we come to the configuration dialog. We are interested in the '''binding to''' entry.

Here we need to select the IP address of our computer, which is typically located in the same network as the computer with our DMXControl 2 installation:

{{Picture_with_subtitle |Adresse_auswählen.png‎|5|Configuration of ArtNet Interface DMXControl 3|center|400px}}

If you start in DMXControl 2 and go to the DMX remote control (Window -> DMXin remote control) then change a value in '''Channel Overview''' of DMXControl 3, it should be displayed on the DMXin remote control:

{{Picture_with_subtitle |ErsterArtNetTest.PNG‎|6|Test the connection DMXControl3 -> DMXControl 2|center|450px}}

This window must remain open to continue operating!
Now we just need to patch the DMXin remote control of DMXControl 2 properly. If you go to '''Configuration -> DMXin Remote control ...''' we get the configuration screen:
{{Picture_with_subtitle |2_12DMXIn-Konfig.png‎|7|Open the DMX-In remote control DMXControl 2|center|300px}}

Here you can now control commands in DMXControl 2. First of all, we would like to patch all channels from ArtNet input in DMXControl 2 to DMX output. For this, we click at the right, in the still empty soft patch list '''1:1''':
{{Picture_with_subtitle |Softpatch212.PNG‎|8|Softpatch configuration DMXControl 2|center|600px}}

In the following dialogues, we select the desired range of values. I decided to patch the entire DMX universe:
{{Picture_with_subtitle |1zu1Patch212.PNG‎|9|Softpatch von Start-DMX-Adresse bis End-DMX-Adresse DMXControl 2|center|600px}}

{{Picture_with_subtitle |Softpatch212fertig.PNG‎|10|Softpatch in DMXControl 2|center|600px}}

By clicking on'' 'OK''' now we have to activate the DMXin remote control:
{{Picture_with_subtitle |DMXIn_Aktivieren212.png‎|11|Activating the DMXIn remote control DMXControl 2|center|600px}}

Now all values of DMXin are directly sent to the DMXOut interface.

You can test the connection by sending color gradient from DMXControl 3 to DMXControl 2. With this workaround, we extend the functionality of DMXControl 2 with features from DMXControl 3.

===Error handling===
If no DMXin values from the remote control are shown, there is still a fault with the network configuration. Please check the following points:
* Are the computers in the same network? Can the computers ping each other?
* Switch off firewalls (for test only), because the often block UDP data (ArtNet is based on UDP)
* Are both DMXControl plug-ins configured on the same subnet?
* Is DMXControl 2 configured for the same universe as a receiver, on which DMXControl 3 sends data?
* No other sender configured in this universe?

==Exercise==
1) Configure the connection between DMXControl 3 and DMXControl 2
 
2) Test the color gradient example mentioned above

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

Lesson 23 Tut3

2025-03-02T18:59:56Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_22_Tut3
| TextBackwards = Lesson 22
| LinkForwards = Lesson_24_Tut3
| TextForwards = Lesson 24
}}
==Overview==
In this lesson we will look at the function to create an RGB matrix. Therefore DMXControl 3 offers already effects for matrix control.

== Lesson 23: RGB Matrix ==
DMXControl 3 has the popular "MadMaxOne Plugin" already integrated.

To set up a matrix we must first set the necessary DDF's in '''Device Manager'''. For this purpose, you add, (as you have already learned in Lesson 3;-), the matrix DDF to the project.
You will find this DDF in the folder '''Generic'''. The matrix uses compared to other DDF's no DMX addresses. In a further step we will later assign the individual matrix-points an address. 

At this point we need to think about what is the size of our matrix. Let's start with a 4x4 matrix, so we have a total of 16 RGB pixels.
For these pixels, we must now add more devices that we then assign to our matrix. Currently only RGB devices are supported as pixels. So now please add another 16 '''Generic RGB PAR''' to our project. Now your '''Project Explorer''' should look as follows (see Figure 1).

{{Picture_with_subtitle |DMXC3L23_Project_Explorer.png|1|Project Explorer Configuration 4x4 Matrix|center|550px}}

In the next step we need to configure our matrix DDF. By right-clicking on the matrix entry in the device list you open the '''Properties''' of matrix DDF's. Here, the following window opens (see Figure 2). 
{{Picture_with_subtitle |DMXC3L23_Matrix_Properties.png|2|Properties of Matrix-DDF's|center|330px}}

The '' 'GUI Properties''' and '''kernel Properties''' are not relevant. What interests us is the '''Device Properties''' in the bottom (see Figure 3). 

{{Picture_with_subtitle |DMXC3L23_Matrix_Device_Properties.png|3|Device Properties of Matrix-DDF's|center|330px}}

In '''Rows''' and '''Columns''' you can change the row and column number of the matrix. Since we want to create a 4x4 Matrtix, we have to change nothing.

The point '''patching''' is interesting for us. When you click on this item, a button appears on the right with 3 points. By clicking on this button, you open the window '''matrix patch'''. Here we can make the assignment of our '''Generic RGB PAR's''' (see Figure 4).

{{Picture_with_subtitle |DMXC3L23_MatrixPatch.png|4|Matrix Patch Window|center|360px}}

Right-clicking on the upper left gray pixels (button) opens the context menu. In this you have to select the menu item '''Configure Devices'''. This opens the selection dialog '''Device Selection''' (see Figure 5).

{{Picture_with_subtitle |DMXC3L23_DeviceSelection.png|5|Device Selection Dialog|center|300px}}

Here you can now assign a device to the pixels (button) by highlighting the appropriate device with a hook.

After clicking on '''OK''' the device for the pixel is taken. The window closes and the associated pixel button changes color from gray to blue. If you now clicks in the '''matrix patch''' window on the button '''Clear Patch''' the assignment of all buttons is released. 

Since this assignment in large matrices is somewhat cumbersome, there is also the possibility to automate it. So once annul assignment with '''Clear Patch'''. 

Again, right click on the upper left pixel gray button. Now you mark all the devices by clicking on the first device and clicking with the Shift key on the last device. For subsequent selecting individual devices, you can also hold down the Ctrl key and select the appropriate device. Now all devices should be selected. Now, when you set the hook on a device, all devices are highlighted. 

Now select in the lower drop down '''Add to Row'''. Thus, the devices from left to right line by line are assigned to the pixels.

In '''Add in Columns''' the devices are assigned from the top to down by column.

 
After clicking on '''OK''' all devices are assigned, causing the pixels button in '''matrix patch''' now should all have blue color. 

After clicking on '''OK''' in '''matrix patch''' window and click on '''OK''' in the "Properties" window of Matrix DDF's our configuration is complete. Now we can see everything in '''Stage View'''. 

We sort the devices as in Figure 6:

{{Picture_with_subtitle |DMXC3L23_Stage_View.png|6|Stage View view of assorted devices|center|600px}}

Here you can try one more time, the sorting function for matrix (press Shift-M)from [[Lesson 4]]. 

Next, highlight all Generic RGB PAR's and set in '''PropertyGrid''' the dimmer to 100% 

Now we will first of all look at the static color assignment. Therefore, you open the '''Matrix Control''' window if it already exists on the register tab, otherwise the menu '''controls -> matrix'''. The window should look something like this after opening (see Figure 7):

{{Picture_with_subtitle |DMXC3L23_Matrix_Control.png|7|The Matrix Control Window|center|340px}}

In order to alter something, you first must have to select the DDF matrix in the '''Stage View'''. Then the matrix window is as follows (see Figure 8).

{{Picture_with_subtitle |DMXC3L23_Matrix_Control2.png|8|View of the matrix in the matrix Control Window |center|340px}}

You can now select different colors by the two color buttons to create color gradients. With the middle drop down you can determine the nature of the course. So check it out and test how they're looking at the '''Stage View'''. There, you'll see the changes in the RGB PAR's. 

That about the assignment of the static color matrix. You could now save individual gradients as cues and bring movement into the matrix. But there is also a more efficient solution: 

For this we turn to the '''Stage View'''. At the bottom of the window you should find '''Effects and Filters''' (see Figure 9), if you have not closed it. 
{{Picture_with_subtitle |DMXC3L23_Matrix_Effect-Fenster.png|9|The effects window|center|280px}}

If you select the tab'' 'Matrix Effect''', you can see there are four existing matrix effects. Mark in the '''Stage View''' the matrix DDF and pull one of the effects by dragging and dropping at the word "matrix" in '''PropertyGrid'''. The effect will be started immediately. 

In the tree structure of the '''Porperty Grid''' you can change the selected effect with respect to color, speed change, etc..

For the matrix effect '''Color Scroll''' you can select the colors from a list. In order to create a color list, you have to return to the '''Project Explorer'''. There you will find in the directory tree the item '''Item selection''', by clicking the right mouse button the context menu opens. Here you use the first entry '''Add Item List''', then a window opens in which you can choose between a '''Color List''' or '''Gobolist'''. Since we need a '''Color List''', you simply click on '''OK'''.

In the window you can now see the container '''New Color List (1)''', which you can give a more meaningful name. By double clicking on the container, a window opens to add the colors. Here you can select and add a color with '''Add''' from the color dialog. With the '''Arrow''' buttons you can change the order of your colors as usual. When you have added all colors to the window '''Color List''', click on '''OK'''to finish.

{{Manual Box | en | Attention | In order to make the Color dropdown list in the '''PropertyGrid''' visible, the matrix DDF in '''Stage View''' must be deselected and selected again.
}}

==Exercise==
1) Try the different options described above and have fun with it.

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

Lesson 20 Tut3

2025-03-02T18:59:15Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_19_Tut3
| TextBackwards = Lesson 19
| LinkForwards = Lesson_21_Tut3
| TextForwards = Lesson 21
}}
==Overview==
In this lesson we will learn how to create and add new device definitions. You need to do this activity only, if your device is not yet defined in the default set of DMXControl 3 device definitions.

==Lecture 20: Create new device definitions ==
A device definition file (short: DDF) is used to inform DMXControl about the properties of a device. A DDF is written in XML language and stored in the path

<DMXControl program path>\kernel\devices
 
If you are familiar with DDFs of DMXControl 2.0 you will see some important differences:

* There is no GUI description part, because DMXControl 3 doesn't provide the device context menus.
* Some syntax elements are very similar (esp. in information part). I.e. you can reuse the existing DDFs
* The function part is much more abstract. You make the definition mainly by properties and not by DMX channels

Currently there is no "DDF creator" available for DMXControl 3. We recommend using a text editor or XML editor tool. (Hint: We need support for adaption of an existing DMXControl 2 php tool towards DMXControl 3)
 
At first lets look at a very simple DDF ("Generic RGB Par"):

----

{| cellspacing="1" cellpadding="1" border="0" align="left" width="200"
|-
| <source lang="xml">01 <?xml version="1.0" encoding="utf-8" ?>
02 <device image="bild" type="DMXDevice">
03 <information>
04 <modell>Generic RGB PAR</modell>
05 <vendor>Generic</vendor>
06 <author>Arne Luedtke</author>
<comment>KLEINER TEXT</comment>
07 </information>
08 <functions>
09 <rgb>
10 <red dmxchannel="0" />
11 <green dmxchannel="1" />
12 <blue dmxchannel="2" />
13 </rgb>
14 </functions>
15 </device></source>
|
 [[Image:DeviceManegerInfoBox.jpg|DeviceManegerInfoBox.jpg]]
|}

----

Line 01 is a mandatory default line for describing the XML version.
Lines 02 and 15 provide the frame for the device definition that contains two parts:
* Information part (lines 03 to 07). No need for further explanation.
* Function(property) specification part (lines 08 to 14)

The "image" can be replaced by another .gif or .png file.

The example device possesses one property: RGB color mode. The mapping to DMX channels is described in lines 10 to 12.

That's all!

Following table shows the supported properties:

{| class="wikitable"
|-
! scope="col" | Property
! colspan="2" scope="col" | Description
! colspan="3" scope="col" | Comment
|-
| switch
| colspan="2" | fixture has a switch channel 
| colspan="3" | <source lang="xml"><switch dmxchannel="0" /></source>
|-
| dimmer
| colspan="2" | fixture has a dimmer channel 
| colspan="3" | <source lang="xml"><dimmer dmxchannel="0" /> </source>
|-
| matrix
| colspan="2" | Fixture ist ein Matrix-Gerät 
| colspan="3" | <source lang="xml"><matrix rows="2" columns="3">
<rgb>
<red dmxchannel="2" />
<green dmxchannel="2" />
<blue dmxchannel="2" />
</rgb>
<rgb>
<red dmxchannel="2" />
<green dmxchannel="2" />
<blue dmxchannel="2" />
</rgb>
<rgb>
<red dmxchannel="2" />
<green dmxchannel="2" />
<blue dmxchannel="2" />
</rgb>
<rgb>
<red dmxchannel="2" />
<green dmxchannel="2" />
<blue dmxchannel="2" />
</rgb>
<rgb>
<red dmxchannel="2" />
<green dmxchannel="2" />
<blue dmxchannel="2" />
</rgb>
<rgb>
<red dmxchannel="2" />
<green dmxchannel="2" />
<blue dmxchannel="2" />
</rgb>
</matrix>
</source>
|-
| fog
| colspan="2" | fod property 
| colspan="3" | <source lang="xml"><fog dmxchannel="0" /></source>
|-
| shutter
| colspan="2" | fixture has a shutter 
| colspan="3" | <source lang="xml"><shutter dmxchannel="0" /></source>
|-
| strobe
| colspan="2" | fixture has a strobe channel 
| colspan="3" | <source lang="xml"><strobe dmxchannel="0" /></source>
|-
| iris 
| colspan="2" | fixture has a iris channel 
| colspan="3" | <source lang="xml"><iris dmxchannel="0"/></source>
|-
| focus 
| colspan="2" | fixture has a focus channel 
| colspan="3" | <source lang="xml"><focus dmxchannel="0"/></source>
|-
| zoom 
| colspan="2" | fixture has a zoom channel 
| colspan="3" | <source lang="xml"><zoom dmxchannel="0"/></source>
|-
| rgb
| colspan="2" | fixture has RGB function
| colspan="3" | <source lang="xml"><rgb>
<red dmxchannel="0" />
<green dmxchannel="1" />
<blue dmxchannel="2" />
</rgb>
</source>
|-
| cmy 
| colspan="2" | fixture has CMY function 
| colspan="3" | <source lang="xml"><cmy>
<cyan dmxchannel="0"/>
<magenta dmxchannel="1"/>
<yellow dmxchannel="2"/>
</cmy>
</source>
|-
| position
| colspan="2" | fixture has Pan and/ or Tilt
| nowrap="nowrap" colspan="3" | <source lang="xml"><position>
<pan dmxchannel="0">
<range range="540" />
</pan>
<tilt dmxchannel="1">
<range range="246" />
</tilt>
</position>
</source>
|-
| color wheel
| colspan="2" | fixtures contains color wheel
| colspan="3" | <source lang="xml"><colorwheel dmxchannel="0">
<step type="color" val="#ffffff" caption="white" mindmx="0" maxdmx="0" />
<step type="color" val="#00bd52" caption="green 203" mindmx="32" maxdmx="32" />
<step type="color" val="#080094" caption="blue 108" mindmx="64" maxdmx="64" />
<step type="color" val="#8e10bc" caption="UV" mindmx="96" maxdmx="96" />
<step type="color" val="#eedefe" caption="1/2 Minus Green" mindmx="128" maxdmx="128" />
<step type="color" val="#ffffff" caption="white" mindmx="160" maxdmx="160" />
</colorwheel>
</source>
|-
| rowspan="4" | gobo wheel
| rowspan="3" | fixture with Gobo wheel
| valign="top" nowrap="nowrap" |
 
Gobo rotation

| valign="top" nowrap="nowrap" rowspan="3" | <source lang="xml"><gobowheel dmxchannel="0">
<goborotation dmxchannel="12" finedmxchannel="13">
<step type="stop" mindmx="0" maxdmx="2" />
<step type="stop" mindmx="253" maxdmx="255" />
<range type="cw" mindmx="3" maxdmx="127" minval="0,1" maxval="8" />
<range type="ccw" mindmx="252" maxdmx="128" minval="0,1" maxval="8" />
</goborotation>
<goboindex dmxchannel="8" finedmxchannel="9">
<range mindmx="0" maxdmx="255" range="395" />
</goboindex>
<step type="open" caption="Open" mindmx="0" maxdmx="11" />
<step type="gobo" caption="Gobo 1" mindmx="12" maxdmx="15" val="gobo1.png">
<step for="goborotation" mindmx="36" maxdmx="39" />
<step handler="shake" mindmx="60" maxdmx="71" minval="0,1" maxval="3" />
</step>
...
</gobowheel></source>
|-
| valign="top" |
Goboposition

|-
|
Rotation Gobo 1

Shake Gobo 1 
|}

If the fixture has a color / gobo wheel that can rotate continuously, then write it as follows:
 
<source lang="xml"><gobowheel dmxchannel="0">
<step type="open" caption="Open" mindmx="0" maxdmx="0" />
<step type="gobo" caption="Gobo 1" mindmx="11" maxdmx="11" />
...
<wheelrotation>
<range type="cw" mindmx="221" maxdmx="203" minval="0,1" maxval="2" />
<range type="ccw" mindmx="222" maxdmx="240" minval="0,1" maxval="2" />
</wheelrotation>
</gobowheel>
</source>
 
If the fixture has a color / gobo wheel, which can rotate at random positions, then write it as follows:
 
<source lang="xml"><gobowheel dmxchannel="0">
<step type="open" caption="Open" mindmx="0" maxdmx="0" />
...
<random>
<step type="fast" mindmx="241" maxdmx="245" />
<step type="medium" mindmx="246" maxdmx="250" />
<step type="slow" mindmx="251" maxdmx="255" />
</random>
</gobowheel>
</source>
 
If a device has fine channels for eg zoom, then write it as follows:
 
<source lang="xml"><zoom dmxchannel="0" finedmxchannel="1"/>
</source>

That works for any property.
 
The different intervals in a DMX channel are defined by the "step" tag:
<source lang="xml">
<step val="0" mindmx="0" maxdmx="127" />;
<step val="100" mindmx="128" maxdmx="255" />;
</source>

or:

<source lang="xml">
<step type="color" val="#FFFFFF" caption="Weiß" mindmx="0" maxdmx="31" />;
<step type="color" val="#FF0000" caption="Rot" mindmx="32" maxdmx="63" />;
</source>

{{Manual Box | en | Hint | A DDF Creator for DMXControl 3 is already in the works. Until then, please create your own DDFs with an XML editor of your choice, or simply a text editor. Sometimes it helps to copy an existing DDF and to adapt it. Please send us your new DDFs, so we can add them to the library.
}}

==Exercise==
1) Have a look into several device definitions before creating your own DDF.
 
2) Open the DDF for TS255. Separate the different properties by blank lines to get a better understanding.
 
3) Create the DDF for your own device.

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

Lesson 19 Tut3

2025-03-02T18:58:57Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_18_Tut3
| TextBackwards = Lesson 18
| LinkForwards = Lesson_20_Tut3
| TextForwards = Lesson 20
}}
==Overview==
In this lesson some additional clients are in focus. The client/server concept of DMXControl allows the connection to other clients (Smartphones, Tabs, etc.) in simple way.

==Lecture 19: Further DMXControl clients ==
{{Manual Box | en | Hint | Currently the OSC plugin is not offered. We expect it in next release.
}}

in development:

* [http://www.dmxcontrol.de/wiki/Projekte/DMXControl-for-Android-Projekt DMXControl-for-Android-Projekt]

The smartphone apps (clients) communicate via OSC with DMXControl 3.
Therefore you have to enable the OSC plugin via "plugin manager", see following figure:
{{Picture_with_subtitle|DMXC3L19_OSC1.JPG|1|Activating OSC-Plugin|center}}

Now, you should define the IP connection in the panel "connection form". Press the "+" button to create a new connection.
In the first approach we use unicast with UDP. Please let the IP address on 0.0.0.0, but set the correct port where your client sends the OSC messages. Now you can start (activate) this connection by a click to start button:
{{Picture_with_subtitle|DMXC3L19_OSC2.JPG|2|OSC-Plugin setup|center}}

==Additional links and references==
* [http://www.hexler.net TouchOSC]

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

Lesson 17 Tut3

2025-03-02T18:58:27Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_16_Tut3
| TextBackwards = Lesson 16
| LinkForwards = Lesson_18_Tut3
| TextForwards = Lesson 18
}}
==Overview==
Here the audio analyzer is presented as a plugin in DMXControl 3.

==Lecture 17: Audio Analyzer ==
The audio analyzer is implemented in DMXControl 3 as plugin and and you will have to enable it via '''Plugin Manager'''. It then appears as a menu item under '''Windows -> Audio Analyzer'''. The audio analyzer provides essentially the same features as the Soundanalyser of DMXControl 2.

{{Manual Box | en | Hint | This plugin is still in an experimental stage.
}}

{{Picture_with_subtitle |DMXC3L17 PluginAudioAnalyser.jpg|1|Audio Analyzer Window|center|450px}}

The main purpose of audio player is the automatic generation of beats from a song in order to trigger the beats in a beat-driven cue list.(see [[Lesson_11_Tut3|Lesson 11: Trigger]]).

The plugin contains several tabs:

* '''Devices''' is responsible for the configuration. Here you choose the particular audio input
* With'''VU meter''', '''Spectrum''' and '''Beat Detection''' you can select the different analysis method
* '''Mood''' should analyze automatically and in real time the mood of an audio signal and the "Automatic Sound Controlled Light Show" lead (Vision!)
* Using '''Beat generator'''You can manually create the Beats (Tap-key) or you can specify a certain Beats-Per-Minute (BPM) value

And now the question remains, how will the results of the analysis be assigned to drive the cuelist? You already have an idea? ... Of course, this is the same as the'' 'input Assignment''' concept introduced in [[Lesson_22_Tut3|Lesson 22]].

{{Picture_with_subtitle |DMXC3L17 PluginAudioAnalyserInputAssignment.JPG|2|Assigning sound events using the input Assignment Window|center|600px}}

==Exercise==
1) Activate the AudioAnalyzer. If your sound card does not feature internal redirection, and you currently have no external player available, use the microphone input as a substitute.

==Additional links and references==
*[http://www.dmxcontrol.de/wiki/Sound_Analyzer_DMXC2 Soundanalyzer DMXControl 2] (only german)

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

Lesson 16 Tut3

2025-03-02T18:58:09Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_15_Tut3
| TextBackwards = Lesson 15
| LinkForwards = Lesson_17_Tut3
| TextForwards = Lesson 17
}}
==Overview==
In this lesson you will learn something about the '''SoftDesk''' plugin. This tool allows you to create lighting consoles that will simulate any physical lighting console, or a custom console using your own design ideas

==Lecture 16: SoftDesk==
DMXControl 3 offers the SoftDesk, which replaces the popular command box from DMXControl 2. The advantages of soft desks are as follows:
* Flexible layout options
* Wider variety of controls
* Potentially there will be SoftDesk variants on external clients (tablets, etc.).

In principle, you can reconstruct any physical console with the SoftDesk editor.

The SoftDesk tool can be enabled via the '''plugin manager''', see Lesson6/en. Afterwards you can find a new menu entry "Softdesk" within the plugins menu. When you open this plugin, a set-up GUI appears at first:

Here you can create, delete, edit, copy, import and export your instances of SoftDesks. Simply select the check box. Then you will find a new entry "SoftDesk" under the menu item "Windows" (restarting the GUI-clients may be required).

{{Picture_with_subtitle |DMXC3L16 SoftDesk plugin.JPG|1|SoftDesk Plug-in Activation|center}}

After opening the plug-in via the menu, a GUI appears for the first set-up of the various consoles. This panel is initially empty, but on the right side are 6 buttons.

Here you can create and edit individual desk surfaces, copy, import or export. By double-clicking in the blue line, you can change the name of the console to be created (if design mode is set). The new consoles will appear in the Project Explorer too.

{{Manual Box | en | Hint | DMXControl 3 stores all SoftDesks automatically within the project (Save Project). The export / import function is used to transfer the created panel to external clients (e.g. Android).
}}

You can create multiple console surfaces, which can then be activated simultaneously at run time (but multiple banks are not available within SoftDesk).

When you select the design mode (edit mode) you can add your favorite elements from the set of sliders, buttons, rotary faders or XYpads. There are also graphical design elements such as labels, separators and group boxes available. Note the design grid mode!

Here you can see one possible result:

{{Picture_with_subtitle |DMXC3L16 SoftDesk.JPG|2|SoftDesk Plug-in|center}}

You can customize the elements in design mode by using the property context menu. Simply double click the control or call it by right click in the '''DesignMode'''. The following figure shows the property box for a button (right mouse click in design mode). For example you can modify the button name, colors and the toggle mode property -
here the name was changed to "Flash button".

{{Picture_with_subtitle |DMXC3L16 CommandboxProperties.JPG|3|Settings|center}}

{{Manual Box | en | Hint | You can change the size of individual elements by dragging the corners with the mouse.
}}

In the next step you have to connect your SoftDesk with your project. I.e. you have to assign functions to your SoftDesk control elements.

This has to be performed with the input assignment panel (menu '''Application Settings''' (-->[[Lesson 22 Tut3|Lesson22]])). On left side you find the controls, and on the right side the DMXControl explorer is shown. Simply drag and drop the control elements to certain properties, attributes or elements to make a connection.

{{Picture_with_subtitle |DMXC3L16 SoftDeskInputAssignment.JPG|4|Input Assignment|center}}

{{Manual Box | en | Hint | Do not forget to switch off the design mode at run time.}}

The SoftDesk windows are integrated into the panel system (-->[[Lesson 2 Tut3|Lesson2]]). That means you can have attached panels or flying windows containing the SoftDesk .
The individual soft desks are then opened with a double click (with Design Mode off).

Have fun trying out your own SoftDesk! We wish you a high level of artistic creativity for your own desks!

==Exercise==
1) Create two SoftDesks, one consisting of buttons only, the other one should contain all types of control elements
 
2) Control colors with your button SoftDesk
 
3) Connect the XYpad with your moving light and test the function

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

Lesson 14 Tut3

2025-03-02T18:57:30Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_13_Tut3
| TextBackwards = Lesson 13
| LinkForwards = Lesson_15_Tut3
| TextForwards = Lesson 15
}}
==Overview==
This chapter provides a summary of the programming capabilities in DMXControl 3.

==Lecture 14:Speed and productivity improvement of show programming ==
DMXControl 3 offers you the following items for advanced use of DMXControl 3.

* Cue list
* The programmer
* Several fading approaches
* The Hardware abstraction
* DMXControl kernel ("Light engine with Fanning algorithms)
* Effect library

Within the programmer, the individual cues can be checked again and tested before they are permanently stored in a cue-list, by means of the programmer filter.

{{Manual Box | en | Hint | DMXControl 3 has not yet provided the popular tools such as audio players, or text book with its graphical programming interfaces. But, the control options of a cue list have grown enormously. You now have different fading and trigger options. Thus, it should, in principle, be possible to effectively create earlier scene lists again. 
The library scene is not found in this form in the current version. But you can use presets for the same purpose. Presets also have a number of additional capabilities.
}}

Note that the fanning and effects possibilities work, not only for the examples shown using dimmer value and color, but for almost all device attributes such as pan / tilt, fade-in, delay, etc. This can be extremely effective, and spectacular effects can be achieved.

A further increase in productivity is obtained by being able to manipulate the cue lists by using the EXCEL spreadsheet program.
Since cues and presets work regardless of device type, you can quickly customize existing shows to new equipment setups.
Thus, it should be possible, with a little practice, to program big shows in minutes!

We still remember a DMXControl meeting in 2008, when we programmed for an entire day, to create a show lasting 5 minutes. At night we proudly presented this show to a professional, and we asked him how long it would take for him to do it.

The answer shocked us at the time: '''15 minutes!''' For us that was almost unimaginable, and sounded like a barely workable vision for a freeware DMXControl. But, we have done everything in recent years to get to that level of professionalism. We think that we've successfully created DMXControl 3 close to this vision!

==Exercise==
1) Assign a new cue directly to an executor
 
2) Assign the existing Cue list to another executor

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

Lesson 12 Tut3

2025-03-02T18:57:09Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}
==Overview==
In this lesson we explain advanced edit features for scenes and scene lists, e.g. for modification of already saved scenes.
So you can copy and customize cues very effectively and almost EXCEL like.

==Lecture 12: Editing scenes and scene lists ==
In Lesson 8 we introduced the scene lists. In this lecture more advanced features are explained.
{{Picture_with_subtitle |DMXC3L12_SL.JPG|1|Menu of the Programmer|center}}

By default, a new scene is added to an existing scene list by pressing the button "Add Cue". When you open the small drop-down arrow on right hand side of this button, you see some more sophisticated capabilities with their keyboard shortcut. In most cases you will first select (i.e. highlight) a scene before modifying it.
{{Picture_with_subtitle |DMXC3L12_SL_storemenue.jpg|2|View of the drop-down-menu of "Add Cue"|center}}

{{Manual Box | en | Hint | The following operations are related to the values in the '''Programmer'''.
}}

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Add || Ctrl+A || add a new scene to scene list at the end || default
|-
| Insert || Ctrl+I || insert a new scene to scene-list before selected scene ||
|-
| Replace || Ctrl+R || replace current scene attributes by the values in the '''Programmer''' ||
|-
| Merge|| Ctrl+M || merges selected scene with '''Programmer''' values || '''Programmer''' values with higher priority
|-
| Append || Ctrl+P || append new property from '''Programmer''' to the selected scene || existing scene with higher priority, new values from '''Programmer''' are added
|-
| Subtract || Ctrl+B || removes a property from selected scene || hint: modify the wanted property so that this appears in the '''Programmer'''
|-
| Sum (Special) || || Inserts current output of devices into '''Cue List''' ||
|-
| PSum (Special) || || Similar to '''Sum''', but related to currently selected devices in '''Stage View''' ||
|-
| Preset (Special) || || Opens a window where you have the capability to add a '''Preset''' to '''Cue List''' ||
|-
| Scenelist (Special) || || Inserts (similar to commands in DMXControl 2) a entry to impact another cue list ||
|}
 
In a similar way, there are also edit operations for the scene list itself. As known from EXCEL you can copy, cut and delete whole rows. With copy and paste you can take single values from one field or a cue to another field of other cues.

{{Picture_with_subtitle |DMXC3L12_SL_editmenue.jpg|3|View of drop-down-menu of "Edit"|center}}

Here is the summarizing table for explanation again:

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Edit in Programmer || || Selected cue is loaded into '''Programmer'''. '''Programmer Output Mode''' is set to '''All''' ||
|-
| Edit in Programmer Blind || || Selected cue is loaded into '''Programmer'''. '''Programmer Output Mode''' is set to '''Blind''' ||
|-
| Cut || Ctrl+X || cut the selected scene || like EXCEL "cut row"
|-
| Copy || Ctrl+C || copy the selected scene || like EXCEL "copy row"
|-
| Paste || Ctrl+V || paste the selected scene || like EXCEL "paste row"
|-
| Delete|| Del || delete the selected scene || like EXCEL "delete row"
|-
| Renumber Cues || || || Renumber Cues
|-
| Cue Timing Editor || || || a separate editor is opened
|}

{{Picture_with_subtitle |DMXC3L12_SL_optionmenue.jpg|4|View of drop-down-menu of "Options"|center}}

{| class="wikitable"
|-
! Function !! Description !! Comment
|-
| Tracking || If tracking is active a value remains active until it is overwritten by another cue (or the cue list is finished). If tracking is disabled, only the stored values are active on output that are in the current cue. All others are faded out. ||
|-
| Reset when Released || '''Cue List''' jumps to first entry, after last cue was executed ||
|-
| Use Cue Time as Back Time || After a jump back in the '''Cue List''', the times of the cues are used for the crossfade. ||
|-
| Use Cue Time as GoTo Time || After a jump forward in the '''Cue List''', the times of the cues are used for the crossfade. ||
|-
| Autoprepare || DMXControl prepares headlights already automatically on the mission (color and gobo is selected in advance etc.). That way you will not need to worry about it. On active '''Autoprepare''' you can deactivate this function for single cues with the checkbox '''Ap'''. ||
|-
|}

==Exercise==
1) Test the append and subtract cue functions

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

Lesson 11 Tut3

2025-03-02T18:56:33Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}
==Overview==
Cue lists are the best tool to control the flow of your show. In this lesson we explain how to define the sequence and the change of scenes by triggers.

==Lecture 11: Triggers in cue lists ==
In previous lessons we learned how to create cues and scene lists. Now that you are familiar with most of the attributes of the scene list, more explanation about triggers is necessary. A trigger is an event that causes a previously saved scene to start. A trigger might come from things like a button press by the user,or an internal timer. The default trigger is "follow". This means the next cue will be started after the previous one has finished fading in.

'''Important:''' When you change the trigger type, you need to apply the changes with the enter-key or by clicking in another field.

There are several types of triggers. The following table describes their behaviors.
{{Picture_with_subtitle|DMXC3L11 trigger.jpg|1|Accepted triggers|center}}

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (optional) 3 || Use GO to fade in next cue.
Optional: Fade cue in after 3 GO presses. The default is 1.
|-
| follow || 5s || Wait until the previous cue is faded in, then wait 5 seconds before starting the next cue.
|-
| wait || 5s || Wait time countdown starts when the wait or follow of the previous cue is completed. In other words, the cue will wait 5 seconds after the prior cue has started, rather than waiting for it to finish.
|-
| timecode || 00:26:05 || Waits for the DMXControl to be given an external timecode signal equal to 00:26:05.
|-
| rtc || 13:00:00 || Real time clock. Fade in a cue at the specified time of 1 pm.
|-
| beat || (optional) 3 || This requires more settings. See the paragraph below.
Optional: Fade in cue after 3 beats. The default is 1.
|}

{{Manual Box | en | Hint | Type in combined time information without "blank" characters, e.g. 1m20s
}}

If you type an incorrect format into the '''trigger value''' field, you will get some hints about the expected input syntax. See the example below for the "follow" type.
{{Picture_with_subtitle|DMXC3L11 triggerhelpcontextfollow.JPG|2|View of Trigger Value help context|center}}

Below is the example for the real time clock selection.
{{Picture_with_subtitle|DMXC3L11 triggerhelpcontext.JPG|3|View of Trigger Value help context|center}}

Currently only the time code from Digital Enlightenment Mediacenter [http://www.digital-enlightenment.de/mediacenter.htm] is supported. Support for other time codes will be created in the future.

===Use of beat trigger===
A '''Beat Trigger''' is a trigger based on the main rhythm of the music. It may be manually set, or automatically generated by DMXControl as it analyzes an audio signal and looks for peak transients.

If you want to have your scenes beat controlled, you need to select the source for the trigger '''beat''' .

{{Manual Box | en | Hint | In the '''Trigger''' field you can specify after how many beat signals the next cue is called
}}
{{Picture_with_subtitle |Beattrigger.PNG|4|Example for beattrigger|center}}

Now you have to inform the '''Cue List''' which source of the beat signal should be used (manual beat/audioanalyzer....)
Therefore you have to assign an input in the [[Lesson_22_Tut3|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).
{{Picture_with_subtitle |DMXC3_L11_InputassignmentBeat.png|5|Input Assignment|center}}

==Summary==
The following figure shows the dependencies and capabilities of mixing several trigger types:
{{Picture_with_subtitle|DMXC3L11 SlideDMXC3Trigger.jpg|6|Overview of possible trigger functions|center|600px}}

* Each cue has its own delay-time (before the fade-in start) - delay1 to delay3
* Cue2 has a follow-trigger of 1s. It starts 1 second after the fade-in of the previous cue is completed
* Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the previous scene is finished.
* Cue4 also has a wait-trigger (1s). So it will wait for 1s after the wait (0s) of the previous scene is finished.

==Exercises==
* Test a mix of "follow" and "wait" triggers in one scene list
 
* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes

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

Lesson 10 Tut3

2025-03-02T18:56:11Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_9_Tut3
| TextBackwards = Lesson 9
| LinkForwards = Lesson_11_Tut3
| TextForwards = Lesson 11
}}
==Overview==
Here we explain the "'''Programmer'''" view - a tool that helps in programming and "debugging" your show.

==Lecture 10: The programmer view ==
The '''Programmer''' tool logs all modifications you made and shows the current content of the "cue buffer".

{{Manual Box | en | Hint | Remember the "save scene" dialog in DMXControl 2? There you were asked to define the channels and values before finally saving the cue. The '''Programmer''' is an extended view of this functionality.
}}

Let's illustrate this by an example. Perform the following steps:

* First, open the moving lights shutters and select the color green
* Second, set the gobos of all devices on "Gobo2"
* Third, set the group of front lights to 50% brightness

{{Picture_with_subtitle |DMXC3L10 liveviewProgrammer.JPG|1|Stage View|center}}

The results are now shown in the programmer. Please be aware that the cue is not saved at this point in time, because further modification might follow.

{{Picture_with_subtitle |DMXC3L10 Programmer.JPG|2|All changes of the device settings are shown in the programmer|center|800px}}

If you change your mind on the current cue, you can press the '''Clear Programmer''' button to remove all settings and refresh the programmer.

Now you can see in the '''Programmer''' which values would be stored in the cue. When you save the cue, you are able to select the desired items in the '''Programmer Filter''' that appeared before. In the following example, we do not save the "Generic Dimmer" (by deselecting them) because we probably want to save them in another cue list.

{{Picture_with_subtitle |DMXC3L10 ProgrammerFilter.JPG|3|View of the Programmer Filter|center}}

If your cue is OK, then assign it to a cue list or an executor by pressing the "'''Add new Cue'''" button and then clear the programmer (to provide "space" for the next cue).

In order to program quicker, there is the snapshot function. With the button '''Write Snapshot''' you can save the current selections in the programmer and reload them later by using the drop-down menu ('''Load Snapshots'''). This helps you to program many similar cues with little effort.

In addition to the above, you can also create a filter with '''Set Filter''' or delete filters with '''Clear Filter'''. Filters are mainly used in '''Output Mode'''. With filters you can adjust the values in the programmer that are actually sent out. If '''All''' is active, all the values in the programmer are sent. With '''Filtered''' only the values that have been activated in the filter are sent. And with '''Blind''' no values are sent out.

==Exercise==
1) Repeat the above scenario

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

Lesson 9 Tut3

2025-03-02T18:55:45Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_8_Tut3
| TextBackwards = Lesson 8
| LinkForwards = Lesson_10_Tut3
| TextForwards = Lesson 10
}}
==Overview==
The previous lession introduced simple cues. In this lesson we explain some more sophisticated features of scenes, e.g. the fanning feature. With fanning you can create impressive effects with groups of lamps, e.g. rainbow effects or waves.
DMXControl 3 provides an effect library.

==Lecture 9: Fanning, chasers and other effects==
DMXControl 3 extends the scope of scenes so that dynamic effects can be included, and you can apply certain algorithms for the attributes (e.g. DMX values) of included devices or groups. This allows you to create highly complex cues with a few mouse clicks. Don't believe it? Let's demonstrate how it works!

===Fanning===
The first mechanism is fanning. Just as you can open an ornate oriental fan, and created a colorful beautiful picture, you can create beautiful color palettes or beam spreads.

From technical point of view fanning means to split a value to a group of devices. We distinguish between linear and alternate fanning. See the following tables explaining the syntax element.

====linear fanning====
{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || Linear interpolation
|-
| <> || 50 <> 100 || Linear interpolation: marginal devices: 100, central devices 50 (mnemonic trick: In the symbol both signs are directed outside; in these positions the first value is applied; the second value is applied in the center.)
|-
| >< || 50 >< 100 || Contrary: marginal devices: 50, central devices 100 (mnemonic trick: In the symbol both signs are directed inside; there the first value is applied (in the center); the second value is applied at the edge.)
|}

=== alternate fanning ===
{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| # || 50 # 100 || Alternate values 100/50/100/50 ...
|-
| # # || 100 # 50 # 0 || Alternate values 100/50/0/100/50/0 ...
|}
 
How does it work?

Lets assume we want to have a cue where the 8 RGB Pars have to be faded from red in the middle to blue at the edges.
{{Picture_with_subtitle|DMXC3L09 Fanning pink.JPG|1|Linear color fanning example|center|600px}}

How many actions are needed for programming? 8? 16? 32?
The answer is: '''Three!''' 
We will apply linear fanning by "><" where we separate the marginal devices from central devices. The actions:
* select the group "RGB pars"
* go to property grid panel and type in for red color "0<>255"
* type for blue color "255<>0"

Here is the amazing result in property grid:
{{Picture_with_subtitle|DMXC3L09 Fanning pink programmer.JPG|2|Settings for linear fanning|center}}

Let's make another exercise with alternate fanning. The task is switching on each second lamp (i.e. setting dimmer to 100%).
{{Picture_with_subtitle|DMXC3L09 Fanning alternate.JPG|3|Alternate color fanning example|center|600px}}

There is a simple solution: Insert "0#100" into the dimmer value text field.
{{Picture_with_subtitle|DMXC3L09 Fanning alternate programmer.JPG|4|Settings for alternate fanning|center}}

=== Effects and filters ===
With fanning you can create static cues. The "effects and filters" panels provides some additional effects that can be used for dynamic changes within a cue (e.g. swinging, flashing, running lights, etc.). Of course that's done fast and easy with DMXControl 3, or did you expect something else? ;)

Let's have an example: You want to have a blinking effect with all front light lamps.

In "'''Effects and filters'''" panel (accessed via '''Windows-> Effects and Filters''') some super effects are offered, which you can use to create a dynamic change within the cues such as "sine", "trapezoid", "Sawtooth". Using drag&drop you can easily attach the sine effect to the dimmer in the '''Property Grid'''.
Now this attribute behaves as it is expected by the symbol or name of the effect. You can change specific effect parameters in the '''Property Grid''' for example to affect the amplitude or frequency of the effect. For examples and details see the table below.
{{Picture_with_subtitle|DMXC3L09 Fanning with Sinus effect.JPG|5|Setting for flash effects|center|600px}}

Try it! You'll love it! 

Tip: Use the chaser effect to implement running lights within our RGB pars:
*Select the RGB group
*Drag the chaser effect to the dimmer in '''Property Grid'''

{{Manual Box | en | Hint | Effects (attachables) will be summed to the values that are manually adjusted. (If the device has a dimmer set at 30%, and you add a sinus with amplitude of 20%, the brightness minimum value will be 30%, the maximum value 50%)}}
 
Hint: Press the '''Del''' key (or delete symbol) in '''Property Grid''' to remove the effect from the attribute.

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribute
! Example
! Description
|-
| Amplitude
| 50 > 100
| Value interval for selected attribute; Can be set to negative value also.
|-
| Phase
| [0..100]
| Offset between group elements.
|-
| Frequency
| [0..1]
| Cycle speed.
|}
 
{{BoxHint
|Text= By fanning the offset, you get interesting chasers.
}}

In order to illustrate the power of this concept we have listed following use cases for you:

{| class="wikitable FCK__ShowTableBorders"
|-
! Use case
! How-to
! Amplitude
|-
|Jump effect: Dimmer should slowly fade to 0, and then will jump to full value
|Srag "Sawtooth" to dimmer property
| -100
|-
|Running light: One changing element of a group has 100% dimmer
|Drag "Chaser" to dimmer property
| 100
|-
|Gobo change:
|Drag "ListSwitch" to gobo property
|
|-
|Fade-in-effect with waiting time: Dimmer fades to 70, waits, Dimmer fades to 0, waits.
|Drag "Trapezoid" to dimmer property
| 70
|-
|Pattern of 8: Moving lights follow the "8" shape.
|Drag "Lissajous" to position property
| 270
|-
|On/off-effect: Lamps are switched on/off
|Drag "Rectangle" to dimmer property
| 100
|-
|Harmonic fade: Lamps dim in a harmonic way to 100% and back to 0.
|Drag "Sinus" to dimmer property
| 100
|-
|Color change: Lamps change sequentially to all possible colors.
|Drag "Sawtooth" to color property
| 100
|-
|}

==Exercise==
1) Try to apply fanning to pan/tilt of your moving lights. That rocks! ;)
 
2) Implement a running light with chaser effect

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

Lesson 8 Tut3

2025-03-02T18:55:04Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_7_Tut3
| TextBackwards = Lesson 7
| LinkForwards = Lesson_9_Tut3
| TextForwards = Lesson 9
}}
==Overview==
Scenes (cues) are the most important elements of your show. Here we will explain the powerful scene concept of DMXControl 3. The terms "cue" and "scene" are used as synonym words.

{{Manual Box | en | Hint | The button for the "Full On" function is labeled "Lumos". This is a Latin word meaning light. It was used in the Harry Potter series as a spell to make the magic wand light up.}}

==Lecture 8: Scenes (cues) and scene lists ==
Now the real work begins - we will create our first cue in DMXControl 3! We will make all RGB lights shine green.
 
* We go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* You can control the intensity of the light by dragging the slider or by pressing the "Lumos" button to bring the light to full brightness.
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)
{{Picture_with_subtitle|DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}

* On the left click on "Add new cue"
* It opens a new window called "Programmer filter", which we will explain in Chapter 10. For now press OK.
{{Picture_with_subtitle|DMXC3L08 programmerFilter.JPG|2|View of the programmer filter|center}}

* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* Here we rename the cue in the ''Name'' field to "My First Cue".
{{Picture_with_subtitle|DMXC3L08 firstCue02.JPG|3|View of the programmer window|center}}

Each scene (cue) needs a "host container" - that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".

You can open this new cue list with a '''double click''' on the object in the project explorer, or using the context menu item "open" (or double click).
In the tabular list you can adjust the individual parameters of the cue.
{{Picture_with_subtitle|DMXC3L08_createSceneListnew.JPG|4|Scenelist in the Project Explorer|center}}

{{Manual Box | en | Hint | The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is, and which target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.}}

The life-cycle of a cue is as follows:
{{Picture_with_subtitle |DMXC3L08 SlideDMXC3cue.jpg|5|Life-cycle of cues in DMXControl 3|center|700px}}
 
A cue waits at first for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).

Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduced compared to the previous cue.
 
Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.

{{Manual Box | en | Attention | You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
}}
{{Picture_with_subtitle |Clear_programmer.jpg|6|Clearing the programmer|center}}

In following table we explain the meaning of cue attributes (which you can see in the scene list header):

{| class="wikitable"
! Attribute
! Description
! Example
|-
| Progress
| shows the status of the scene during execution of scene list (wait time and progress)
| in percent
|-
| Trigger
| relation to predecessor cue, use "follow" as default
| see Lesson 11
|-
| Trigger Value
|
| see Lesson 11
|-
| Name
| free name of scene
| should explain the content of cue
|-
| Fade
| fade-in value
| in milli seconds [ms]
|-
| Delay
| fanning for fades
| see Lesson 9
|-
| Ac (active)
| is this cue active or should it be ignored?
| default: active
|-
| Ap (autoprepare)
| Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of color wheel for next cue)
| default: active
|-
| Re (ReExecute)
| If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the ''actual'' value to the destination value.
| Example: 
Cue 39 Fade 0s: 1 + 2 at full 
Cue 40 Fade 500s: 1 at 0 
Cue 41 Fade 10s: 2 at 0 
(Cue 41 should be a blackout) 
Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds. 
Now someone on stage forgets his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left). 
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in the residual 60s 
If '''Re''' is active for cue 41 the 1 immediately goes down from the ''actual value at this time'' to 0 in 10s together with device 2.
|-
| Comment
| for free use, insert explaining words
|
|-
|}

In the same way you can create some more cues and store it in the scene list.
{{Picture_with_subtitle |DMXC3L08 SecondScene.JPG|7|Cuelist with some cues|center}}

===Playing back cues===
Go, Back, etc.

However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.

===Using advanced timing (=> Property Based Timing)===
It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color, and after that change the gobo.

In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in milliseconds. Also you can use fanned values here. See [[Lesson_9_Tut3|Lesson 9]].

The following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.
{| align="center"
|{{Picture_with_subtitle |Dmxc3 advanced timing value.jpg|8|Value mode|center}}
|{{Picture_with_subtitle |Dmxc3 advanced timing fade.jpg|9|Fade mode|center}}
|-
|align="center" colspan="2"|{{Picture_with_subtitle |Dmxc3 advanced timing delay.jpg|10|Delay mode|center}}
|}
 
===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values.
 
==Exercises==
1) Generate your own cues
 
2) Try the buttons "STOP", "GO" and "Mode" in the cue list
 
3) Work with different fade times

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

Lesson 7 Tut3

2025-03-02T18:54:23Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_6_Tut3
| TextBackwards = Lesson 6
| LinkForwards = Lesson_8_Tut3
| TextForwards = Lesson 8
}}
==Overview==
In this lesson a final overview about the basic concepts for setting up the DMXControl 3 software is given. This completes the first part of the lectures "Basics, Setup and configuration".

==Lecture 7: Summary and details of setup ==
Now we will finalize our first expedition through DMXControl by investigating other generic features.
 
DMXControl 3 is very focused on working with groups of devices. These groups can be defined in a very effective and flexible way. Due to the strong abstraction of device properties, you can also combine different types of devices in groups (to program them later uniformly). Also adding devices to a group later is no problem.
 
The management of all elements is centralized in the '''Project Explorer'''. Here you keep control over your devices, groups, views, cue lists, and so on.
The new panel concept requires some practice, but you'll love it if you mastered it. So you can adjust the DMXControl 3 completely according to your needs!
 
There are lots of additional buttons in the main menu for operational support:
* File
** Here you can create, open and save projects
** With "project properties" you can assign some notices to the current project
* Windows
** Beside some tools that will be explained later on, here you find a chat tool. The chat tool is helpful if several operators and programmers work in parallel with DMXControl 3. They can exchange messages here.
** The "manual beat tool" can be compared to the corresponding tool in DMXControl 2. By pressing the space key you can generate manual beats.
* Settings
** '''Application settings''': Double click the icons in order to set configuration options.
** Here we refer to the affinity feature: DMXControl is trying to calculate similarities of gobos. If you have two moving lights with different gobos and, for example, you select in the (mixed) property grid a "starry sky" gobo, it tries automatically to take the most similar gobo on each device.
With the option '''Affinity View''' you can manually adjust the "similarities" to your subjective view.
{{Picture_with_subtitle|DMXC3L07 AffinityView.JPG|1|View of AffinityView-Tool|center}}

If you choose a gobo on the left side, you will logically find the same logo in the first place on the righ side. If this does not exist on your device, it will automatically take the next one in the list and so on. With the up and down arrows you can manually change the order.

On left hand side of your screen you have some global icons. Here we want to refer to
* Fog
** Here you have several operation modes for your DMX-controled fog device
* Highlight
** Rapid activation and deactivation of a device by simply clicking on it. Particularly suitable for setting up your stage.
* Blackout
** As the name indicates: Blackout of all devices
 
The project explorer also contains some general buttons:
* Edit
* Create directory / create device group
* Up / Down
* Device Manager
* Add item list / add Live view
* Import / export files

This is for administrative operations in your device configuration.
{{Picture_with_subtitle|DMXC3L07 ProjectExplorerMenues.JPG|2|Project explorer menu|center|700px}}

One helpful tool is missing for basic checks and setting up of DMX channels: the channel overview (Windows -> channel overview). Here you will get an overview about the current output. With the slider on left hand side you can also modify the value of the selected channel.

{{Manual Box | en | Hint | Please be aware that the '''Channel Overview''' is not finally ready and still is under construction.}}
{{Picture_with_subtitle|DMXC3L07 channelOverview.JPG|3|View of channel overview|center|700px}}

==Exercise==
1) Set channel 34 to DMX value 128 with help of channel overview
 
2) Try the Highlight and Blackout mode (observe results in Stage view panel)

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

Lesson 6 Tut3

2025-03-02T18:54:05Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_5_Tut3
| TextBackwards = Lesson 5
| LinkForwards = Lesson_7_Tut3
| TextForwards = Lesson 7
}}
In order to control your lamps you need to send out "real" DMX signals to your universes. In this lesson we explain how to configure your output devices.

==Lecture 6: Configuring the output plugins ==
In the menu "settings" you can find the panel '''DMX interfaces'''. There you can select your DMX transmitter/sender by choosing it in the new window that appears when pressing button '''Add interfaces'''.
{{Picture_with_subtitle|DMXC3L06_DE_IF_plugin.JPG|1|Adding Interfaces|center}}

Then, the interface has to be configured on "Advanced Interface Settings". Here you can make fine tuning and set the configuration settings that are supported by your DMX transmitter. In the shown case you can modify e.g. the break time if the DMX receiver in one of your lamps requires a higher value. In "Set Interface Mode" you can choose a mode that corresponds to your application.
In Figure 2, the mode is still set to '''0 - Standby'''. In order for the DE or fx5 interface to output something, you should select Mode '''2 - PC Out -> select DMX Out'''.

{{Picture_with_subtitle |DMXC3L06_DE_IF_plugin_settings.JPG|2|View of the advanced settings of the DE- or fx5-Interfaces|center}}

Interfaces that support more than one DMX universe (such as the visualization tool 3D Easy View), have a line in the table for each DMX Universe. Therefore, 3D EasyView gets four lines.

The field '''Port''' indicates the corresponding input or output of the interface. In the columns '''DMX Out Address''' and '''DMX-In Address''' you can assign a port to a DMX Universe with a double click.

The entry must be constructed as shown below:
Universe.DMX start channel

The DMX512 standard only supports 512 address (also called channels). If more than 512 are needed, people will start a new set of DMX network connections and cabling. Each of these is called a "DMX Universe". Your DMX control device may support multiple DMX universes.

DMXControl 3 supports 16 DMX universes (Universe 1 to 16) with 512 channels each (channel 1 to channel 512).

For example, if it is intended for the DE or fx5 interface to send all channel values from channel 83-512 in Universe 4, and DMXControl should use received DMX values via DMX in on Universe 6, you have to enter '''4.83''' within the appropriate field '''DMX-out address''' and '''6.1''' in '''DMX-In Address'''.

On some interfaces (such as the Nicolaudie SIUDI) a port can only act either as a DMX-In or as DMX-Out. In this case, check boxes that appear in columns '''DMX-Out Enabled''' and '''DMX-In Enabled''', to adjust the respective wanted behavior.

{{Manual Box | en | Hint | There are DMX devices that have problems with the timing. These devices respond completely wrong or only partially to transmitted DMX values. A change in the values "Break Time" may remedy the situation. Just try it. You can adjust these values also under "Advanced Interface Settings".
}}

==Exercise==
1) Activate and configure your DMX transmitter
 
2) Configure an ArtNet Interface ("Artistic License")
 
3) Set the Output-Universe of Port2 of ArtNet-Interfaces to channel 65 of third universe
 
4) What happens by inserting '''2.513''' or '''17.1'''?

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

Lesson 3 Tut3

2025-03-02T11:03:45Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_2_Tut3
| TextBackwards = Lesson 2
| LinkForwards = Lesson_4_Tut3
| TextForwards = Lesson 4
}}
==Overview==
In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and patching fixtures==
The starting point for adding devices is the '''project explorer''' (pic.1). Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. These are controlled by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{Manual Box | en | Hint | The project explorer is the central project tree containing all elements of your project. It is primarily intended to create and browse your items. For usage in the show programming, you would use "stage view" and other tools.
}}
{{Picture_with_subtitle|DMXC3L03 projectExplorer.JPG|1|The project explorer|center|500px}}

==Add Devices==
As an example, in the following step we will create 4 moving lights of type "TS-255".

Click either on the button '''Device Manager''' in the menu bar of the Project Explorer or choose in the left pane of the Project Explorer the folder '''Devices''' and do a right mouse click into the right pane and select '''device manager''' (pic.2).
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses. Fill out the fields in the window named "Add new device" as follows;
* Number of Devices; 4
* Device Name; TS-255
* DMX Start Address; 200
* DMX Space; 4
* Select the check-box marked "Autogenerate Group".
* Group Name; TS-255 Group 2
* Repeat; 1

{{Picture_with_subtitle|DMXC3L03 createDevice.JPG|2|The device manager, create device|center|650px}}

===Device Groups===
By setting the check mark for "Autogenerate Group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer (pic.3).
 
{{Picture_with_subtitle|DMXC3L03 createDeviceGroup.JPG|3|Create device groups|center|500px}}

When you do a right mouse click on an item the property menu appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or choose ''rename'' in the context menu (right mouse click).

==Exercise==
1) Create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
 
2) Create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

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

Lesson 1 Tut3

2025-03-02T11:03:28Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkForwards = Lesson_2_Tut3
| TextForwards = Lesson 2
}}

==Overview==
Because the operating concept changed completely compared to DMXControl 2 it is necessary to nearly start all over again for the use of DMXControl 3. These lessons will help you to become familiar with this concept and provide you the skills necessary for the basic characteristics of the new user interface. First of a small glimpse of what is waiting for you (pic.1):
{{Picture_with_subtitle|DMXC3 Overview.jpg|1|A selection of some windows of DMXControl 3|center|600px}}

This lesson is an introduction to the distributed architecture of DMXControl 3.0. You will learn some facts about the client and server communication and how to operate the kernel.
 
==Lecture: Installation and Configuration==
DMXControl 3 is installed with the help of a setup wizard. It verifies that the required software is installed on the PC (see below) and offers to install it if necessary. Optionally, EasyView (a visualizer) can be selected.

DMXControl 3.0 consists of two programs. One acts as server, the other one as client. The server (hereafter referred to as kernel) manages all information related to the project, such as the list of lighting instruments, and the cue list, etc. The kernel runs on the Windows operating system, but can also be launched on Linux (with Mono). The client acts as an interface between the server and the user.

''Advanced note; One or more clients can run on several systems (PCs) in parallel. This structure enables you to work in teams for building and performing your show. DMXControl 3.0 also supports cooperation during the life cycle, i.e. you can execute scene lists during someone else is still programming the missing cues!

''The separation of the server and the client has following advantages: 
* ''if the client (user interface) fails, the kernel (server) continues including sending DMX output
* ''several users can share the kernel to work in a team
* ''kernel and user interface could run on different computers
 
===The kernel===
At first, lets start the kernel that is the DMXControl server. Currently this application is called "DMXControl 3 Kernel" or "Lumos.exe" (pic.2).

In future a default user don't have to be aware about the kernel process. It will be automatically started with DMXControl and is (hopefully) continuously running.

{{Picture_with_subtitle|DMXC3L01 kernel.JPG|2|Kernel window with miscellaneous information|center|600px}}

During the start-up process of the kernel you can observe what is loaded by DMXControl. The kernel is the central master of all information about devices, cues, projects etc. that can be accessed by the clients. And it provides the DMX mixer engine and output system.

The kernel provides a command shell (pic.3). By typing "help" you get an overview about all supported commands.
 
{{Picture_with_subtitle|DMXC3L01 konsole.JPG|3|Kernel window with command shell "help" overview|center|600px}}

Here are a few command line options to get more detailed information about the status of the kernel:
*shutdown: Ends the kernel
*status: Displays status information
*menu: menu-access control?
*clear: Clears the console
*notification xxx: Sends a notification to all clients
*width xxx: Specifies the width of the console (number of characters)
*load xxx: Loading a project
*save xxx: Saves the current project
*dmxout [channel, val] +: Sets DMX Out Values
*DMXin [channel, val] +: Sets DMX In Values
*help: help menu (also accessible via '?')

For further details on ''menu'' and ''status'' see Appendix 2.
 
===The client / user interface===
In the next step you should start the windows-based user interface (currently called "DMXControl 3 GUI" or LumosGUI.exe"), which is located in the sub-folder "GUI" in the program directory. This client is explained in more detail in the next lessons.
First, however, the communication between kernel and client is initiated automatically. When you start the client a connection window opens. You can also select the Menu ''Connection-->Connect'' in order to connect with the server. In the lower right corner of the DMXControl window there is a small blue/grey server-icon that shows a small cross in red if no connection exists. The connection window also opens if you click on that icon (pic.4).

{{Picture_with_subtitle|DMXC3L01 connect.JPG|4|Lumos GUI "Connect to DMXControl Server" window|center|500px}}

If you have installed a firewall you have to grant the communication between client and server(pic.5).

{{Picture_with_subtitle|DMXC3_Tutorial_Lektion1_Firewall.png|5|Firewall setup|center|700px}}

After establishing the connection you should see a small blue icon in the lower line of the DMXControl main window indicating the existing connection. A red cross indicates that the connection failed.

{{Manual Box | en | Hint |If you execute the "LumosGUI.exe" with the parameter "-nonetwork", the kernel will automatically start up a client and connect it directly to the kernel. Thereby you do not have to connect the client manually and the system is ready to go. '''After installation you will find an entry in your start-menu called "DMXControl 3". This option includes this parameter.'''
}}
 
===Project Management===
To start a new project, choose '''File => New Project'''. If you want to save the current project, click on '''File => Save Project''' or '''File => Save Project As...'''. All project files are saved in a zip-file. You can load saved files with '''File => Load Project'''.

The name of current project is indicated in the top line of DMXControl window.
 
==Exercise==
1) Please try following commands in command shell:
* menu
* status
* shutdown -> uups!
 
2) Restart kernel and GUI and connect your client ("DMXControl 3 GUI") with DMXControl server.

3) Try it: exit your DMXControl GUI by task manager and start again: The kernel continues running.
 
Congratulation! Now you have successfully installed your own DMXControl configuration!
 
==Assumptions for installation==
DMXControl 3.0 requires following software to be installed:

* DirectX 9.0c
* .NET Framework 3.5 SP1 or higher
* XNA Framework 3.0(xnafx30_redist.msi)

{{Manual Box | en | Hint | In the GUI folder, there is a program called '''GraphicalView.exe'''. With this program, you can check your system for compatibility with DMXControl 3. It contains a test scene.
}}
 
==Additional links and references==
# [http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=9226A611-62FE-4F61-ABA1-914185249413&displaylang=de DirectX 9.0c]
# [http://www.microsoft.com/downloads/de-de/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6 .NET Framework 3.5]
# [http://www.microsoft.com/downloads/de-de/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7 .NET Framework 3.5 Service Pack 1]
# [http://www.microsoft.com/downloads/details.aspx?FamilyID=6521d889-5414-49b8-ab32-e3fff05a4c50&displaylang=en XNA Framework 3.0] (Has to be installed even if a higher version of XNA framework is already installed)
__NOTOC__
__NOTITLE__
[[de:Lektion_1_Tut3]]
[[Category: Tutorials DMXControl 3]]

Lesson 2 Tut3

2025-03-02T11:02:39Z

Jnoetzel: /* Hideaway Forms */

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0.0
| LinkBackwards = Lesson_1_Tut3
| TextBackwards = Lesson 1
| LinkForwards = Lesson_3_Tut3
| TextForwards = Lesson 3
}}
==Overview==
In this lessons you will learn how to operate with the panel system of DMXControl 3.0. You can assign your panels in a flexible way and save and restore your favorite configurations.

==Lecture 2: The panel concept of the DMXControl 3 client==
DMXControl 3 provides a lot of tools and windows. For different usage situations, different designs will be in focus. Therefore DMXControl uses a very flexible panel mechanism. You can create your own individual panel configurations.
The forms in the program can be unlocked to float above the main window or can be docked to the top, bottom, left or right margins. This versatility gives you the power to build screens that are easy to use and tailored to your personal preference and to move panels to several monitors. You can drag a window by grabbing its header bar. It will turn transparent, and small icons will appear on the screen to show where you can dock the window. A panel can also be set to occupy the left-over space in the middle (pic.1).

{{Picture_with_subtitle|DMXC3_Manual_Panel-Konzept_Example.png|1|Panel assignment shown with the project explorer.|center|960px}}

Some important explanations:

* A "floating" form is simply one that isn’t docked to any side.
* A pane or panel is a container for several forms.
* The docking suggestion is a symbol indicating the options where a form can be docked. It is available both in the main window and in each '''pane'''. The potential position of the form is indicated by a blue rectangle.
* Forms are created via the "Windows" system and are closed with the ‘X’ in its top right corner. This will close the form but leave other forms in a pane untouched.
* The (vertical) push-pin is the small pin icon that appears by default within docked forms that always show. Clicking the push-pin changes the forms status to hide-away form, i.e. the form becomes unpinned and disappears, but a tab is created within the pane. Note that this tab is created on the side that the form was originally docked.
* Pane splitting - a pane can be split into 2 visible panes
* Pane sharing - several forms share a pane, but only the top one is displayed. The other ones are in status "auto hide" and show as tabs.

===Panes===
A docking pane can accommodate more than one form. A pane is automatically created by docking more than one form. All forms contained are represented by a tab strip. Moving the mouse cursor over the tab displays the form (but it doesn't get the focus). By clicking the tab the form is brought into front (with getting the focus).

There are several ways for releasing docking and getting a floating window:
* After creation a form is already floating
* Double-click on the blue or grey header bar of a docked form
* Double-click on the tab of a docked form
* Click, hold and drag on the header bar of a form
* Click, hold and drag on the tab of a form

Once a form is floating it can be dragged to be docked anywhere.

Even within a panel you have new docking suggestion points for pane splitting.

===Pane-splitting===
By dragging the floating window and positioning your mouse cursor near the pane you get an internal docking suggestion. You can get the two windows to split the space in half and see both, but with only half the space each. This can be done vertically or horizontally.
In the upper example (Picture 1) the floating window "Project Explorer" would share the space with the "Programmer" if you release the mouse button.

===Pane Sharing===
As an alternative to pane-splitting, you can get your windows to share a space – they will share a single pane. You choose the form to be seen from the tabs displayed at the edge of the pane. Drag the floating form so that the mouse cursor is over the top of the form.
There are two slight variations on this, depending on the original form occupying the space. The form can be:
*Docked on the side
*Filling the spare space in the middle (a ‘Document’ form)

If you add more forms to the pane than there is room to display the tab, he left and right arrows become active and can be used to show the tabs that are hidden.

===Hideaway Forms===
When you click the push-pin at the top of the forms next to the close-down ‘X’, it falls over.
The form becomes ‘unpinned’ and appears to slide off the edge of the screen. The remaining screen re-arranges itself and the space previously taken by the hideaway form is shared with the nearby forms (pic.2.

{{Manual Box | en | Hint |The push-pin applies to the PANE, not to a single window in it. When forms are sharing a pane they are hidden or revealed together.
}}

{{Picture_with_subtitle|DMXC3_Manual_Panel-Konzept_Hideaway_forms_hidden.png|2|View with different hideaway forms.|center|960px}}
{{Picture_with_subtitle|DMXC3_Manual_Panel-Konzept_Hideaway_forms_shown.png|3|Device control shown.|center|960px}}

In this panel configuration the left, right and bottom panel are used. The left panel is a split one. The right panel contains one auto-hide window (see tab strip). The Project Explorer window is floating.

===Auto-Hide===
DockPanel has an auto-hide feature that can be very useful.
If there is any auto hide window, DockPanel will display a tab strip on the out-most edge.
An auto hide window has 3 statuses:
*hide
*mouse-hover-display and
*click-display.
In hide status, only the tab is displayed. The window itself is completely hidden. This will preserve valuable screen space so it can display more information.

===Save/Restore Layout settings===
You can save and restore your individual layout setting by menu ''Settings->Layout''.

==Further Information==
The handling of different panels is based on Dockpanel suite of Weifen Luo (also some text reused).
[http://www.codeproject.com/KB/miscctrl/DockManager.aspx]

==Exercise==
1) Create a new form (Menu "Windows") and dock and release it at several positions
 
2) Save and reload your own panel configuration

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

Appendix 2 Tut3

2025-03-02T10:48:31Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0
| LinkBackwards = Appendix_1_Tut3
| TextBackwards = Appendix_1
}}
==Hints for testing and error handling==
In this article you will find out what you should do in case of a fault in order to support developers with debugging. You will receive information on how you can check for errors and how and where you can report a bug. But first, you learn something about the targeted search for errors.

==An error occurs==
You are doing something in DMXControl 3. Then suddenly:
{{Picture_with_subtitle |DMXC3_Tutorial_Appendix_Error.png|1|Error in DMXControl 3 Beta|center|700px}}

The error occurs in the beta. It is not serious and can happen. But, it would be bad if this error is undocumented, because it can not be resolved. Therefore, you should proceed as follows:

Have a look into the '''Logs panel''' ('''Help''' => '''Logs''').
There DMXControl writes information about the latest events. At the bottom now one or more entries, as can be seen in Figure 2, are probably present.

{{Picture_with_subtitle |DMXC3_Tutorial_Appendix_Logs.png|2|Logs-Panel in DMXControl 3|center|700px}}

Furthermore, these log messages are stored in files. This you should definitely export ('''Help =>'''Export log files'''), because they are needed later.
{{Picture_with_subtitle |DMXC3_Tutorial_Appendix_ExportLogs.png|3|Export function for log files|center}}

If you can reproduce this fault, please report it via '''bug tracker''' on DMXControl home page.
The '''bugtracker''' for DMXControl 3 you can also find directly under www.dmxcontrol.de/flyspray/index.php?project=3&do=index&switch=1.

There all errors are collected so that the developers can easily see the error and fix it. You can report a fault completely anonymously, but it's better to register if there are any further questions. There is no further obligation.

Before you report a bug, please, first search if this bug is already listed in the bug tracker. If the fault a new one, you can report it via '''Create new task'''.
{{Picture_with_subtitle |DMXC3_Tutorial_Appendix_Bugtracker.png|4|View of our Bugtracker|center|700px}}

Please describe as accurately as possible how you came to this error. Please also attach your project and the exported log files to the new task in the bugtracker. Then, hopefully, the developers can fix this soon.
Thanks for your support!

==Known Issues==
===Issue: GUI Elements display glitches===
Symptoms:
* This could look like shown below:
* Also if you move windows it happens that thay are not displayed correct.
Dmxc_3_menu_errors.jpg
* This can occur if you have a NVidia graphics card and use an old driver version.

Prerequisites:
* I experienced this issue with a GeForce G 103M Driver Version 258.96 + PhysX 09.10.0513 on Windows XP x86_64.

Cause:
* unknown

Resolution:
* Consider updating the driver to the latest version. Version 266.58 + PhysX 09.10.0514 is known to work.

===Issue: Kernel not starting===
Symptoms:
* Kernel does not start.
sourcecode
1 2013-01-07 12:50:38,692 [Main] ERROR org.dmxc.lumos.Kernel.Resource.Xml2ManagedTreeConverter - Error in Reading KeyValue Pair: Attribute
2 System.InvalidOperationException: Temporäre Klasse kann nicht generiert werden (result=1).
3 error CS0016: In die Ausgabedatei c:\Users\Jens\AppData\Local\Temp\tugsyzgs.dll konnte nicht geschrieben werden -- Zugriff verweigert.

Prerequisites:
* Comodo Personal Firewall / Internet security installed

Cause:
* Comodo runs Lumos in a sandbox. This sandbox prohibits access to some files or locations.
* Lumos uses XmlSerializer to (de)serialize objects that it doesn't know. To instantiate a XmlSerializer object the CLR creates temporary assemblies and loads them afterwards. These assemblies are stored in AppData\Local\Temp\ however the sandbox doesn't allow (write) access to this directory (wtf?)

Resolution:
* Put Lumos.exe on the list of trusted applications

* Should we contact Comodo and try to get on their shipped whitelist?

* There is the possibility to generate this XmlSerializer assemblies at compile time and then ship them, but plugin authors would need to do the same. Then we get a huge chaos because there are different versions for the same types out. Also this stuff needs to be in the Kernel root dir... Stuff from third parties belongs in the plugin dir.

===Issue: Grouping of icons ins stage view does not work.===
Symptoms:
* If you hold down a button (e.g. m for matrix grouping) and move the mouse, the icons are not getting moved. Btw. this is not an issue in regards to Lumos, this symptom also occurs if you try this on your desktop

Prerequisites:
* Synaptics Touchpad

Cause:
* Synaptics implemented an option called PalmCheck which should reduce cursormovement while typing. Whenever a button is pressed the mouse input gets disabled...

Resolution:
* This option can be disabled unter Control Panel->Mice->Device Settings->Settings->(Point)->Sensitivity->PalmCheck

{{NavigationTop-Tut3
| LinkBackwards = Appendix_1_Tut3
| TextBackwards = Appendix_1
}}
[[de: Anhang_2_Tut3]]
[[Category: Tutorials DMXControl 3]]

Appendix 1 Tut3

2025-03-02T10:48:27Z

Jnoetzel:

{{Manual Header
| Type = DMXC3 Tutorials
| Version = 3.0
| LinkBackwards = Lesson_24_Tut3
| TextBackwards = Lesson 24
| LinkForwards = Appendix_2_Tut3
| TextForwards = Appendix 2
}}
==Summary of commands and shortcuts==
===Linear fanning===
{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || linear interpolation
|-
| <> || 50 <> 100 || linear interpolation: marginal devices: 50, central devices 100 (mnemonic trick: In the symbol both signs are directed outside; there the first value is applied; the second value is applied in the center.)
|-
| >< || 50 >< 100 || contrary: marginal devices: 100, central devices 50 (mnemonic trick: In the symbol both signs are directed inside; there the first value is applied (in the center); the second value is applied at the edge.)
|}

=== Alternate fanning ===
{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| # || 50 # 100 || alternate values 100/50/100/50 ...
|-
| # # || 100 # 50 # 0 || alternate values 100/50/0/100/50/0 ...
|}

=== Fanning in property grid with mouse wheel===
{| class="wikitable"
|-
! Key !! Value !! Description
|-
| no key pressed || +1 / -1 || dedicated color changes value
|-
| Shift || +10 / -10 || dedicated color changes value
|-
| STRG || +1 & -1 || Fanning / values are changed, z.B.118 > 154
|-
| ALT || +1 / -1 || values are changed
|-
| Shift+STRG || +10 / -10 || values are changed
|-
| Shift+ALT || +10 & -10 || values are changed in block
|}

=== Property Panels ===
{| class="wikitable"
|-
! Key !! Reaction !! Description
|-
| Double click || zero position || e.g. Color panel, Position panel
|-
| Simple click to fader || stepwise increase/decrease value || depending on whether one clicks above or below the current position
|}

=== Programmer ===
{| class="wikitable"
|-
! Key !! Reaction !! Description
|-
| ENTF || Deletes current line || select line, value is deleted from programmer
|-
| || ||
|}

=== effect parameters ===
{| class="wikitable FCK__ShowTableBorders"
|-
! Attribute
! Example
! Description
|-
| Amplitude
| 50 > 100
| value interval for selected attribute; can be set to negative value too
|-
| Phase
| [0..1]
| offset between group elements
|-
| Frequency
| [0..1]
|  cycle speed 
|}

===Stage View===
{| class="wikitable"
|-
! key !! action !! result
|-
| M ("Matrix") || press key M and drag mouse || a matrix is created from the selected icons
|-
| F ("Fanning") || press key F and drag mouse || icons are proportionally aligned (e.g. in a row)
|-
| C ("Circle") || press key C and drag mouse || icons are aligned in shape of circle
|}

===Cue list===
{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Add || Strg+A || Add a new scene to scene list at the end || default
|-
| Insert || Strg+I || Insert a new scene to scenelist before selected scene ||
|-
| Replace || Strg+R || Replace current scene attributes by the values in the programmer ||
|-
| Merge|| Strg+M || Merges selected scene with programmer values || programmer values with higher priority
|-
| Append || Strg+P || Append new property from programmer to the selected scene || existing scene with higher priority, new values from programmer are added
|-
| Subtract || Strg+B || Removes a property from selected scene || hint: modify the wanted property so that this appears in the programmer
|-
| Sum (Special) || || Inserts current output of devices into Cue List ||
|-
| PSum (Special) || || Similar to Sum, but related to currently selected devices in Stage View ||
|-
| Preset (Special) || || Opens a window, where you have the capability to add a Preset to Cue List ||
|-
| Scenelist (Special) || || Inserts (similar to commands in DMXControl 2) a entry to impact another cue list ||
|}

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Edit in Programmer || || Selected cue is loaded into Programmer. Programmer Output Mode is set to '''All''' ||
|-
| Edit in Programmer Blind || || Selected cue is loaded into Programmer. Programmer Output Mode is set to '''Blind''' ||
|-
| Cut || Strg+X || cut the selected scene || like EXCEL "cut row"
|-
| Copy || Strg+C || copy the selected scene || like EXCEL "copy row"
|-
| Paste || Strg+V || paste the selected scene || like EXCEL "paste row"
|-
| Delete|| Del(Entf) || delete the selected scene || like EXCEL "delete row"
|-
| Renumber Cues || || || Renumber Cues
|-
| Cue Timing Editor || || || a separate editor is opened
|}

===Kernel===
There are some command options in the command line mode for getting detailed information on the status of the kernel:

* shutdown: Shut down the kernel.
* status: Displays information about the status
* menu: Access to control menu
* clear: Clears the console
* notification: Send a notification to all clients
* width: Defines width of console (number of characters)
* help: Help menu (also accessible via "?")

Additional second level menu commands exists for "menu" and "status".

{{NavigationTop-Tut3
| LinkBackwards = Lesson_24_Tut3
| TextBackwards = Lesson 24
| LinkForwards = Appendix_2_Tut3
| TextForwards = Appendix 2
}}
[[de:Anhang_1_Tut3]]
[[Category: Tutorials DMXControl 3]]