English DMXC-Wiki - User contributions [en]

Lesson 12 Tut3

2013-01-28T19:38:17Z

Vrystyle: corr

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}
==Overview==
In this lesson we explain advanced edit features for scenes and scene lists, e.g. for modification of already saved scenes.
So you can copy and customize cues very effectively and almost EXCEL like.

==Lecture 12: Editing scenes and scenelists ==

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

{{Picture_with_subtitle |DMXC3L12_SL.JPG|1|Menu of the Programmer|center}}

By default a new scene is added to an existing scene list by pressing the button "Add Cue". When you open the small 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.

{{Picture_with_subtitle |DMXC3L12_SL_storemenue.jpg|2|View of the dropdownmenu of "Add Cue"|center}}

{{BoxHint
|Text= 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 a similar way, there are also edit operations for the scene list itself. As known from EXCEL you can copy, cut and delete whole rows. With copy and paste you can take single values from one field or a cue to another field of other cues.

{{Picture_with_subtitle |DMXC3L12_SL_editmenue.jpg|3|View of dropdownmenu of "Edit"|center}}

Here is the summarizing table for explanation again:

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Edit in Programmer || || Selected cue is loaded into '''Programmer'''. '''Programmer Output Mode''' is set to '''All''' ||
|-
| Edit in Programmer Blind || || Selected cue is loaded into '''Programmer'''. '''Programmer Output Mode''' is set to '''Blind''' ||
|-
| Cut || 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

|}

{{Picture_with_subtitle |DMXC3L12_SL_optionmenue.jpg|4|View of dropdownmenu of "Options"|center}}

{| class="wikitable"
|-
! Function !! Description !! Comment
|-
| Tracking || If tracking is active a value remains active until it is overwritten by another cue (or the cue list is finished). If tracking is disabled, only the stored values are active on output that are in the current cue. All others are faded out. ||
|-
| Reset when Released || '''Cue List''' jumps to first entry, after last cue was executed ||
|-
| Use Cue Time as Back Time || After a jump back in the '''Cue List''', the times of the cues are used for the crossfade. ||
|-
| Use Cue Time as GoTo Time || After a jump forward in the '''Cue List''', the times of the cues are used for the crossfade. ||
|-
| Autoprepare || DMXControl prepares headlights already automatically on the mission (color and gobo is selected in advance etc.). That way you will not need to worry about it. On active '''Autoprepare''' you can deactivate this function for single cues with the checkbox '''Ap'''. ||
|-
|}

==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_Tut3]]
[[en:Lesson_12_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}

[[category:DMXControl 3]]

ToC Manual DMXC3

2013-01-23T07:43:24Z

Vrystyle: /* Proposal for further discussion */

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

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

Lesson 11 Tut3

2013-01-22T11:17:27Z

Vrystyle: /* Use of beat trigger */ minor fixes

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}
==Overview==
Cue lists are the best tool to control the flow of your show. In this lesson we explain how to define the sequence and the change of scenes by triggers.

==Lecture 11: Trigger in cue lists ==

In previous lessons we learnt how to create cues and scene lists. Now we are familar with most of the attributes of the scene list but some more explanation about the trigger is nessecary. The default trigger is "follow". That means 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 the enter-key or by clicking in another field.

Besides of '''follow''' there are some other types of triggers. The following table informs you about their behaviours.

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (optional) 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 || (optional) 3 || you have to do some more settings, see next paragraph below!
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" characters, e.g. 1m20s
}}

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the realtimecode selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

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

===Use of beat trigger===

If you want to have your scenes beat controled, you need to select the trigger '''beat''' .
{{BoxHint|Text=In the '''Trigger''' field you can specify after how many beat signals the next cue is called
}}

{{Picture_with_subtitle |Beattrigger.PNG|4|Example for beattrigger|center}}

Now you have to inform the '''Cue List''' which source of the beat signal should be used (manual beat/audioanalyzer....)
Therefore you have to assign an input in the [[Lesson_22_Tut3|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).

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

==Summary==

The following figure shows the dependencys and capabilitys of mixing several trigger types:

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

* Each cue has its delay-time (before the fade-in start) - delay1 to delay3
* Cue2 has a follow-trigger of 1s. It starts 1s after the fade-in of the previous cue is completed
* Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the follow of 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_Tut3]]
[[en:Lesson_11_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}

[[category:DMXControl 3]]

Lesson 10 Tut3

2013-01-22T11:13:29Z

Vrystyle: minor fixes

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_9_Tut3
| TextBackwards = Lesson 9
| LinkForwards = Lesson_11_Tut3
| TextForwards = Lesson 11
}}
==Overview==
Here we explain the "'''Programmer'''" view - a tool that helps in programming and "debuging" your show.

==Lecture 10: The programmer view ==

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

{{BoxHint
| Text= Remember the "save scene" dialog in DMXControl 2. On that step you have been asked to define the channels and values before finally saving the cue. The '''Programmer''' is a more extended view of this functionality.
}}

Let's illustrate this by an example. Perform the following steps:

* at first we open the moving lights shutters and select the color green
* second, set the gobos of all devices on "Gobo2"
* third, we set the group of front lights to 50% brightness

{{Bild_mit_Unterschrift |DMXC3L10 liveviewProgrammer.JPG|1|Stage View|center}}

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

{{Bild_mit_Unterschrift |DMXC3L10 Programmer.JPG|2|All changes of the device settings are shown in the programmer|center|800px}}

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

Now you can see in the '''Programmer''' which values would be stored in the cue. When we save the cue you are able to select the desired items in the '''Programmer Filter''' that appears before. In the following example we do not save the "Generic Dimmer" (by deselecting them) because we probably want to save them in another cuelist.

{{Bild_mit_Unterschrift |DMXC3L10 ProgrammerFilter.JPG|3|View of the Programmer Filter|center}}

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

In order to program quicker, there is the snapshot function. With the button '''Write Snapshot''' you can cache the current selctions in the programmer and reload them later by using the drop-down menu ('''Load Snapshots'''). This helps you to program many similar cues with lowest effort.

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

In addition to that you can also create a filter with '''Set Filter''' or delete filters with '''Clear Filter'''. This function is mainly used in '''Output Mode'''. With this tool you can adjust the values of the programmer that are actually sent out. If '''All''' is active, all the values in the programmer are sent, with '''Filtered''' only the values that have been activated in the filter and with '''Blind''' no values are sent out.

[[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_Tut3]]
[[en:Lesson_10_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_9_Tut3
| TextBackwards = Lesson 9
| LinkForwards = Lesson_11_Tut3
| TextForwards = Lesson 11
}}

[[category:DMXControl 3]]

Lesson 8 Tut3

2013-01-22T11:11:53Z

Vrystyle: minor fixes part2

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_7_Tut3
| TextBackwards = Lesson 7
| LinkForwards = Lesson_9_Tut3
| TextForwards = Lesson 9
}}
==Overview==
Scenes (cues) are the most important elements of your show. Here we will explain the powerful scene concept of DMXControl 3. The terms "cue" and "scene" are used as synonym words.

==Lecture 8: Scenes (cues) and scene lists ==

Now the real work begins - we will create our first cue in DMXControl 3! All RGB lights will shine green.

* We go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* The intensity of the dimmer panel is pulled or press the "Lumos" button
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)

{{Picture_with_subtitle |DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}

* On the left click on "Add new cue"
* It opens a new window called "Programmer filter" which we will explain in Chapter 10. For now press OK.
[[File:DMXC3L08 programmerFilter.JPG]]

* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* Here we rename the cue in the ''Name'' field to "My First Cue".

{{Picture_with_subtitle |DMXC3L08 firstCue02.JPG|2|View of the programmer window|center}}

Each scene (cue) needs a "host container" - that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".

[[File:DMXC3L08_createSceneListnew.JPG|600px]]

You can open this new cue list with a '''double click''' on the object in the project explorer or using the context menu item "open" (or double click).
In the tabular list you can adjust the individual parameters of the cue.

[[File:DMXC3L08 changeLiveView.JPG]]
{{BoxHint
|Text =The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is and wich target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.}}

The life cycle of a cue is as following:
{{Picture_with_subtitle |DMXC3L08 SlideDMXC3cue.jpg|3|Lifecycle of cues in DMXControl 3|center|700px}}

A cue waits at first for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).

Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduceded compared to the previous cue.

Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.

[[File:DMXC3L08 FirstScene.JPG]]

{{BoxAttention
|Text = You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
}}
{{Bild_mit_Unterschrift |Clear_programmer.jpg|4|Clearing the programmer|center}}

In following table we explain the meaning of cue attributes (which you can see in the scene list header):

{| class="wikitable"
! Attribute
! Description
! Example
|-
| Progress
| shows the status of the scene during execution of scene list (wait time and progress)
| in percent
|-
| Trigger
| relation to predecessor cue, use "follow" as default
| see Lesson 11
|-
| Trigger Value
|
| see Lesson 11
|-
| Name
| free name of scene
| should explain the content of cue
|-
| Fade
| fade-in value
| in milli seconds [ms]
|-
| Delay
| fanning for fades
| see Lesson 9
|-
| Ac (active)
| is this cue active or should it be ignored?
| default: active
|-
| Ap (autoprepare)
| Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue)
| default: active
|-
| Re (ReExecute)
| If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the ''actual'' value to the destination value.
| Example: 
Cue 39 Fade 0s: 1 + 2 at full 
Cue 40 Fade 500s: 1 at 0 
Cue 41 Fade 10s: 2 at 0 
(Cue 41 should be a blackout) 
Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds. 
Now someone on stage forgets his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left). 
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in the residual 60s 
If '''Re''' is active for cue 41 the 1 immedately goes down from the ''actual value at this time'' to 0 in 10s together with device 2.
|-
| Comment
| for free use, insert explaining words
|
|-
|}

In the same way you can create some more cues and store it in the scene list.
{{Bild_mit_Unterschrift |DMXC3L08 SecondScene.JPG|5|Cuelist with some cues|center}}

===Playing back cues===
Go, Back, etc.

However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.

===Using advanced timing (=> Property Based Timing)===
It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color and after that change the gobo.

In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in milliseconds. Also you can use fanned values here. See Lesson 9.

The following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.

[[File:Dmxc3 advanced timing value.jpg]]  
[[File:Dmxc3 advanced timing fade.jpg]]

[[File:Dmxc3 advanced timing delay.jpg]]

===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.

==Excercise==
* Generate your own cues
* Try the buttons "STOP", "GO" and "Mode" in the cue list
* Work with different fade times

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

[[de:Lektion_8_Tut3]]
[[en:Lesson_8_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_7_Tut3
| TextBackwards = Lesson 7
| LinkForwards = Lesson_9_Tut3
| TextForwards = Lesson 9
}}

[[category:DMXControl 3]]

Lesson 8 Tut3

2013-01-22T11:10:32Z

Vrystyle: minor fixes

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_7_Tut3
| TextBackwards = Lesson 7
| LinkForwards = Lesson_9_Tut3
| TextForwards = Lesson 9
}}
==Overview==
Scenes (cues) are the most important elements of your show. Here we will explain the powerful scene concept of DMXControl 3. The terms "cue" and "scene" are used as synonym words.

==Lecture 8: Scenes (cues) and scene lists ==

Now the real work begins - we will create our first cue in DMXControl 3! All RGB lights will shine green.

* We go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* The intensity of the dimmer panel is pulled or press the "Lumos" button
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)

{{Picture_with_subtitle |DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}

* On the left click on "Add new cue"
* It opens a new window called "Programmer filter" which we will explain in Chapter 10. For now press OK.
[[File:DMXC3L08 programmerFilter.JPG]]

* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* Here we rename the cue in the ''Name'' field to "My First Cue".

{{Picture_with_subtitle |DMXC3L08 firstCue02.JPG|2|View of the programmer window|center}}

Each scene (cue) needs a "host container" - that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".

[[File:DMXC3L08_createSceneListnew.JPG|600px]]

You can open this new cue list with a '''double click''' on the object in the project explorer or using the context menu item "open" (or double click).
In the tabular list you can adjust the individual parameters of the cue.

[[File:DMXC3L08 changeLiveView.JPG]]
{{BoxHint
|Text =The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is and wich target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.}}

The life cycle of a cue is as following:
{{Picture_with_subtitle |DMXC3L08 SlideDMXC3cue.jpg|3|Lifecycle of cues in DMXControl 3|center|700px}}

A cue waits at first for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).

Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduceded compared to the previous cue.

Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.

[[File:DMXC3L08 FirstScene.JPG]]

{{BoxAttention
|Text = You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
}}
{{Bild_mit_Unterschrift |Clear_programmer.jpg|4|Clearing the programmer|center}}
[[File:Clear_programmer.jpg]]

In following table we explain the meaning of cue attributes (which you can see in the scene list header):

{| class="wikitable"
! Attribute
! Description
! Example
|-
| Progress
| shows the status of the scene during execution of scene list (wait time and progress)
| in percent
|-
| Trigger
| relation to predecessor cue, use "follow" as default
| see Lesson 11
|-
| Trigger Value
|
| see Lesson 11
|-
| Name
| free name of scene
| should explain the content of cue
|-
| Fade
| fade-in value
| in milli seconds [ms]
|-
| Delay
| fanning for fades
| see Lesson 9
|-
| Ac (active)
| is this cue active or should it be ignored?
| default: active
|-
| Ap (autoprepare)
| Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue)
| default: active
|-
| Re (ReExecute)
| If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the ''actual'' value to the destination value.
| Example: 
Cue 39 Fade 0s: 1 + 2 at full 
Cue 40 Fade 500s: 1 at 0 
Cue 41 Fade 10s: 2 at 0 
(Cue 41 should be a blackout) 
Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds. 
Now someone on stage forgets his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left). 
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in the residual 60s 
If '''Re''' is active for cue 41 the 1 immedately goes down from the ''actual value at this time'' to 0 in 10s together with device 2.
|-
| Comment
| for free use, insert explaining words
|
|-
|}

