English DMXC-Wiki - User contributions [en]

Lesson 19 Tut3

2013-04-18T18:32:28Z

Frank Burghardt:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| 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 ==

{{BoxHint
|Text= Currently the OSC plugin if 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:

[[file:DMXC3L19_OSC1.JPG]]

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:

[[file:DMXC3L19_OSC2.JPG]]

==Exercise==

==Additional links and references==
* [http://www.hexler.net TouchOSC]

[[de:Lektion 19]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| LinkBackwards = Lesson_18_Tut3
| TextBackwards = Lesson 18
| LinkForwards = Lesson_20_Tut3
| TextForwards = Lesson 20
}}

[[category:DMXControl 3]]

Lesson 19 Tut3

2013-04-18T18:31:08Z

Frank Burghardt:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| 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 ==

{{BoxHint
|Text= Currently the OSC plugin if 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:

[[Datei:DMXC3L19_OSC1.JPG]]

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:

[[Datei:DMXC3L19_OSC2.JPG]]

==Exercise==

==Additional links and references==
* [http://www.hexler.net TouchOSC]

[[de:Lektion 19]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| LinkBackwards = Lesson_18_Tut3
| TextBackwards = Lesson 18
| LinkForwards = Lesson_20_Tut3
| TextForwards = Lesson 20
}}

[[category:DMXControl 3]]

ToC Manual DMXC3

2013-01-22T15:59:43Z

Frank Burghardt:

=Proposal for further discussion=

Chapter 1: Preamble/Vorwort

Chapter 2: Introduction/Einleitung

Chapter 3: Installation

Chapter 4: Project Explorer

Chapter 5: Stage View

Chapter 7: DMX Interaces

Chapter 8: Property Panels

Chapter 9: Property Grid

Chapter 10: Channel overview

 

Chapter 11: Cues

Chapter 12: Cue lists

Chapter 13: Executor

Chapter 14: Master

Chapter 15: Sound Analyzer

Chapter 16: Softdesk

 

Chapter 17: Program configuration

Chapter 18: Plugin administration

Chapter 19: DDF Basics

Chapter 20: DDFCreator

Chapter 21: Plugin: Beamertool

Chapter 22: Plugin: Matrixeffects

Chapter 23: Plugin: OSC Receiver Modul

 

Chapter 24: Addon: Magic EasyView Visualizer

Appendix1: Glossar

Appendix2: Shortcuts

Appendix3: System requirements

Appendix4: Panel system

ToC Manual DMXC3

2013-01-21T21:40:30Z

Frank Burghardt:

Proposal for further discussion

Chapter 1: Preamble/Vorwort

Chapter 2: Introduction/Einleitung

Chapter 3: Installation

Panel system?

Chapter 4: Project Explorer

Chapter 5: Stage View

Chapter 7: DMX Interaces

Chapter 8: Kanalübersicht

 

Chapter 9: Cues

Chapter 10: Cue lists

Chapter 11: Executor

Chapter 13: Master

Chapter 14: Sound Analyzer

Chapter 16: Softdesk

 

Chapter 29: Program configuration

Chapter 30: Plugin administration

Chapter 32: DDF Basics

Chapter 33: DDFCreator

Chapter 34: Plugin: Beamertool

Chapter 35: Plugin: Matrixeffects

Chapter 36: Plugin: OSC Receiver Modul

 

Chapter 37: Addon: Magic EasyView Visualizer

Appendix1: Glossar

Appendix2: Shortcuts

ToC Manual DMXC3

2013-01-21T21:38:54Z

Frank Burghardt: draft proposal for Table of Content Manual DMXC3

Proposal for further discussion

Chapter 1: Preamble/Vorwort
Chapter 2: Introduction/Einleitung
Chapter 3: Installation
Panel system?
Chapter 4: Project Explorer
Chapter 5: Stage View
Chapter 7: DMX Interaces
Chapter 8: Kanalübersicht

Chapter 9: Cues
Chapter 10: Cue listsChapter 11: Executor

Chapter 13: Master
Chapter 14: Sound Analyzer
Chapter 16: Softdesk

Chapter 29: Program configuration
Chapter 30: Plugin administration
Chapter 32: DDF Basics
Chapter 33: DDFCreator
Chapter 34: Plugin: Beamertool
Chapter 35: Plugin: Matrixeffects
Chapter 36: Plugin: OSC Receiver Modul

Chapter 37: Addon: Magic EasyView Visualizer
Appendix1: Glossar
Appendix2: Shortcuts

Lesson 15 Tut3

2013-01-19T07:46:38Z

Frank Burghardt: Cue list Cue eingefügt

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_14_Tut3
| TextBackwards = Lesson 14
| LinkForwards = Lesson_16_Tut3
| TextForwards = Lesson 16
}}
==Overview==

In this lesson, you learn how to perform cue lists by executors.

==Lecture 15: Executors and execution of show ==

In Lesson 8 and 12 it was explained how to create scenes and scenelists. Now we want to execute our scene lists.

This works like in DMXControl 2, by opening the cuelist and using the '''Go''' and '''STOP''' buttons.

To run cues and cue lists you can also use '''executors'''. These correspond roughly to the submasters from DMXControl 2.

Again you can create various "banks" - in DMXControl 3 '' Pages''' called - in order to increase the number of executors in groups of 8. So, we create first in the '''Project Explorer''' a new executor page:

[[File:DMXC3L15 firstExecutorBank.JPG]]
{{Bild_mit_Unterschrift |DMXC3L15 firstExecutorBank.JPG|1|Executorbank|center|600px}}

By default we have 8 executors in one page (the number may be adjusted in '''Application Settings''').
The assignment to the executors happens as follows:

===Assignment of cues===

When creating the cue ("Add cue" button) you have a small selection button next to the triangle. There you can assign the new cue to an executor directly. After selection, then please'' 'add cue''' button again.

===Assignment of cuelists===

In Project Explorer you can assign the cue list using "drag and drop" to the executors.
{{Bild_mit_Unterschrift |DMXC3L15 firstExecutor.JPG|2|Executor|center|600px}}

That an item has been assigned to an executor, is evident from the small green LED in select field. Try out what happens if you click on the "Select field".

There are other ways that you can affect the playback of a scene list:

{| class="wikitable"
|-
! Functionality !! Description
|-
| Intensity ||
|-
| Scene list Speed || The speed with which the scene list is traversed is affected. The speed of the effects will be unaffected.
|-
| Effect Speed || The speed of the used in the scene list is influenced effects. The speed of the scene list is not changed.
|}

You can select between different execution modes as you know it from the playlist mode of your favorite audio player:

[[File:DMXC3L15 firstExecutor.JPG]]

{| class="wikitable"
|-
! Functionality !! Description
|-
| Single || Die cue list is executed once
|-
| Repeat || Die cue list is repeated
|-
| Bounce || If the scene list arrived at the end it is repeated in the reverse order
|}

{{Bild_mit_Unterschrift |DMXC3L12 SL modemenue.jpg|3|Modes|center}}

==Work with multiple Cue lists==

There are different strategies for the design and splitting of the show in cue lists. You can create cue lists for the parts of the show (verse, chorus, Act) or you can divide groups of devices in cue lists (background LEDs, moving lights, etc.) or make a combination of both. It depends on personal taste and the size of the show.

You can insert a special "Cue list Cue" within a Cue list (Add --> Special --> Cue list). This lets you easily control another cue list. Thus, you could apply it for example for a recurring refrain.

==Excercise==
* Assign a new cue to to an executor directly
* Assign a cue list to an executor

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
Lesson 16

[[de:Lektion 15]]
[[en:Lesson 15]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| LinkBackwards = Lesson_14_Tut3
| TextBackwards = Lesson 14
| LinkForwards = Lesson_16_Tut3
| TextForwards = Lesson 16
}}

[[category:DMXControl 3]]

Getting started with DMXControl 3

2013-01-17T20:05:14Z

Frank Burghardt:

=Why DMXControl 3?=

DMXControl 3 is a new tool for controlling DMX lighting fixtures, which has implemented advanced concepts that you will be thrilled:

* The programming of the devices is at a very high level of abstraction. You take care not to DMX values per se, but you think only in the device properties (color, dimmer, gobo, etc.).
* You work mostly with groups of devices, on these you can apply prepared effects and fanning functionality. Then you get impressive light effects with minimal coding. In principle, every LED-bar/tube is already a group. Groups can be dynamically changed, and can also consist of various types of devices.
* The new cue lists provide very flexible triggering and control capabilities. They combine scene lists, timecode lists, effect lists, etc. A cue can be extremely powerful, e.g. by controlling creatively multiple groups of devices with multiple properties on a dynamic effect. So you can setup very quickly a show.
* DMXControl 3 supports team-oriented programming and execution of the show. By a separate kernel the stability and reliability of the control increases.

=Installation=

DMXControl 3 runs on all modern Windows systems. It is installed using a setup wizard that can also install the required additional software (DirectX,. NET). At program start two processes are started, see
[[Lesson 1 Tut3]].
 
[[File:DMXC3_Overview.jpg|center|400px]]
 

=Processing steps with DMXControl 3=

DMXControl 3 uses a very flexible windows / panel system [[Lesson 2 Tut3]]. For the different steps you can create and save different panel configurations. In essence, the work can be divided into three phases, for which you should define different panel configurations:

* Setup of the device configuration
* Editing and programming the show
* Execution (running the show, playback)

==Setup of the device configuration==

The most important tools for setup are the '''Device Manager''', the 2D '''Stage View''' and '''Project Explorer'''. The fixtures are added to the project by '''Device Manager'''. If your device is not visible in the offered list of devices, you will find [[Lektion_22_Tut3 | here]] about how a so-called DDF must be created. The '''Project Explorer''' will provide you an overview of all the equipment used, defined groups and controls that you can also create and delete with this tool. You can combine elements by drag and drop, e.g. add devices to groups. Try out the buttons and context menus (right-click).

In '''Stage View''' animated icons for devices are created that can be positioned according to its stage configuration. Here you can also create multiple views, e.g. to divide the devices or to model different locations.
 
[[File:DMXC3L04_liveView.JPG|center|400px]]
 

For DMX output configuration you need to select your transmitter in the "Interface Setting" menu item. DMXControl works also without attached interface. If your interface is not supported there is a workaround available for you [[Lektion_24_Tut3 | here]] using ArtNet and DMXControl 2. In the tool '''Channel view''' the distribution of equipment in the DMX universe can be observed.

==Editing and programming the show==

Cues are the means for programming your show. The cues can be much more powerful than in other lighting control programs and consoles. Creating a cue works as following:

* Definition of the desired devices in the Stage View by selecting the device icons or group icons
* Set the desired properties on the '''Property panel''' (intensity, color, pan / tilt, gobo) or the '''PropertyGrid'''
* Press the "Add Cue" button

You can assign with the selection triangle besides "Add Cue" button, in which cue list to the new queue shall be inserted. Especially interesting for creating a cue is the fanning feature ("fanning" means split a value to a group). For example if you are inserting "0>100" in a characteristic field in the '''PropertyGrid''', it is a linear distribution of the values on the group (for example, 0, 20, 40, 60, 80, 100 at 6 units). And the best part: It works for both the dimmer capacity as well as color, position, etc.

 
[[File:DMXC3L05_propertyTS.JPG|center|200px]]
 

And it gets even better: You can also drag & drop effects such as Sine, Chaser, Rectangle, etc. on these properties. The result you can see in the '''Stage View'''. You'll love it.
Even more options for fanning you can read in the [[Lesson_24_Tut3 | Tutorial]].

A new tool in DMXControl 3 is the '''Programmer'''. This is a sort of buffer, in which all changes to the current cue to be created are stored. Before saving, you can still specify a filter for specifying which values are actually to be stored in the cue. Note: After saving the cue you have to apply necessarily "Clear Programmer" button.

In cuelists there are different triggers for manual and automatic playback of the cues as well as attributes to define fade times and waiting times [[Lesson 11 Tut3]]. With the "mode" button you choose whether a cuelist to be executed repeatedly.
 
[[File:DMXC3L08_SecondScene.JPG|center|600px]]
 

There are different strategies for the design and splitting of the show in cue lists. You can create cue lists for the parts of the show (verse, chorus, Act) or you can divide groups of devices in cue lists (background LEDs, moving lights, etc.) or make a combination of both. It depends on personal taste and the size of the show.

Programming the show includes the '''Input Assignment''' too. This replaces the former command concept. With this panel, you arrange external signals (DMX-in, beat trigger, ...) to the DMXControl elements.

==Execution (running the show, playback)==

For running the show, the following tools are available:'''Executors''', '''cue lists''' and '''Softdesk'''.

Typically you assign the cuelist (of course, by drag and drop) to '''Executors''' (they are created via "Executor pages", [[Lesson_15_Tut3]]). By means of the slider you adjust the intensity and you can use the buttons "GO", "Pause / Back" and "Stop" for playback the cue list. Some of the control options are also on the panel of the cue list itself and this can of course also be used.

 
[[File:DMXC3L15_firstExecutor.JPG|center|400px]]
 

The'' 'Softdesk''' is the replacement of the previous command box ([[Lesson_16_Tut3]]). Here you can add buttons at which "special effects" such as Blinder, mirror ball or simply "mood changes" (different background colors) should be placed.

 
[[File:DMXC3L16_SoftDesk.JPG|center|300px]]
 

Only in very exceptional cases, you should interfere with the show via the programming interface. 

We wish you success in the incorporation into DMXControl 3 and a lot of fun in the programming and execution of the show.

==Links==

* Homepage/Download
* complete tutorial

Getting started with DMXControl 3

2013-01-17T19:35:50Z

Frank Burghardt:

=Why DMXControl 3?=

DMXControl 3 is a new tool for controlling DMX lighting fixtures, which has implemented advanced concepts that you will be thrilled:

* The programming of the devices is at a very high level of abstraction. You take care not to DMX values per se, but you think only in the device properties (color, dimmer, gobo, etc.).
* You work mostly with groups of devices, on these you can apply prepared effects and fanning functionality. Then you get impressive light effects with minimal coding. In principle, every LED-bar/tube is already a group. Groups can be dynamically changed, and can also consist of various types of devices.
* The new cue lists provide very flexible triggering and control capabilities. They combine scene lists, timecode lists, effect lists, etc. A cue can be extremely powerful, e.g. by controlling creatively multiple groups of devices with multiple properties on a dynamic effect. So you can setup very quickly a show.
* DMXControl 3 supports team-oriented programming and execution of the show. By a separate kernel the stability and reliability of the control increases.

=Installation=

DMXControl 3 runs on all modern Windows systems. It is installed using a setup wizard that can also install the required additional software (DirectX,. NET). At program start two processes are started, see
[[Lesson 1 Tut3]].
 
[[File:DMXC3_Overview.jpg|center|400px]]
 

=Processing steps with DMXControl 3=

DMXControl 3 uses a very flexible windows / panel system [[Lesson_2_Tut3]]. For the different steps you can create and save different panel configurations. In essence, the work can be divided into three phases, for which you should define different panel configurations:

* Setup of the device configuration
* Editing and programming the show
* Execution (running the show, playback)

==Setup of the device configuration==

The most important tools for setup are the '''Device Manager''', the 2D '''Stage View''' and '''Project Explorer'''. The fixtures are added to the project by '''Device Manager'''. If your device is not visible in the offered list of devices, you will find [[Lektion_22_Tut3 | here]] about how a so-called DDF must be created. The '''Project Explorer''' will provide you an overview of all the equipment used, defined groups and controls that you can also create and delete with this tool. You can combine elements by drag and drop, e.g. add devices to groups. Try out the buttons and context menus (right-click).

In '''Stage View''' animated icons for devices are created that can be positioned according to its stage configuration. Here you can also create multiple views, e.g. to divide the devices or to model different locations.
 
[[File:DMXC3L04_liveView.JPG|center|400px]]
 

For DMX output configuration you need to select your transmitter in the "Interface Setting" menu item. DMXControl works also without attached interface. If your interface is not supported there is a workaround available for you [[Lektion_24_Tut3 | here]] using ArtNet and DMXControl 2. In the tool '''Channel view''' the distribution of equipment in the DMX universe can be observed.

==Editing and programming the show==

Cues are the means for programming your show. The cues can be much more powerful than in other lighting control programs and consoles. Creating a cue works as following:

* Definition of the desired devices in the Stage View by selecting the device icons or group icons
* Set the desired properties on the '''Property panel''' (intensity, color, pan / tilt, gobo) or the '''PropertyGrid'''
* Press the "Add Cue" button

You can assign with the selection triangle besides "Add Cue" button, in which cue list to the new queue shall be inserted. Especially interesting for creating a cue is the fanning feature ("fanning" means split a value to a group). For example if you are inserting "0>100" in a characteristic field in the '''PropertyGrid''', it is a linear distribution of the values on the group (for example, 0, 20, 40, 60, 80, 100 at 6 units). And the best part: It works for both the dimmer capacity as well as color, position, etc.

 
[[File:DMXC3L05_propertyTS.JPG|center|200px]]
 

And it gets even better: You can also drag & drop effects such as Sine, Chaser, Rectangle, etc. on these properties. The result you can see in the '''Stage View'''. You'll love it.
Even more options for fanning you can read in the [[Lesson_24_Tut3 | Tutorial]].

A new tool in DMXControl 3 is the '''Programmer'''. This is a sort of buffer, in which all changes to the current cue to be created are stored. Before saving, you can still specify a filter for specifying which values are actually to be stored in the cue. Note: After saving the cue you have to apply necessarily "Clear Programmer" button.

In cuelists there are different triggers for manual and automatic playback of the cues as well as attributes to define fade times and waiting times [[Lesson_11_Tut3]]. With the "mode" button you choose whether a cuelist to be executed repeatedly.
 
[[File:DMXC3L08_SecondScene.JPG|center|600px]]
 

There are different strategies for the design and splitting of the show in cue lists. You can create cue lists for the parts of the show (verse, chorus, Act) or you can divide groups of devices in cue lists (background LEDs, moving lights, etc.) or make a combination of both. It depends on personal taste and the size of the show.

Programming the show includes the '''Input Assignment''' too. This replaces the former command concept. With this panel, you arrange external signals (DMX-in, beat trigger, ...) to the DMXControl elements.

Getting started with DMXControl 3

2013-01-17T18:55:44Z

Frank Burghardt: Created page with "=Why DMXControl 3?= DMXControl 3 is a new tool for controlling DMX lighting fixtures, which has implemented advanced concepts that you will be thrilled: * The programming ..."

Appendix 2 Tut3

2013-01-09T15:56:13Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Anhang_1_Tut3
| zurückText = Anhang 1
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
}}

