__NOTITLE__
{{Hauptüberschrift
| logo = Kcmpartitions.png
| ueberschrift = Supported DMX Interfaces
}}
Column S: In and out port can be used simultaneously 
{| class="wikitable sortable" style="width:100%"
!style="width:10em"|Vendor
!Model
!style="width:4em"|DMX OUT
!style="width:4em"|DMX IN
!style="width:1em"|S
!style="width:4em"|CON
!style="width:4em"|RDM
!style="width:10em"|Vendor ID
!Model ID
|-
|American DJ
|myDMX
|512
| -
| -
|USB
| -
|Nicolaudie
|SIDU
|-
|Artistic License
|Art-Net
|4x 512
|4x 512
|x
|ETH
|x
|Artisic License
|Art-Net
|-
|Daslight
|generic
|?
|?
| -
|USB
| -
|Nicolaudie
|SIDU
|-
|Digital Enlightenment
|FX5
|512
|512
| x
|USB
| -
|Digital Enlightenment
|USBDMX
|-
|Digital Enlightenment
|USBDMX
|512
|512
| x
| USB
| -
|Digital Enlightenment
|USBDMX
|-
|DMX4ALL
|generic
| ?
| ?
| -
|USB
| -
|DMX4ALL
|Generic DMX4ALL
|-
|Enttec
|DMX USB Pro
|512
|512
| ?
| USB
| -
|Enttec
|DMX USB Pro
|-
|Enttec
|Open DMX USB
|512
| -
| -
| USB
| -
|Enttec
|Open DMX USB
|-
|Enttec
|RDM USB Pro
|512
|512
| ?
| USB
| x
|Enttec
|DMX USB Pro
|-
|Eurolite

|USB-DMX512-PRO
|512
| -
| -
| USB
| -
|Eurolite
|USB-DMX512-PRO
|-
|IMG Stage Line
|DMX-60
|60
| -
| -
| USB
| -
|Monacor
|DMX60
|-
|IMG Stage Line
|DMX-120
|120
| -
| -
| USB
| -
|Monacor
|DMX120
|-
|IMG Stage Line
|DMX-510
|512
| -
| -
| USB
| -
|Monacor
|DMX510
|-
|JMS
|USB2DMX
|512
| -
| -
|USB
| -
|Enttec
|Open DMX USB
|-
|Sunlite
|Magic 3D Easy View
|4x 512
| -
| -
| -
| -
|Sunlite
|Magic 3D Easy View
|}
x Feature supported 
- Feature not supported
{| class="wikitable sortable"
!Vendor ID
!Model ID
!Instances
|-
|Artistic License
|Art-Net
|1
|-
|Digital Enlightenment
|USBDMX
|32
|-
|DMX4ALL
|*
|1
|-
|Enttec
|USB DMX Pro
|ftdi limit?
|-
|Enttec
|Open DMX USB
|fdti limit!
|-
|Eurolite
|USB-DMX512-Pro
|1?
|-
|Monacor
|*
|1 each?
|-
|Nicolaudie
|SIDU
|10
|-
|Soundlight
|USBDMX-ONE
|?
|}

Supported DMX Interfaces

2011-12-10T17:18:48Z

Fisl:

Supported DMX Interfaces

2011-12-10T17:14:06Z

Fisl: Created page with "__NOTITLE__ {{Hauptüberschrift | logo = Kcmpartitions.png | ueberschrift = Supported DMX Interfaces }} Column S: In and out port can be used simultaneously {| class="wikitab..."

Lesson 1 Tut3

2011-06-28T18:30:05Z

Fisl: /* Project Management */