In the same way you can create some more cues and store it in the scene list.
{{Bild_mit_Unterschrift |DMXC3L08 SecondScene.JPG|5|Cuelist with some cues|center}}
[[File:DMXC3L08 SecondScene.JPG]]

===Playing back cues===
Go, Back, etc.

However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.

===Using advanced timing (=> Property Based Timing)===
It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color and after that change the gobo.

In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in milliseconds. Also you can use fanned values here. See Lesson 9.

The following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.

[[File:Dmxc3 advanced timing value.jpg]]  
[[File:Dmxc3 advanced timing fade.jpg]]

[[File:Dmxc3 advanced timing delay.jpg]]

===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.

==Excercise==
* Generate your own cues
* Try the buttons "STOP", "GO" and "Mode" in the cue list
* Work with different fade times

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

[[de:Lektion_8_Tut3]]
[[en:Lesson_8_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_7_Tut3
| TextBackwards = Lesson 7
| LinkForwards = Lesson_9_Tut3
| TextForwards = Lesson 9
}}

[[category:DMXControl 3]]

Lesson 7 Tut3

2013-01-22T11:06:39Z

Vrystyle: minor fixes

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_6_Tut3
| TextBackwards = Lesson 6
| LinkForwards = Lesson_8_Tut3
| TextForwards = Lesson 8
}}
==Overview==
In this lesson a final overview about the basic concepts for setting up the DMXControl 3 software is given. This completes the first part of the lectures "Basics, Setup and configuration".

==Lecture 7: Summary and details of setup ==

Now we will finalise our first expedition through DMXControl by investigating other generic features.

DMXControl 3 is very focused on working with groups of devices. These groups can be defined in a very effective and flexible way. Due to the strong abstraction of device properties you can also combine different types of devices in groups (to programm them later uniformly). Also adding devices to a group later is no problem.

The management of all elements is centralized in the '''Project Explorer'''. Here you keep control over your devices, groups, views, cue lists, and so on.
The new panel concept requires some practice, but you'll love it if you mastered it. So you can adjust the DMXControl 3 completely according to your needs!

There are lots of additional buttons in the main menu for operational support:
* File
** Here you can create, open and save projects
** With "project properties" you can assign some notices to the current project
* Windows
** Beside some tools that will be explained later on, here you find a chat tool. It is helpful if several operators and programmers work in parallel with DMXControl 3. They can exchange some messages here.
** The "manual beat tool" can be compared to the corresponding tool in DMXControl 2. By pressing the space key you can generate manual beats
* Settings
** '''Application settings''': Double click the icons in order to set configuration options.
** Here we refer to the affinity feature: DMXControl is trying to calculate similarities of gobos. If you have two moving lights with different gobos and for example you select in the (mixed) property grid a "starry sky" gobo, it tries automatically to take the most similar gobo on each device.
With the option '''Affinity View''' you can manually adjust the "similarities" to your subjective view.
{{Bild_mit_Unterschrift |DMXC3L07 AffinityView.JPG|1|View of AffinityView-Tool|center}}

If you choose a gobo on the left side, you will logically find the same logo in the first place on the righ side. If this does not exist on your device, it will automatically take the next one in the list and so on. With the up and down arrows you can manually change the order.

On left hand side of your screen you have some global icons. Here we want to refer to
* Fog
** Here you have several operation modes for your DMX-controled fog device
* Highlight
** Rapid activation and deactivation of a device by simply clicking on it. Particularly suitable for setting up your stage.
* Blackout
** As the name indicates: Blackout of all devices

The project explorer also contains some general buttons:
* Edit
* Create directory / create device group
* Up / Down
* Device Manager
* Add item list / add Live view
* Import / export files
This is for administative operations in your device configuration.
[[File:DMXC3L07 ProjectExplorerMenues.JPG]]

[[File:DMXC3L07 menuelist.JPG|600px]]

One helpful tool is missing for basic checks and setting up of DMX channels: the channel overview (Windows -> channel overview). Here you get an overview about the current output. With the slider on left hand side you can also modify the value of the selected channel.

[[File:DMXC3L07 channelOverview.JPG|600px]]

{{BoxHint
|Text =Please be aware that the '''Channel Overview''' is not finally ready and still is under construction.}}

==Excercise==
* Set channel 34 to DMX value 128 with help of channel overview
* Try the Highlight and Blackout mode (observe results in Stage view panel)
*

==Certificate==
Great! You have now completed the first part of the DMXControl lecture!

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

[[de:Lektion_7_Tut3]]
[[en:Lesson_7_Tut3]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| LinkBackwards = Lesson_6_Tut3
| TextBackwards = Lesson 6
| LinkForwards = Lesson_8_Tut3
| TextForwards = Lesson 8
}}

[[category:DMXControl 3]]

Lesson 6 Tut3

2013-01-22T11:04:30Z

Vrystyle: /* Lecture 6: Configuring the output plugins */ fixed images

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_5_Tut3
| TextBackwards = Lesson 5
| LinkForwards = Lesson_7_Tut3
| TextForwards = Lesson 7
}}
==Overview==
In order to control your lamps you need to send out "real" DMX signals to your universes. In this lesson we explain how to configure your output devices.

==Lecture 6: Configuring the output plugins ==

In the menue "settings" you can find the panel '''DMX interfaces'''. There you can select your DMX transmitter/sender by choosing it in the new window that appears when pressing button '''Add interfaces'''.

{{Picture_with_subtitle |DMXC3L06_AddInterface.JPG|1|Adding of Interfaces|center}}

{{BoxHint|Text = In the current beta version only a subset of DMX Interfaces is supported (compared to DMXControl 2). But this is no blocking point for testing the software, if you are an owner of a different interface. On one hand the software also works without DMX-Interface, on the other hand you can use the Artnet-Interface to connect to a light control software supporting your interface, e.g. DMXControl 2.12. See [[Lesson_24_Tut3|Lesson 24]].
}}

[[File:DMXC3L06_DE_IF_plugin.JPG]]

Then, the interface has to be configured on "Advanced Interface Settings". Here you can make fine tuning and set the configuration settings that are supported by your DMX transmitter. In the shown case you can modify e.g. the break time if the DMX receiver in one of your lamps requires a higher value. In "Set Interface Mode" you can choose a mode that corresponds to your application.
In Figure 2, the mode is still set to '''0 - Standby'''. In order that the DE or fx5 interface outputs something, you can select Mode '''2 - PC Out -> select DMX Out'''.

{{Picture_with_subtitle |DMXC3L06_DE_IF_plugin_settings.JPG|2|View of the advanced settings of the DE- or fx5-Interfaces|center}}

Interfaces that support more than one DMX universe (such as the visualization tool 3D Easy View), obtain a line in the table for each DMX Universe. Therefore e.g. 3D EasyView gets four lines.

The field '''Port''' indicates the corresponding input or output of the interface. In the columns '''DMX Out Address''' and '''DMX-In Address''' you can assign a a port to a DMX Universe by a double click.

The entry must be constructed in accordance with the scheme:
Universe.DMX start channel

DMXControl 3 supports 16 DMX universes (Universe Universe 1 to 16) with each 512 channels (channel 1 to channel 512).

If it is intended that the DE or fx5 interface for example has to send all channel values from channel 83-512 in Universe 4 and DMXControl should use received DMX values via DMX in on Universe 6, you have to enter '''4.83''' within the appropriate field '''DMX-out address''' and '''6.1''' in '''DMX-In Address'''.

On some interfaces (such as the Nicolaudie SIUDI) a port can only act either as a DMX-in or as DMX out. In this case, check boxes that appear in columns '''DMX-Out Enabled''' and '''DMX-In Enabled''', to adjust the respective wanted behavior.
{{BoxHint
|Text=There are DMX devices that have problems with the timing. These devices respond completely wrong or only partially to transmitted DMX values. A change in the values "Break Time" may remedy the situation. Just try it. You can adjust these values also under "Advanced Interface Settings".
}}

==Excercise==
* Activate and configure your DMX transmitter
* Configure an ArtNet Interface ("Artistic Licence")
* Set the Output-Universe of Port2 of ArtNet-Interfaces to channel 65 of third universe
* What happens by inserting '''2.513''' or '''17.1'''?

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

[[de:Lektion 6]]
[[en:Lesson 6]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_5_Tut3
| TextBackwards = Lesson 5
| LinkForwards = Lesson_7_Tut3
| TextForwards = Lesson 7
}}

[[category:DMXControl 3]]

Template:Bild mit Unterschrift zu loeschen

2013-01-22T10:55:39Z

Vrystyle: Fixed error from "Datei:" to "File:"