===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 in 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:
{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_Fehlermeldung.png|1|Fehlermeldung in DMXControl 3 Beta|center|700px}}

The error occurs in the beta is not serious and can happen. Bad it would be 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 the be seen in Figure 2 are probably present.

{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_Logs.png|2|Logs-Panel von 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 laterly.
{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_ExportLogs.png|3|Exportfunktion für die Log-Dateien|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 quite easy can see the error and fix it. You can report a fault completely anonymous, but it's better if there are any further questions, to register without any further obligation.

Before you report a bug, please search at first if this bug is already listed in the bug tracker. Is your fault a new one, you can report it via '''Create new task'''.
{{Bild_mit_Unterschrift |DMXC3_Tutorial_Anhang_Bugtracker.png|4|Ansicht des Bugtrackers|center|700px}}

Please describe as accurately as possible, as it has come to this error. Please also attach your project and the exported log files to the new task in the bugtracker. Then the developers can fix this soon hopefully.
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:
Don't ask me.

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.

Quellcode 1 2 3 2013-01-07 12:50:38,692 [Main] ERROR org.dmxc.lumos.Kernel.Resource.Xml2ManagedTreeConverter - Error in Reading KeyValue Pair: Attribute System.InvalidOperationException: Temporäre Klasse kann nicht generiert werden (result=1). 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:
Don't use this crap (i mean comodo not lumos)
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... Suff 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

__NOTOC__
__NOTITLE__

[[de:Anhang 2]]
[[en:Appendix 2]]
{{NavigationTop-Tut3
| zurückLink = Anhang_1_Tut3
| zurückText = Anhang 1
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
}}

[[Kategorie:DMXControl 3]]

Appendix 2 Tut3

2013-01-06T18:12:51Z

Frank Burghardt:

Appendix 1 Tut3

2013-01-06T17:53:52Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_24_Tut3
| zurückText = Lektion 24
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Anhang_2_Tut3
| vorText = Anhang 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 increasement/decreasement of value || depending on whether one clicks above or below the current position
|}

=== Programmer ===

{| class="wikitable"
|-
! Key !! Reaktion !! Description
|-
| ENTF || Deletes current line || select line, value is deleted from programmer
|-
| || ||
|}

=== effect parameters ===

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribut
! 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 || || Selekted 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".

Go to [[Appendix 2]]

[[de:Anhang 1]]
[[en:Appendix 1]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_24_Tut3
| zurückText = Lektion 24
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Anhang_2_Tut3
| vorText = Anhang 2
}}

[[Kategorie:DMXControl 3]]

Lesson 23 Tut3

2013-01-06T17:52:00Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_22_Tut3
| zurückText = Lektion 22
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_24_Tut3
| vorText = Lektion 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.

