English DMXC-Wiki - User contributions [en]

Tutorials DMXControl 3

2012-05-24T19:54:47Z

Julien:

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

{{DMXC3_lesson/en}}

=Tutorial for DMXControl 3.0=

This is the first version of the tutorial for the brand new software DMXControl 3.0.

DMXControl 3.0 provides some new concepts such as "hardware abstraction layer" (HAL) for DMX fixtures, new group and effect concepts and a separation into server and client. Therefore a new tutorial is required too.

On the other hand there are lots of differences in comparision to DMXControl 2.x (see German article http://www.dmxcontrol.de/wiki/Uebergang_von_DMXControl_2_zu_3 ). Shortly summarized, DMXControl 3 supports modern lighting concepts, but there are still some gaps related to DMXControl 2.x, because it takes time to re-implement all popular features of DMXControl 2.x.

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

Thanks for using DMXControl and working with this tutorial.

www.dmxcontrol.org

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

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

__NOTOC__
__NOTITLE__

Tutorials DMXControl 3

2012-05-24T19:54:08Z

Julien: moved Preamble to Tutorials DMXControl 3

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

{{DMXC3_lesson/en}}

=Tutorial for DMXControl 3.0=

This is the first version of the tutorial for the brand new software DMXControl 3.0.

DMXControl 3.0 provides some new concepts such as "hardware abstraction layer" (HAL) for DMX fixtures, new group and effect concepts and a separation into server and client. Therefore a new tutorial is required too.

On the other hand there are lots of differences in comparision to DMXControl 2.x (see German article http://www.dmxcontrol.de/wiki/Uebergang_von_DMXControl_2_zu_3 ). Shortly summarized, DMXControl 3 supports modern lighting concepts, but there are still some gaps related to DMXControl 2.x, because it takes time to re-implement all popular features of DMXControl 2.x.

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

Thanks for using DMXControl and working with this tutorial.

www.dmxcontrol.org

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

[[de:Vorwort]]
[[en:preamble]]

__NOTOC__
__NOTITLE__

MediaWiki:Sidebar

2012-05-24T19:53:45Z

Julien:

MediaWiki:Sidebar

2012-05-24T19:42:15Z

Julien:

Manual DMXControl 3

2012-05-24T19:41:55Z

Julien: Created page with "__NOTITLE__ {{Hauptüberschrift | logo = Books.png | ueberschrift = Manual DMXControl 3 }} TBD de:Handbuch DMXControl 3 en:Manual DMXControl 3"

__NOTITLE__
{{Hauptüberschrift
| logo = Books.png
| ueberschrift = Manual DMXControl 3
}}

TBD

[[de:Handbuch DMXControl 3]]
[[en:Manual DMXControl 3]]

Manual DMXControl 2

2012-05-24T19:41:04Z

Julien: Created page with "__NOTITLE__ {{Hauptüberschrift | logo = Books.png | ueberschrift = Manual DMXControl 2 }} TBD de:Handbuch DMXControl 2 en:Manual DMXControl 2"

__NOTITLE__
{{Hauptüberschrift
| logo = Books.png
| ueberschrift = Manual DMXControl 2
}}

TBD

[[de:Handbuch DMXControl 2]]
[[en:Manual DMXControl 2]]

MediaWiki:Sidebar

2012-05-24T19:39:51Z

Julien:

Tutorials DMXControl 3

2011-06-26T18:13:26Z

Julien:

Lesson 2 Tut3

2011-06-26T16:48:04Z

Julien:

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

{{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 concepts of DMXControl 3 client==

DMXControl 3 provides a lot of tools and windows. For different use cases different forms 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 left to float above the main window or can be docked to the top, bottom, left or right margins. This versatility give you the power to build screens that are easy to use and tailored to your personal preference. Catch a form with the mouse pointer and move the pointer over one transparent arrow to dock the form at wanted place. A form can also be made to occupy the left-over space in the middle.

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

Some important explanations:
* A floating form is simply one that isn’t docked to any side.
* A pane 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 as else in each pane. The potential position of the form is indicated by a blue rectangle.
* Forms are created via the "Windows" menu and closed with the ‘X’ in its top right corner. This will shut the form down but leave other forms in its 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 a 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 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.

===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 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, the 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 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:DMXC30 WindowsManager3.JPG]]

In this panel configuration the left, right and buttom panel are used. The left panel is a splitted one. The right panel containes 3 auto-hide windows (see tab strip). The Live view window is floating.

===Auto-Hide===
DockPanel has an auto-hide feature that enables valuable screen real estate to be preserved.
If there is any auto hide window, DockPanel will display a tab strip on the out-most edge.
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.

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

'''topics to do be added (by beta testers)'''
* describe how to save a panel configuration
* add screenshots
* show examples

==Excercise==
* Create a new form (Menu "Windows") and dock and relaese it at several positions
* Save and reload a 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__

MediaWiki:Sidebar

2011-06-24T18:55:51Z

Julien:

MediaWiki:Sidebar

2011-06-24T18:51:11Z

Julien:

Tutorials

2011-06-24T18:50:06Z

Julien: moved Dokumentation:Tutorials to Tutorials

__NOTITLE__
{{Hauptüberschrift
| logo = Books.png
| ueberschrift = Tutorials
}}

MediaWiki:Sidebar

2011-06-24T17:44:22Z

Julien:

Article in English

2011-06-24T17:19:28Z

Julien: Protected "Article in English" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

This is no article.

Only for demonstration.

Article in English

2011-06-24T17:19:16Z

Julien: Created page with "This is no article. Only for demonstration."

This is no article.

Only for demonstration.

Lesson 1 Tut3

2011-06-24T16:53:08Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==

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.0 provides a distributed architecture, i.e. there is a kernel that can communicate with several clients. The kernel runs basically on Windows operating system, but can also be launched on Linux (with Mono).

One or multiple clients can be started on different systems (Windows, iOS, Android). Thus, you can even 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 server and clients provides some 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 "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|600px]]

There are some command options in the command line mode for getting detailed information on the status of the kernel:

* shutdown: Shut down the kernel.
* status: Displays information about the status
* menu: Access to control menu
* clear: Clears the console
* notification: Send a notification to all clients
* width: Defines width of console (number of characters)
* help: Help menu (also accessible via "?")

Additional second level menu commands exists for "menu" and "status".

===The client===

In next step you should start the Windows based GUI client (currently called "LumosGUI.exe"). This client will be explained in next lectures. At first you have to select the "Tools->Connection" panel in order to connect with the server.

[[File:DMXC3L01 connect.JPG]]

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

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

After establishing the connection you should see a small icon in the lower line of the client indicating the existing connection.

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

===Project Management===

You can save a project as a default project. If you use Project -> 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 Project -> Save Project as, type the name "DefaultProject" an save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\"

'''topics to be added (by beta testers)'''
* how to save a project
*

==Excercise==

1) Please try following commands in command shell:
* menue
* status
* shutdown -> uups!

2) Restart kernel and GUI and connect your client with DMXControl server.