{{#switch: {{{4}}}
| center = <center>
 
{{(!}}
{{!-}}
{{!}}[[File:{{{1}}}{{!}}{{{5}}}{{!}}Bild {{#expr:{{{2}}}}}: {{{3}}}]]
{{!-}}
{{!}}
{{!-}}
{{!}}align="left" style="font-size:85%;"{{!}}'''Bild {{#expr:{{{2}}}}}: {{{3}}}'''
{{!)}}
</center>
| left
| right = {{(!}} style="float:{{{4}}}"
{{!-}}
{{!}}[[File:{{{1}}}{{!}}{{{5}}}{{!}}Bild {{#expr:{{{2}}}}}: {{{3}}}]]
{{!-}}
{{!}}
{{!-}}
{{!}}style="font-size:85%; align:left;"{{!}}'''Bild {{#expr:{{{2}}}}}: {{{3}}}'''
{{!)}}
| #default = {{(!}}
{{!-}}
{{!}}[[File:{{{1}}}{{!}}{{{4}}}{{!}}Bild {{#expr:{{{2}}}}}: {{{3}}}]]
{{!-}}
{{!}}
{{!-}}
{{!}}style="font-size:85%; align:left;"{{!}}'''Bild {{#expr:{{{2}}}}}: {{{3}}}'''
{{!)}}
}}
<noinclude>

Diese Vorlage erzeugt die Bildunterschrift. Die Syntax lautet wie folgt:
 

<nowiki>{{Bild_mit_Unterschrift | <Dateiname> | <Bildnummer> | <Bildunterschrift> | <Position (optional)> | <Bildgröße (optional)>}}</nowiki>
 
 
Zum Beispiel:
 

<nowiki>{{Bild_mit_Unterschrift | DMXC2_Manual_Kanaluebersicht_Fenster.png | 2 | Die Kanalübersicht | center | 400px}}</nowiki>
</noinclude>

Lesson 12 Tut3

2013-01-21T18:27:39Z

Vrystyle: quick correction of all pictures with subtitle

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}
==Overview==
In this lesson we explain advanced edit features for scenes and scene lists, e.g. for modification of already saved scenes.
So you can copy and customize cues very effectively and almost EXCEL like.

==Lecture 12: Editing scenes and scenelists ==

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

{{Picture_with_subtitle |DMXC3L12_SL.JPG|1|Menu of the Programmer|center}}

By default a new scene is added to an existing scene list by pressing the button "Add Cue". When you open the small 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.

{{Picture_with_subtitle |DMXC3L12_SL_storemenue.jpg|2|View of the dropdownmenu of "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.

{{Picture_with_subtitle |DMXC3L12_SL_editmenue.jpg|3|View of dropdownmenu of "Edit"|center}}

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

|}

{{Picture_with_subtitle |DMXC3L12_SL_optionmenue.jpg|4|View of dropdownmenu of "Options"|center}}

{| 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_Tut3]]
[[en:Lesson_12_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}

[[category:DMXControl 3]]

Lesson 12 Tut3

2013-01-21T18:21:38Z

Vrystyle: first corrections

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}
==Overview==
In this lesson we explain advanced edit features for scenes and scene lists, e.g. for modification of already saved scenes.
So you can copy and customize cues very effectively and almost EXCEL like.

==Lecture 12: Editing scenes and scenelists ==

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

{{Picture_with_subtitle |DMXC3L12_SL.JPG|1|Menu of the Programmer|center}}

By default a new scene is added to an existing scene list by pressing the button "Add Cue". When you open the small 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
| LinkBackwards = Lesson_11_Tut3
| TextBackwards = Lesson 11
| LinkForwards = Lesson_13_Tut3
| TextForwards = Lesson 13
}}

[[category:DMXControl 3]]

Template:Picture with subtitle

2013-01-21T18:17:11Z

Vrystyle: Tried to generate an fix template

{{#switch: {{{4}}}
| center = <center>
 
{{(!}}
{{!-}}
{{!}}[[File:{{{1}}}{{!}}{{{5}}}{{!}}Picture {{#expr:{{{2}}}}}: {{{3}}}]]
{{!-}}
{{!}}
{{!-}}
{{!}}align="left" style="font-size:85%;"{{!}}'''Picture {{#expr:{{{2}}}}}: {{{3}}}'''
{{!)}}
</center>
| left
| right = {{(!}} style="float:{{{4}}}"
{{!-}}
{{!}}[[File:{{{1}}}{{!}}{{{5}}}{{!}}Picture {{#expr:{{{2}}}}}: {{{3}}}]]
{{!-}}
{{!}}
{{!-}}
{{!}}style="font-size:85%; align:left;"{{!}}'''Picture {{#expr:{{{2}}}}}: {{{3}}}'''
{{!)}}
| #default = {{(!}}
{{!-}}
{{!}}[[File:{{{1}}}{{!}}{{{4}}}{{!}}Picture {{#expr:{{{2}}}}}: {{{3}}}]]
{{!-}}
{{!}}
{{!-}}
{{!}}style="font-size:85%; align:left;"{{!}}'''Picture {{#expr:{{{2}}}}}: {{{3}}}'''
{{!)}}
}}
<noinclude>

This Template generates the Pictur subtitle. The syntax is as followed:
 

<nowiki>{{picture_with_subtitle | <Filename> | <Number of picture> | <Subtitle> | <Position (optional)> | <Picturesize (optional)>}}</nowiki>
 
 
For example:
 

<nowiki>{{Picture_with_subtitle | DMXC2_Manual_Kanaluebersicht_Fenster.png | 2 | The channel overview | center | 400px}}</nowiki>
</noinclude>

Lesson 11 Tut3

2013-01-21T17:54:56Z

Vrystyle: /* Use of beat trigger */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}
==Overview==
Cue lists are the best tool to control the flow of your show. In this lesson we explain how to define the sequence and the change of scenes by triggers.

==Lecture 11: Trigger in cue lists ==

In previous lessons we learnt how to create cues and scene lists. Now we are familar with most of the attributes of the scene list but some more explanation about the trigger is nessecary. The default trigger is "follow". That means 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 the enter-key or by clicking in another field.

Besides of '''follow''' there are some other types of triggers. The following table informs you about their behaviours.

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (optional) 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 || (optional) 3 || you have to do some more settings, see next paragraph below!
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" characters, e.g. 1m20s
}}

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the realtimecode selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

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

===Use of beat trigger===

If you want to have your scenes beat controled, you need to select the trigger '''beat''' .
{{BoxHint|Text=In the '''Trigger''' field you can specify after how many beat signals the next cue is called
}}

{{Bild_mit_Unterschrift |Beattrigger.PNG|4|Example for beattrigger|center}}

Now you have to inform the '''Cue List''' which source of the beat signal should be used (manual beat/audioanalyzer....)
Therefore you have to assign an input in the [[Lesson_22_Tut3|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).

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

==Summary==

The following figure shows the dependencys and capabilitys of mixing several trigger types:

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

* Each cue has its delay-time (before the fade-in start) - delay1 to delay3
* Cue2 has a follow-trigger of 1s. It starts 1s after the fade-in of the previous cue is completed
* Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the follow of 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_Tut3]]
[[en:Lesson_11_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}

[[category:DMXControl 3]]

Lesson 11 Tut3

2013-01-21T17:51:19Z

Vrystyle: corr

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}
==Overview==
Cue lists are the best tool to control the flow of your show. In this lesson we explain how to define the sequence and the change of scenes by triggers.

==Lecture 11: Trigger in cue lists ==

In previous lessons we learnt how to create cues and scene lists. Now we are familar with most of the attributes of the scene list but some more explanation about the trigger is nessecary. The default trigger is "follow". That means 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 the enter-key or by clicking in another field.

Besides of '''follow''' there are some other types of triggers. The following table informs you about their behaviours.

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (optional) 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 || (optional) 3 || you have to do some more settings, see next paragraph below!
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" characters, e.g. 1m20s
}}

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the realtimecode selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

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

===Use of beat trigger===

If you want to have your scenes beat controled, you need to select the trigger '''beat''' .
{{BoxHint|Text
In the '''Trigger''' field you can specify after how many beat signals the next cue is called
}}

{{Bild_mit_Unterschrift |Beattrigger.PNG|4|Example for beattrigger|center}}

Now you have to inform the '''Cue List''' which source of the beat signal should be used (manual beat/audioanalyzer....)
Therefore you have to assign an input in the [[Lesson_22_Tut3|'''Input Assignment''']] via drag&drop to the beat entry of the cue list (see linked Lesson 22 "Input Assignment" for further details!).

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

==Summary==

The following figure shows the dependencys and capabilitys of mixing several trigger types:

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

* Each cue has its delay-time (before the fade-in start) - delay1 to delay3
* Cue2 has a follow-trigger of 1s. It starts 1s after the fade-in of the previous cue is completed
* Cue3 has a wait-trigger, but 0s. Thus cue3 starts immediately after the follow of 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_Tut3]]
[[en:Lesson_11_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_10_Tut3
| TextBackwards = Lesson 10
| LinkForwards = Lesson_12_Tut3
| TextForwards = Lesson 12
}}

[[category:DMXControl 3]]

Lesson 10 Tut3

2013-01-21T17:08:28Z

Vrystyle: corr

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_9_Tut3
| TextBackwards = Lesson 9
| LinkForwards = Lesson_11_Tut3
| TextForwards = Lesson 11
}}
==Overview==
Here we explain the "'''Programmer'''" view - a tool that helps in programming and "debuging" your show.

==Lecture 10: The programmer view ==

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

{{BoxHint
| Text= Remember the "save scene" dialog in DMXControl 2. On that step you have been asked to define the channels and values before finally saving the cue. The '''Programmer''' is a more extended view of this functionality.
}}

Let's illustrate this by an example. Perform the following steps:

* at first we open the moving lights shutters and select the color green
* second, set the gobos of all devices on "Gobo2"
* third, we set the group of front lights to 50% brightness

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

The result is exactly shown in the programmer. Please be aware that 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|All changes of the device settings are shown in the programmer|center|800px}}

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

Now you can see in the '''Programmer''' which values would be stored in the cue. When we save the cue you are able to select the desired items in the '''Programmer Filter''' that appears before. In the following example we do not save the "Generic Dimmer" (by deselecting them) because we probably want to save them in another cuelist.

{{Bild_mit_Unterschrift |DMXC3L10 ProgrammerFilter.JPG|3|View of the Programmer Filter|center}}

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

In order to program quicker, there is the snapshot function. With the button '''Write Snapshot''' you can cache the current selctions in the programmer and reload them later by using the drop-down menu ('''Load Snapshots'''). This helps you to program many similar cues with lowest effort.

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

In addition to that you can also create a filter with '''Set Filter''' or delete filters with '''Clear Filter'''. This function is mainly used in '''Output Mode'''. With this tool you can adjust the values of the programmer that are actually sent out. If '''All''' is active, all the values in the programmer are sent, with '''Filtered''' only the values that have been activated in the filter and with '''Blind''' no values are sent out.

[[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_Tut3]]
[[en:Lesson_10_Tut3]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_9_Tut3
| TextBackwards = Lesson 9
| LinkForwards = Lesson_11_Tut3
| TextForwards = Lesson 11
}}

[[category:DMXControl 3]]

Lesson 9 Tut3

2013-01-13T16:38:15Z

Vrystyle: /* Effects and filters */ corr

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_8_Tut3
| TextBackwards = Lesson 8
| LinkForwards = Lesson_10_Tut3
| TextForwards = Lesson 10
}}
==Overview==
The previous lession introduced simple cues. In this lesson we explain some more sophisticated features of scenes, e.g. the fanning feature. With fanning you can create impressive effects with groups of lamps, e.g. rainbow effects or waves.
DMXControl 3 provides an effect library.

==Lecture 9: Fanning, chasers and other effects==

DMXControl 3 extends the scope of scenes in that way that dynamic effects can be included and that you can apply certain algorithms for the attributes (e.g. DMX values) of included devices or groups. This allows you to create highly complex cues with a few mouse clicks. Don't believe it? Let's demonstrate how it works!

===Fanning===

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

From technical point of view fanning means to split a value to a group of devices. We distinguish between linear and alternate fanning. See the following tables explaining the syntax element.

====linear fanning====

{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || linear interpolation
|-
| <> || 50 <> 100 || linear interpolation: marginal devices: 100, central devices 50 (mnemonic trick: In the symbol both signs are directed outside; in these positions the first value is applied; the second value is applied in the center.)
|-
| >< || 50 >< 100 || contrary: marginal devices: 50, central devices 100 (mnemonic trick: In the symbol both signs are directed inside; there the first value is applied (in the center); the second value is applied at the edge.)
|}

=== alternate fanning ===

{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| # || 50 # 100 || alternate values 100/50/100/50 ...
|-
| # # || 100 # 50 # 0 || alternate values 100/50/0/100/50/0 ...
|}

How does it work?

Lets assume we want to have a cue where the 8 RGB Pars have to be faded from red in the middle to blue at the edges.

[[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's done fast and easy with DMXControl 3, or did you expect something else? ;)

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

In "'''Effects and filters'''" panel (accessed via '''Windows-> Effects and Filters''') some super effects are offered, which you can use to create a dynamic change within the cues such as "sine", "trapezoid", "Sawtooth". Using drag&drop you can easily attach the sine effect to the dimmer in the '''Property Grid'''.
Now this attribute behaves as it is expected by the symbol or name of the effect. You can change specific effect parameters in the '''Property Grid''' for example to affect the amplitude or frequency of the effect. For examples and details see the table below.

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

Try it! You'll love it! 

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

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

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribute
! Example
! Description
|-
| Amplitude
| 50 > 100
| value interval for selected attribute; can be set to negative value 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"
|-
! Use case
! How-to
! 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 a group 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
|-
|Pattern of 8: Moving lights follow the "8" shape
|drag "Lissajous" to position property
| 270
|-
|On/off-effect: Lamps are switched on/off
|drag "Rectangle" to dimmer property
| 100
|-
|Harmonic fade: Lamps dimm in a harmonic way to 100% and back to 0
|drag "Sinus" to dimmer property
| 100
|-
|color change: Lamps change 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
| LinkBackwards = Lesson_8_Tut3
| TextBackwards = Lesson 8
| LinkForwards = Lesson_10_Tut3
| TextForwards = Lesson 10
}}

[[category:DMXControl 3]]

Lesson 9 Tut3

2013-01-12T17:46:30Z

Vrystyle: corrections up to ---Effects and filters--- (not corrected yet)

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

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

==Overview==
The previous lession introduced simple cues. In this lesson we explain some more sophisticated features of scenes, e.g. the fanning feature. With fanning you can create impressive effects with groups of lamps, e.g. rainbow effects or waves.
DMXControl 3 provides an effect library.

==Lecture 9: Fanning, chasers and other effects==

DMXControl 3 extends the scope of scenes in that way that dynamic effects can be included and that you can apply certain algorithms for the attributes (e.g. DMX values) of included devices or groups. This allows you to create highly complex cues with a few mouse clicks. Don't believe it? Let's demonstrate how it works!

===Fanning===

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

From technical point of view fanning means to split a value to a group of devices. We distinguish between linear and alternate fanning. See the following tables explaining the syntax element.

====linear fanning====

{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || linear interpolation
|-
| <> || 50 <> 100 || linear interpolation: marginal devices: 100, central devices 50 (mnemonic trick: In the symbol both signs are directed outside; in these positions the first value is applied; the second value is applied in the center.)
|-
| >< || 50 >< 100 || contrary: marginal devices: 50, central devices 100 (mnemonic trick: In the symbol both signs are directed inside; there the first value is applied (in the center); the second value is applied at the edge.)
|}

=== alternate fanning ===

{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| # || 50 # 100 || alternate values 100/50/100/50 ...
|-
| # # || 100 # 50 # 0 || alternate values 100/50/0/100/50/0 ...
|}

How does it work?

Lets assume we want to have a cue where the 8 RGB Pars have to be faded from red in the middle to blue at the edges.

[[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 8 Tut3

2013-01-12T17:19:57Z

Vrystyle:

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_7_Tut3
| zurückText = Lektion 7
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_9_Tut3
| vorText = Lektion 9
}}
{{DMXC3_lesson/en}}

==Overview==
Scenes (cues) are the most important elements of your show. Here we will explain the powerful scene concept of DMXControl 3. The terms "cue" and "scene" are used as synonym words.

==Lecture 8: Scenes (cues) and scene lists ==

Now the real work begins - we will create our first cue in DMXControl 3! All RGB lights will shine green.

* We go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* The intensity of the dimmer panel is pulled or press the "Lumos" button
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)

{{Bild_mit_Unterschrift |DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}

* On the left click on "Add new cue"
* It opens a new window called "Programmer filter" which we will explain in Chapter 10. For now press OK.
[[File:DMXC3L08 programmerFilter.JPG]]

* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* Here we rename the cue in the ''Name'' field to "My First Cue".

{{Bild_mit_Unterschrift |DMXC3L08 firstCue02.JPG|2|View of the programmer window|center}}

Each scene (cue) needs a "host container" - that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".

[[File:DMXC3L08 secondScene.JPG]]
[[File:DMXC3L08 SlideDMXC3cue.jpg]]
[[File:DMXC3L08 firstCue02.JPG]]
[[File:DMXC3L08 firstCue01.JPG]]

[[File:DMXC3L08_createSceneListnew.JPG|600px]]

You can open this new cue list with a '''double click''' on the object in the project explorer or using the context menu item "open" (or double click).
In the tabular list you can adjust the individual parameters of the cue.

[[File:DMXC3L08 changeLiveView.JPG]]
{{BoxHint
|Text =The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is and wich target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.}}

The life cycle of a cue is as following:
{{Bild_mit_Unterschrift |DMXC3L08 SlideDMXC3cue.jpg|3|Lifecycle of cues in DMXControl 3|center|700px}}

A cue waits at first for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).

Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduceded compared to the previous cue.

Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.

[[File:DMXC3L08 FirstScene.JPG]]

{{BoxAttention
|Text = You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
}}
{{Bild_mit_Unterschrift |Clear_programmer.jpg|4|Clearing the programmer|center}}
[[File:Clear_programmer.jpg]]

In following table we explain the meaning of cue attributes (which you can see in the scene list header):

{| class="wikitable"
! Attribute
! Description
! Example
|-
| Progress
| shows the status of the scene during execution of scene list (wait time and progress)
| in percent
|-
| Trigger
| relation to predecessor cue, use "follow" as default
| see [[Lesson 11]]
|-
| Trigger Value
|
| see [[Lesson 11]]
|-
| Name
| free name of scene
| should explain the content of cue
|-
| Fade
| fade-in value
| in milli seconds [ms]
|-
| Delay
| fanning for fades
| see [[Lesson 9]]
|-
| Ac (active)
| is this cue active or should it be ignored?
| default: active
|-
| Ap (autoprepare)
| Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue)
| default: active
|-
| Re (ReExecute)
| If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the ''actual'' value to the destination value.
| Example: 
Cue 39 Fade 0s: 1 + 2 at full 
Cue 40 Fade 500s: 1 at 0 
Cue 41 Fade 10s: 2 at 0 
(Cue 41 should be a blackout) 
Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds. 
Now someone on stage forgets his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left). 
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in the residual 60s 
If '''Re''' is active for cue 41 the 1 immedately goes down from the ''actual value at this time'' to 0 in 10s together with device 2.
|-
| Comment
| for free use, insert explaining words
|
|-
|}

In the same way you can create some more cues and store it in the scene list.
{{Bild_mit_Unterschrift |DMXC3L08 SecondScene.JPG|5|Cuelist with some cues|center}}
[[File:DMXC3L08 SecondScene.JPG]]

===Playing back cues===
Go, Back, etc.

However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.

===Using advanced timing (=> Property Based Timing)===
It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color and after that change the gobo.

In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in milliseconds. Also you can use fanned values here. See [[Lesson 9]].

The following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.

[[File:Dmxc3 advanced timing value.jpg]]  
[[File:Dmxc3 advanced timing fade.jpg]]

[[File:Dmxc3 advanced timing delay.jpg]]

===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.

==Excercise==
* Generate your own cues
* Try the buttons "STOP", "GO" and "Mode" in the cue list
* Work with different fade times

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

[[de:Lektion_8_Tut3]]
[[en:Lesson_8_Tut3]]

__NOTOC__
__NOTITLE__

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

[[Kategorie:DMXControl 3]]

Lesson 8 Tut3

2013-01-12T17:16:23Z

Vrystyle: /* Lecture 8: Scenes (cues) and scene lists */ corr

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_7_Tut3
| zurückText = Lektion 7
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_9_Tut3
| vorText = Lektion 9
}}
{{DMXC3_lesson/en}}