= Lektion 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).
{{Bild_mit_Unterschrift |DMXC3L23_Project_Explorer.png|1|Project Explorer Konfiguration 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). 
{{Bild_mit_Unterschrift |DMXC3L23_Matrix_Properties.png|2|Properties des Matrix-DDF's|center|330px}}

The '' 'GUI Proprties''' and '''kernel Properties''' are not relevant. What interests us is the '''Device Properties''' in the bottom (see Figure 3). 
{{Bild_mit_Unterschrift |DMXC3L23_Matrix_Device_Properties.png|3|Device Properties des 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).
{{Bild_mit_Unterschrift |DMXC3L23_MatrixPatch.png|4|Ansicht des Fensters MatrixPatch|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).
{{Bild_mit_Unterschrift |DMXC3L23_DeviceSelection.png|5|Ansicht des Auswahldialogs DeviceSelection|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 columnwisely.

 
After clicking o n'''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 Martix DDF's our configuration is complete. Now we can see everything in '''Stage View'''. 

We sort the devices as in Figure 6:
{{Bild_mit_Unterschrift |DMXC3L23_Stage_View.png|6|Stage View Ansicht der sortierten Devices|center|600px}}

Here you can try one more time, the sorting function for matrix (press Shift-M)from [[Lesson 4]]. 

Next you please 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):
{{Bild_mit_Unterschrift |DMXC3L23_Matrix_Control.png|7|Ansicht des Fensters Matrix Control|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).
{{Bild_mit_Unterschrift |DMXC3L23_Matrix_Control2.png|8|Ansicht der Matrix im Fenster Matrix Control|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. 
{{Bild_mit_Unterschrift |DMXC3L23_Matrix_Effect-Fenster.png|9|Ansicht des Effekt-Fensters|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, the window 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.

{{BoxAttention
|Text=In order to make the Color dropdown list in the '''PropertyGrid''' visible, the matrix DDF in '''Stage View''' must be deselected and selected again.
}}

==Excercise==
* Try the different options described above and have fun with it.

Next Lesson: [[Lesson 24|ArtNet]]

[[de:Lektion 23]]
[[en:Lesson 23]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_22_Tut3
| zurückText = Lektion 22
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_24_Tut3
| vorText = Lektion 24
}}

[[Kategorie:DMXControl 3]]

Lesson 24 Tut3

2013-01-06T16:13:30Z

Frank Burghardt: Created page with "{{Hauptüberschrift | logo = Im-aim.png | ueberschrift = First Steps: {{PAGENAME}} }} {{DMXC3_lesson/en}} {{NavigationTop-Tut3 | zurückLink = Lektion_23_Tut3 | zurückText ..."

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_23_Tut3
| zurückText = Lektion 23
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_23_Tut3
| vorText = Lektion 23
}}

==Overview==

In this lesson we look at how we can combine the advantages of the 3-Series with those of series 2 by connection the tools via ArtNet.

= Lektion 24: Transfer of DMX values over Artnet to DMXControl 2 =

{{BoxHinweis
|Text = This lesson works in compliance with the order for Win XP and Win 7. Win 8 makes the moment even more problems, but it is worked to make this possible on Windows 8 also.
}}

Since DMXControl 3 still is in an early stage, some functions of the series 2 does not yet exist. This will be improved in the future, but it will still take some time before all the functions of the series 2 are present.

Nevertheless, we do not want to miss the advantages when using the 3-series. 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":

{{Bild_mit_Unterschrift |2.12_Ausgabeplugin_Konfiguration.PNG|1|Konfiguration ArtNet-Ausgabeplugin DMXControl 2|center|400px}}

Important here are the settings '''SubNet''' and for '''input node''' the '''Universe'''. We will configure DMXControl 3 in this way, 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.

We close the window by clicking OK and activate the output plugin by setting the hook before the name of the interface:
{{Bild_mit_Unterschrift |2.12_Ausgabeplugin.PNG|2|Ausgabepluginverwaltung DMXControl 2|center|400px}}

DMXControl 2 is now ready to receive ArtNet data. In the next step we need to bring DMXControl 3 for sending its DMX output via Artnet. At '''Settings--> DMX Interfaces''' we find the output plugins of DMXControl 3:

{{Bild_mit_Unterschrift |3.0_Ausgabeplugin.PNG‎|3|Ausgabepluginverwaltung DMXControl 3|center|600px}}

With '''Add Interface ...'''we now select the ArtNet plugin:
{{Bild_mit_Unterschrift |Art-Net_auswählen.PNG‎|4|ArtNet Interface hinzufügen DMXControl 3|center|350px}}

In simple configurations the ArtNet transmitter is running now. But to be sure we 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:

{{Bild_mit_Unterschrift |Adresse_auswählen.png‎|5|ArtNet Interface konfigurieren DMXControl 3|center|400px}}

If you start in DMXControl 2 now the DMX remote control (Window -> DMXin remote control) and change in '''Channel Overview''' of DMXControl 3 a value, it should be displayed on the DMXin remote control:

{{Bild_mit_Unterschrift |ErsterArtNetTest.PNG‎|6|Verbindung überprüfen DMXControl3 -> DMXControl 2|center|450px}}

This window must remain open for further operating!
Now we just need to patch the DMXin remote control of DMXControl 2 properly. About '''Configuration -> DMXin Remote control ...''' we get the configuration screen:
{{Bild_mit_Unterschrift |2_12DMXIn-Konfig.png‎|7|Aufrufen der DMXIn Konfiguration in DMXControl 2|center|300px}}

Here you could now control commands of DMXControl 2. We would like first of all patch all channels from ArtNet input of DMXControl 2 to DMX output. For this, we click at the right, still empty soft patch list '''1:1''':
{{Bild_mit_Unterschrift |Softpatch212.PNG‎|8|Konfiguration DMXIn Fernbedienung mit Softpatch DMXControl 2|center|600px}}

In the following dialogues we select the desired range of values. I decided to patch the entire DMX universe:
{{Bild_mit_Unterschrift |1zu1Patch212.PNG‎|9|Softpatch von Start-DMX-Adresse bis End-DMX-Adresse DMXControl 2|center|600px}}

{{Bild_mit_Unterschrift |Softpatch212fertig.PNG‎|10|DMXIn-Fenster nach Softpatch DMXControl 2|center|600px}}

By clicking on'' 'OK''' now we have to activate the DMXin remote control:
{{Bild_mit_Unterschrift |DMXIn_Aktivieren212.png‎|11|Aktivieren der DMXIn Fernbedienung DMXControl 2|center|600px}}

Now all values of DMXin are directly sent to the DMXOut interface.

You can test the connection e.g. by sending color gradient from DMXControl 3 to DMXControl 2. With this workaround we extend the functionality of DMXContro 2 with features from DMXControl 3.

===Error handling===

If no DMXin values of the remote control are shown, there is still a fault with the network configuration, so 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?

==Excercise==
* Configure the connection between DMXControl 3 and DMXControl 2
* Test the color gradient example mentioned above

Next Lesson: [[Lesson 23|RGB Matrix]]

[[de:Lektion 24]]
[[en:Lesson 24]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_23_Tut3
| zurückText = Lektion 23
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_23_Tut3
| vorText = Lektion 23
}}

[[Kategorie:DMXControl 3]]

Lesson 23 Tut3

2013-01-06T15:17:56Z

Lesson 22 Tut3

2013-01-06T15:15:27Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_21_Tut3
| zurückText = Lektion 21
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_23_Tut3
| vorText = Lektion 23
}}

==Overview==

In this lesson, we explain the so-called input assignment. This allows external signals such as DMX-in for control of DMXControl 3.

= Lektion 22: Input Assignment =

By means of '''Input Assignment''' external signals such as DMX-in can be used for control of DMXControl 3. This function is similar to the DMX In / MIDI remote control of DMXControl 2.

You find this tool here:

Settings -> Application Settings -> Input Assignment

You can simply drag and drop the available inputs on the left side on the logical channels and control structures on the right side.

 
{{Bild_mit_Unterschrift |DMXC3L21_InputAssignment.JPG|1|Input Assignment Fenster|center|600px}}
 [[File:DMXC3L21_InputAssignment.JPG|center]]

In the above example, the two front lights (white lights - generic dimmer) were associated with DMX-IN channel 1 and 2, so you can use an external board to control this dimmer channels.

Furthermore, the manual beat was associated with the first cuelist as an example.

{{BoxHinweis
|Text = In the beta version, there is no MIDI support.
}}

==Excercise==
* Perform the above example with your own project (assignment of the first two channels of DMX-In)

Next Lesson: [[Lesson 23|RGB Matrix]]

[[de:Lektion 22]]
[[en:Lesson 22]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_21_Tut3
| zurückText = Lektion 21
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_23_Tut3
| vorText = Lektion 23
}}

[[Kategorie:DMXControl 3]]

Appendix 1 Tut3

2013-01-06T09:11:55Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_24_Tut3
| zurückText = Lektion 24
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Anhang_2_Tut3
| vorText = Anhang 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 increasement/decreasement of value || depending on whether one clicks above or below the current position
|}

=== Programmer ===

{| class="wikitable"
|-
! Key !! Reaktion !! Description
|-
| ENTF || Deletes current line || select line, value is deleted from programmer
|-
| || ||
|}

=== effect parameters ===

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribut
! 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 || || Selekted 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".

[[de:Anhang 1]]
[[en:Appendix 1]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_24_Tut3
| zurückText = Lektion 24
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Anhang_2_Tut3
| vorText = Anhang 2
}}

[[Kategorie:DMXControl 3]]

Appendix 1 Tut3

2013-01-06T09:10:44Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_24_Tut3
| zurückText = Lektion 24
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Anhang_2_Tut3
| vorText = Anhang 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 increasement/decreasement of value || depending on whether one clicks above or below the current position
|}

=== Programmer ===

{| class="wikitable"
|-
! Key !! Reaktion !! Description
|-
| ENTF || Deletes current line || select line, value is deleted from programmer
|-
| || ||
|}

=== effect parameters ===

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribut
! 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
|}

{| 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 || || Selekted 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

|}

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".

[[de:Anhang 1]]
[[en:Appendix 1]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_24_Tut3
| zurückText = Lektion 24
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Anhang_2_Tut3
| vorText = Anhang 2
}}

[[Kategorie:DMXControl 3]]

File:DMXC3L21 InputAssignment.JPG

2013-01-06T09:01:34Z

Frank Burghardt:

Lesson 22 Tut3

2013-01-06T08:58:35Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_21_Tut3
| zurückText = Lektion 21
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_23_Tut3
| vorText = Lektion 23
}}

==Overview==

In this lesson, we explain the so-called input assignment. This allows external signals such as DMX-in for control of DMXControl 3.

= Lektion 22: Input Assignment =

By means of '''Input Assignment''' external signals such as DMX-in can be used for control of DMXControl 3. This function is similar to the DMX In / MIDI remote control of DMXControl 2.

You find this tool here:

Settings -> Application Settings -> Input Assignment

You can simply drag and drop the available inputs on the left side on the logical channels and control structures on the right side.

 
{{Bild_mit_Unterschrift |DMXC3L21_InputAssignment.JPG|1|Input Assignment Fenster|center|600px}}
 [[File:DMXC3L21_InputAssignment.JPG|center]]

In the above example, the two front lights (white lights - generic dimmer) were associated with DMX-IN channel 1 and 2, so you can use an external board to control this dimmer channels.

Furthermore, the manual beat was associated with the first cuelist as an example.

{{BoxHinweis
|Text = In the beta version, there is no MIDI support.
}}

==Excercise==
* Perform the above example with your own project (assignment of the first two channels of DMX-In)

[[de:Lektion 22]]
[[en:Lesson 22]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_21_Tut3
| zurückText = Lektion 21
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_23_Tut3
| vorText = Lektion 23
}}

[[Kategorie:DMXControl 3]]

Lesson 22 Tut3

2013-01-06T08:29:28Z

Frank Burghardt:

Lesson 21 Tut3

2013-01-06T08:23:35Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_20_Tut3
| zurückText = Lektion 20
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_22_Tut3
| vorText = Lektion 22
}}

==Overview==

Here you'll receive a summary of the possible executions of the show with DMXControl 3.

==Lecture 17: Summary Execution of show==

The two most important means of DMXControl 3 for controlling a show are
* Executors [[Lession 15 Tut3]] and
* Softdesks [[Lession 16 Tut3]]
 

Furthermore, one can directly use the cuelist and external clients (eg OSC clients). With the soft-desk concept you can practically rebuild any pult.
Particularly ingenious is that multiple people can control a show in parallel, e.g.:

* One person controls the front light
* A second person is responsible for stage lighting
* A third person controls certain pieces of music (via timecode triggered cuelists)

There is yet another control agent in the execution:

In comparason to DMXControl 2 we have only 1 Grandmaster, but it does its job: All dimmer channels are impacted.

[[File:DMXC3L17 GrandMaster.JPG]]
 
{{Bild_mit_Unterschrift |DMXC3L17 GrandMaster.JPG|1|Grandmaster|center}}
 

You get the Grandmaster via '''Controls -> Master'''

==Excercise==
* Set the Grandmaster to 50% and 100%
* Use two clients simultanously in a network

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 22]]

__NOTOC__
__NOTITLE__

[[de:Lektion 21]]
[[en:Lesson 21]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_20_Tut3
| zurückText = Lektion 20
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_22_Tut3
| vorText = Lektion 22
}}

[[Kategorie:DMXControl 3]]

Lesson 21 Tut3

2013-01-06T08:21:58Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_20_Tut3
| zurückText = Lektion 20
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_22_Tut3
| vorText = Lektion 22
}}

==Overview==

Here you'll receive a summary of the possible executions of the show with DMXControl 3.

==Lecture 17: Summary Execution of show==

The two most important means of DMXControl 3 for controlling a show are
* Executors [[Lession 15 Tut3]] and
* Softdesks [[Lession 16 Tut3]]
 

Furthermore, one can directly use the cuelist and external clients (eg OSC clients). With the soft-desk concept you can practically rebuild any pult.
Particularly ingenious is that multiple people can control a show in parallel, e.g.:

* One person controls the front light
* A second person is responsible for stage lighting
* A third person controls certain pieces of music (via timecode triggered cuelists)

There is yet another control agent in the execution:

In comparason to DMXControl 2 we have only 1 Grandmaster, but it does its job: All dimmer channels are impacted.

[[File:DMXC3L17 GrandMaster.JPG]]
 
{{Bild_mit_Unterschrift |DMXC3L17 GrandMaster.JPG|1|Grandmaster|center}}
 

You get the Grandmaster via '''Controls -> Master'''

==Excercise==
* Set the Grandmaster to 50% and 100%
* Use two clients simultanously in a network

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 18]]

__NOTOC__
__NOTITLE__

[[de:Lektion 21]]
[[en:Lesson 21]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_20_Tut3
| zurückText = Lektion 20
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_22_Tut3
| vorText = Lektion 22
}}

[[Kategorie:DMXControl 3]]

Lesson 20 Tut3

2013-01-06T08:14:00Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_19_Tut3
| zurückText = Lektion 19
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_21_Tut3
| vorText = Lektion 21
}}

==Overview==
In this lesson we will learn how to create and add new device definitions. You need to do this acivity 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 wiritten in XML language and stored in the path
<DMXControl program path>\kernel\devices

If you are familar 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 menues
* Sone 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 fpr DMXControl 3, we recommend to use 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 have a view to a very simple DDF ("Generic RGB Par"):

----

 

{| cellspacing="1" cellpadding="1" border="0" align="center" 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 mandatory default line for describing the XML version.
Lines 02 and 15 provide the frame for the device definition that contains of 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 posesses one property: RGB colar mode. The mapping to DMX channels is described in lines 10 to 12.

Thats 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 channe 
| colspan="3" | <pre><switch dmxchannel="0" /></pre>
|-
| dimmer
| colspan="2" | fixture has a dimmer channel 
| colspan="3" | <pre><dimmer dmxchannel="0" /> </pre>
|-
| fog
| colspan="2" | fod property 
| colspan="3" | <pre><fog dmxchannel="0" /></pre>
|-
| shutter
| colspan="2" | fixture has a shutter 
| colspan="3" | <pre><shutter dmxchannel="0" /></pre>
|-
| strobe
| colspan="2" | fixture has a strobe channel 
| colspan="3" | <pre><strobe dmxchannel="0" /></pre>
|-
| iris 
| colspan="2" | fixture has a iris channel 
| colspan="3" | <pre><iris dmxchannel="0"/></pre>
|-
| focus 
| colspan="2" | fixture has a fokus channel 
| colspan="3" | <pre><focus dmxchannel="0"/></pre>
|-
| zoom 
| colspan="2" | fixture has a zoom channel 
| colspan="3" | <pre><zoom dmxchannel="0"/></pre>
|-
| rgb
| colspan="2" | fixture has RGB function
| colspan="3" | <pre><rgb>
<red dmxchannel="0" />
<green dmxchannel="1" />
<blue dmxchannel="2" />
</rgb>
</pre>
|-
| cmy 
| colspan="2" | fixture has CMY function 
| colspan="3" | <pre><cmy>
<cyan dmxchannel="0"/>
<magenta dmxchannel="1"/>
<yellow dmxchannel="2"/>
</cmy>
</pre>
|-
| position
| colspan="2" | fixture has Pan and/ or Tilt
| nowrap="nowrap" colspan="3" | <pre><position>
<pan dmxchannel="0">
<range range="540" />
</pan>
<tilt dmxchannel="1">
<range range="246" />
</tilt>
</position>
</pre>
|-
| color wheel
| colspan="2" | fixtures contains color wheel
| colspan="3" | <pre><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>
</pre>
|-
| rowspan="4" | gobo wheel
| rowspan="3" | fixture with Gobo wheel
| valign="top" nowrap="nowrap" |
 

Gobo rotation

| valign="top" nowrap="nowrap" rowspan="3" | <pre><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></pre>
|-
| 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:
 
<pre><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>
</pre>
 

If the fixture has a color / gobo wheel, which can rotate at random positions, then write it as follows:
 
<pre><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>
</pre>
 

If a device has fine channels for eg zoom, then write it as follows:
 
<pre><zoom dmxchannel="0" finedmxchannel="1"/>
</pre>

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>

 

{{BoxHinweis|Text=A DDF Creator for DMXControl 3 is already in work. 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.
}}

==Excercise==
* Have a look into several device definitions before creating your own DDF.
* Open the DDF for TS255. Separate the different properties by blank lines to get a better understanding.
* Create the DDF for your own device.

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 21]]

[[de:Lektion 20]]
[[en:Lesson 20]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_19_Tut3
| zurückText = Lektion 19
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_21_Tut3
| vorText = Lektion 21
}}

[[Kategorie:DMXControl 3]]

Lesson 20 Tut3

2013-01-06T08:00:37Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_19_Tut3
| zurückText = Lektion 19
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_21_Tut3
| vorText = Lektion 21
}}

==Overview==
In this lesson we will learn how to create and add new device definitions. You need to do this acivity 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 wiritten in XML language and stored in the path
<DMXControl program path>\kernel\devices

If you are familar 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 menues
* Sone 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 fpr DMXControl 3, we recommend to use 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 have a view to a very simple DDF ("Generic RGB Par"):

----

 

{| cellspacing="1" cellpadding="1" border="0" align="center" 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 mandatory default line for describing the XML version.
Lines 02 and 15 provide the frame for the device definition that contains of 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 posesses one property: RGB colar mode. The mapping to DMX channels is described in lines 10 to 12.

Thats 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 channe 
| colspan="3" | <pre><switch dmxchannel="0" /></pre>
|-
| dimmer
| colspan="2" | fixture has a dimmer channel 
| colspan="3" | <pre><dimmer dmxchannel="0" /> </pre>
|-
| fog
| colspan="2" | fod property 
| colspan="3" | <pre><fog dmxchannel="0" /></pre>
|-
| shutter
| colspan="2" | fixture has a shutter 
| colspan="3" | <pre><shutter dmxchannel="0" /></pre>
|-
| strobe
| colspan="2" | fixture has a strobe channel 
| colspan="3" | <pre><strobe dmxchannel="0" /></pre>
|-
| iris 
| colspan="2" | fixture has a iris channel 
| colspan="3" | <pre><iris dmxchannel="0"/></pre>
|-
| focus 
| colspan="2" | fixture has a fokus channel 
| colspan="3" | <pre><focus dmxchannel="0"/></pre>
|-
| zoom 
| colspan="2" | fixture has a zoom channel 
| colspan="3" | <pre><zoom dmxchannel="0"/></pre>
|-
| rgb
| colspan="2" | fixture has RGB function
| colspan="3" | <pre><rgb>
<red dmxchannel="0" />
<green dmxchannel="1" />
<blue dmxchannel="2" />
</rgb>
</pre>
|-
| cmy 
| colspan="2" | fixture has CMY function 
| colspan="3" | <pre><cmy>
<cyan dmxchannel="0"/>
<magenta dmxchannel="1"/>
<yellow dmxchannel="2"/>
</cmy>
</pre>
|-
| position
| colspan="2" | fixture has Pan and/ or Tilt
| nowrap="nowrap" colspan="3" | <pre><position>
<pan dmxchannel="0">
<range range="540" />
</pan>
<tilt dmxchannel="1">
<range range="246" />
</tilt>
</position>
</pre>
|-
| color wheel
| colspan="2" | fixtures contains gobo wheel
| colspan="3" | <pre><colorwheel dmxchannel="0">
<step type="color" val="#ffffff" caption="Weiß" mindmx="0" maxdmx="0" />
<step type="color" val="#00bd52" caption="Grün 203" mindmx="32" maxdmx="32" />
<step type="color" val="#080094" caption="Blau 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="Weiß" mindmx="160" maxdmx="160" />
</colorwheel>
</pre>
|-
| rowspan="4" | gobo wheel
| rowspan="3" | fixture with Gobo wheel
| valign="top" nowrap="nowrap" |
 

Gobo rotation

| valign="top" nowrap="nowrap" rowspan="3" | <pre><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></pre>
|-
| valign="top" |
Goboposition

|-
|
Rotation Gobo 1

Shake Gobo 1 

 

|}

Wenn das Fixture über ein Farb/Goborad verfügt , das sich Kontinuirlich drehen kann, dann schreibt man das so: 
<pre><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>
</pre>
 

Wenn das Fixture über ein Farb/Goborad verfügt , das sich auf zufällige positionen drehen kann, dann schreibt man das so: 
<pre><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>
</pre>
 

Wenn ein Gerät über feine Kanäle für z.B Zoom verfügt, dann schreibt man das so: 
<pre><zoom dmxchannel="0" finedmxchannel="1"/>
</pre>
das funktioniert bei jedem 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>

 

{{BoxHinweis|Text=Ein DDF-Creator für DMXControl 3 ist bereits in Arbeit. Bis dahin bitte die eigenen DDFs mit einem XML-Editor Eurer Wahl oder einfach mit einem Texteditor erstellen. Manchmal hilft es, ein bereits existierendes DDF zu kopieren und anzupassen.
Bitte sendet uns Eure neuen DDFs, damit wir sie in die Bibliothek aufnehmen können.}}

==Excercise==
* Have a look into several device definitions before creating your own DDF.
* Open the DDF for TS255. Separate the different properties by blank lines to get a better understanding.
* Create the DDF for your own device.

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 21]]

[[de:Lektion 20]]
[[en:Lesson 20]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_19_Tut3
| zurückText = Lektion 19
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_21_Tut3
| vorText = Lektion 21
}}

[[Kategorie:DMXControl 3]]

Lesson 20 Tut3

2013-01-06T07:52:34Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_19_Tut3
| zurückText = Lektion 19
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_21_Tut3
| vorText = Lektion 21
}}

==Overview==
In this lesson we will learn how to create and add new device definitions. You need to do this acivity 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 wiritten in XML language and stored in the path
<DMXControl program path>\kernel\devices

If you are familar 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 menues
* Sone 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 fpr DMXControl 3, we recommend to use 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 have a view to a very simple DDF ("Generic RGB Par"):