Congratulation! Now you have successfully installed your own DMXControl configuration!

==Assumptions for installation==

DMXControl 3.0 requires following software to be installed before executing the setup program:

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

==Known Issues==

===GUI Elements display glitches===
This could look like shown below:
Also if you move windows it happens that thay are not displayed correct.

[[File:Dmxc_3_menu_errors.jpg]]

This can occur if you have a NVidia graphics card and use an old driver version.

I experienced this issue with a GeForce G 103M Driver Version 258.96 + PhysX 09.10.0513 on Windows XP x86_64.

Consider updating the driver to the latest version. Version 266.58 + PhysX 09.10.0514 is known to work.

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

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

__NOTOC__
__NOTITLE__

Template:Stub

2011-06-24T16:51:02Z

Julien:

<div id="Vorlage_Stub" style="border: 1px solid #CCCCCC; background-color: #F8F8F8; border-left: 5px solid #AAAAAA; font-size: 95%; padding: 10px 7px;"><span style="float: left; padding-right: 10px;">[[File:pencil.png]]</span>
This arcticle is very '''short''' and possibly as regards content still '''incomplete'''. Please help us<span class="hidereg">: [[Special:Userlogin|Sign up]] or [[Special:Userlogin|log in]]</span>, '''[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} edit]''' and complete the article and remove this note afterwards. <span style="font-size: 80%;">([[Help:First Steps|Editing help]].)</span></div>

Appendix 1 Tut3

2011-06-24T16:37:49Z

Julien:

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

{{DMXC3_lesson/en}}

==Summary of commands and shortcuts==

There are some command options in the command line mode for getting detailed information on the status of the kernel:

* shutdown: Shut down the kernel.
* status: Displays information about the status
* menu: Access to control menu
* clear: Clears the console
* notification: Send a notification to all clients
* width: Defines width of console (number of characters)
* help: Help menu (also accessible via "?")

Additional second level menu commands exists for "menu" and "status".

===linear fanning===

{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || linear interpolation
|-
| <> || 50 <> 100 || linear interpolation: marginal devices: 100, central devices 50
|-
| >< || 50 >< 100 || contrary: marginal devices: 50, central devices 100
|}

=== alternate fanning ===

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

=== Fanning in property grid with mouse wheel===

{| class="wikitable"
|-
! Key !! Value !! Description
|-
| no key pressed || +1 / -1 || dedicated color changes value
|-
| Shift || +10 / -10 || dedicated color changes value
|-
| STRG || +1 & -1 || Fanning / values are changed, z.B.118 > 154
|-
| ALT || +1 / -1 || values are changed
|-
| Shift+STRG || +10 / -10 || values are changed
|-
| Shift+ALT || +10 & -10 || values are changed in block
|}

=== effect parameters ===

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

===LiveView===

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

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

__NOTOC__
__NOTITLE__

Lesson 22 Tut3

2011-06-24T16:33:53Z

Julien:

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

{{DMXC3_lesson/en}}

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

==Hints for beta testers ==

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

==Excercise==
* Create ...
*

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

Lesson 21 Tut3

2011-06-24T16:32:38Z

Julien:

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