==Overview==
Scenes (cues) are the most important elements of your show. Here we will explain the powerful scene concept of DMXControl 3. The terms "cue" and "scene" are used as synonym words.

==Lecture 8: Scenes (cues) and scene lists ==

Now the real work begins - we will create our first cue in DMXControl 3! All RGB lights will shine green.

* We go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* The intensity of the dimmer panel is pulled or press the "Lumos" button
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)

{{Bild_mit_Unterschrift |DMXC3L08 firstCue01.JPG|1|Setting the floodlights on the desired settings|center|700px}}

* On the left click on "Add new cue"
* It opens a new window called "Programmer filter" which we will explain in Chapter 10. For now press OK.
[[File:DMXC3L08 programmerFilter.JPG]]

* Because we do not have any cue list yet, a new one will be created now automatically. This is displayed in a new panel.
* Here we rename the cue in the ''Name'' field to "My First Cue".

{{Bild_mit_Unterschrift |DMXC3L08 firstCue02.JPG|2|View of the programmer window|center}}

Each scene (cue) needs a "host container" - that's a scenelist (cuelist). New cuelists can be created clicking the small triangle besides the "Add new cue" button and there follow the drop. Then again press "Add new cue!".

[[File:DMXC3L08 secondScene.JPG]]
[[File:DMXC3L08 SlideDMXC3cue.jpg]]
[[File:DMXC3L08 firstCue02.JPG]]
[[File:DMXC3L08 firstCue01.JPG]]

[[File:DMXC3L08_createSceneListnew.JPG|600px]]

You can open this new cue list with a '''double click''' on the object in the project explorer or using the context menu item "open" (or double click).
In the tabular list you can adjust the individual parameters of the cue.

[[File:DMXC3L08 changeLiveView.JPG]]
{{BoxHint
|Text =The name of the cue should always be changed so that you can remember later quickly what the cue includes, what the reason is and wich target this cue has (e.g., "First scene", "Start cue", "ML red", etc.). There is even a comment box at the far right side in the scene list.}}

The life cycle of a cue is as following:
{{Bild_mit_Unterschrift |DMXC3L08 SlideDMXC3cue.jpg|3|Lifecycle of cues in DMXControl 3|center|700px}}

A cue waits at first for its trigger point, see [[Lesson_11_Tut3|Lesson 11]]. Then the delay-time becomes relevant if it is defined. Finally a fade-in time can be specified where the cue is faded in (increasing particular the dimmer channel).

Alternatively to ''delay / fade-in'' you may define ''delay down / fade down''. This is common in the theater control when the value should be reduceded compared to the previous cue.

Please note that a cue by itself never "completes" but is always "overwritten" with a different cue.

[[File:DMXC3L08 FirstScene.JPG]]

{{BoxAttention
|Text = You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button. More details will follow in the next chapter.
}}
{{Bild_mit_Unterschrift |Clear_programmer.jpg|4|Clearing the programmer|center}}
[[File:Clear_programmer.jpg]]

In following table we explain the meaning of cue attributes (which you can see in the scene list header):

{| class="wikitable"
! Attribute
! Description
! Example
|-
| Progress
| shows the status of the scene during execution of scene list (wait time and progress)
| in percent
|-
| Trigger
| relation to predecessor cue, use "follow" as default
| see [[Lesson 11]]
|-
| Trigger Value
|
| see [[Lesson 11]]
|-
| Name
| free name of scene
| should explain the content of cue
|-
| Fade
| fade-in value
| in milli seconds [ms]
|-
| Delay
| fanning for fades
| see [[Lesson 9]]
|-
| Ac (active)
| is this cue active or should it be ignored?
| default: active
|-
| Ap (autoprepare)
| Autoprepare - prepares certain channels for next cue (e.g. prepare correct position of clor wheel for next cue)
| default: active
|-
| Re (ReExecute)
| If ReExecute is active on a cue this cue takes all probably running fades and then it fades all of them with the selected fadetime from the ''actual'' value to the destination value.
| Example: 
Cue 39 Fade 0s: 1 + 2 At Full 
Cue 40 Fade 500s: 1 At 0 
Cue 41 Fade 10s: 2 At 0 
Cue 41 should be a blackout 
Normally cue 41 follows if cue 40 is ready. Fading on black within 10 seconds. 
Now someone on stage forgetts his/her text and cue 41 must start faster than expected. Cue 40 is still running (60s left). 
What normally happens when you start cue 41 manually: 2 fades on 0 in 10s, 1 continues the fade to 0 in 60s 
If Re is active for cue 41 the 1 immedately goes down from the ''actual value'' to 0 in 10s together with device 2.
|-
| Comment
| for free use, insert explaining words
|
|-
|}

In the same way you can create some more cues and store it in the scene list.
{{Bild_mit_Unterschrift |DMXC3L08 SecondScene.JPG|5|Cuelist with some cues|center}}
[[File:DMXC3L08 SecondScene.JPG]]

===Playing back cues===
Go, Back, etc.

However you can also play a cue that is not in sequence by holding down CTRL and double clicking the cue you want to play.

===Using advanced timing (=> Property Based Timing)===
It is possible to set delay and fade times for each property individually. You can use this feature to build a cue that moves your moving lights to a different position, then change the color and after that change the gobo.

In the property grid, change "Values" to "Fade" or "Delay". You can now set fade or delay for each property. DMXControl expects time in milliseconds. Also you can use fanned values here. See [[Lesson 9]].

The following example will immediately open the shutter and fade the intensity from 0 to 100% within 1 second (dimmer fade) after this 1 second (color delay) the color will be faded within 5 seconds (color fade). The total duration of this cue will be 6 seconds, because the longest action is the color fade: delay 1s + fade 5s.

[[File:Dmxc3 advanced timing value.jpg]]  
[[File:Dmxc3 advanced timing fade.jpg]]

[[File:Dmxc3 advanced timing delay.jpg]]

===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values: ... i guess should work but i don't know how.

==Excercise==
* Generate your own cues
* Try the buttons "STOP", "GO" and "Mode" in the cue list
* Work with different fade times

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

[[de:Lektion 8]]
[[en:Lesson 8]]

__NOTOC__
__NOTITLE__

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

[[Kategorie:DMXControl 3]]

Lesson 7 Tut3

2013-01-12T15:01:43Z

Vrystyle: /* Lecture 7: Summary and details of setup */ Added BoxHint below

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

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

==Overview==
In this lesson a final overview about the basic concepts for setting up the DMXControl 3 software is given. This completes the first part of the lectures "Basics, Setup and configuration".

==Lecture 7: Summary and details of setup ==

Now we will finalise our first expedition through DMXControl by investigating other generic features.

DMXControl 3 is very focused on working with groups of devices. These groups can be defined in a very effective and flexible way. Due to the strong abstraction of device properties you can also combine different types of devices in groups (to programm them later uniformly). Also adding devices to a group later is no problem.

The management of all elements is centralized in the '''Project Explorer'''. Here you keep control over your devices, groups, views, cue lists, and so on.
The new panel concept requires some practice, but you'll love it if you mastered it. So you can adjust the DMXControl 3 completely according to your needs!

There are lots of additional buttons in the main menu for operational support:
* File
** Here you can create, open and save projects
** With "project properties" you can assign some notices to the current project
* Windows
** Beside some tools that will be explained later on, here you find a chat tool. It is helpful if several operators and programmers work in parallel with DMXControl 3. They can exchange some messages here.
** The "manual beat tool" can be compared to the corresponding tool in DMXControl 2. By pressing the space key you can generate manual beats
* Settings
** '''Application settings''': Double click the icons in order to set configuration options.
** Here we refer to the affinity feature: DMXControl is trying to calculate similarities of gobos. If you have two moving lights with different gobos and for example you select in the (mixed) property grid a "starry sky" gobo, it tries automatically to take the most similar gobo on each device.
With the option '''Affinity View''' you can manually adjust the "similarities" to your subjective view.
{{Bild_mit_Unterschrift |DMXC3L07 AffinityView.JPG|1|View of AffinityView-Tool|center}}
[[File:DMXC3L07 AffinityView.JPG]]

If you choose a gobo on the left side, you will logically find the same logo in the first place on the righ side. If this does not exist on your device, it will automatically take the next one in the list and so on. With the up and down arrows you can manually change the order.

On left hand side of your screen you have some global icons. Here we want to refer to
* Fog
** Here you have several operation modes for your DMX-controled fog device
* Highlight
** Rapid activation and deactivation of a device by simply clicking on it. Particularly suitable for setting up your stage.
* Blackout
** As the name indicates: Blackout of all devices

The project explorer also contains some general buttons:
* Edit
* Create directory / create device group
* Up / Down
* Device Manager
* Add item list / add Live view
* Import / export files
This is for administative operations in your device configuration.
[[File:DMXC3L07 ProjectExplorerMenues.JPG]]

[[File:DMXC3L07 menuelist.JPG|600px]]

One helpful tool is missing for basic checks and setting up of DMX channels: the channel overview (Windows -> channel overview). Here you get an overview about the current output. With the slider on left hand side you can also modify the value of the selected channel.

[[File:DMXC3L07 ChannelOverview.JPG]]
[[File:DMXC3L07 channelOverview.JPG|600px]]

{{BoxHint
|Text =Please be aware that the '''Channel Overview''' is not finally ready and still is under construction.}}

==Excercise==
* Set channel 34 to DMX value 128 with help of channel overview
* Try the Highlight and Blackout mode (observe results in Stage view panel)
*

==Certificate==
Great! You have now completed the first part of the DMXControl lecture!

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

[[de:Lektion 7]]
[[en:Lesson 7]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| zurückLink = Lektion_6_Tut3
| zurückText = Lektion 6
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_8_Tut3
| vorText = Lektion 8
}}

[[Kategorie:DMXControl 3]]

Lesson 7 Tut3

2013-01-12T14:51:53Z

Vrystyle: /* Lecture 7: Summary and Details of Setup */ corr

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

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

==Overview==
In this lesson a final overview about the basic concepts for setting up the DMXControl 3 software is given. This completes the first part of the lectures "Basics, Setup and configuration".

==Lecture 7: Summary and details of setup ==

Now we will finalise our first expedition through DMXControl by investigating other generic features.

DMXControl 3 is very focused on working with groups of devices. These groups can be defined in a very effective and flexible way. Due to the strong abstraction of device properties you can also combine different types of devices in groups (to programm them later uniformly). Also adding devices to a group later is no problem.

The management of all elements is centralized in the '''Project Explorer'''. Here you keep control over your devices, groups, views, cue lists, and so on.
The new panel concept requires some practice, but you'll love it if you mastered it. So you can adjust the DMXControl 3 completely according to your needs!

There are lots of additional buttons in the main menu for operational support:
* File
** Here you can create, open and save projects
** With "project properties" you can assign some notices to the current project
* Windows
** Beside some tools that will be explained later on, here you find a chat tool. It is helpful if several operators and programmers work in parallel with DMXControl 3. They can exchange some messages here.
** The "manual beat tool" can be compared to the corresponding tool in DMXControl 2. By pressing the space key you can generate manual beats
* Settings
** '''Application settings''': Double click the icons in order to set configuration options.
** Here we refer to the affinity feature: DMXControl is trying to calculate similarities of gobos. If you have two moving lights with different gobos and for example you select in the (mixed) property grid a "starry sky" gobo, it tries automatically to take the most similar gobo on each device.
With the option '''Affinity View''' you can manually adjust the "similarities" to your subjective view.
{{Bild_mit_Unterschrift |DMXC3L07 AffinityView.JPG|1|View of AffinityView-Tool|center}}
[[File:DMXC3L07 AffinityView.JPG]]