----

 

{| cellspacing="1" cellpadding="1" border="0" align="center" 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 mandatory default line for describing the XML version.
Lines 02 and 15 provide the frame for the device definition that contains of 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 posesses one property: RGB colar mode. The mapping to DMX channels is described in lines 10 to 12.

Thats 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 hat einen Switch-Kanal 
| colspan="3" | <pre><switch dmxchannel="0" /></pre>
|-
| dimmer
| colspan="2" | Fixture hat einen Dimmer-Kanal 
| colspan="3" | <pre><dimmer dmxchannel="0" /> </pre>
|-
| fog
| colspan="2" | Nebel-Kanal 
| colspan="3" | <pre><fog dmxchannel="0" /></pre>
|-
| shutter
| colspan="2" | Fixture hat einen Shutter 
| colspan="3" | <pre><shutter dmxchannel="0" /></pre>
|-
| strobe
| colspan="2" | Fixture hat einen Strobe-Kanal 
| colspan="3" | <pre><strobe dmxchannel="0" /></pre>
|-
| iris 
| colspan="2" | Fixture hat einen Iris-Kanal 
| colspan="3" | <pre><iris dmxchannel="0"/></pre>
|-
| focus 
| colspan="2" | Fixture hat einen Fokus-Kanal 
| colspan="3" | <pre><focus dmxchannel="0"/></pre>
|-
| zoom 
| colspan="2" | Fixture hat einen Zoom-Kanal 
| colspan="3" | <pre><zoom dmxchannel="0"/></pre>
|-
| rgb
| colspan="2" | Fixture hat die RGB-Funktion
| colspan="3" | <pre><rgb>
<red dmxchannel="0" />
<green dmxchannel="1" />
<blue dmxchannel="2" />
</rgb>
</pre>
|-
| cmy 
| colspan="2" | Fixture hat die CMY-Funktion 
| colspan="3" | <pre><cmy>
<cyan dmxchannel="0"/>
<magenta dmxchannel="1"/>
<yellow dmxchannel="2"/>
</cmy>
</pre>
|-
| position
| colspan="2" | Fixture hat Pan und/ oder Tilt
| nowrap="nowrap" colspan="3" | <pre><position>
<pan dmxchannel="0">
<range range="540" />
</pan>
<tilt dmxchannel="1">
<range range="246" />
</tilt>
</position>
</pre>
|-
| color wheel
| colspan="2" | Fixture mit Farbrad
| colspan="3" | <pre><colorwheel dmxchannel="0">
<step type="color" val="#ffffff" caption="Weiß" mindmx="0" maxdmx="0" />
<step type="color" val="#00bd52" caption="Grün 203" mindmx="32" maxdmx="32" />
<step type="color" val="#080094" caption="Blau 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="Weiß" mindmx="160" maxdmx="160" />
</colorwheel>
</pre>
|-
| rowspan="4" | gobo wheel
| rowspan="3" | Fixture mit Gobobrad
| valign="top" nowrap="nowrap" |
 

Goborotation

| valign="top" nowrap="nowrap" rowspan="3" | <pre><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></pre>
|-
| valign="top" |
Gobopositi

|-
|
Rotation Gobo 1

Shake Gobo 1 

 

|}

Wenn das Fixture über ein Farb/Goborad verfügt , das sich Kontinuirlich drehen kann, dann schreibt man das so: 
<pre><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>
</pre>
 

Wenn das Fixture über ein Farb/Goborad verfügt , das sich auf zufällige positionen drehen kann, dann schreibt man das so: 
<pre><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>
</pre>
 

Wenn ein Gerät über feine Kanäle für z.B Zoom verfügt, dann schreibt man das so: 
<pre><zoom dmxchannel="0" finedmxchannel="1"/>
</pre>
das funktioniert bei jedem 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>

 

{{BoxHinweis|Text=Ein DDF-Creator für DMXControl 3 ist bereits in Arbeit. Bis dahin bitte die eigenen DDFs mit einem XML-Editor Eurer Wahl oder einfach mit einem Texteditor erstellen. Manchmal hilft es, ein bereits existierendes DDF zu kopieren und anzupassen.
Bitte sendet uns Eure neuen DDFs, damit wir sie in die Bibliothek aufnehmen können.}}

==Excercise==
* Have a look into several device definitions before creating your own DDF.
* Open the DDF for TS255. Separate the different properties by blank lines to get a better understanding.
* Create the DDF for your own device.

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 21]]

[[de:Lektion 20]]
[[en:Lesson 20]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_19_Tut3
| zurückText = Lektion 19
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_21_Tut3
| vorText = Lektion 21
}}

[[Kategorie:DMXControl 3]]

File:DeviceManegerInfoBox.jpg

2013-01-06T07:40:20Z

Frank Burghardt:

Lesson 19 Tut3

2013-01-06T07:38:15Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_18_Tut3
| zurückText = Lektion 18
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_20_Tut3
| vorText = Lektion 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 ==

{{BoxHint
|Text= Currently the OSC plugin if 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:

[[Datei:DMXC3L19_OSC1.JPG]]

Now, you should define the IP connection in the panel "connection form". Press the "+" button to create a new connention.
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:

[[Datei:DMXC3L19_OSC2.JPG]]

==Excercise==

==Additional links and references==
* [http://www.hexler.net TouchOSC]

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 20]]

[[de:Lektion 19]]
[[en:Lesson 19]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_18_Tut3
| zurückText = Lektion 18
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_20_Tut3
| vorText = Lektion 20
}}

[[Kategorie:DMXControl 3]]

Lesson 18 Tut3

2013-01-05T10:53:50Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_17_Tut3
| zurückText = Lektion 17
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_19_Tut3
| vorText = Lektion 19
}}

==Overview==
In this lesson we explain how to connect DMXControl with the beamer tool. The beamer tool is a multimedia software that allows playing videos and other multimedia effects.

==Lecture 18: Multimedia Support ==

There is already an existing interworking between DMXControl 3 and the beamer tool.

'''Unfortunately, the current version is not available for this beta release. Please have a little patience ...

==Excercise==
*
*

==Additional links and references==
*

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 19]]

[[de:Lektion 18]]
[[en:Lesson 18]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_17_Tut3
| zurückText = Lektion 17
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_19_Tut3
| vorText = Lektion 19
}}

[[Kategorie:DMXControl 3]]

Lesson 17 Tut3

2013-01-05T10:51:16Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_16_Tut3
| zurückText = Lektion 16
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_18_Tut3
| vorText = Lektion 18
}}

==Overview==

Here the audio analyzer is presented which is implemented as a plugin in DMXControl 3.

==Lecture 17: Audio Analyser ==

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 Analyser'''. The audio analyzer provides essentially the same features as the Soundanalyser([[Sound_Analyzer_DMXC2|Soundanalyser]]) of DMXControl 2.
{{BoxHinweis
| Text = This plugin is still in an experimental stage.
}}

{{Bild_mit_Unterschrift |DMXC3L17 PluginAudioAnalyser.jpg|1|Ansicht des Audioanalyser Fensters|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 analyse 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 a special clock (BPM) pretend

And now the question remains, how it will be allocated between the results of the analysis to beat the device properties and cuelist. You already have an idea? ... Of course, this is also consistent in the'' 'input Assigment''' concept introduced in([[Lektion_22_Tut3]]).

{{Bild_mit_Unterschrift |DMXC3L17 PluginAudioAnalyserInputAssignment.JPG|2|Zuordnung der Soundevents im Input Assigment|center|600px}}

==Excercise==* Activate the AudioAnalyser. If your sound card does not have an internal redirection and you currently have no external player available, use the microphone input as a substitute.

==Additional links and references==
*[[Sound_Analyzer_DMXC2|Soundanalyser DMXControl 2]]

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 18]]

[[de:Lektion 17]]
[[en:Lesson 17]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_16_Tut3
| zurückText = Lektion 16
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_18_Tut3
| vorText = Lektion 18
}}

[[Kategorie:DMXControl 3]]

File:DMXC3L17 PluginAudioAnalyserInputAssignment.JPG

2013-01-05T10:39:47Z

Frank Burghardt:

File:DMXC3L17 PluginAudioAnalyser.jpg

2013-01-05T10:39:27Z

Frank Burghardt:

Lesson 21 Tut3

2013-01-05T10:38:02Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

==Overview==
Now we present the GrandMaster.

==Lecture 17: Master ==
In comparason to DMXControl 2 we have only 1 Grandmaster, but it does its job: All dimmer channels are impacted.

[[File:DMXC3L17 GrandMaster.JPG]]

You get the Grandmaster via '''Controls -> Master'''

'''topics to be added (by beta testers)'''
*

==Excercise==
* Set the Grandmaster to 50% and 100%
*

==Additional links and references==
*

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 18]]

__NOTOC__
__NOTITLE__

[[de:Lektion 21]]
[[en:Lesson 21]]

__NOTOC__
__NOTITLE__

Lesson 16 Tut3

2013-01-05T10:36:12Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_15_Tut3
| zurückText = Lektion 15
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_17_Tut3
| vorText = Lektion 17
}}

==Overview==
In this lesson you will learn something about the Softpult plugin. This tool allows you to create panels simulating a pult according to your own design ideas.

==Lecture 16: Softpult ==

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 consoles with the Softdesk editor.

The Softpult (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 an administration GUI appears at first:

[[File:DMXC3L16 SoftDesk plugin.JPG]]

Here you can create, delete, edit, copy, import and export your instancies of softdesks. There simply set the hook.
Then you find a new entry "Softdesk" under the menu item "Windows" (possibly restarting the GUI-clients required).

 
{{Bild_mit_Unterschrift |DMXC3L16 SoftDesk plugin.JPG|1|Softdeskplugin aktivieren|center}}
 

After opening the plugin via the menu a GUI appears for the first administration 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.

 
{{BoxHinweis
|Text=DMXControl 3 stores all soft desks automatically within the project (Save Project). The export / import function is used to transfer the created panel to external clients (eg Android).
}}

You can create multiple console surfaces, which can then be activated simultaneously at run time (but you don't have several banks within a softpult available).

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. Try it, also the design grid mode!

Here you can see one possible result:

[[File:DMXC3L16 SoftDesk.JPG]]
 
{{Bild_mit_Unterschrift |DMXC3L16 SoftDesk.JPG|2|Softdeskplugin|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".

[[File:DMXC3L16 CommandboxProperties.JPG]]
 
{{Bild_mit_Unterschrift |DMXC3L16 CommandboxProperties.JPG|3|Einstellungen|center}}
 
{{BoxHinweis
|Text=Note the need for the change the size of individual elements using the mouse as they occur at the corners.
}}

In the next step you have to connect your softdesk with your project, i.e. you have to assign functions to your softpult resp. control elements.

This has to be performed with the input assignment panel (menu '''Application Settings''' (-->[[Lesson 22 Tut3|Lesson22]])). On left hand side you find the controls, on right hand side the DMXControl explorer is shown. Simply drag and drop the control elements to certain properties, attributes or elements to make a connection.

[[File:DMXC3L16 SoftDeskInputAssignment.JPG]]
 
{{Bild_mit_Unterschrift |DMXC3L16 SoftDeskInputAssignment.JPG|4|Input Assignment|center}}
 
{{BoxHinweis|Text=Do not forget switching off the design mode at run time.}}

The softpult windows are integrated into the panel system, see [[Lesson2/en]]. That means you can have attached panels or flying windows containing the softpult.
The individual soft desks are then opened with a double (with Design Mode off).

Have fun trying! We wish you a high level of artistic creativity for your own desks!

==Excercise==
* Create two softpults, one consisting of buttons only, the other one should contain all types of control elements
* Control colors with your button softpult
* connect the XYpad with your moving light and test the function

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 17]]

[[de:Lektion 16]]
[[en:Lesson 16]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_15_Tut3
| zurückText = Lektion 15
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_17_Tut3
| vorText = Lektion 17
}}

[[Kategorie:DMXControl 3]]

Lesson 15 Tut3

2013-01-05T09:00:57Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_14_Tut3
| zurückText = Lektion 14
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_16_Tut3
| vorText = Lektion 16
}}