{{DMXC3_lesson/en}}

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

__NOTOC__
__NOTITLE__

Lesson 20 Tut3

2011-06-24T16:31:41Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
In this lesson we will learn how to create and add new device definitions. You need to do this acivity only, if your device is not yet defined in the default set of DMXControl 3 device definitions.

==Lecture 20: Create new device definitions ==

A device definition file (short: DDF) is used to inform DMXControl about the properties of a device. A DDF is wiritten in XML language and stored in the path
<DMXControl program path>\kernel\devices

If you are familar with DDFs of DMXControl 2.0 you will see some important differences:
* There is no GUI description part, because DMXControl 3 doesn't provide the device context menues
* Sone syntax elements are very similar (esp. in information part), i.e. you can reuse the existing DDFs
* The function part is much more abstract: You make the definition mainly by properties and not by DMX channels

Currently there is no "DDF creator" available fpr DMXControl 3, we recommend to use a text editor or XML editor tool. (Hint: We need support for adaption of an existing DMXControl 2 php tool towards DMXControl 3)

At first lets have a view to a very simple DDF ("Generic RGB Par"):

<source lang="xml">
01 <?xml version="1.0" encoding="utf-8" ?>
02 <device image="bild" type="DMXDevice">
03 <information>
04 <modell>Generic RGB PAR</modell>
05 <vendor>Generic</vendor>
06 <author>Arne Luedtke</author>
07 </information>
08 <functions>
09 <rgb>
10 <red dmxchannel="0" />
11 <green dmxchannel="1" />
12 <blue dmxchannel="2" />
13 </rgb>
14 </functions>
15 </device>
</source>

Line 01 is mandatory default line for describing the XML version.
Lines 02 and 15 provide the frame for the device definition that contains of two parts:
* information part (lines 03 to 07), no need for further explanation.
* function(property) specification part (lines 08 to 14)

The example device posesses one property: RGB colar mode. The mapping to DMX channels is described in lines 10 to 12.

Thats all!

Following table shows the existing properties:

{| class="wikitable"
! Property
! Description
! Comment
|-
| switch
| fixture has a switch channel
| <switch dmxchannel="0" />
|-
| dimmer
| fixture has a dimmer channel
| <dimmer dmxchannel="0" />
|-
| fog
| fod property
| <fog dmxchannel="0" />
|-
| shutter
| fixture has a shutter
| <shutter dmxchannel="4" />
|-
| strobe
| fixture has a strobe channel
| <strobe dmxchannel="7" />
|-
| rgb
| fixture uses RGB color mode
|<red dmxchannel="0" />
<green dmxchannel="1" />
<blue dmxchannel="2" />
|-
| position
| fixture has pan/tilt control
| <position>
<pan dmxchannel="0" >
<range range="170" />
</pan>
<tilt dmxchannel="1" >
<range range="110" />
</tilt>
|-
| color wheel
| fixtures contains color wheel
| <colorwheel dmxchannel="2"/>
|-
| gobo wheel
| fixtures contains gobo wheel
| <gobowheel dmxchannel="2"/>
|-
|}

The different intervals in a DMX channel are defined by the "step" tag:
<source lang="xml">
<step val="0" mindmx="0" maxdmx="127" />
<step val="100" mindmx="128" maxdmx="255" />
</source>

or:

<source lang="xml">
<step type="color" val="#FFFFFF" caption="Weiß" mindmx="0" maxdmx="31" />
<step type="color" val="#FF0000" caption="Rot" mindmx="32" maxdmx="63" />
</source>

'''topics to be added (by beta testers)'''
* Please complete the description
* During the beta test there is no upload capability for new DDFs. This topic must be updated.

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

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 19 Tut3

2011-06-24T16:28:11Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
In this lesson some additional clients are in focus. The client/server concept of DMXControl allows the connection to other clients (Smartphones, Tabs, etc.) in simple way.

==Lecture 19: Further DMXControl clients ==

in development:

* [http://www.dmxcontrol.de/wiki/Projekte/DMXControl-for-Android-Projekt DMXControl-for-Android-Projekt]
* [http://www.hexler.net TouchOSC]

Both smartphone apps (clients) communicate via OSC with DMXControl 3.
Therefore you have to enable the OSC plugin via "plugin manager", see following figure:

[[Datei:DMXC3L19_OSC1.JPG]]

Now, you should define the IP connection in the panel "connection form". Press the "+" button to create a new connention.
In the first approach we use unicast with UDP. Please let the IP address on 0.0.0.0, but set the correct port where your client sends the OSC messages. Now you can start (activate) this connection by a click to start button:

[[Datei:DMXC3L19_OSC2.JPG]]

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

==Excercise==
* Create ...
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 18 Tut3

2011-06-24T16:26:54Z

Julien:

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

{{DMXC3_lesson/en}}

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

==Lecture 18: Multimedia Support ==

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

description: to be done!

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

==Excercise==
* Create ...
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 17 Tut3

2011-06-24T16:25:48Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
ArtNet is not yet supported. But this is an urgent topic. Therefore we have a high ranking for this feature.

==Lecture 17: ArtNet ==

ArtNet is not yet supported.

It could be very helpful for interworking between DMXControl 3 and DMXControl 2.x. In this way you could use DMXControl 2.x as gateway, if your DMX sender is not supported by DMXControl 3 , but it is by DMXControl 2.x.

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

==Excercise==
* Create ...
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 16 Tut3

2011-06-24T16:22:12Z

Julien:

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

{{DMXC3_lesson/en}}

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

==Lecture 16: Softpult ==

The Softpult (Softdesk) tool can be enabled via the plugin manager, see [[Einsteiger:Lesson6/en]]. Afterwards you can find a new menu entry "Softdesk" within the plugins menu. When you open this plugin an administration GUI appears at first:

[[Datei:DMXC3L16 SoftDesk plugin.JPG]]

Here you can create, delete, edit, copy, import and export your instancies of softdesks. At runtime you can activate several instancies of softpults in parallel (but you don't have several banks within a softpult available).

When you select the design mode (edit mode) you can add your favorite elements from the set of sliders, buttons, rotary faders or XYpads. There are also graphical design elements such as labels, separators and group boxes available. Try it, also the design grid mode!

Here you can see one possible result:

[[Datei:DMXC3L16 SoftDesk.JPG]]

You can customize the elements in design mode by using the property context menu. The following figure shows the property box for a button (right mouse click in design mode). For example you can modify the button name, colors and the toggle mode property.

[[Datei:DMXC3L16 CommandboxProperties.JPG]]

The softpult windows are integrated into the panel system, see [[Einsteiger:Lesson2/en]]. That means you can have attached panels or flying windows.

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

This has to be performed with the input assignment panel. On left hand side you find the controls, on right hand side the DMXControl explorer is shown. Simply drag and drop the control elements to certain properties, attributes or elements to make a connection.

[[Datei:DMXC3L16 SoftDeskInputAssignment.JPG]]

'''topics to be added (by beta testers)'''
* complement this text

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

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 15 Tut3

2011-06-24T16:18:40Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
In this lesson we learn how to execute our scene list(s).

==Lecture 15: Working with (multiple) scene lists ==

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

The most important means are the three big buttons in the scene list panel:

* Go Next
* GO Back
* Pause list

The functionality is as expected by the name of the buttons ;)

[[Datei:DMXC3L08 FirstScene.JPG]]

Nevertheless, lets tell us some additional hints ...

tbc.....

* Intensity
* Scene list Speed
* Effect Speed

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

[[Datei:DMXC3L12 SL modemenue.jpg]]

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

==Excercise==
* Create ...
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 14 Tut3

2011-06-24T16:07:10Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
In this lesson we explain ....

==Lecture 14: Summary - programming ==

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

==Excercise==
* Try to generate
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 13 Tut3

2011-06-24T16:05:19Z

Julien:

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

{{DMXC3_lesson/en}}

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

==Lecture 13: Presets ==

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

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

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

[[Datei:DMXC3L13 Preset.jpg]]

===Recording Presets===

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

===Modifying Presets===

If you want to modify an existing preset, select the preset you want to modify and click on the arrow right of the "Store Preset" Button. A menu will pop up, where you can choose how to modify the preset. Options are explained in the following

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

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

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

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

===Deleteing Presets===

You can delete existing presets by selecting the preset you want to delete and then press Delete or in the presets window use Edit -> Delete Preset

===Applying Presets===

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

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

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

===Applying Selected Properties of Presets===

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

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

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

===Applying Multiple Presets to All or Selected Fixtures===

TODO

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

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

===Shortcuts===

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

===TODO===

*TODO: some paragraphs sound odd, going to change that later ...
*TODO: add some better explanation what presets are.

==Excercise==
* Create some presets and use it in your scene list
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 12 Tut3

2011-06-24T16:03:58Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
In this lesson we explain advanced edit features for scenes and scene lists, e.g. for modification of already saved scenes.

==Lecture 12: Editing scenes and scenelists ==

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

[[Datei:DMXC3L12 SL.JPG]]

By default a new scene is added to an existing scene list by pressing the button "Store 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]]

'''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 || remove a property from selected scene || hint: modify the wanted property so that this appears in the programmer
|-
| Update || Strg+U || no function yet ||

|}

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.

[[Datei:DMXC3L12 SL editmenue.jpg]]

Again, here is the summarizing table for explanation:

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| 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"
|-
| Copy content || Strg+Alt+C || to copy single value || like EXCEL "copy cell"
|-
| Paste content || Strg+Alt+V || tp paste single value || like EXCEL "paste cell"

|}

'''Example:''' You have a scene list containing 10 cues. You set fade=2sec in first scene and want to take over thies value to the remaining cues:

* mark fade cell of first scene,
* select menue "copy content",
* mark the fade cells of other cues,
* select menue "paste content",
* ready!

[[Datei:DMXC3L12 SL optionmenue.jpg]]

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

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

==Additional links and references==
*

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

Lesson 11 Tut3

2011-06-24T16:01:57Z

Julien:

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

{{DMXC3_lesson/en}}

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

==Lecture 11: Trigger in scene lists ==

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

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

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

[[Datei:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (opt) 3 || use GO to fade in next cue
optional: fade in cue after 3 GO presses, default is 1
|-
| follow || 5s || wait until the cue is faded in, then the countdown is started
|-
| wait || 5s || countdown starts when the previous cue fades in
|-
| timecode || 00:26:05 || expects external timecode information
|-
| rtc || ?? || ??
|-

| beat || (opt) 3 || connect in Input Layer panel the "manual beat" output per Drag & Drop with "Beat" input of scene list
optional: fade in cue after 3 beats, default is 1
|}

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

''Hint:'' Type in combined time information without "blank" character, e.g. 1m20s

[[Datei:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the timecode selection.

[[Datei:DMXC3L11 triggerhelpcontext.JPG]]

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

'''topics to be added (by beta testers)'''
* What about "rtc"?
* Example for external timecode usage
* How to configure "beat"?

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

==Additional links and references==
*

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

[[Datei:001DMXCTreffen DMXC3Trigger.jpg|300px]]

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

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

__NOTOC__
__NOTITLE__

Lesson 10 Tut3

2011-06-24T15:59:07Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
This is an optional lesson for expert users. Here we explain the "programmer view" - a tool that helps to "debug" your show programming.

==Lecture 10: The programmer view ==

The programmer is a helpful tool during programming your show. It logs all modifications you have made and shows the current content of the "cue buffer". Let's illustrate this by an example. We make following actions:

* at first we open the moving lights shutters and select the color green
* secondly, we set the group of front lights to 50% brightness
* thirdly, all RGB Pars are set to color X
* finally, the RGB Pars 3 and 6 are set to color Y

[[Datei:DMXC3L10 liveviewProgrammer.JPG]]

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

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

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

'''topics to be added (by beta testers)'''
* Are there further operations with programmer?

==Excercise==
* Repeat the above scenario
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 9 Tut3

2011-06-24T15:52:00Z

Julien:

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

{{DMXC3_lesson/en}}

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

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

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

===Fanning===

The first mechanism is fanning.

Fanning means from technical point of view to split a value oder domain to a group of devices. We distinguish between linear and alternate fanning, see following tables explaining the syntax element.

====linear fanning====

{| class="wikitable"
|-
! Syntax !! Example !! Description
|-
| > || 50 > 100 || linear interpolation
|-
| <> || 50 <> 100 || linear interpolation: marginal devices: 100, central devices 50
|-
| >< || 50 >< 100 || contrary: marginal devices: 50, central devices 100
|}

=== 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 ends.

[[Datei: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 result in property grid:

[[Datei: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%).

[[Datei:DMXC3L09 Fanning alternate.JPG]]

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

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

=== Effects and attachables ===

With fanning you can create static cues. The attachables panels provides some effects that can be used for dynamic changes within a cue.

'''Remember: '''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%) 

Let's have an example: You want to have a blinking effects with all frontlight lamps with lowest brightness for the central devices.

Here we will use the "attachable" pannel showing some effects such as "Sinus", Trapezoid", "Sawtooth" etc. Per drag&drop we can load the Sinus effect to the dimmer attribute within property grid.

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

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

Try it!

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

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

<br>'''Tipp''': By fanning the offset you get interesting chasers.

In order to illustrate the power of this concept we have listed following use cases for you:

{| class="wikitable FCK__ShowTableBorders"
|-
! Use case
! Visual effect description
! Amplitude
! Offset
! Phase
! Frequency
|-
|Jump Effect: Dimmer should slowly fade to 0 and will jump to full value
|set dimmer to 100, drag sawtooth effect to dimmer attribute
| -100
|
|
|
|-
|}

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

* add some additional use cases

==Excercise==
* Try to apply fanning to moving lights. That rocks! ;)
*

==Additional links and references==
*

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

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

__NOTOC__
__NOTITLE__

Lesson 8 Tut3

2011-06-24T15:34:34Z

Julien:

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

{{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 ==
Each scene needs a "host container"- that's a scene list. Therefore you have to create at first one or more scene lists by clicking the button "Create scenelist" which you can find in the project explorer main menu. Of course, the created scene list will appear in the folder "Scene list".

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

You can open this new scene list with a '''double click''' on the object in the project explorer or using the context menu item "open". Next step is to create a new scene. For creating a new cue we will change the color of the moving lights to "red" (please open the shutter too) and we turn on the two middle front lights.

[[Datei:DMXC3L08 changeLiveView.JPG]]

Return to the scene list panel and press the '''Store cue''' button. At first the programmer filter tool will appear where you can manually influence which devices and which attributes should be really taken over into the new scene. Typically you can confirm without modification.

[[Datei:DMXC3L08 programmerFilter.JPG]]

The result is your first cue (scene) in your scene list. You should change the name of the cue thus you can remember laterly what is the reason and target of this cue (e.g. "First Scene", "Start cue", "ML to red", etc.)

[[Datei:DMXC3L08 FirstScene.JPG]]

You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button
[[Datei: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 status of scene during execution of scene list
| 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
|-
| Delay
| fanning for fades
| see lesson 9
|-
| Act.
| is this cue active or should it be ignored?
| default: active
|-
| Ap.
| Autoprepare (not yet implemented)
| default: active
|-
| Comment
| for free use, insert explaining words
|
|-
|}

In the same way you can create some more cues and store it in the scene list.

[[Datei:DMXC3L08 SecondScene.JPG]]

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

In 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, beacause the longest action is the color fade: delay 1s + fade 5s.

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

[[Datei: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.

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

==Excercise==
* Generate your own cues
* Try the buttons "All", "Clear" and "Selected" in the programmer filter
* Work with different fade times

==Additional links and references==
*

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

Lesson 7 Tut3

2011-06-24T15:00:34Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==
In this lesson a final overview about the basic concepts for using the DMXControl 3 software is given. This finalises 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.

There are lots of additional buttons in the main menu for operational support:
* Clear -
* Test -
* Output Mode -
* Fog -
* Highlight -
* Blind -
* Save -
* Clear selection -
* Select All -
* Shuffle -
* Next fixture -

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

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

One helpful tool is missing for basic checks and settings of DMX channels: the 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 selected channel.

[[Datei: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 Blind mode
*

==Additional links and references==
*

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

Lesson 6 Tut3

2011-06-24T14:54:33Z

Julien:

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

{{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 "windows" you can find the panel "output devices". There you can select your DMX transmitter/sender by setting the hook.

'''Hint:''' in the current beta version only the DMX Interface from "Digital Enlightenment" is supported. 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.11.

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

In the settings menu another dialog for interface configuration is included:

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

Here you can make fine tuning and configuration setting that are supported by your DMX transmitter. In the shown case you can modify e.g. break time if the DMX receiver in one of your lamps requires a greater value.

'''topics to be added (by beta testers)'''
* other supported interfaces
* how to load an external interface (where to place the dll etc.)

==Excercise==
* Activate and configure your DMX transmitter
*

==Additional links and references==
*

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

Lesson 5 Tut3

2011-06-24T13:33:47Z

Julien:

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

{{DMXC3_lesson/en}}

==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 liveview, see previous lesson.
You can set properties of the selected devices by means of the "property panels".
Simply click to a color or select a gobo within the beam panel. Of course, you shouldn't forgot to open the shutter or to set the brightness in the intensity panel.

[[Datei:DMXC3L05 propertyPanels.JPG|600px]]

Movements can be controlled by the X/Y panel. It is also shown in the live view icons. But please consider, that not the moving path, but only the destination position will be stored laterly.

Most of the property panels are self explaining. We have
* color panel - pich 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
| direct function for dimmer/shutter, Lumos opens it (100%), NoX closes is (0%)
| you don't need to know if the device includes a shutter or dimmer
|-
|}

[[Datei: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 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.

[[Datei:DMXC3L05 propertyRGBPar.JPG]]

[[Datei:DMXC3L05 propertyRGBParColor.jpg]]

The following picture demonstrates a very interesting capability: You can even select different device types and set a common property in one step. The DMXControl kernel engine will assign the best matching values automatically. Of course, if required you can modify the manually.

[[Datei:DMXC3L05 propertyMix.JPG]]

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

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

==Additional links and references==
*

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

Lesson 4 Tut3

2011-06-24T13:31:42Z

Julien:

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

{{DMXC3_lesson/en}}

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

==Lecture 4: The live view ==

The liveView tool is one of the several tool in the tool menue. When creating devices and groups some (animated) icons are automatically generated in the liveview. You can shift these icon to a wanted place by mouse dragging. This way you can model your stage in 2D representation.

It could be helpful to load an background picture for better mapping your stage (right mouse context menue).

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

The liveview distunguishes in "single lamp" icons and "group" icons. If you select an group icon all following operational actions are related to each group member.

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 "Strg" key. Marking such a set of device can also be helpful for positioning the icons.

[[Datei:DMXC3L04 liveView groups.jpg]]

There are some helpful shortcuts helping to improve the assignment of icons in the liveview (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
|}

'''topics to be added (by beta testers)'''
* Welche Tasten sind in der Liveview interessant (Selektieren, Verschieben, automatisch anordnen, ...
* Beschreiben, dass mehrere liveviews existieren
* Wie kann ich Geräte in die verschiedenen liveviews bringen?

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

==Additional links and references==
*

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

Lesson 3 Tut3

2011-06-24T13:29:13Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==

This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show, 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 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.

[[Datei:DMXC3L03 projectExplorer.JPG]]

In following step we will create 4 moving lights of type "TS-255". You have to fill in the requested data. Please pay attention to define the correct start addresses.

[[Datei:DMXC3L03 createDevice.JPG|600px]]

By setting the hook for "autogenerate group" an group element is created automatically containing all devices of this definition step.

'''topics to be added (by beta tester)'''

* normal group creation - Wie läuft das? Nur im Kontextmenü liveview?
* assignment of device numbers - Property view?
* work with DDF - Wie erzeugen?
*

==Exercise==
* create all devices as shown in the figure above: 4 TS-255, 8 generic dimmer (as front lights) and 8 RGB-PARs
*

==Additional links and references==
*

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

__NOTOC__
__NOTITLE__

Lesson 2 Tut3

2011-06-24T13:25:13Z

Julien:

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

{{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 concepts of DMXControl 3 client==

DMXControl 3 provides a lot of tools and windows. For different use cases different forms 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 left to float above the main window or can be docked to the top, bottom, left or right margins. This versatility give you the power to build screens that are easy to use and tailored to your personal preference. Catch a form with the mouse pointer and move the pointer over one transparent arrow to dock the form at wanted place. A form can also be made to occupy the left-over space in the middle.

[[Datei:DMXC3L02 PanelAssignment.jpg|600px]]

Some important explanations:
* A floating form is simply one that isn’t docked to any side.
* A pane 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 as else in each pane. The potential position of the form is indicated by a blue rectangle.
* Forms are created via the "Windows" menu and closed with the ‘X’ in its top right corner. This will shut the form down but leave other forms in its 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 a 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 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.

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

[[Bild:DMXC30 WindowsManager3.JPG]]

In this panel configuration the left, right and buttom panel are used. The left panel is a splitted one. The right panel containes 3 auto-hide windows (see tab strip). The Live view window is floating.

===Auto-Hide===
DockPanel has an auto-hide feature that enables valuable screen real estate to be preserved.
If there is any auto hide window, DockPanel will display a tab strip on the out-most edge.
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.

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

'''topics to do be added (by beta testers)'''
* describe how to save a panel configuration
* add screenshots
* show examples

==Excercise==
* Create a new form (Menu "Windows") and dock and relaese it at several positions
* Save and reload a 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__

Lesson 1 Tut3

2011-06-24T13:10:43Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==

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.0 provides a distributed architecture, i.e. there is a kernel that can communicate with several clients. The kernel runs basically on Windows operating system, but can also be launched on Linux (with Mono).

One or multiple clients can be started on different systems (Windows, iOS, Android). Thus, you can even 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 server and clients provides some 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 "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.

[[Datei: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.

[[Datei:DMXC3L01 konsole.JPG|600px]]

There are some command options in the command line mode for getting detailed information on the status of the kernel:

* shutdown: Shut down the kernel.
* status: Displays information about the status
* menu: Access to control menu
* clear: Clears the console
* notification: Send a notification to all clients
* width: Defines width of console (number of characters)
* help: Help menu (also accessible via "?")

Additional second level menu commands exists for "menu" and "status".

===The client===

In next step you should start the Windows based GUI client (currently called "LumosGUI.exe"). This client will be explained in next lectures. At first you have to select the "Tools->Connection" panel in order to connect with the server.

[[Datei:DMXC3L01 connect.JPG]]

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

[[Datei:DMXC3L01 startGUI.JPG|600px]]

After establishing the connection you should see a small icon in the lower line of the client indicating the existing connection.

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

===Project Management===

You can save a project as a default project. If you use Project -> 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 Project -> Save Project as, type the name "DefaultProject" an save it to the ressources folder of the kernel "\path\to\your\DMXControl 3.0\Kernel\Ressources\"

'''topics to be added (by beta testers)'''
* how to save a project
*

==Excercise==

1) Please try following commands in command shell:
* menue
* status
* shutdown -> uups!

2) Restart kernel and GUI and connect your client with DMXControl server.

Congratulation! Now you have successfully installed your own DMXControl configuration!

==Assumptions for installation==

DMXControl 3.0 requires following software to be installed before executing the setup program:

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

==Known Issues==

===GUI Elements display glitches===
This could look like shown below:
Also if you move windows it happens that thay are not displayed correct.

[[Datei:Dmxc_3_menu_errors.jpg]]

This can occur if you have a NVidia graphics card and use an old driver version.

I experienced this issue with a GeForce G 103M Driver Version 258.96 + PhysX 09.10.0513 on Windows XP x86_64.

Consider updating the driver to the latest version. Version 266.58 + PhysX 09.10.0514 is known to work.

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

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

__NOTOC__
__NOTITLE__

Tutorials DMXControl 3

2011-06-24T13:08:27Z

Julien:

Lesson 2 Tut3

2011-06-24T12:36:47Z

Julien:

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

{{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 concepts of DMXControl 3 client==

DMXControl 3 provides a lot of tools and windows. For different use cases different forms 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 left to float above the main window or can be docked to the top, bottom, left or right margins. This versatility give you the power to build screens that are easy to use and tailored to your personal preference. Catch a form with the mouse pointer and move the pointer over one transparent arrow to dock the form at wanted place. A form can also be made to occupy the left-over space in the middle.

[[Datei:DMXC3L02 PanelAssignment.jpg|600px]]

Some important explanations:
* A floating form is simply one that isn’t docked to any side.
* A pane 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 as else in each pane. The potential position of the form is indicated by a blue rectangle.
* Forms are created via the "Windows" menu and closed with the ‘X’ in its top right corner. This will shut the form down but leave other forms in its 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 a 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 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.

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

[[Bild:DMXC30 WindowsManager3.JPG]]

In this panel configuration the left, right and buttom panel are used. The left panel is a splitted one. The right panel containes 3 auto-hide windows (see tab strip). The Live view window is floating.

===Auto-Hide===
DockPanel has an auto-hide feature that enables valuable screen real estate to be preserved.
If there is any auto hide window, DockPanel will display a tab strip on the out-most edge.
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.

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

'''topics to do be added (by beta testers)'''
* describe how to save a panel configuration
* add screenshots
* show examples

==Excercise==
* Create a new form (Menu "Windows") and dock and relaese it at several positions
* Save and reload a 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__

Lesson 1 Tut3

2011-06-24T12:36:09Z

Julien:

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

{{DMXC3_lesson/en}}

==Overview==

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.0 provides a distributed architecture, i.e. there is a kernel that can communicate with several clients. The kernel runs basically on Windows operating system, but can also be launched on Linux (with Mono).

One or multiple clients can be started on different systems (Windows, iOS, Android). Thus, you can even 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 server and clients provides some 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 "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.

[[Datei: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.

[[Datei:DMXC3L01 konsole.JPG|600px]]

There are some command options in the command line mode for getting detailed information on the status of the kernel:

* shutdown: Shut down the kernel.
* status: Displays information about the status
* menu: Access to control menu
* clear: Clears the console
* notification: Send a notification to all clients
* width: Defines width of console (number of characters)
* help: Help menu (also accessible via "?")

Additional second level menu commands exists for "menu" and "status".

===The client===

In next step you should start the Windows based GUI client (currently called "LumosGUI.exe"). This client will be explained in next lectures. At first you have to select the "Tools->Connection" panel in order to connect with the server.

[[Datei:DMXC3L01 connect.JPG]]

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

[[Datei:DMXC3L01 startGUI.JPG|600px]]

After establishing the connection you should see a small icon in the lower line of the client indicating the existing connection.

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

'''topics to be added (by beta testers)'''
* how to save a project
*

==Excercise==

1) Please try following commands in command shell:
* menue
* status
* shutdown -> uups!

2) Restart kernel and GUI and connect your client with DMXControl server.

Congratulation! Now you have successfully installed your own DMXControl configuration!

==Assumptions for installation==

DMXControl 3.0 requires following software to be installed before executing the setup program:

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

==Known Issues==

===GUI Elements display glitches===
This could look like shown below:
Also if you move windows it happens that thay are not displayed correct.

[[Datei:Dmxc_3_menu_errors.jpg]]

This can occur if you have a NVidia graphics card and use an old driver version.

I experienced this issue with a GeForce G 103M Driver Version 258.96 + PhysX 09.10.0513 on Windows XP x86_64.

Consider updating the driver to the latest version. Version 266.58 + PhysX 09.10.0514 is known to work.

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

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

__NOTOC__
__NOTITLE__

Tutorials DMXControl 3

2011-06-24T12:33:04Z

Julien:

Main Page

2011-06-24T12:19:50Z

Julien:

{| style="border:0px #ff0000 solid; padding:10px; background-color:white" cellspacing="0"
| width="65%" style="padding-right:1.5em;" valign="top" |

{{Portalhead|ff0000|Welcome}}
...

{{Portalhead|ff0000|Current Projects}}
...

{{Portalhead|ff0000|ToDo's}}
...

| width="35%" valign="top" |
{{Portalhead|ff0000|Recently Updated Articles}}
<DynamicArticleList>
type=update
count=5
</DynamicArticleList>

{{Portalhead|ff0000|Similar Projects}}
...

|}

[[de:Hauptseite]]
[[en:Main Page]]

__NOTOC__ __NOEDITSECTION__ __NOTITLE__

MediaWiki:Sidebar

2011-06-24T11:59:49Z

Julien:

New here?

2011-06-23T21:19:21Z

Julien:

{{Hauptüberschrift
| logo = Info.png
| ueberschrift = New here?
}}
{{Stub}}

__NOTITLE__

MediaWiki:Sidebar

2011-06-23T21:18:57Z

Julien:

New here?

2011-06-23T21:16:48Z

Julien: moved Neu hier? to New here?

{{Hauptüberschrift
| logo = Info.png
| ueberschrift = Neu hier ?
}}
{{Stub}}

__NOTITLE__

Template:Stub

2011-06-23T21:08:15Z

Julien:

<div id="Vorlage_Stub" style="border: 1px solid #CCCCCC; background-color: #F8F8F8; border-left: 5px solid #AAAAAA; font-size: 95%; padding: 10px 7px;"><span style="float: left; padding-right: 10px;">[[File:pencil.png]]</span>
Dieser Artikel ist sehr '''kurz''' und möglicherweise inhaltlich noch sehr '''unvollständig'''. Bitte helfen Sie mit<span class="hidereg">: [[Spezial:Userlogin|Melden Sie sich an]] oder [[Spezial:Userlogin|loggen Sie sich ein]]</span>, '''[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} bearbeiten]''' und vervollständigen Sie den Artikel und entfernen Sie anschließend diesen Hinweis. <span style="font-size: 80%;">([[Hilfe:Erste_Schritte|Anleitung zum Bearbeiten]].)</span></div>