If you choose a gobo on the left side, you will logically find the same logo in the first place on the righ side. If this does not exist on your device, it will automatically take the next one in the list and so on. With the up and down arrows you can manually change the order.

On left hand side of your screen you have some global icons. Here we want to refer to
* Fog
** Here you have several operation modes for your DMX-controled fog device
* Highlight
** Rapid activation and deactivation of a device by simply clicking on it. Particularly suitable for setting up your stage.
* Blackout
** As the name indicates: Blackout of all devices

The project explorer also contains some general buttons:
* Edit
* Create directory / create device group
* Up / Down
* Device Manager
* Add item list / add Live view
* Import / export files
This is for administative operations in your device configuration.
[[File:DMXC3L07 ProjectExplorerMenues.JPG]]

[[File:DMXC3L07 menuelist.JPG|600px]]

One helpful tool is missing for basic checks and setting up of DMX channels: the channel overview (Windows -> channel overview). Here you get an overview about the current output. With the slider on left hand side you can also modify the value of the selected channel.

[[File:DMXC3L07 ChannelOverview.JPG]]
[[File:DMXC3L07 channelOverview.JPG|600px]]

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

==Excercise==
* Set channel 34 to DMX value 128 with help of channel overview
* Try the Highlight and Blackout mode (observe results in Stage view panel)
*

==Certificate==
Great! You have now completed the first part of the DMXControl lecture!

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

[[de:Lektion 7]]
[[en:Lesson 7]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| zurückLink = Lektion_6_Tut3
| zurückText = Lektion 6
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_8_Tut3
| vorText = Lektion 8
}}

[[Kategorie:DMXControl 3]]

Lesson 6 Tut3

2013-01-10T19:08:19Z

Vrystyle: /* Lecture 6: Configuring the output plugins */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3| zurückLink = Lektion_5_Tut3| zurückText = Lektion 5| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]| vorLink = Lektion_7_Tut3| vorText = Lektion 7}}
{{DMXC3_lesson/en}}

==Overview==
In order to control your lamps you need to send out "real" DMX signals to your universes. In this lesson we explain how to configure your output devices.

==Lecture 6: Configuring the output plugins ==

In the menue "settings" you can find the panel '''DMX interfaces'''. There you can select your DMX transmitter/sender by choosing it in the new window that appears when pressing button '''Add interfaces'''.

{{Bild_mit_Unterschrift |DMXC3L06 AddInterface.JPG|1|Hinzufügen eines Interfaces|center}}

{{BoxHint|Text = In the current beta version only a subset of DMX Interfaces is supported (compared to DMXControl 2). But this is no blocking point for testing the software, if you are an owner of a different interface. On one hand the software also works without DMX-Interface, on the other hand you can use the Artnet-Interface to connect to a light control software supporting your interface, e.g. DMXControl 2.12. See [[Lesson_24_Tut3|Lesson 24]].
}}

[[File:DMXC3L06 DE IF plugin.JPG]]

Then, the interface has to be configured on "Advanced Interface Settings". Here you can make fine tuning and set the configuration settings that are supported by your DMX transmitter. In the shown case you can modify e.g. the break time if the DMX receiver in one of your lamps requires a higher value. In "Set Interface Mode" you can choose a mode that corresponds to your application.
In Figure 2, the mode is still set to '''0 - Standby'''. In order that the DE or fx5 interface outputs something, you can select Mode '''2 - PC Out -> select DMX Out'''.

{{Bild_mit_Unterschrift |DMXC3L06 DE IF plugin settings.JPG|2|Ansicht der Erweiterten Einstellungen des DE- bzw. fx5-Interfaces|center}}

[[File:DMXC3L06 DE IF plugin settings.JPG]]

Interfaces that support more than one DMX universe (such as the visualization tool 3D Easy View), obtain a line in the table for each DMX Universe. Therefore e.g. 3D EasyView gets four lines.

The field '''Port''' indicates the corresponding input or output of the interface. In the columns '''DMX Out Address''' and '''DMX-In Address''' you can assign a a port to a DMX Universe by a double click.

The entry must be constructed in accordance with the scheme:
Universe.DMX start channel

DMXControl 3 supports 16 DMX universes (Universe Universe 1 to 16) with each 512 channels (channel 1 to channel 512).

If it is intended that the DE or fx5 interface for example has to send all channel values from channel 83-512 in Universe 4 and DMXControl should use received DMX values via DMX in on Universe 6, you have to enter '''4.83''' within the appropriate field '''DMX-out address''' and '''6.1''' in '''DMX-In Address'''.

On some interfaces (such as the Nicolaudie SIUDI) a port can only act either as a DMX-in or as DMX out. In this case, check boxes that appear in columns '''DMX-Out Enabled''' and '''DMX-In Enabled''', to adjust the respective wanted behavior.
{{BoxHint
|Text=There are DMX devices that have problems with the timing. These devices respond completely wrong or only partially to transmitted DMX values. A change in the values "Break Time" may remedy the situation. Just try it. You can adjust these values also under "Advanced Interface Settings".
}}

==Excercise==
* Activate and configure your DMX transmitter
* Configure an ArtNet Interface ("Artistic Licence")
* Set the Output-Universe of Port2 of ArtNet-Interfaces to channel 65 of third universe
* What happens by inserting '''2.513''' or '''17.1'''?

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

[[de:Lektion 6]]
[[en:Lesson 6]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_5_Tut3
| zurückText = Lektion 5
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_7_Tut3
| vorText = Lektion 7
}}

[[Kategorie:DMXControl 3]]

Lesson 6 Tut3

2013-01-10T18:57:15Z

Vrystyle: /* Lecture 6: Configuring the output plugins */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3| zurückLink = Lektion_5_Tut3| zurückText = Lektion 5| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]| vorLink = Lektion_7_Tut3| vorText = Lektion 7}}
{{DMXC3_lesson/en}}

==Overview==
In order to control your lamps you need to send out "real" DMX signals to your universes. In this lesson we explain how to configure your output devices.

==Lecture 6: Configuring the output plugins ==

In the menue "settings" you can find the panel '''DMX interfaces'''. There you can select your DMX transmitter/sender by choosing it in the new window that appears when pressing button '''Add interfaces'''.

{{Bild_mit_Unterschrift |DMXC3L06 AddInterface.JPG|1|Hinzufügen eines Interfaces|center}}

{{BoxHint|Text = In the current beta version only a subset of DMX Interfaces is supported (compared to DMXControl 2). But this is no blocking point for testing the software, if you are an owner of a different interface. On one hand the software also works without DMX-Interface, on the other hand you can use the Artnet-Interface to connect to a light control software supporting your interface, e.g. DMXControl 2.12 [[Lesson_24_Tut3]].
}}

[[File:DMXC3L06 DE IF plugin.JPG]]

Then, the interface has to be configured on "Advanced Interface Settings". Here you can make fine tuning and set the configuration settings that are supported by your DMX transmitter. In the shown case you can modify e.g. the break time if the DMX receiver in one of your lamps requires a higher value. In "Set Interface Mode" you can choose a mode that corresponds to your application.
In Figure 2, the mode is still set to '''0 - Standby'''. In order that the DE or fx5 interface outputs something, you can select Mode '''2 - PC Out -> select DMX Out'''.

{{Bild_mit_Unterschrift |DMXC3L06 DE IF plugin settings.JPG|2|Ansicht der Erweiterten Einstellungen des DE- bzw. fx5-Interfaces|center}}

[[File:DMXC3L06 DE IF plugin settings.JPG]]

Interfaces that support more than one DMX universe (such as the visualization tool 3D Easy View), obtain a line in the table for each DMX Universe. Therefore e.g. 3D EasyView gets four lines.

The field '''Port''' indicates the corresponding input or output of the interface. In the columns '''DMX Out Address''' and '''DMX-In Address''' you can assign a a port to a DMX Universe by a double click.

The entry must be constructed in accordance with the scheme:
Universe.DMX start channel

DMXControl 3 supports 16 DMX universes (Universe Universe 1 to 16) with each 512 channels (channel 1 to channel 512).

If it is intended that the DE or fx5 interface for example has to send all channel values from channel 83-512 in Universe 4 and DMXControl should use received DMX values via DMX in on Universe 6, you have to enter '''4.83''' within the appropriate field '''DMX-out address''' and '''6.1''' in '''DMX-In Address'''.

On some interfaces (such as the Nicolaudie SIUDI) a port can only act either as a DMX-in or as DMX out. In this case, check boxes that appear in columns '''DMX-Out Enabled''' and '''DMX-In Enabled''', to adjust the respective wanted behavior.
{{BoxHint
|Text=There are DMX devices that have problems with the timing. These devices respond completely wrong or only partially to transmitted DMX values. A change in the values "Break Time" may remedy the situation. Just try it. You can adjust these values also under "Advanced Interface Settings".
}}

==Excercise==
* Activate and configure your DMX transmitter
* Configure an ArtNet Interface ("Artistic Licence")
* Set the Output-Universe of Port2 of ArtNet-Interfaces to channel 65 of third universe
* What happens by inserting '''2.513''' or '''17.1'''?

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

[[de:Lektion 6]]
[[en:Lesson 6]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_5_Tut3
| zurückText = Lektion 5
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_7_Tut3
| vorText = Lektion 7
}}

[[Kategorie:DMXControl 3]]

Lesson 6 Tut3

2013-01-10T18:56:03Z

Vrystyle: /* Lecture 6: Configuring the output plugins */ corr

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3| zurückLink = Lektion_5_Tut3| zurückText = Lektion 5| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]| vorLink = Lektion_7_Tut3| vorText = Lektion 7}}
{{DMXC3_lesson/en}}

==Overview==
In order to control your lamps you need to send out "real" DMX signals to your universes. In this lesson we explain how to configure your output devices.

==Lecture 6: Configuring the output plugins ==

In the menue "settings" you can find the panel '''DMX interfaces'''. There you can select your DMX transmitter/sender by choosing it in the new window that appears when pressing button '''Add interfaces'''.

{{Bild_mit_Unterschrift |DMXC3L06 AddInterface.JPG|1|Hinzufügen eines Interfaces|center}}

{{BoxHint|Text = In the current beta version only a subset of DMX Interfaces is supported (compared to DMXControl 2). But this is no blocking point for testing the software, if you are an owner of a different interface. On one hand the software also works without DMX-Interface, on the other hand you can use the Artnet-Interface to connect to a light control software supporting your interface, e.g. DMXControl 2.12 [[Lesson_24_Tut3]].
}}

[[File:DMXC3L06 DE IF plugin.JPG]]

Then, the interface has to be configured on "Advanced Interface Settings". Here you can make fine tuning and set the configuration settings that are supported by your DMX transmitter. In the shown case you can modify e.g. the break time if the DMX receiver in one of your lamps requires a higher value. In "Set Interface Mode" you can choose a mode that corresponds to your application.
In Figure 2, the mode is still set to '''0 - Standby'''. In order that the DE or fx5 interface outputs something, you can select Mode '''2 - PC Out -> select DMX Out'''.

{{Bild_mit_Unterschrift |DMXC3L06 DE IF plugin settings.JPG|2|Ansicht der Erweiterten Einstellungen des DE- bzw. fx5-Interfaces|center}}

[[File:DMXC3L06 DE IF plugin settings.JPG]]

Interfaces that support more than one DMX universe (such as the visualization tool 3D Easy View), obtain a line in the table for each DMX Universe. Therefore e.g. 3D EasyView gets four lines.

The field '''Port''' indicates the corresponding input or output of the interface. In the columns '''DMX Out Address''' and '''DMX-In Address''' you can assign a a port to a DMX Universe by a double click.

The entry must be constructed in accordance with the scheme:
Universe.DMX DMX start channel

DMXControl 3 supports 16 DMX universes (Universe Universe 1 to 16) with each 512 channels (channel 1 to channel 512).

If it is intended that the DE or fx5 interface for example has to send all channel values from channel 83-512 in Universe 4 and DMXControl should use received DMX values via DMX in on Universe 6, you have to enter '''4.83''' within the appropriate field '''DMX-out address''' and '''6.1''' in '''DMX-In Address'''.

On some interfaces (such as the Nicolaudie SIUDI) a port can only act either as a DMX-in or as DMX out. In this case, check boxes that appear in columns '''DMX-Out Enabled''' and '''DMX-In Enabled''', to adjust the respective wanted behavior.
{{BoxHint
|Text=There are DMX devices that have problems with the timing. These devices respond completely wrong or only partially to transmitted DMX values. A change in the values "Break Time" may remedy the situation. Just try it. You can adjust these values also under "Advanced Interface Settings".
}}

==Excercise==
* Activate and configure your DMX transmitter
* Configure an ArtNet Interface ("Artistic Licence")
* Set the Output-Universe of Port2 of ArtNet-Interfaces to channel 65 of third universe
* What happens by inserting '''2.513''' or '''17.1'''?

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

[[de:Lektion 6]]
[[en:Lesson 6]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_5_Tut3
| zurückText = Lektion 5
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_7_Tut3
| vorText = Lektion 7
}}

[[Kategorie:DMXControl 3]]

Lesson 5 Tut3

2013-01-10T18:36:21Z

Vrystyle: /* Lecture 5: Setting properties of fixtures */ corr

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

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_4_Tut3
| zurückText = Lektion 4
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_6_Tut3
| vorText = Lektion 6
}}

==Overview==
In this lesson we explain how to control the properties of devices by several property panels. DMXControl 3 provides an very powerful abstraction level for properties, allowing to handle different devices in the same way.

==Lecture 5: Setting properties of fixtures ==