==Overview==

In this lesson, you learn how to perform cue lists by executors.

==Lecture 15: Executors and execution of show ==

In [[Lesson 8]] and 12 it was explained how to create scenes and scenelists. Now we want to execute our scene lists.

This works like in DMXControl 2, by opening the cuelist and using the '''Go''' and '''STOP''' buttons.

To run cues and cue lists you can also use '''executors'''. These correspond roughly to the submasters from DMXControl 2.

Again you can create various "banks" - in DMXControl 3 '' Pages''' called - in order to increase the number of executors in groups of 8. So, we create first in the '''Project Explorer''' a new executor page:

[[File:DMXC3L15 firstExecutorBank.JPG]]
{{Bild_mit_Unterschrift |DMXC3L15 firstExecutorBank.JPG|1|Executorbank|center|600px}}

By default we have 8 executors in one page (the number may be adjusted in '''Application Settings''').
The assignment to the executors happens as follows:

===Assignment of cues===

When creating the cue ("Add cue" button) you have a small selection button next to the triangle. There you can assign the new cue to an executor directly. After selection, then please'' 'add cue''' button again.

===Assignment of cuelists===

In Project Explorer you can assign the cue list using "drag and drop" to the executors.
{{Bild_mit_Unterschrift |DMXC3L15 firstExecutor.JPG|2|Executor|center|600px}}

That an item has been assigned to an executor, is evident from the small green LED in select field. Try out what happens if you click on the "Select field".

There are other ways that you can affect the playback of a scene list:

{| class="wikitable"
|-
! Functionality !! Description
|-
| Intensity ||
|-
| Scene list Speed || The speed with which the scene list is traversed is affected. The speed of the effects will be unaffected.
|-
| Effect Speed || The speed of the used in the scene list is influenced effects. The speed of the scene list is not changed.
|}

You can select between different execution modes as you know it from the playlist mode of your favorite audio player:

[[File:DMXC3L15 firstExecutor.JPG]]

{| class="wikitable"
|-
! Functionality !! Description
|-
| Single || Die cue list is executed once
|-
| Repeat || Die cue list is repeated
|-
| Bounce || If the scene list arrived at the end it is repeated in the reverse order
|}

{{Bild_mit_Unterschrift |DMXC3L12 SL modemenue.jpg|3|Modes|center}}

==Excercise==
* Assign a new cue to to an executor directly
* Assign a cue list to an executor

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 16]]

[[de:Lektion 15]]
[[en:Lesson 15]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_14_Tut3
| zurückText = Lektion 14
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_16_Tut3
| vorText = Lektion 16
}}

[[Kategorie:DMXControl 3]]

Lesson 15 Tut3

2013-01-05T08:59:57Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_14_Tut3
| zurückText = Lektion 14
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_16_Tut3
| vorText = Lektion 16
}}

==Overview==

In this lesson, you learn how to perform cue lists by executors.

==Lecture 15: Executors and execution of show ==

In [[Lesson 8]] and 12 it was explained how to create scenes and scenelists. Now we want to execute our scene lists.

This works like in DMXControl 2, by opening the cuelist and using the '''Go''' and '''STOP''' buttons.

To run cues and cue lists you can also use '''executors'''. These correspond roughly to the submasters from DMXControl 2.

Again you can create various "banks" - in DMXControl 3 '' Pages''' called - in order to increase the number of executors in groups of 8. So, we create first in the '''Project Explorer''' a new executor page:

[[File:File:DMXC3L15 firstExecutorBank.JPG]]
{{Bild_mit_Unterschrift |DMXC3L15 firstExecutorBank.JPG|1|Executorbank|center|600px}}

By default we have 8 executors in one page (the number may be adjusted in '''Application Settings''').
The assignment to the executors happens as follows:

===Assignment of cues===

When creating the cue ("Add cue" button) you have a small selection button next to the triangle. There you can assign the new cue to an executor directly. After selection, then please'' 'add cue''' button again.

===Assignment of cuelists===

In Project Explorer you can assign the cue list using "drag and drop" to the executors.
{{Bild_mit_Unterschrift |DMXC3L15 firstExecutor.JPG|2|Executor|center|600px}}

That an item has been assigned to an executor, is evident from the small green LED in select field. Try out what happens if you click on the "Select field".

There are other ways that you can affect the playback of a scene list:

{| class="wikitable"
|-
! Functionality !! Description
|-
| Intensity ||
|-
| Scene list Speed || The speed with which the scene list is traversed is affected. The speed of the effects will be unaffected.
|-
| Effect Speed || The speed of the used in the scene list is influenced effects. The speed of the scene list is not changed.
|}

You can select between different execution modes as you know it from the playlist mode of your favorite audio player:

[[File:File:DMXC3L15 firstExecutor.JPG]]
{| class="wikitable"
|-
! Functionality !! Description
|-
| Single || Die cue list is executed once
|-
| Repeat || Die cue list is repeated
|-
| Bounce || If the scene list arrived at the end it is repeated in the reverse order
|}

{{Bild_mit_Unterschrift |DMXC3L12 SL modemenue.jpg|3|Modes|center}}

==Excercise==
* Assign a new cue to to an executor directly
* Assign a cue list to an executor

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 16]]

[[de:Lektion 15]]
[[en:Lesson 15]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_14_Tut3
| zurückText = Lektion 14
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_16_Tut3
| vorText = Lektion 16
}}

[[Kategorie:DMXControl 3]]

Lesson 14 Tut3

2013-01-04T23:13:53Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_13_Tut3
| zurückText = Lektion 13
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_15_Tut3
| vorText = Lektion 15
}}

==Overview==
This chapter provides a summary of the programming capabilities of DMXControl 3.

==Lecture 14:Speed and productivity improvement of show programming ==

DMXControl 3 offers you with

* Cue list,
* the programmer,
* sevaral fading approaches,
* the Hardware abstraction,
* DMXControl kernel ("Light engine with Fanning algorithms) and
* effect library

features as professional DMX tools.

Within the programmer the individual cues can be checked again and tested before they are permanently stored in a cuelist by means of the programmer filter.

This beta version of DMXControl 3 provides not yet 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.

{{BoxHinweis
|Text =The library scene is not found in this form in the current version. But you can use for this same purpose the presets which even has a number of additional capabilities.
}}

Note that the fanning and effects possibilities not only can be used as in the examples shown for dimmer value and color, but for almost all device attributes such as pan / tilt, fade-in, delay, etc. This can be extremely effective and brilliant effects can be achieved.

A further increase in productivity is obtained by being able to manipulate the cue lists EXCEL moderately.
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 you to program big shows in minutes!

We still remember a DMXControl meeting in 2008, when we programmed an entire day on a show of the length of 5 minutes. At night we proudly present this show a professional and we asked him how long it would take for him?

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 in recent years everything to get there. We think that we've landed with DMXControl 3 near this vision!

==Excercise==
* Assign a new cue directly to an executor
* Assign the existing Cue list to another executor

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 15]]

[[de:Lektion 14]]
[[en:Lesson 14]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_13_Tut3
| zurückText = Lektion 13
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_15_Tut3
| vorText = Lektion 15
}}

[[Kategorie:DMXControl 3]]

Lesson 13 Tut3

2013-01-04T22:57:34Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_12_Tut3
| zurückText = Lektion 12
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_14_Tut3
| vorText = Lektion 14
}}

==Overview==
In this lesson we explain how to apply presets. By re-using presets you are more efficiently when programming your show.

==Lecture 13: Presets ==

Presets are very similar to cues. You can create them in the same way, see [[Lesson 8]]. Similar to the button "Create cue" here you find the button "Create preset". You can use presets to store different values for the parameters of your fixtures. You can store:

* moving light positions
* colors of RGB Pars
* combination of gobo, shutter on and color
* generic chasers (where you later only replace/modify the color)
* or simply intensities of your conventional fixtures
* etc.

The big advantage of using presets is, that it's referenced data. That means, whenever you record a cue using presets, not the actual values, but a link to the preset is stored. So keep in mind, if you change your preset, all cues that use this preset will use the new values. A simple example where presets can rapidly speed up programming would be:
You've recorded a color of your cyc wash as a preset and used this preset in five cues. If you later decide to modify the cyc wash a bit, you just need to update one preset instead of five cues. However if you just want to change the color in one cue you can do that by overwriting the reference with manual data.

[[File:DMXC3L13 Preset.jpg]]

===Recording Presets===

To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See [[Lesson 8]] how to use the programmer filter. After you pressed OK in the programmer filter, a new preset will be recorded. You can now use F2 (or click into name field) to rename it.

===Modifying Presets===

If you want to modify an existing preset, select the preset you want to modify and click on the arrow right of the "Add Preset" button. A menu will pop up, where you can choose how to modify the preset.

====Replace====
Replace will remove all existing entries from the preset and save everything that is in the programmer to the preset.

====Merge====
Entries that are not in the programmer but in the preset, are not touched. Existing entries will be updated and missing ones will be added

====Append====
Entries that are in the programmer but not in the preset will be appended to the preset. Entries that are in the programmer and in the preset, will stay untouched in the preset.

====Substract====
Entries that are in the programmer and also exist in the preset will be removed from the preset. However keep in mind, not the new value is substracted from the old, but the whole property will be removed from the preset.

===Deleteing Presets===

You can delete existing presets by selecting the preset you want to delete and then press Delete or using the context menue -> Delete Preset

===Applying Presets===

You can "drag&drop" a preset into your cue list. A new cue is created. You can set timing and triggers for this cue. The name will stat with "--> ", however you can rename it to what you want. The complete preset will be played back when you use this cue.

===Applying Presets for Selected Fixtures Only===

Select the fixtures you want to apply your preset to. Then doubleclick on the preset you want to use. The entrys will show up in the Programmer window. Keep in mind, if you store this to a cue, not the actual values are stored, but a reference to this preset. So if you change something in you preset, everywhere you used this preset the changed values will be used

===Applying Selected Properties of Presets===

It is also possible to use ''not'' the whole preset, but only a selected property from the preset. Select all fixtures and drag&drop the preset to the property you want use in property grid. In the programmer the values for the property will show up

===Applying Selected Parameters of Presets for Selected Fixtures Only===

You can also apply only a selected property of your preset to selected fixtures only. First select you fixtures then drag&drop the preset to the properties you want to use in the property grid. The value for the selected property for the selected fixtures will show up in the programmer window

===Applying a Preset for Fixtures that are Not in the Preset===

Also you can use a Preset to set a property of a fixture that has no value stored in the preset to a value from the preset. First a short example:
A preset with some RGB Pars set at a color. Later you want that your moving lights change to the same color as your RGB Pars. You can either remember or look up this color.
Actually there is a third possibility, select you fixtures, in this example you moving lights, and move your preset (drag&drop) to the property grid, now hold "Ctrl" key down and drop your preset to the color property of your fixture. The color of your fixture will be set to the last found value of the used property in your preset, i.e. the filtering of devices is switched of by the "Ctrl" key.