{{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" and 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__

Lesson 10 Tut3

2011-06-27T19:20:12Z

Fisl: /* Lecture 10: The programmer view */

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

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

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

===Filter Output (not yet implemented)===
You can filter the output of the programmer. Use "Set Filter", the Programmer Filter will be opened. Deselect all Properties that should be filtered out and close the programmer filter. If you now select "Filtered" as Output Mode, only the selected properties will be outputted. The Programmer highlights the outputted properties.

'''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 11 Tut3

2011-06-27T11:04:51Z

Fisl: /* Lecture 11: Trigger in scene lists */

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

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (opt) 3 || use GO to fade in next cue
optional: fade in cue after 3 GO presses, default is 1
|-
| follow || 5s || wait until the 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 || 13:00:00 || real time clock, fade in a cue at a specified time
|-

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

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

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

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the timecode selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

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

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

[[File: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 11 Tut3

2011-06-27T11:03:06Z

Fisl:

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

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (opt) 3 || use GO to fade in next cue
optional: fade in cue after 3 GO presses, default is 1
|-
| follow || 5s || wait until the 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

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Here is the example for the timecode selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

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

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

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

2011-06-25T11:35:54Z

Fisl: /* Using Advanced Timing (=> Property Based Timing) */

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

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

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

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

[[File:DMXC3L08 FirstScene.JPG]]

You have to clean the '''programmer'''! Otherwise nothing will happen, when you press the play button
[[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 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.

[[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. 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, 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.

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

File:Dmxc3 advanced timing value.jpg

2011-06-25T11:31:20Z

Fisl:

File:Dmxc3 advanced timing fade.jpg

2011-06-25T11:31:07Z

Fisl:

File:Dmxc3 advanced timing delay.jpg

2011-06-25T11:30:19Z

Fisl:

Lesson 13 Tut3

2011-06-25T11:29:40Z

Fisl: /* Lecture 13: Presets */

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

[[File:DMXC3L13 Preset.jpg]]

===Recording Presets===

To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See Lesson 8 (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 8 Tut3

2011-06-24T17:29:48Z

2011-06-10T21:25:13Z

Fisl: /* GUI Elements display glitches */

<h2 style="{{Style:Hauptseite:Überschrift}}" align="center">DMXControl 3 lessons</h2>
<div style="{{Style:Hauptseite:Box}} background-color:#ffffff">

<div class="floatright" style="width: 78%; margin-top:-8px;">

==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:
[http://www.dmxcontrol.de/mediawiki_beta/index.php?title=Einsteiger:Lesson2/en Lecture2: The panel concept]

</div>


<div style="{{Style:Hauptseite:Box}} width: 17%; background-color:#f5faff">
{{DMXC3_lesson/en}}
</div>

__NOTOC__
{{Languages|Einsteiger:lesson1}}

Lesson 1 Tut3

2011-06-10T13:30:40Z

Fisl: /* GUI Elements display glitches */

<h2 style="{{Style:Hauptseite:Überschrift}}" align="center">DMXControl 3 lessons</h2>
<div style="{{Style:Hauptseite:Box}} background-color:#ffffff">

<div class="floatright" style="width: 78%; margin-top:-8px;">

==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|600px]]

This can occur if you have a NVidia graphics card an 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:
[http://www.dmxcontrol.de/mediawiki_beta/index.php?title=Einsteiger:Lesson2/en Lecture2: The panel concept]

</div>


<div style="{{Style:Hauptseite:Box}} width: 17%; background-color:#f5faff">
{{DMXC3_lesson/en}}
</div>

__NOTOC__
{{Languages|Einsteiger:lesson1}}

Lesson 1 Tut3

2011-06-10T13:24:00Z

Fisl: Known Issues added

<h2 style="{{Style:Hauptseite:Überschrift}}" align="center">DMXControl 3 lessons</h2>
<div style="{{Style:Hauptseite:Box}} background-color:#ffffff">

<div class="floatright" style="width: 78%; margin-top:-8px;">

==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|600px]]

This can occur if you have a NVidia Graphics card an 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:
[http://www.dmxcontrol.de/mediawiki_beta/index.php?title=Einsteiger:Lesson2/en Lecture2: The panel concept]

</div>


<div style="{{Style:Hauptseite:Box}} width: 17%; background-color:#f5faff">
{{DMXC3_lesson/en}}
</div>

__NOTOC__
{{Languages|Einsteiger:lesson1}}

2011-05-23T19:52:58Z

Fisl: /* Deleteing Presets */

<h2 style="{{Style:Hauptseite:Überschrift}}" align="center">DMXControl 3 lessons</h2>
<div style="{{Style:Hauptseite:Box}} background-color:#ffffff">

<div class="floatright" style="width: 78%; margin-top:-8px;">

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

===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 and the entries in the programmer will be removed.

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

====Update====

don't ask me... no clue

===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 scene list. A copy of your "preset cue" will be inserted. All values from the preset are taken over into the new cue.

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

TODO: uhm should work, ha?

===Applying Selected Parameters of Presets===

It is also possible to take ''not'' the whole preset, but only a selected attribute from the preset for your current cue. For this case you drag&drop the preset to your dedicated attribute, e.g. the dimmer. Please have a view to the programmer: You can see that in our case the dimmer value was taken from the preset.

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

TODO: i guess this should work, too.

/*'''Attention''' Presets resp. values from presets are taken as references to original preset. If you modidy afterwards the preset, all reference values are changed automatically. This behaviour can be beneficially applied when adapting a show by only modifying few presets.*/

'''topics to be added (by beta testers)'''
*yah first release the beta, than we'll see what to add here...

*TODO: some paragraphs sound odd, going to change that later ...
*TODO: check terms that dmxc uses, here is what i normaly use:
** - intensity of fixture or just intensity instead of dimmer value
** - parameters are pan/tilt, color, intensity
** - pan/tilt: focus?
** - attributes: follow, wait, trigger in cue list...
** -
*TODO: remove attention notice. That should be clear to the reader till there.
*TODO: add some better explanation what presets are.
*TODO: capitalization of paragraph heading?

==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:
[http://www.dmxcontrol.de/mediawiki_beta/index.php?title=Einsteiger:Lesson14/en Lecture14: XXXX]

</div>


<div style="{{Style:Hauptseite:Box}} width: 17%; background-color:#f5faff">
{{DMXC3_lesson/en}}
</div>

__NOTOC__
{{Languages|Einsteiger:lesson13}}

Lesson 13 Tut3

2011-05-23T19:49:14Z

Fisl: /* Lecture 13: Presets */

<h2 style="{{Style:Hauptseite:Überschrift}}" align="center">DMXControl 3 lessons</h2>
<div style="{{Style:Hauptseite:Box}} background-color:#ffffff">

<div class="floatright" style="width: 78%; margin-top:-8px;">

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

===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 and the entries in the programmer will be removed.

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

====Update====

don't ask me... no clue

===Deleteing Presets===

/*After you have created your presets you can use it in two (TODO: should be more than two scenarios) scenarios: using the complete preset or using of parts of a preset*/

===Applying Presets===

You can "drag&drop" a preset into your scene list. A copy of your "preset cue" will be inserted. All values from the preset are taken over into the new cue.

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

TODO: uhm should work, ha?

===Applying Selected Parameters of Presets===

It is also possible to take ''not'' the whole preset, but only a selected attribute from the preset for your current cue. For this case you drag&drop the preset to your dedicated attribute, e.g. the dimmer. Please have a view to the programmer: You can see that in our case the dimmer value was taken from the preset.

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

TODO: i guess this should work, too.

/*'''Attention''' Presets resp. values from presets are taken as references to original preset. If you modidy afterwards the preset, all reference values are changed automatically. This behaviour can be beneficially applied when adapting a show by only modifying few presets.*/

'''topics to be added (by beta testers)'''
*yah first release the beta, than we'll see what to add here...

*TODO: some paragraphs sound odd, going to change that later ...
*TODO: check terms that dmxc uses, here is what i normaly use:
** - intensity of fixture or just intensity instead of dimmer value
** - parameters are pan/tilt, color, intensity
** - pan/tilt: focus?
** - attributes: follow, wait, trigger in cue list...
** -
*TODO: remove attention notice. That should be clear to the reader till there.
*TODO: add some better explanation what presets are.
*TODO: capitalization of paragraph heading?

==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:
[http://www.dmxcontrol.de/mediawiki_beta/index.php?title=Einsteiger:Lesson14/en Lecture14: XXXX]

</div>


<div style="{{Style:Hauptseite:Box}} width: 17%; background-color:#f5faff">
{{DMXC3_lesson/en}}
</div>

__NOTOC__
{{Languages|Einsteiger:lesson13}}