First step is to select devices or groups in the '''stage view''', see previous lesson [[Lesson 4]].
You can set properties of the selected devices by means of the "property panels".
Simply click on a color or select a gobo within the beam panel. Of course, you shouldn't forget to open the shutter or to set the brightness in the intensity panel.

In the animation of the icons in the '''Stage View''' you can see the impact very well, especially for the moving lights.

[[File:DMXC3L05 propertyPanels.JPG|center|600px]]

Movements can be controlled by the X/Y (pan/tilt)panel. The movement is also shown in the live view icons. But please consider that only the destination position will be stored later and not the path towards it.

Most of the property panels are self explaining. We have
* color panel - pick the wanted color
* position panel - set the pan/tilt position
* intensity panel - set brightness
* gobo panel - select gobo
* beam panel - fade between two beams (e.g. in beamer tool)

Some remarks to the intensity panel:

{| class="wikitable"
! Attribute
! Description
! Example
|-
| dimmer
| set dimmer value by fader or by static values
| in percent
|-
| strobe
| strobe speed
|
|-
| shutter
| open or close shutter
|
|-
| Lumos
| Lumos stands for "light", it is a direct function for dimmer/shutter. Lumos opens it (100%), NoX closes it (0%).
| You don't need to know if the device includes a shutter and/or dimmer.
|-
|}

[[File:DMXC3L05 propertyTS.JPG]]

A more sophisticated way of property settings is provided by the "property panel". In this panel the properties are shown with current values. Sometimes you can modify the values by typing in a percentage/beam angle/DMX value, more often you can find a dropdown menu that allows to select properties in more abstract or graphical view, see the color dropdown as example for setting the RGB value of RGB Pars.

{{Bild_mit_Unterschrift |DMXC3L05 propertyRGBParColor.jpg|3|Property Grid mit geöffneter Farbauswahl|center}}
[[File:DMXC3L05 propertyRGBPar.JPG]]

[[File:DMXC3L05 propertyRGBParColor.jpg]]

The following picture demonstrates a very interesting capability of the new DMXControl kernel: You can even select different device types in parallel and set a common property in one step.
This also works with devices that have different functions (such as scanners and LED lights).
The DMXControl kernel engine will assign the best matching values automatically. Of course, if required, you can modify the attributes manually.

[[File:DMXC3L05 propertyMix.JPG]]

In this example, a moving light and PAR lights were selected. Both devices can be assigned the color yellow in one step in the Property Grid.

In addition to the simultaneous control of multiple devices, you can also control multiple groups as if they were one unit. Therefore you have to change the option in the Property Grid from '''value''' to '''Group handling''' .

[[File:DMXC3L05 PropertyGroupHandling.jpg]]

==Excercise==
* Set the moving lights to red color, the RBG Pars to blue and open the two front light lamps (dimmer) to 100%
* Now set all left hand lamps to yellow and all right hand lamps to pink. You should need just 4 operations (mouse clicks) for this task.
* Observe the movement of TS-255 devices when using the X/Y pad (position panel).

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

[[de:Lektion 5]]
[[en:Lesson 5]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| zurückLink = Lektion_4_Tut3
| zurückText = Lektion 4
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_6_Tut3
| vorText = Lektion 6
}}

[[Kategorie:DMXControl 3]]

Lesson 4 Tut3

2013-01-06T19:33:50Z

Vrystyle: /* Certificate */

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

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_3_Tut3
| zurückText = Lektion 3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_5_Tut3
| vorText = Lektion 5
}}

==Overview==
This lesson introduces into the stage view panel - a minimal 2D visualisation tool which offers valueable support for programming your show.

==Lecture 4: The Live View (Stage View) ==

The '''Stage View''' is one of the several tools in the tool menue. When you create devices and/or groups, some (interactive) icons are automatically generated in the '''Stage View'''. You can move these icons to any place you want by dragging them with the mouse. In this way you can model your stage in 2D representation.

It could be helpful to load a background picture for better mapping your stage. Click on the background with right mouse button and choose "Edit Background". Additional background pictures can be inserted in the folder ".../DMMXControl3.0/Kernel/Pictures".

It is possible to create several '''Stage View''' panels that are administrated with the '''Project Explorer'''. In this way you can split your devices or map different locations for your show.

To add devices or device groups in a '''Stage View''', let's move into the '''Project Explorer''' and drag&drop units into the respective '''Stage View'''. In the current betaversion it is not possible to drag&drop a device from the devices branch directly into the '''Live View''' window. Move it within the directory tree instead.

[[File:DMXC3L04 liveView.JPG|600px]]

The '''Stage View''' distinguishes in "single lamp" icons and "group" icons. If you select an group icon all following operational actions are applied to each group member item.

You can select a set of devices by drawing a frame around them (this is a kind of temporary group - please do not confuse this with the default groups) or by single selection holding the "CTRL" key. Marking such a set of devices can also be helpful for positioning the icons. With the "create group" button you can define permanent groups from the selection.

[[File:DMXC3L04 liveView groups.jpg]]

There are some helpful shortcuts helping to improve the assignment of icons in the '''Live View''' (moving and alignment of symbols). At first you have to select the device icons by drawing a frame or pressing the "STRG/CTRL" key (windows style selection).

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

By using the '''Show/Hide''' button you can choose which attributes are displayed near the icons (device name, selection number, intensity, ...).

==Excercise==
* Try to generate the same layout in the live view panel as shown above by shifting the icons
* Mark a subset of devices and align an operation with the property panels (press "Lumos" button at first in intensity panel to open shutter/dim up lamp)

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

[[de:Lektion_4_Tut3]]
[[en:Lesson_4_Tut3]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| zurückLink = Lesson_3_Tut3
| zurückText = Lesson 3
| hoch = [[Tutorials DMXControl 3|Table of content]]
| vorLink = Lesson_5_Tut3
| vorText = Lesson 5
}}

[[Kategorie:DMXControl 3]]

Lesson 4 Tut3

2013-01-06T19:32:19Z

Vrystyle: /* Excercise */ corrections

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

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_3_Tut3
| zurückText = Lektion 3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_5_Tut3
| vorText = Lektion 5
}}

==Overview==
This lesson introduces into the stage view panel - a minimal 2D visualisation tool which offers valueable support for programming your show.

==Lecture 4: The Live View (Stage View) ==

The '''Stage View''' is one of the several tools in the tool menue. When you create devices and/or groups, some (interactive) icons are automatically generated in the '''Stage View'''. You can move these icons to any place you want by dragging them with the mouse. In this way you can model your stage in 2D representation.

It could be helpful to load a background picture for better mapping your stage. Click on the background with right mouse button and choose "Edit Background". Additional background pictures can be inserted in the folder ".../DMMXControl3.0/Kernel/Pictures".

It is possible to create several '''Stage View''' panels that are administrated with the '''Project Explorer'''. In this way you can split your devices or map different locations for your show.

To add devices or device groups in a '''Stage View''', let's move into the '''Project Explorer''' and drag&drop units into the respective '''Stage View'''. In the current betaversion it is not possible to drag&drop a device from the devices branch directly into the '''Live View''' window. Move it within the directory tree instead.

[[File:DMXC3L04 liveView.JPG|600px]]

The '''Stage View''' distinguishes in "single lamp" icons and "group" icons. If you select an group icon all following operational actions are applied to each group member item.

You can select a set of devices by drawing a frame around them (this is a kind of temporary group - please do not confuse this with the default groups) or by single selection holding the "CTRL" key. Marking such a set of devices can also be helpful for positioning the icons. With the "create group" button you can define permanent groups from the selection.

[[File:DMXC3L04 liveView groups.jpg]]

There are some helpful shortcuts helping to improve the assignment of icons in the '''Live View''' (moving and alignment of symbols). At first you have to select the device icons by drawing a frame or pressing the "STRG/CTRL" key (windows style selection).

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

By using the '''Show/Hide''' button you can choose which attributes are displayed near the icons (device name, selection number, intensity, ...).

==Excercise==
* Try to generate the same layout in the live view panel as shown above by shifting the icons
* Mark a subset of devices and align an operation with the property panels (press "Lumos" button at first in intensity panel to open shutter/dim up lamp)

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

[[de:Lektion4]]
[[en:Lesson 4]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| zurückLink = Lektion_3_Tut3
| zurückText = Lektion 3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_5_Tut3
| vorText = Lektion 5
}}

[[Kategorie:DMXControl 3]]

Lesson 4 Tut3

2013-01-06T19:29:47Z

Vrystyle: /* Lecture 4: The live view (stage view) */ corrections

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

{{DMXC3_lesson/en}}
{{NavigationTop-Tut3
| zurückLink = Lektion_3_Tut3
| zurückText = Lektion 3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_5_Tut3
| vorText = Lektion 5
}}

==Overview==
This lesson introduces into the stage view panel - a minimal 2D visualisation tool which offers valueable support for programming your show.

==Lecture 4: The Live View (Stage View) ==

The '''Stage View''' is one of the several tools in the tool menue. When you create devices and/or groups, some (interactive) icons are automatically generated in the '''Stage View'''. You can move these icons to any place you want by dragging them with the mouse. In this way you can model your stage in 2D representation.

It could be helpful to load a background picture for better mapping your stage. Click on the background with right mouse button and choose "Edit Background". Additional background pictures can be inserted in the folder ".../DMMXControl3.0/Kernel/Pictures".

It is possible to create several '''Stage View''' panels that are administrated with the '''Project Explorer'''. In this way you can split your devices or map different locations for your show.

To add devices or device groups in a '''Stage View''', let's move into the '''Project Explorer''' and drag&drop units into the respective '''Stage View'''. In the current betaversion it is not possible to drag&drop a device from the devices branch directly into the '''Live View''' window. Move it within the directory tree instead.

[[File:DMXC3L04 liveView.JPG|600px]]

The '''Stage View''' distinguishes in "single lamp" icons and "group" icons. If you select an group icon all following operational actions are applied to each group member item.

You can select a set of devices by drawing a frame around them (this is a kind of temporary group - please do not confuse this with the default groups) or by single selection holding the "CTRL" key. Marking such a set of devices can also be helpful for positioning the icons. With the "create group" button you can define permanent groups from the selection.

[[File:DMXC3L04 liveView groups.jpg]]

There are some helpful shortcuts helping to improve the assignment of icons in the '''Live View''' (moving and alignment of symbols). At first you have to select the device icons by drawing a frame or pressing the "STRG/CTRL" key (windows style selection).

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

By using the '''Show/Hide''' button you can choose which attributes are displayed near the icons (device name, selection number, intensity, ...).

==Excercise==
* Try to generate the same layout in the live view panel as shown above by shifting the icons
* Mark a subset of devices and take place an operation with property panels (below, press at first "Lumos" button in intensity panel)

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

[[de:Lektion4]]
[[en:Lesson 4]]

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| zurückLink = Lektion_3_Tut3
| zurückText = Lektion 3
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_5_Tut3
| vorText = Lektion 5
}}

[[Kategorie:DMXControl 3]]

Lesson 3 Tut3

2013-01-06T18:31:36Z

Vrystyle: /* Device Groups */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

{{DMXC3_lesson/en}}

==Overview==

In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and patching fixtures==

The starting point for adding devices is the '''project explorer'''. Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. The administration is intuitive by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{BoxHint
|Text = The project explorer is the central project tree containing all elements of your project. It is primary intended to create and browse your items. For usage in the show programming we refer to "stage view" and other tools.
}}

[[File:DMXC3L03 projectExplorer.JPG|center]]

==Add devices==
In the following step we will create 4 moving lights of type "TS-255".

Click either on the button '''Device Manager''' in the menu bar of the Project Explorer or choose in the left pane of the Project Explorer the folder '''Devices''' and do a right mouse click into the right pane and select '''device manager'''.
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses.

[[File:DMXC3L03 createDevice.JPG|center|600px]]

===Device Groups===
By setting the hook for "autogenerate group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer.

[[File:DMXC3L03 createDeviceGroup.JPG|600px]]

When you do a right mouse click on an item the property menu appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or choose ''rename'' in the context menu (right mouse click).

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
* create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

[[de:Lektion_3_Tut3]]
[[en:Lesson 3]]
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

[[Kategorie:DMXControl 3]]

Lesson 3 Tut3

2013-01-06T18:27:38Z

Vrystyle: /* Certificate */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

{{DMXC3_lesson/en}}

==Overview==

In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and patching fixtures==

The starting point for adding devices is the '''project explorer'''. Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. The administration is intuitive by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{BoxHint
|Text = The project explorer is the central project tree containing all elements of your project. It is primary intended to create and browse your items. For usage in the show programming we refer to "stage view" and other tools.
}}

[[File:DMXC3L03 projectExplorer.JPG|center]]

==Add devices==
In the following step we will create 4 moving lights of type "TS-255".

Click either on the button '''Device Manager''' in the menu bar of the Project Explorer or choose in the left pane of the Project Explorer the folder '''Devices''' and do a right mouse click into the right pane and select '''device manager'''.
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses.

[[File:DMXC3L03 createDevice.JPG|center|600px]]

===Device Groups===
By setting the hook for "autogenerate group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer.

[[File:DMXC3L03 createDeviceGroup.JPG|600px]]

When you do a right mouse click on an item the property menu appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or the context menu.

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
* create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

[[de:Lektion_3_Tut3]]
[[en:Lesson 3]]
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

[[Kategorie:DMXControl 3]]

Lesson 3 Tut3

2013-01-06T18:26:00Z

Vrystyle: /* Certificate */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

{{DMXC3_lesson/en}}

==Overview==

In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and patching fixtures==

The starting point for adding devices is the '''project explorer'''. Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. The administration is intuitive by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{BoxHint
|Text = The project explorer is the central project tree containing all elements of your project. It is primary intended to create and browse your items. For usage in the show programming we refer to "stage view" and other tools.
}}

[[File:DMXC3L03 projectExplorer.JPG|center]]

==Add devices==
In the following step we will create 4 moving lights of type "TS-255".

Click either on the button '''Device Manager''' in the menu bar of the Project Explorer or choose in the left pane of the Project Explorer the folder '''Devices''' and do a right mouse click into the right pane and select '''device manager'''.
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses.

[[File:DMXC3L03 createDevice.JPG|center|600px]]

===Device Groups===
By setting the hook for "autogenerate group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer.

[[File:DMXC3L03 createDeviceGroup.JPG|600px]]

When you do a right mouse click on an item the property menu appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or the context menu.

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
* create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

[[de:Lektion 3]]
[[en:Lesson 3]]
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

[[Kategorie:DMXControl 3]]

Lesson 3 Tut3

2013-01-06T18:24:58Z

Vrystyle: /* Add devices */ corrections

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

{{DMXC3_lesson/en}}

==Overview==

In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and patching fixtures==

The starting point for adding devices is the '''project explorer'''. Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. The administration is intuitive by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{BoxHint
|Text = The project explorer is the central project tree containing all elements of your project. It is primary intended to create and browse your items. For usage in the show programming we refer to "stage view" and other tools.
}}

[[File:DMXC3L03 projectExplorer.JPG|center]]

==Add devices==
In the following step we will create 4 moving lights of type "TS-255".

Click either on the button '''Device Manager''' in the menu bar of the Project Explorer or choose in the left pane of the Project Explorer the folder '''Devices''' and do a right mouse click into the right pane and select '''device manager'''.
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses.

[[File:DMXC3L03 createDevice.JPG|center|600px]]

===Device Groups===
By setting the hook for "autogenerate group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer.

[[File:DMXC3L03 createDeviceGroup.JPG|600px]]

When you do a right mouse click on an item the property menu appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or the context menu.

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
* create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

[[de:Lektion 3]]
[[en:Lesson 3]]
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

[[Kategorie:DMXControl 3]]

Lesson 3 Tut3

2013-01-06T18:15:00Z

Vrystyle: /* Lecture 3: Creating and Patching fixtures */ corrections

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

{{DMXC3_lesson/en}}

==Overview==

In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and patching fixtures==

The starting point for adding devices is the '''project explorer'''. Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. The administration is intuitive by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{BoxHint
|Text = The project explorer is the central project tree containing all elements of your project. It is primary intended to create and browse your items. For usage in the show programming we refer to "stage view" and other tools.
}}

[[File:DMXC3L03 projectExplorer.JPG|center]]

==Add devices==
In following step we will create 4 moving lights of type "TS-255".

Click either on the button '' 'Device Manager''' in the menu bar of the Project Explorer or
you choose in the left pane of the Project Explorer the folder '''Devices''' and make a right mouse click into the right pane and select '''device manager'''.
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses.

[[File:DMXC3L03 createDevice.JPG|center|600px]]

===Device Groups===
By setting the hook for "autogenerate group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and to press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer.

[[File:DMXC3L03 createDeviceGroup.JPG|600px]]

By right mouse click the property menu for each item appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or the context menu.

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
* create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

[[de:Lektion 3]]
[[en:Lesson 3]]
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

[[Kategorie:DMXControl 3]]

Lesson 3 Tut3

2013-01-06T18:05:46Z

Vrystyle: /* Overview */ corrections

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

{{DMXC3_lesson/en}}

==Overview==

In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

==Lecture 3: Creating and Patching fixtures==

The starting point for creation of devices is the '''project explorer'''. Here you can find a tree of directories displaying the equipment and other items such as fixtures, devices, scene lists etc. The administration is intuitive by context menus (right mouse click) or buttons, e.g. for adding or deleting items.

Elements can also be moved by drag and drop or added to other elements. Whether an operation is allowed, is symbolized by the mouse icon.

{{BoxHint
|Text = The project explorer is the central project tree containing all elements of your project. It is primary intended to create and browse your items. For usage in the show programming we refer to "stage view" and other tools.
}}

[[File:DMXC3L03 projectExplorer.JPG|center]]

==Add devices==
In following step we will create 4 moving lights of type "TS-255".

Click either on the button '' 'Device Manager''' in the menu bar of the Project Explorer or
you choose in the left pane of the Project Explorer the folder '''Devices''' and make a right mouse click into the right pane and select '''device manager'''.
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses.

[[File:DMXC3L03 createDevice.JPG|center|600px]]

===Device Groups===
By setting the hook for "autogenerate group" a group element is created automatically containing all devices of this definition step.
You can also create "user defined groups". Therefore you have to select the devices (e.g. in '''project explorer''' or in '''Stage View''') and to press the "Create Device Group" button. Renaming of groups (and other items) also can be made within the project explorer.

[[File:DMXC3L03 createDeviceGroup.JPG|600px]]

By right mouse click the property menu for each item appears. Here you can set additional properties such as "device id", "enabled flag" etc.

In the '''Project Explorer''' you can also rename items by two single clicks on the name or the context menu.

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 2 generic dimmer (as front lights) and 8 RGB-PARs
* create two additional groups: all devices on left hand side and all devices on right hand side, rename these groups to "left" and "right"

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

[[de:Lektion 3]]
[[en:Lesson 3]]
{{NavigationTop-Tut3
| zurückLink = Lektion_2_Tut3
| zurückText = Lektion 2
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_4_Tut3
| vorText = Lektion 4
}}

[[Kategorie:DMXControl 3]]

Lesson 2 Tut3

2013-01-04T16:25:27Z

Vrystyle: /* Additional links and references */

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_1_Tut3
| zurückText = Lektion 1
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_3_Tut3
| vorText = Lektion 3
}}
{{DMXC3_lesson/en}}

==Overview==

In this lessons you will learn how to operate with the panel system of DMXControl 3.0. You can assign your panels in a flexible way and save and restore your favorite configurations.

==Lecture 2: The panel concept of the DMXControl 3 client==

DMXControl 3 provides a lot of tools and windows. For different use cases different designs will be in focus. Therefore DMXControl uses a very flexiblel panel mechanism. You can create your own individual panel configurations.
The forms in the program can be unlocked to float above the main window or can be docked to the top, bottom, left or right margins. This versatility gives you the power to build screens that are easy to use and tailored to your personal preference and to move panels to several monitors. Catch a form with the mouse pointer and move the pointer over one transparent arrow to dock the form at wanted places. A panel can also be set to occupy the left-over space in the middle.

[[File:DMXC3L02 PanelAssignment.jpg|center|600px]]

Some important explanations:

* A "floating" form is simply one that isn’t docked to any side.
* A pane or panel is a container for several forms.
* The docking suggestion is a symbol indicating the options where a form can be docked. It is available both in the main window and in each '''pane'''. The potential position of the form is indicated by a blue rectangle.
* Forms are created via the "Windows" system and are closed with the ‘X’ in its top right corner. This will close the form but leave other forms in a pane untouched.
* The (vertical) push-pin is the small pin icon that appears by default within docked forms that are shown permanently. Clicking the push-pin changes the forms status to hide-away form, i.e. the form becomes unpinned and disappeares, but a tab is created within the pane.
* pane splitting - a pane can be splitted into 2 visible panes
* pane sharing - several forms share a pane, but only the top one is displayed, the other ones are in status "auto hide"

===Panes===
A docking pane can accommodate more than one form. A pane is automatically created by docking more than one form. All forms contained are represented by a tab strip. Moving the mouse curser over the tab displays the form (but it doesn't get the focus). By clicking the tab the form is brought into front (with getting the focus).

There are several ways for releasing docking and getting a floating window:
* After creation a form is already floating
* Double-click on the blue or grey header bar of a docked form
* Double-click on the tab of a docked form
* Click, hold and drag on the header bar of a form
* Click, hold and drag on the tab of a form

Once a form is floating it can be dragged to be docked anywhere.

Even within a panel you have new docking suggestion points for pane splitting.

===Pane-splitting===
By dragging the floating window and positioning your mouse cursor near the pane you get an internal docking suggestion. You can get the two windows to split the space in half and see both, but with only half the space each. This can be done vertically or horizontally.
In the upper example (Picture 1) the floating window "Project Explorer" would share the space with the "Programmer" if you release the mousebutton.

===Pane Sharing===
As an alternative to pane-splitting, you can get your windows to share a space – they will share a single pane. You choose the form to be seen from the tabs displayed at the edge of the pane. Drag the floating form so that the mouse cursor is over the top of the form.
There are two slight variations on this, depending on the original form occupying the space. The form can be:
*Docked on the side
*Filling the spare space in the middle (a ‘Document’ form)

If you add more forms to the pane than there is room to display the tab, he left and right arrows become active and can be used to show the tabs that are hidden.

===Hideaway Forms===
When you click the push-pin at the top of the forms next to the close-down ‘X’, it falls over.
The form becomes ‘unpinned’ and appears to slide off the edge of the screen. The remaining screen re-arranges itself and the space previously taken by the hideaway form is shared out amongst the nearby forms.
(CHECK:::The push-pin applies to the PANE, not to a single window in it. When forms are sharing a pane they are hidden or revealed together./CHECK)

[[File:DMXC3L02 WindowsManager.JPG|center]]

In this panel configuration the left, right and bottom panel are used. The left panel is a splitted one. The right panel containes one auto-hide window (see tab strip). The Project Explorer window is floating.

===Auto-Hide===

DockPanel has an auto-hide feature that can be very useful.
If there is any auto hide window, DockPanel will display a tab strip on the out-most edge.
An auto hide window has 3 statuses:
*hide
*mouse-hover-display and
*click-display.
In hide status, only the tab is displayed. The window itself is completely hidden. That can preserve the valuable screen to display more information.

===Save/Restore Layout settings===

You can save and restore your individual layout setting by menu ''Settings->Layout''.

===Further information===
The handling of different panels is based on Dockpanel suite of Weifen Luo (also some text reused).
[http://www.codeproject.com/KB/miscctrl/DockManager.aspx]

==Excercise==
* Create a new form (Menu "Windows") and dock and relaese it at several positions
* Save and reload your own panel configuration

==Additional links and references==

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

[[de:Lektion 2]]
[[en:Lesson 2]]

__NOTOC__
__NOTITLE__

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

[[Kategorie:DMXControl 3]]

Lesson 2 Tut3

2013-01-04T16:23:55Z

Vrystyle: /* Lecture 2: The Panel concepts of DMXControl 3 client */ corrections

{{Hauptüberschrift
| logo = Im-aim.png
| ueberschrift = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| zurückLink = Lektion_1_Tut3
| zurückText = Lektion 1
| hoch = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| vorLink = Lektion_3_Tut3
| vorText = Lektion 3
}}
{{DMXC3_lesson/en}}

==Overview==

In this lessons you will learn how to operate with the panel system of DMXControl 3.0. You can assign your panels in a flexible way and save and restore your favorite configurations.

==Lecture 2: The panel concept of the DMXControl 3 client==

DMXControl 3 provides a lot of tools and windows. For different use cases different designs will be in focus. Therefore DMXControl uses a very flexiblel panel mechanism. You can create your own individual panel configurations.
The forms in the program can be unlocked to float above the main window or can be docked to the top, bottom, left or right margins. This versatility gives you the power to build screens that are easy to use and tailored to your personal preference and to move panels to several monitors. Catch a form with the mouse pointer and move the pointer over one transparent arrow to dock the form at wanted places. A panel can also be set to occupy the left-over space in the middle.

[[File:DMXC3L02 PanelAssignment.jpg|center|600px]]

Some important explanations:

* A "floating" form is simply one that isn’t docked to any side.
* A pane or panel is a container for several forms.
* The docking suggestion is a symbol indicating the options where a form can be docked. It is available both in the main window and in each '''pane'''. The potential position of the form is indicated by a blue rectangle.
* Forms are created via the "Windows" system and are closed with the ‘X’ in its top right corner. This will close the form but leave other forms in a pane untouched.
* The (vertical) push-pin is the small pin icon that appears by default within docked forms that are shown permanently. Clicking the push-pin changes the forms status to hide-away form, i.e. the form becomes unpinned and disappeares, but a tab is created within the pane.
* pane splitting - a pane can be splitted into 2 visible panes
* pane sharing - several forms share a pane, but only the top one is displayed, the other ones are in status "auto hide"

===Panes===
A docking pane can accommodate more than one form. A pane is automatically created by docking more than one form. All forms contained are represented by a tab strip. Moving the mouse curser over the tab displays the form (but it doesn't get the focus). By clicking the tab the form is brought into front (with getting the focus).

There are several ways for releasing docking and getting a floating window:
* After creation a form is already floating
* Double-click on the blue or grey header bar of a docked form
* Double-click on the tab of a docked form
* Click, hold and drag on the header bar of a form
* Click, hold and drag on the tab of a form

Once a form is floating it can be dragged to be docked anywhere.

Even within a panel you have new docking suggestion points for pane splitting.

===Pane-splitting===
By dragging the floating window and positioning your mouse cursor near the pane you get an internal docking suggestion. You can get the two windows to split the space in half and see both, but with only half the space each. This can be done vertically or horizontally.
In the upper example (Picture 1) the floating window "Project Explorer" would share the space with the "Programmer" if you release the mousebutton.

===Pane Sharing===
As an alternative to pane-splitting, you can get your windows to share a space – they will share a single pane. You choose the form to be seen from the tabs displayed at the edge of the pane. Drag the floating form so that the mouse cursor is over the top of the form.
There are two slight variations on this, depending on the original form occupying the space. The form can be:
*Docked on the side
*Filling the spare space in the middle (a ‘Document’ form)

If you add more forms to the pane than there is room to display the tab, he left and right arrows become active and can be used to show the tabs that are hidden.

===Hideaway Forms===
When you click the push-pin at the top of the forms next to the close-down ‘X’, it falls over.
The form becomes ‘unpinned’ and appears to slide off the edge of the screen. The remaining screen re-arranges itself and the space previously taken by the hideaway form is shared out amongst the nearby forms.
(CHECK:::The push-pin applies to the PANE, not to a single window in it. When forms are sharing a pane they are hidden or revealed together./CHECK)

[[File:DMXC3L02 WindowsManager.JPG|center]]

In this panel configuration the left, right and bottom panel are used. The left panel is a splitted one. The right panel containes one auto-hide window (see tab strip). The Project Explorer window is floating.

===Auto-Hide===

DockPanel has an auto-hide feature that can be very useful.
If there is any auto hide window, DockPanel will display a tab strip on the out-most edge.
An auto hide window has 3 statuses:
*hide
*mouse-hover-display and
*click-display.
In hide status, only the tab is displayed. The window itself is completely hidden. That can preserve the valuable screen to display more information.

===Save/Restore Layout settings===

You can save and restore your individual layout setting by menu ''Settings->Layout''.

===Further information===
The handling of different panels is based on Dockpanel suite of Weifen Luo (also some text reused).
[http://www.codeproject.com/KB/miscctrl/DockManager.aspx]

==Excercise==
* Create a new form (Menu "Windows") and dock and relaese it at several positions
* Save and reload your own panel configuration

==Additional links and references==
*

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

[[de:Lektion 2]]
[[en:Lesson 2]]

__NOTOC__
__NOTITLE__

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

[[Kategorie:DMXControl 3]]

Lesson 1 Tut3

2013-01-04T10:07:28Z

Vrystyle: /* Excercise */

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

==Excercise==

1) Please try following commands in command shell:
* menue
* status
* shutdown

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__

Lesson 1 Tut3

2013-01-04T10:05:50Z

Vrystyle: /* Project Management */ corrections and adaption to german description

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

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

Lesson 1 Tut3

2013-01-04T10:00:53Z

Vrystyle: /* The client */ corrections

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

You can save a project as a default project. If you use '''File -> New Project''', DMXControl will load your default project, which can be a project you already patched your fixtures. To save a project as a default project, goto '''File -> Save Project''' as, type the name "DefaultProject" and save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\". All project files are archived in a zip-file.

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__

Lesson 1 Tut3

2013-01-04T09:19:30Z

Vrystyle: /* Lecture: Installation and Configuration */ corrections

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

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. You can also select the Menu '''Connection-->Connect''' in order to connect with the server. When you start the client a connection window opens.

[[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. A click on the icon will open the Connection window.

Now you are able to load your project. DMXControl will provide a default demo project. You can open it with menue point '''File ->Open Project".

{{BoxHint
|Text=If you program the "Lumos.exe" when running the parameter "-nonetwork" are relaying, the kernel will boot automatically mitgestartet a client and connected directly to the kernel. This is you and you avoid the manual and connect the system to the start ready to go. From the Start menu when you install a link is generated that passes these parameters at startup. The link is called "DMXControl 3".
}}

===Project Management===

You can save a project as a default project. If you use '''File -> New Project''', DMXControl will load your default project, which can be a project you already patched your fixtures. To save a project as a default project, goto '''File -> Save Project''' as, type the name "DefaultProject" and save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\". All project files are archived in a zip-file.

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__

Lesson 1 Tut3

2013-01-04T08:44:12Z

Vrystyle: corrections

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

You can install DMXControl 3 by 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 with the installation of DMXControl 2 EasyView can be selected.

DMXControl 3.0 provides a distributed architecture, i.e. there is a server that can communicate with several clients. 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 is a Windows program. The client provides the interface between the server and the user. One or more clients can run on several systems (PCs) in parallel.
Thus, you can work in teams for implementing and performing your show. DMXControl 3.0 supports also cooperation during the life cycle, i.e. you can execute scene lists during your mate is still programming the missing cues!

The separation of the server and the client brings the following benefits:

* the kernel continues in case of malfunction in the user interface and continues 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, i.e. 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 have 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 launching 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
*xxx notification: Sends a notification to all clients
*xxx width: Specifies the width of the console fixed (number of characters)
*xxx load: Loading a project
*xxx save: 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 see Appendix 3.

===The client===

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. You can also select the Menu '''Connection-->Connect''' in order to connect with the server. When you start the client a connection window opens.

[[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. A click on the icon will open the Connection window.

Now you are able to load your project. DMXControl will provide a default demo project. You can open it with menue point '''File ->Open Project".

{{BoxHint
|Text=If you program the "Lumos.exe" when running the parameter "-nonetwork" are relaying, the kernel will boot automatically mitgestartet a client and connected directly to the kernel. This is you and you avoid the manual and connect the system to the start ready to go. From the Start menu when you install a link is generated that passes these parameters at startup. The link is called "DMXControl 3".
}}

===Project Management===

You can save a project as a default project. If you use '''File -> New Project''', DMXControl will load your default project, which can be a project you already patched your fixtures. To save a project as a default project, goto '''File -> Save Project''' as, type the name "DefaultProject" and save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\". All project files are archived in a zip-file.

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__

Tutorials DMXControl 3

2013-01-03T13:05:28Z

Vrystyle: /* Tutorial for DMXControl 3.0 */ Some corrections

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

{{DMXC3_lesson/en}}

=Tutorial for DMXControl 3.0=

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

The basic differences between the releases of DMXControl 3 and 2 are described in the german article http://www.dmxcontrol.de/wiki/Uebergang_von_DMXControl_2_zu_3 . It should be emphasized that DMXControl 2 will be maintained for some time and is provisionally proposed for usage as your main light control program.

Because of altered concepts the nature of the programming and operation has fundamentally changed. This requires that you start from the beginning again. We encourage you to study the following tutorial of the operating concepts of DMXControl 3 and to accept the changes. If you have understood the concepts, everything will be as common and simple as in DMXControl 2.

This tutorial is split into three parts:

* [[Lesson 1]] to 7: Basic concepts, setup and configuration
* [[Lesson 8]] to 14: Programming your cues and show
* [[Lesson 15]] to 21: Execution of show and add-ons

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

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

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

Now have fun in learning DMXControl 3!

= Table of content =

{| width=100%
| width="50%" valign=top |
[[Lesson_1_Tut3|Lesson 1: Installation and configuration]] 
[[Lesson_2_Tut3|Lesson 2: The Panel conzept of DMXControl 3 GUI]] 
[[Lesson_3_Tut3|Lesson 3: TheProject Explorer]] 
[[Lesson_4_Tut3|Lesson 4: The Stage view ]] 
[[Lesson_5_Tut3|Lesson 5: Device properties and its control ]] 
[[Lesson_6_Tut3|Lesson 6: Configuration of output plugins ]] 
[[Lesson_7_Tut3|Lesson 7: Summary and some more details of setup ]] 
[[Lesson_8_Tut3|Lesson 8: Cues and cue lists ]] 
[[Lesson_9_Tut3|Lesson 9: Fanning, Chasers and other effects ]] 
[[Lesson_10_Tut3|Lesson 10: The Programmer view ]] 
[[Lssson_11_Tut3|Lesson 11: Triggers in cue lists ]] 
[[Lesson_12_Tut3|Lesson 12: Edit of Cues and cue lists ]] 
[[Lesson_13_Tut3|Lesson 13: Presets ]] 
|valign=top |
[[Lesson_14_Tut3|Lesson 14: Summary and details - Programming ]] 
[[Lesson_15_Tut3|Lesson 15: Executors and use of cue lists ]] 
[[Lesson_16_Tut3|Lesson 16: Softdesk ]] 
[[Lesson_17_Tut3|Lesson 17: Audio analyser ]] 
[[Lession_18_Tut3|Lesson 18: Beamer Tool ]] 
[[Lession_19_Tut3|Lesson 19: Other DMX Clients ]] 
[[Lession_20_Tut3|Lesson 20: Create new device definitions ]] 
[[Lession_21_Tut3|Lesson 21: Summary and details for Execution ]] 
[[Lession_22_Tut3|Lesson 22: Input Assignment ]] 
[[Lession_23_Tut3|Lesson 23: Create a RGB Matrix]] 
[[Lession_24_Tut3|Lesson 24: Transfer DMX values via ArtNet to DMXControl 2]] 
[[Appendix_1_Tut3|Appendix 1: Commands and Shortcuts]] 
[[Appendix_2_Tut3|Appendix 2: Tipps for Testing and behaviot in error case]] 
|}

= Links & References =
{| width=100%
| width="150px" valign=top | '''Videos:'''
| [[DMXControl_3.0_-_Videos|DMXControl 3.0 - Videos]]
|-
|'''FAQs:'''
| [[DMXControl_3.0_(FAQ)|DMXControl 3.0 (FAQ)]]
|-
|'''more infos:'''
| [[Uebergang_von_DMXControl_2_zu_3|Uebergang von DMXControl 2 zu 3]]
|}

Thanks for using DMXControl and working with this tutorial.

www.dmxcontrol.org

Now, let's start with
[[Lesson 1]] Tut3

[[de:Tutorials DMXControl 3]]
[[en:Tutorials DMXControl 3]]

__NOTOC__
__NOTITLE__

[[Category: DMXControl 3]]

Lesson 1 Tut3

2013-01-03T12:13:42Z

Vrystyle: /* Certificate */

{{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 of changed operating concept compared to DMXControl 2 a fundamental rethink in the use of DMXControl 3 is necessary. These lessons will help you to become familiar with this concept and provide the skills necessary on the basic characteristics of the new user interface. Here at the beginning a preview as a taste of what awaits you:

{{Bild_mit_Unterschrift |DMXC3 Overview.jpg|1|Auswahl von Fenstern von 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==

You can install DMXControl 3 by 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 with the installation of DMXControl 2 EasyView can be selected.

DMXControl 3.0 provides a distributed architecture, i.e. there is a server that can communicate with several clients. 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 is a Windows program. The client provides the interface between the server and the user. One or more clients can run on several systems (PCs) in parallel.
Thus, you can work in teams for implementing and performing your show. DMXControl 3.0 supports also cooperation during the life cycle, i.e. you can execute scene lists during your mate is still programming the missing cues!

The separation of the server and the client brings the following benefits:

* the kernel continues in case of malfunction in the user interface and continues 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, i.e. 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 have 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 launching 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
*xxx notification: Sends a notification to all clients
*xxx width: Specifies the width of the console fixed (number of characters)
*xxx load: Loading a project
*xxx save: 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 see Appendix 3.

===The client===

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. You can also select the Menu '''Connection-->Connect''' in order to connect with the server. When you start the client a connection window opens.

[[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. A click on the icon will open the Connection window.

Now you are able to load your project. DMXControl will provide a default demo project. You can open it with menue point '''File ->Open Project".

{{BoxHint
|Text=If you program the "Lumos.exe" when running the parameter "-nonetwork" are relaying, the kernel will boot automatically mitgestartet a client and connected directly to the kernel. This is you and you avoid the manual and connect the system to the start ready to go. From the Start menu when you install a link is generated that passes these parameters at startup. The link is called "DMXControl 3".
}}

===Project Management===

You can save a project as a default project. If you use '''File -> New Project''', DMXControl will load your default project, which can be a project you already patched your fixtures. To save a project as a default project, goto '''File -> Save Project''' as, type the name "DefaultProject" and save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\". All project files are archived in a zip-file.

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__

Lesson 1 Tut3

2013-01-03T12:13:14Z

Vrystyle: /* Excercise */ Replaces "Shut up" with "exit"

{{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 of changed operating concept compared to DMXControl 2 a fundamental rethink in the use of DMXControl 3 is necessary. These lessons will help you to become familiar with this concept and provide the skills necessary on the basic characteristics of the new user interface. Here at the beginning a preview as a taste of what awaits you:

{{Bild_mit_Unterschrift |DMXC3 Overview.jpg|1|Auswahl von Fenstern von 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==

You can install DMXControl 3 by 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 with the installation of DMXControl 2 EasyView can be selected.

DMXControl 3.0 provides a distributed architecture, i.e. there is a server that can communicate with several clients. 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 is a Windows program. The client provides the interface between the server and the user. One or more clients can run on several systems (PCs) in parallel.
Thus, you can work in teams for implementing and performing your show. DMXControl 3.0 supports also cooperation during the life cycle, i.e. you can execute scene lists during your mate is still programming the missing cues!

The separation of the server and the client brings the following benefits:

* the kernel continues in case of malfunction in the user interface and continues 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, i.e. 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 have 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 launching 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
*xxx notification: Sends a notification to all clients
*xxx width: Specifies the width of the console fixed (number of characters)
*xxx load: Loading a project
*xxx save: 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 see Appendix 3.

===The client===

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. You can also select the Menu '''Connection-->Connect''' in order to connect with the server. When you start the client a connection window opens.

[[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. A click on the icon will open the Connection window.

Now you are able to load your project. DMXControl will provide a default demo project. You can open it with menue point '''File ->Open Project".

{{BoxHint
|Text=If you program the "Lumos.exe" when running the parameter "-nonetwork" are relaying, the kernel will boot automatically mitgestartet a client and connected directly to the kernel. This is you and you avoid the manual and connect the system to the start ready to go. From the Start menu when you install a link is generated that passes these parameters at startup. The link is called "DMXControl 3".
}}

===Project Management===

You can save a project as a default project. If you use '''File -> New Project''', DMXControl will load your default project, which can be a project you already patched your fixtures. To save a project as a default project, goto '''File -> Save Project''' as, type the name "DefaultProject" and save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\". All project files are archived in a zip-file.

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 have 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__