===Shortcuts===

Of course there are shortcuts that help to increase save time working with presets. But keep in mind, if you use Shortcuts the programmer filter will not be used.

===Tips===
Tip 1: By activating the "highlight" button the selected preset is shown in the live view.

Tip 2: By applying fanning in a preset you can use it for smaller or larger device groups with amazing effects.

==Excercise==
* Create a preset "yellow" and use it per drag&drop in Stage View
* Use some presets in your cue list

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 14]]

[[de:Lektion 13]]
[[en:Lesson 14]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_12_Tut3
| zurückText = Lektion 12
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_14_Tut3
| vorText = Lektion 14
}}

[[Kategorie:DMXControl 3]]

Lesson 13 Tut3

2013-01-04T22:56:36Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

==Overview==
In this lesson we explain how to apply presets. By re-using presets you are more efficiently when programming your show.

==Lecture 13: Presets ==

Presets are very similar to cues. You can create them in the same way, see [[Lesson 8]]. Similar to the button "Create cue" here you find the button "Create preset". You can use presets to store different values for the parameters of your fixtures. You can store:

* moving light positions
* colors of RGB Pars
* combination of gobo, shutter on and color
* generic chasers (where you later only replace/modify the color)
* or simply intensities of your conventional fixtures
* etc.

The big advantage of using presets is, that it's referenced data. That means, whenever you record a cue using presets, not the actual values, but a link to the preset is stored. So keep in mind, if you change your preset, all cues that use this preset will use the new values. A simple example where presets can rapidly speed up programming would be:
You've recorded a color of your cyc wash as a preset and used this preset in five cues. If you later decide to modify the cyc wash a bit, you just need to update one preset instead of five cues. However if you just want to change the color in one cue you can do that by overwriting the reference with manual data.

[[File:DMXC3L13 Preset.jpg]]

===Recording Presets===

To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See [[Lesson 8]] how to use the programmer filter. After you pressed OK in the programmer filter, a new preset will be recorded. You can now use F2 (or click into name field) to rename it.

===Modifying Presets===

If you want to modify an existing preset, select the preset you want to modify and click on the arrow right of the "Add Preset" button. A menu will pop up, where you can choose how to modify the preset.

====Replace====
Replace will remove all existing entries from the preset and save everything that is in the programmer to the preset.

====Merge====
Entries that are not in the programmer but in the preset, are not touched. Existing entries will be updated and missing ones will be added

====Append====
Entries that are in the programmer but not in the preset will be appended to the preset. Entries that are in the programmer and in the preset, will stay untouched in the preset.

====Substract====
Entries that are in the programmer and also exist in the preset will be removed from the preset. However keep in mind, not the new value is substracted from the old, but the whole property will be removed from the preset.

===Deleteing Presets===

You can delete existing presets by selecting the preset you want to delete and then press Delete or using the context menue -> Delete Preset

===Applying Presets===

You can "drag&drop" a preset into your cue list. A new cue is created. You can set timing and triggers for this cue. The name will stat with "--> ", however you can rename it to what you want. The complete preset will be played back when you use this cue.

===Applying Presets for Selected Fixtures Only===

Select the fixtures you want to apply your preset to. Then doubleclick on the preset you want to use. The entrys will show up in the Programmer window. Keep in mind, if you store this to a cue, not the actual values are stored, but a reference to this preset. So if you change something in you preset, everywhere you used this preset the changed values will be used

===Applying Selected Properties of Presets===

It is also possible to use ''not'' the whole preset, but only a selected property from the preset. Select all fixtures and drag&drop the preset to the property you want use in property grid. In the programmer the values for the property will show up

===Applying Selected Parameters of Presets for Selected Fixtures Only===

You can also apply only a selected property of your preset to selected fixtures only. First select you fixtures then drag&drop the preset to the properties you want to use in the property grid. The value for the selected property for the selected fixtures will show up in the programmer window

===Applying a Preset for Fixtures that are Not in the Preset===

Also you can use a Preset to set a property of a fixture that has no value stored in the preset to a value from the preset. First a short example:
A preset with some RGB Pars set at a color. Later you want that your moving lights change to the same color as your RGB Pars. You can either remember or look up this color.
Actually there is a third possibility, select you fixtures, in this example you moving lights, and move your preset (drag&drop) to the property grid, now hold "Ctrl" key down and drop your preset to the color property of your fixture. The color of your fixture will be set to the last found value of the used property in your preset, i.e. the filtering of devices is switched of by the "Ctrl" key.

===Shortcuts===

Of course there are shortcuts that help to increase save time working with presets. But keep in mind, if you use Shortcuts the programmer filter will not be used.

===Tips===
Tip 1: By activating the "highlight" button the selected preset is shown in the live view.

Tip 2: By applying fanning in a preset you can use it for smaller or larger device groups with amazing effects.

==Excercise==
* Create a preset "yellow" and use it per drag&drop in Stage View
* Use some presets in your cue list

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 14]]

[[de:Lektion 13]]
[[en:Lesson 14]]

__NOTOC__
__NOTITLE__

Lesson 12 Tut3

2013-01-04T22:47:02Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

==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 very effectively and almost EXCEL like copy and customize cues.

==Lecture 12: Editing scenes and scenelists ==

In [[Lesson 8]] we introduced the scene lists. In this lecture more advanced features are explained.

[[Datei:DMXC3L12 SL.JPG]]
{{Bild_mit_Unterschrift |DMXC3L12 SL.JPG|1|Menüleiste des Programmers|center}}

By default a new scene is added to an existing scene list by pressing the button "Add Cue". When you open the small dropdown arrow on right hand side of this button you see some more sophisticated capabilities with their short code. In most cases you have to mark a scene at first before applying this modification.

[[Datei:DMXC3L12 SL storemenue.jpg]]
{{Bild_mit_Unterschrift |DMXC3L12 SL storemenue.jpg|2|Anzeige der Menüeinträge des Dropdownmenüs von Add Cue|center}}

'''Hint:''' The following operations are related to the values in the programmer.

{| 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 ||

|}

In 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 the copy/paste content operations you can take over the value from single fields to other cues.

{{Bild_mit_Unterschrift |DMXC3L12 SL editmenue.jpg|3|Anzeige der Menüeinträge des Dropdownmenüs von Edit|center}}
[[Datei:DMXC3L12 SL editmenue.jpg]]

Again, here is the summarizing table for explanation:

{| 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 || || Selekted 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

|}

{{Bild_mit_Unterschrift |DMXC3L12 SL optionmenue.jpg|4|Anzeige der Menüeinträge des Dropdownmenüs von Options|center}}
[[Datei:DMXC3L12 SL optionmenue.jpg]]

{| class="wikitable"
|-
! Funktion !! Beschreibung !! Kommentar
|-
| Tracking || If Tracking is active a value remains until it is overwritten by another cue (or the cue list is finished). If tracking is disabled, only the values are output that is stored 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 || With a jump back in the Cue List, the times of the cues are used for the crossfade. ||
|-
| Use Cue Time as GoTo Time || With 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. ||
|-
|}

==Excercise==
* Test the append and subtract cue functions

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 13]]

[[de:Lektion 12]]
[[en:Lesson 12]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_11_Tut3
| zurückText = Lektion 11
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_13_Tut3
| vorText = Lektion 13
}}

[[Kategorie:DMXControl 3]]

Lesson 11 Tut3

2013-01-04T22:21:07Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

{{NavigationTop-Tut3
| zurückLink = Lektion_10_Tut3
| zurückText = Lektion 10
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_12_Tut3
| vorText = Lektion 12
}}

==Overview==
Cue lists are the best means to control your show. In this lesson we explain how to define the sequence and the flow of scenes by triggers.

==Lecture 11: Trigger in cue lists ==

In previous lesson we learnt how to create cues and scene lists. Now we are familar with most of the attributes of scene list, but some more explanation about the trigger is nessecary. The default trigger is "follow", i.e. the next cue will be started after the previous one is faded-in.

'''Important:''' When you change the trigger type, you need to apply the changes with Enter.

But there are some other types of triggers, the following table informs you about its behaviour.

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (opt) 3 || use GO to fade in next cue
optional: fade in cue after 3 GO presses, default is 1
|-
| follow || 5s || wait until the previous cue is faded in, then the countdown is started
|-
| wait || 5s || wait time countdown starts when wait or follow of previous cue is completed
|-
| timecode || 00:26:05 || expects external timecode information
|-
| rtc || 13:00:00 || real time clock, fade in a cue at a specified time
|-
| beat || (opt) 3 || connect in Input Layer panel the "manual beat" output per Drag & Drop with "Beat" input of scene list
optional: fade in cue after 3 beats, default is 1
|}

In case you type a wrong format into the '''trigger value''' field you will get some hints about the expected input syntax. See the example for the "follow" type.

{{BoxHint
|Text= Type in combined time information without "blank" character, e.g. 1m20s
}}

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the timecode selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

Currently the time code from Digital Enlightenment Mediacenter [http://www.digital-enlightenment.de/mediacenter.htm] is supported only. Support of other time codes will follow.

===Use of beat trigger===

If you want to keep off your scenes beat controled, you need to select the trigger '''beat''' .
{{BoxHinweis|Text
In the Trigger field value is specified after how many Beat signals the next cue is called
}}

{{Bild_mit_Unterschrift |Beattrigger.PNG|4|Beispiel für Beattrigger|center}}

Now you should inform the '''Cue List''' what is the source of Beat Signal (Manual Beat/Audioanalyzer....)
Therefore you have to make an assignment [[Lektion_22_Tut3|'''Input Assignment''']] , where you must drag an item per Drag&Drop to the beat entry of the cue list.

{{Bild_mit_Unterschrift |DMXC3_L11_InputassignmentBeat.png|5|Input Assignment|center}}

==Summary==

Following figure shows the dependency and capability of mixing several trigger types:

[[File:DMXC3L11 SlideDMXC3Trigger.jpg|600px]]

* Each cue has its delay-time (before the fade in start) - delay1 to delay4
* Cue2 has a follow-trigger of 1s, it starts 1s after the fade in the previous cue is completed
* Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the follow the previous scene has expired
* Cue4 also has a wait-trigger (1s). So it will wait for 1s after the wait (0s) of the previous scene has expired.

==Excercise==
* Test a mix of "follow" and "wait" triggers in one scene list
* Use a tool providing timecodes (DE MediaCenter) and test a scenelist that is completely based on timecodes

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 12]]

[[de:Lektion 11]]
[[en:Lesson 11]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_10_Tut3
| zurückText = Lektion 10
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_12_Tut3
| vorText = Lektion 12
}}

[[Kategorie:DMXControl 3]]

File:DMXC3 L11 InputassignmentBeat.png

2013-01-04T22:14:01Z

Frank Burghardt:

File:DMXC3L11 Beattrigger.PNG

2013-01-04T22:13:24Z

Frank Burghardt:

Lesson 10 Tut3

2013-01-04T21:44:22Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_9_Tut3
| zurückText = Lektion 9
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_11_Tut3
| vorText = Lektion 11
}}

==Overview==
Here we explain the "programmer view" - a tool that helps to "debug" your show programming.

==Lecture 10: The programmer view ==

The programmer is a helpful tool during programming your show. It logs all modifications you have made and shows the current content of the "cue buffer".

{{BoxHint
| Text= Remember the "save scene" dialog in DMXControl 2. Here you were requested to determine the channels and values before finally saving the cue. The programmer ist a more extended view of this functionality.
}}

Let's illustrate this by an example. We make following actions:

* at first we open the moving lights shutters and select the color green

* secondly, the gobos are set for all devices on "Gobo2"
* thirddly, we set the group of front lights to 50% brightness

[[File:DMXC3L10 liveviewProgrammer.JPG|center]]
{{Bild_mit_Unterschrift |DMXC3L10 liveviewProgrammer.JPG|1|Ansicht des Stage View|center}}

The result is exactly shown in the programmer. Please be aware the the cue is not saved at this point of time, because further modification could follow.

[[File:DMXC3L10 Programmer.JPG|center|600px]]
{{Bild_mit_Unterschrift |DMXC3L10 Programmer.JPG|2|Alle Änderungen der Gerätewerte werden im Programmer angezeigt|center|800px}}

In case you change your mindset on the current cue, you can press the '''Clear''' button in order to remove all settings und refresh the programmer.

Now you have in the programmer close eye on what values would be stored in the cue. Therefore you are also in the "Programmer filter" that appears before saving the cue, select the desired values. The following example shows the generic dimmers are not yet saved (because we decide they perhaps want to be controled in a separate cue).

{{Bild_mit_Unterschrift |DMXC3L10 ProgrammerFilter.JPG|3|Ansicht des Programmer Filters|center}}

If your cue is OK, then assign it to a cue list or an executor by "Add new cue" button - a clear the programmer too (to provide "space" for the next cue).

To program more quickly, there is the snapshot function. With it you can cache the latest entries of the programmer and later reload with the drop-down menu in which Load Snapshot is shown. This helps you to program many similar cues with lowest effort.

[[File:DMXC3L10 Programmer.JPG|600px]]

Besides, you can also create a filter with '''Set filter''' or delete filters with '''Clear Filter'''. This function is mainly used in output mode. By this tool you can adjust the values of the programmer that are actually spent. If '''All''' is active, all the values in the programmer are sent, at '''Filtered''' only the values that have been activated in the filter. With '''blind''' no values are issued.

[[File:DMXC3L10 ProgrammerFilter.JPG]]

==Excercise==
* Repeat the above scenario

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 11]]

[[de:Lektion 10]]
[[en:Lesson 10]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_9_Tut3
| zurückText = Lektion 9
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_11_Tut3
| vorText = Lektion 11
}}

[[Kategorie:DMXControl 3]]

Lesson 9 Tut3

2013-01-04T21:25:29Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_8_Tut3
| zurückText = Lektion 8
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_10_Tut3
| vorText = Lektion 10
}}

==Overview==
The previous lession introduced into 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 in that way that dynamic effects can be included and that you can apply certain algorithms for the attributes (DMX values) of included devices resp. groups. This allows you to create highly complex cues with few mouse clicks. Don't believe it? Let's demonstrate how it works!

===Fanning===

The first mechanism is fanning. Just as you can pull up a fan and created a colorful beautiful picture, you can create with Fanning beautiful color palettes or beam radiation.

Fanning means from technical point of view to split a value oder domain to a group of devices. We distinguish between linear and alternate fanning, see 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; there 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.

[[File:DMXC3L09 Fanning pink.JPG]]

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:

[[File:DMXC3L09 Fanning pink programmer.JPG]]

Let's make another excercise with alternate fanning. The task is switching on each second lamp (i.e. setting dimmer to 100%).

[[File:DMXC3L09 Fanning alternate.JPG]]

There is a simple solution: Insert "0#100" into the dimmer value text field.

[[File:DMXC3L09 Fanning alternate programmer.JPG]]

=== 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 goes with DMXControl 3 also completely fixed, or did you expect something else? ;)

Let's have an example: You want to have a blinking effects with all front light lamps.

In "Effects and filters" panel (accessed via Windows> Effects and Filters) some super effects are offered, by which a dynamic change within the cues can be produced, such as "sine", "trapezoid", "Sawtooth". Using drag and drop you can easily e.g. the sine effect put to the dimmer in the Property Grid.
Already, this attribute behaves as it is expected by the symbol or name of the effect. You can then change specific effect parameters in the property grid for example, to affect the amplitude or frequency of the effect.

Following settings are nessecary (the amplitude will vary between 30 and 100 %):

[[Image:DMXC3L09 Fanning with Sinus effect.JPG]]

Try it! You'll love it! 

Tip: Use the chaser effect to implement running lightswithin our RGB pars:
*select the RGB group
*drag the chaser effect to the dimmer in Property Grid

{{BoxHinweis
| Text= '''Effects (attachables) will be summed to the values that are manually adjusted. (If the device has a dimmer of 30% adjusted und you add a sinus with amplitude of 20%, the brightness minimum value will be 30%, the maximum value 50%) 
}}

Hint: Press the '''Del''' key (ot delete symbol) in Property Grid to remove the effect from the attribute.

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribut
! Example
! Description
|-
| Amplitude
| 50 > 100
| value interval for selected attribute; can be set to negative value too
|-
| 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"
|-
! Anwendungsfall
! Veranschaulichung
! Amplitude
|-
|Jump Effect: Dimmer should slowly fade to 0 and will jump to full value
|drag "Sawtooth" to dimmer property
| -100
|-
|running light: one changing element of groups has 100% dimmer
|drag "Chaser" to dimmer property
| 100
|-
|Gobo change: Changing of Gobos
|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
|-
|8-ter Figur: 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 dimm in harmonic way to 100% and back to 0
|drag "Sinus" to dimmer property
| 100
|-
|color change: Lamps changes sequently to all possible colors
|drag "Sawtooth" to color property
| 100
|-
|}

==Excercise==
* Try to apply fanning to pan/tilt of your moving lights. That rocks! ;)
* Implement a running light with chaser effect

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 10]]

[[de:Lektion 9]]
[[en:Lesson 9]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_8_Tut3
| zurückText = Lektion 8
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_10_Tut3
| vorText = Lektion 10
}}

[[Kategorie:DMXControl 3]]

Lesson 9 Tut3

2013-01-04T20:57:33Z

Frank Burghardt:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}

{{DMXC3_lesson/en}}

==Overview==
The previous lession introduced into 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 in that way that dynamic effects can be included and that you can apply certain algorithms for the attributes (DMX values) of included devices resp. groups. This allows you to create highly complex cues with few mouse clicks. Don't believe it? Let's demonstrate how it works!

===Fanning===

The first mechanism is fanning. Just as you can pull up a fan and created a colorful beautiful picture, you can create with Fanning beautiful color palettes or beam radiation.

Fanning means from technical point of view to split a value oder domain to a group of devices. We distinguish between linear and alternate fanning, see 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; there 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.

[[File:DMXC3L09 Fanning pink.JPG]]

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:

[[File:DMXC3L09 Fanning pink programmer.JPG]]

Let's make another excercise with alternate fanning. The task is switching on each second lamp (i.e. setting dimmer to 100%).

[[File:DMXC3L09 Fanning alternate.JPG]]

There is a simple solution: Insert "0#100" into the dimmer value text field.

[[File:DMXC3L09 Fanning alternate programmer.JPG]]

=== 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 goes with DMXControl 3 also completely fixed, or did you expect something else? ;)

Let's have an example: You want to have a blinking effects with all front light lamps.

In "Effects and filters" panel (accessed via Windows> Effects and Filters) some super effects are offered, which can also be a dynamic change within the cues are produced, such as "sine", "trapezoid", "Sawtooth"
Here we will use the "effects and filters" pannel showing some effects such as "Sinus", Trapezoid", "Sawtooth" etc. Per drag&drop we can load the Sinus effect to the dimmer attribute within property grid.

Following settings are nessecary (the amplitude will vary between 30 and 100 %):

[[Image:DMXC3L09 Fanning with Sinus effect.JPG]]

Try it!

'''Remember: '''Effects (attachables) will be summed to the values that are manually adjusted. (If the device has a dimmer of 30% adjusted und you add a sinus with amplitude of 20%, the brightness minimum value will be 30%, the maximum value 50%) 

Hint: Press the '''Del''' key to remove the effect from the attribute.

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribut
! Example
! Description
|-
| Amplitude
| 50 > 100
| value interval for selected attribute; can be set to negative value too
|-
| Offset
| [0..100]
| offset between group elements
|-
| Phase
| [0..1]
|  ?
|-
| Frequency
| [0..1]
|  cycle speed 
|}

 '''Tipp''': 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
! Visual effect description
! Amplitude
! Offset
! Phase
! Frequency
|-
|Jump Effect: Dimmer should slowly fade to 0 and will jump to full value
|set dimmer to 100, drag sawtooth effect to dimmer attribute
| -100
|
|
|
|-
|}

'''to be added (by beta testers)'''

* add some additional use cases

==Excercise==
* Try to apply fanning to pan/tilt of your moving lights. That rocks! ;)
*

==Additional links and references==
*

==Certificate==
I have understood the topics of this lecture and want to continue with next course:
[[Lesson 10]]

[[de:Lektion 9]]
[[en:Lesson 9]]

__NOTOC__
__NOTITLE__

Lesson 1 Tut3

2013-01-04T20:07:56Z

Frank Burghardt: Nicht vergessen: Die engl. Version ist eigentlich die Masterversion!

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = Erste Schritte: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lesson_2_Tut3
| vorText = Lesson 2
}}

{{DMXC3_lesson/en}}

==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:

{{Bild_mit_Unterschrift |DMXC3 Overview.jpg|1|A selection of some windows of DMXControl 3|center|600px}}

[[File:DMXC3 Overview.jpg]]

This lecture introduces into 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, as known in the installation of DMXControl 2, EasyView (a visualizer) can be selected.

{{BoxAttention
|Text=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!
}}

DMXControl 3.0 consists out of two softwares. One acts as server, the other one as client. The server (hereinafter referred to as kernel) manages all information related to the project. The kernel runs basically on Windows operating system, but can also be launched on Linux (with Mono). The client acts as an interface between the server and the user.

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" (hint: in the beta version you have to start the kernel as administrator when you used the standard installation).
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.

[[File:DMXC3L01 kernel.JPG|600px]]

During the startup 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. By typing "help" you get an overview about all supported commands.

[[File:DMXC3L01 konsole.JPG|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 subfolder "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.

[[File:DMXC3L01 connect.JPG]]

If you have installed a firewall you have to grant the communication between client and server.

[[File:700px-DMXC3 Tutorial Lektion1 Firewall.png|600px]]

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.

{{BoxHint
|Text=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 startmenue 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.
.

==Excercise==

1) Please try following commands in command shell:
* menue
* 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)

==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)

==Certificate==
I understood the topics of this lecture and want to continue with next course:
[[Lesson 2]]

{{NavigationTop-Tut3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lesson_2_Tut3
| vorText = Lesson 2
}}

[[Kategorie: DMXControl 3]]

[[de:Lektion 1]]
[[en:Lesson 1]]

__NOTOC__
__NOTITLE__

File:DMXC2 Manual Box Reference.png

2013-01-03T09:08:28Z

Frank Burghardt:

File:DMXC2 Manual Box Important.png

2013-01-03T09:08:10Z

Frank Burghardt:

File:DMXC2 Manual Box Hint.png

2013-01-03T09:07:53Z

Frank Burghardt: