English DMXC-Wiki - User contributions [en]

Category:Assemblys General

2014-09-12T09:42:14Z

Jmintenbeck: Created page with "Category:General Reports"

[[Category:General Reports]]

Category:General Reports

2014-09-12T09:41:15Z

Jmintenbeck: Created page with "In this section are mainly reports about the DMXControl Projects association. de:Kategorie:Berichte_Allgemein"

In this section are mainly reports about the DMXControl Projects association.

[[de:Kategorie:Berichte_Allgemein]]

Lesson 17 Tut3

2013-04-17T13:38:59Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_16_Tut3
| TextBackwards = Lesson 16
| LinkForwards = Lesson_18_Tut3
| TextForwards = Lesson 18
}}
==Overview==

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

==Lecture 17: Audio Analyzer ==

The audio analyzer is implemented in DMXControl 3 as plugin and and you will have to enable it via '''Plugin Manager'''. It then appears as a menu item under '''Windows -> Audio Analyzer'''. The audio analyzer provides essentially the same features as the Soundanalyser([[Sound_Analyzer_DMXC2|Soundanalyser]]) of DMXControl 2.
{{BoxHinweis
| Text = This plugin is still in an experimental stage.
}}

{{Picture_with_subtitle |DMXC3L17 PluginAudioAnalyser.jpg|1|Audio Analyzer Window|center|450px}}

The main purpose of audio player is the automatic generation of beats from a song in order to trigger the beats in a beat-driven cue list.(see [[Lesson 11 Tut3|Lesson 11: Trigger]]).

The plugin contains several tabs:

* '''Devices''' is responsible for the configuration. Here you choose the particular audio input
* With'''VU meter''', '''Spectrum''' and '''Beat Detection''' you can select the different analysis method
* '''Mood''' should analyze automatically and in real time the mood of an audio signal and the "Automatic Sound Controlled Light Show" lead (Vision!)
* Using '''Beat generator'''You can manually create the Beats (Tap-key) or you can specify a certain Beats-Per-Minute (BPM) value

And now the question remains, how will the results of the analysis be assigned to drive the cuelist? You already have an idea? ... Of course, this is the same as the'' 'input Assignment''' concept introduced in Tutorial 11.

{{Picture_with_subtitle |DMXC3L17 PluginAudioAnalyserInputAssignment.JPG|2|Assigning sound events using the input Assignment Window|center|600px}}

==Exercise==
Activate the AudioAnalyzer. If your sound card does not feature internal redirection, and you currently have no external player available, use the microphone input as a substitute.

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

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

[[category:DMXControl 3]]

[[de:Lektion 17]]

Lesson 16 Tut3

2013-04-17T13:38:35Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_15_Tut3
| TextBackwards = Lesson 15
| LinkForwards = Lesson_17_Tut3
| TextForwards = Lesson 17
}}
==Overview==
In this lesson you will learn something about the '''SoftDesk''' plugin. This tool allows you to create lighting consoles that will simulate any physical lighting console, or a custom console using your own design ideas

==Lecture 16: SoftDesk==

DMXControl 3 offers the SoftDesk, which replaces the popular command box from DMXControl 2. The advantages of soft desks are as follows:
* Flexible layout options
* Wider variety of controls
* Potentially there will be SoftDesk variants on external clients (tablets, etc.).

In principle, you can reconstruct any physical console with the SoftDesk editor.

The SoftDesk tool can be enabled via the '''plugin manager''', see Lesson6/en. Afterwards you can find a new menu entry "Softdesk" within the plugins menu. When you open this plugin, a set-up GUI appears at first:

Here you can create, delete, edit, copy, import and export your instances of SoftDesks. Simply select the check box. Then you will find a new entry "SoftDesk" under the menu item "Windows" (restarting the GUI-clients may be required).

 
{{Picture_with_subtitle |DMXC3L16 SoftDesk plugin.JPG|1|SoftDesk Plug-in Activation|center}}
 

After opening the plug-in via the menu, a GUI appears for the first set-up of the various consoles. This panel is initially empty, but on the right side are 6 buttons.

Here you can create and edit individual desk surfaces, copy, import or export. By double-clicking in the blue line, you can change the name of the console to be created (if design mode is set). The new consoles will appear in the Project Explorer too.

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

You can create multiple console surfaces, which can then be activated simultaneously at run time (but multiple banks are not available within SoftDesk).

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

Here you can see one possible result:

 
{{Picture_with_subtitle |DMXC3L16 SoftDesk.JPG|2|SoftDesk Plug-in|center}}
 

You can customize the elements in design mode by using the property context menu. Simply double click the control or call it by right click in the '''DesignMode'''. The following figure shows the property box for a button (right mouse click in design mode). For example you can modify the button name, colors and the toggle mode property -
here the name was changed to "Flash button".

 
{{Picture_with_subtitle |DMXC3L16 CommandboxProperties.JPG|3|Settings|center}}
 
{{BoxHinweis
|Text=You can change the size of individual elements by dragging the corners with the mouse.
}}

In the next step you have to connect your SoftDesk with your project. I.e. you have to assign functions to your SoftDesk control elements.

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

 
{{Picture_with_subtitle |DMXC3L16 SoftDeskInputAssignment.JPG|4|Input Assignment|center}}
 
{{BoxHinweis|Text=Do not forget to switch off the design mode at run time.}}

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

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

==Exercise==
* Create two SoftDesks, one consisting of buttons only, the other one should contain all types of control elements
* Control colors with your button SoftDesk
* Connect the XYpad with your moving light and test the function

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_15_Tut3
| TextBackwards = Lesson 15
| LinkForwards = Lesson_17_Tut3
| TextForwards = Lesson 17
}}

[[category:DMXControl 3]]

[[de:Lektion 16]]

Lesson 15 Tut3

2013-04-17T13:38:11Z

Jmintenbeck:

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

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

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

In Lesson 8 and 12. it was explained how to create scenes and scene-lists. Now, suppose we want to execute our scene lists. This works like in DMXControl 2, by opening the cue-list and using the '''Go''' and '''STOP''' buttons.

To run cues and cue lists you can also use '''executors'''. These correspond roughly to the submasters from DMXControl 2. As in version 2, you can create various "banks" - in DMXControl 3, called "Pages". This will allow you to increase the number of executors in groups of 8. First create a new executor page in the '''Project Explorer''':

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

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

===Assignment of cues===

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

===Assignment of cue-lists===

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

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

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

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

You can select between different execution modes the same way you use a standard audio player:

[[File:DMXC3L15 firstExecutor.JPG]]

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

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

==Work with multiple Cue lists==

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

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

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

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

[[category:DMXControl 3]]

[[de:Lektion 15]]

Lesson 14 Tut3

2013-04-17T13:37:51Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_13_Tut3
| TextBackwards = Lesson 13
| LinkForwards = Lesson_15_Tut3
| TextForwards = Lesson 15
}}
==Overview==
This chapter provides a summary of the programming capabilities in DMXControl 3.

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

DMXControl 3 offers you the following items for advanced use of DMXControl 3.

* Cue list
* The programmer
* Several fading approaches
* The Hardware abstraction
* DMXControl kernel ("Light engine with Fanning algorithms)
* Effect library

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

{{BoxHinweis
|Text = This beta version of DMXControl 3 has not yet provided the popular tools such as audio players, or text book with its graphical programming interfaces. But, the control options of a cue list have grown enormously. You now have different fading and trigger options. Thus, it should, in principle, be possible to effectively create earlier scene lists again. 
The library scene is not found in this form in the current version. But you can use presets for the same purpose. Presets also have a number of additional capabilities.
}}

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

A further increase in productivity is obtained by being able to manipulate the cue lists by using the EXCEL spreadsheet program.
Since cues and presets work regardless of device type, you can quickly customize existing shows to new equipment setups.
Thus, it should be possible, with a little practice, to program big shows in minutes!

We still remember a DMXControl meeting in 2008, when we programmed for an entire day, to create a show lasting 5 minutes. At night we proudly presented this show to a professional, and we asked him how long it would take for him to do it.

The answer shocked us at the time: '''15 minutes!''' For us that was almost unimaginable, and sounded like a barely workable vision for a freeware DMXControl. But, we have done everything in recent years to get to that level of professionalism. We think that we've successfully created DMXControl 3 close to this vision!

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

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_13_Tut3
| TextBackwards = Lesson 13
| LinkForwards = Lesson_15_Tut3
| TextForwards = Lesson 15
}}

[[category:DMXControl 3]]

[[de:Lektion 14]]

Lesson 13 Tut3

2013-04-17T13:37:23Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_12_Tut3
| TextBackwards = Lesson 12
| LinkForwards = Lesson_14_Tut3
| TextForwards = Lesson 14
}}
==Overview==
In this lesson we explain how to apply presets. By re-using presets you are more efficiently when programming your show.

==Lecture 13: Presets ==

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

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

The big advantage of using presets is, that it's referenced data. That means whenever you record a cue using presets, a link to the preset is stored, and not the actual values. So keep in mind, that 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 cyclorama wash as a preset and used this preset in five cues. If you later decide to modify the cyclorama wash a bit, you just need to update one preset, instead of five cues. However, if you just want to change the color in one cue you can do that by overwriting the reference with manual data.

[[File:DMXC3L13 Preset.jpg]]

===Recording Presets===

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

===Modifying Presets===

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

====Replace====

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

====Merge====

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

====Append====

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

====Subtract====

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

===Deleting Presets===

Select the preset you want to delete, then press Delete or use the context menu, -> 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 start 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 double-click on the preset you want to use. The entry will show up in the Programmer window. Keep in mind, if you store this to a cue, it is not the actual values that are stored, but a reference to this preset. So if you change something in your preset, the changed values will be used everywhere that you used this preset.

===Applying Selected Properties of Presets===

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

===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 your fixtures, then drag&drop the preset to the properties you want to use in the property grid. The value for the selected property of the selected fixtures will show up in the programmer window

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

Also you can use a Preset to set a property of a fixture that has no value stored in the preset to a value from the preset. First a short example: A preset with some RGB Par-cans are set to a color. Later you want your moving lights change to the same color as your RGB Par-cans. You might do this by remembering, or looking up this color. But, there is a third possibility. Select your fixtures, in this example you moving lights, and move your preset (drag&drop) to the property grid. Now hold "Ctrl" key down and drop your preset to the color property of your fixture. The color of your fixture will be set to the last found value of the used property in your preset. I.e., the filtering of devices is switched off by the "Ctrl" key.

===Shortcuts===

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

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

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

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

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_12_Tut3
| TextBackwards = Lesson 12
| LinkForwards = Lesson_14_Tut3
| TextForwards = Lesson 14
}}

[[category:DMXControl 3]]

[[de:Lektion 13]]

Lesson 12 Tut3

2013-04-17T13:36:58Z

Jmintenbeck:

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

==Lecture 12: Editing scenes and scene lists ==

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

{{Picture_with_subtitle |DMXC3L12_SL.JPG|1|Menu of the Programmer|center}}
By default, a new scene is added to an existing scene list by pressing the button "Add Cue". When you open the small drop-down arrow on right hand side of this button, you see some more sophisticated capabilities with their keyboard shortcut. In most cases you will first select (i.e. highlight) a scene before modifying it.

{{Picture_with_subtitle |DMXC3L12_SL_storemenue.jpg|2|View of the drop-down-menu of "Add Cue"|center}}

{{BoxHint
|Text= The following operations are related to the values in the '''Programmer'''.
}}

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Add || Ctrl+A || add a new scene to scene list at the end || default
|-
| Insert || Ctrl+I || insert a new scene to scene-list before selected scene ||
|-
| Replace || Ctrl+R || replace current scene attributes by the values in the '''Programmer''' ||
|-
| Merge|| Ctrl+M || merges selected scene with '''Programmer''' values || '''Programmer''' values with higher priority
|-
| Append || Ctrl+P || append new property from '''Programmer''' to the selected scene || existing scene with higher priority, new values from '''Programmer''' are added
|-
| Subtract || Ctrl+B || removes a property from selected scene || hint: modify the wanted property so that this appears in the '''Programmer'''
|-
| Sum (Special) || || Inserts current output of devices into '''Cue List''' ||
|-
| PSum (Special) || || Similar to '''Sum''', but related to currently selected devices in '''Stage View''' ||
|-
| Preset (Special) || || Opens a window where you have the capability to add a '''Preset''' to '''Cue List''' ||
|-
| Scenelist (Special) || || Inserts (similar to commands in DMXControl 2) a entry to impact another cue list ||

|}

In a similar way, there are also edit operations for the scene list itself. As known from EXCEL you can copy, cut and delete whole rows. With copy and paste you can take single values from one field or a cue to another field of other cues.

{{Picture_with_subtitle |DMXC3L12_SL_editmenue.jpg|3|View of drop-down-menu of "Edit"|center}}

Here is the summarizing table for explanation again:

{| class="wikitable"
|-
! Function !! short code !! Description !! Comment
|-
| Edit in Programmer || || Selected cue is loaded into '''Programmer'''. '''Programmer Output Mode''' is set to '''All''' ||
|-
| Edit in Programmer Blind || || Selected cue is loaded into '''Programmer'''. '''Programmer Output Mode''' is set to '''Blind''' ||
|-
| Cut || Ctrl+X || cut the selected scene || like EXCEL "cut row"
|-
| Copy || Ctrl+C || copy the selected scene || like EXCEL "copy row"
|-
| Paste || Ctrl+V || paste the selected scene || like EXCEL "paste row"
|-
| Delete|| Del || delete the selected scene || like EXCEL "delete row"
|-
| Renumber Cues || || || Renumber Cues
|-
| Cue Timing Editor || || || a separate editor is opened

|}

{{Picture_with_subtitle |DMXC3L12_SL_optionmenue.jpg|4|View of drop-down-menu of "Options"|center}}

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

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

__NOTOC__
__NOTITLE__

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

[[category:DMXControl 3]]

[[de:Lektion_12_Tut3]]

Lesson 11 Tut3

2013-04-17T13:36:33Z

Jmintenbeck:

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

==Lecture 11: Triggers in cue lists ==
In previous lessons we learned how to create cues and scene lists. Now that you are familiar with most of the attributes of the scene list, more explanation about triggers is necessary. A trigger is an event that causes a previously saved scene to start. A trigger might come from things like a button press by the user,or an internal timer. The default trigger is "follow". This means the next cue will be started after the previous one has finished fading in.

'''Important:''' When you change the trigger type, you need to apply the changes with the enter-key or by clicking in another field.

There are several types of triggers. The following table describes their behaviors.

[[File:DMXC3L11 trigger.jpg]]

{| class="wikitable"
|-
! Type !! Example format !! Description
|-
| manual || (optional) 3 || Use GO to fade in next cue.
Optional: Fade cue in after 3 GO presses. The default is 1.
|-
| follow || 5s || Wait until the previous cue is faded in, then wait 5 seconds before starting the next cue.
|-
| wait || 5s || Wait time countdown starts when the wait or follow of the previous cue is completed. In other words, the cue will wait 5 seconds after the prior cue has started, rather than waiting for it to finish.
|-
| timecode || 00:26:05 || Waits for the DMXControl to be given an external timecode signal equal to 00:26:05.
|-
| rtc || 13:00:00 || Real time clock. Fade in a cue at the specified time of 1 pm.
|-
| beat || (optional) 3 || This requires more settings. See the paragraph below.
Optional: Fade in cue after 3 beats. The default is 1.
|}

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

If you type an incorrect format into the '''trigger value''' field, you will get some hints about the expected input syntax. See the example below for the "follow" type.

[[File:DMXC3L11 triggerhelpcontextfollow.JPG]]

Below is the example for the real time clock selection.

[[File:DMXC3L11 triggerhelpcontext.JPG]]

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

===Use of beat trigger===

A '''Beat Trigger''' is a trigger based on the main rhythm of the music. It may be manually set, or automatically generated by DMXControl as it analyzes an audio signal and looks for peak transients.

If you want to have your scenes beat controlled, you need to select the source for the trigger '''beat''' .

{{BoxHint|Text=In the '''Trigger''' field you can specify after how many beat signals the next cue is called
}}

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

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

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

==Summary==

The following figure shows the dependencies and capabilities of mixing several trigger types:

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

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

==Exercises==
* Test a mix of "follow" and "wait" triggers in one scene list
* Use a tool providing time codes, such as MediaCenter, and test a scene list that is completely based on time codes

__NOTOC__
__NOTITLE__

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

[[category:DMXControl 3]]

[[de:Lektion_11_Tut3]]

Lesson 10 Tut3

2013-04-17T13:36:02Z

Jmintenbeck:

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

==Lecture 10: The programmer view ==

The '''Programmer''' tool logs all modifications you made and shows the current content of the "cue buffer".

{{BoxHint
| Text= Remember the "save scene" dialog in DMXControl 2? There you were asked to define the channels and values before finally saving the cue. The '''Programmer''' is an extended view of this functionality.
}}

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

* First, open the moving lights shutters and select the color green
* Second, set the gobos of all devices on "Gobo2"
* Third, set the group of front lights to 50% brightness

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

The results are now shown in the programmer. Please be aware that the cue is not saved at this point in time, because further modification might follow.

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

If you change your mind on the current cue, you can press the '''Clear Programmer''' button to remove all settings and refresh the programmer.

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

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

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

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

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

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

[[File:DMXC3L10 ProgrammerFilter.JPG]]

==Exercise==
* Repeat the above scenario

__NOTOC__
__NOTITLE__

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

[[category:DMXControl 3]]

[[de:Lektion_10_Tut3]]

Lesson 9 Tut3

2013-04-17T13:35:35Z

Jmintenbeck:

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

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

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

===Fanning===

The first mechanism is fanning. Just as you can open an ornate oriental fan, and created a colorful beautiful picture, you can create beautiful color palettes or beam spreads.

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

====linear fanning====

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

=== alternate fanning ===

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

How does it work?

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

[[File:DMXC3L09 Fanning pink.JPG]]

How many actions are needed for programming? 8? 16? 32?
The answer is: '''Three!''' 
We will apply linear fanning by "><" where we separate the marginal devices from central devices. The actions:
* select the group "RGB pars"
* go to property grid panel and type in for red color "0<>255"
* type for blue color "255<>0"

Here is the amazing result in property grid:

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

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

[[File:DMXC3L09 Fanning alternate.JPG]]

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

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

=== Effects and filters ===

With fanning you can create static cues. The "effects and filters" panels provides some additional effects that can be used for dynamic changes within a cue (e.g. swinging, flashing, running lights, etc.). Of course that's done fast and easy with DMXControl 3, or did you expect something else? ;)

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

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

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

Try it! You'll love it! 

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

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

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Attribute
! Example
! Description
|-
| Amplitude
| 50 > 100
| Value interval for selected attribute; Can be set to negative value also.
|-
| Phase
| [0..100]
| Offset between group elements.
|-
| Frequency
| [0..1]
| Cycle speed.
|}

 
{{BoxHint
|Text= By fanning the offset, you get interesting chasers.
}}

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

{| class="wikitable FCK__ShowTableBorders"
|-
! Use case
! How-to
! Amplitude
|-
|Jump effect: Dimmer should slowly fade to 0, and then will jump to full value
|Srag "Sawtooth" to dimmer property
| -100
|-
|Running light: One changing element of a group has 100% dimmer
|Drag "Chaser" to dimmer property
| 100
|-
|Gobo change:
|Drag "ListSwitch" to gobo property
|
|-
|Fade-in-effect with waiting time: Dimmer fades to 70, waits, Dimmer fades to 0, waits.
|Drag "Trapezoid" to dimmer property
| 70
|-
|Pattern of 8: Moving lights follow the "8" shape.
|Drag "Lissajous" to position property
| 270
|-
|On/off-effect: Lamps are switched on/off
|Drag "Rectangle" to dimmer property
| 100
|-
|Harmonic fade: Lamps dim in a harmonic way to 100% and back to 0.
|Drag "Sinus" to dimmer property
| 100
|-
|Color change: Lamps change sequentially to all possible colors.
|Drag "Sawtooth" to color property
| 100
|-
|}

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

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_8_Tut3
| TextBackwards = Lesson 8
| LinkForwards = Lesson_10_Tut3
| TextForwards = Lesson 10
}}

[[category:DMXControl 3]]

[[de:Lektion 9]]

Lesson 8 Tut3

2013-04-17T13:35:09Z

Jmintenbeck:

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

{{BoxHint
|Text =The button for the "Full On" function is labeled "Lumos". This is a Latin word meaning light. It was used in the Harry Potter series as a spell to make the magic wand light up.}}

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

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

* We go to the '''Stage View'''
* We select the "Generic RGB PAR Group" (or choose all RGB light with one of the other methods)
* You can control the intensity of the light by dragging the slider or by pressing the "Lumos" button to bring the light to full brightness.
* In the color panel select "green". The 8 headlights in the '''Stage View''' should now respond accordingly (see figure)

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

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

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

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

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

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

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

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

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

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

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

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

[[File:DMXC3L08 FirstScene.JPG]]

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

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

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

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

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

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

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

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

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

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

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

===Editing Property Based Timing===
Once you saved a cue with property based timing you can edit the values.

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

__NOTOC__
__NOTITLE__

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

[[category:DMXControl 3]]

[[de:Lektion_8_Tut3]]

Lesson 7 Tut3

2013-04-17T13:34:37Z

Jmintenbeck:

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

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

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

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

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

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

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

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

The project explorer also contains some general buttons:
* Edit
* Create directory / create device group
* Up / Down
* Device Manager
* Add item list / add Live view
* Import / export files

This is for administrative operations in your device configuration.
[[File:DMXC3L07 ProjectExplorerMenues.JPG]]

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

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

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

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

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

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

[[category:DMXControl 3]]

[[de:Lektion_7_Tut3]]

Lesson 6 Tut3

2013-04-17T12:02:38Z

Jmintenbeck:

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

==Lecture 6: Configuring the output plugins ==

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

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

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

[[File:DMXC3L06_DE_IF_plugin.JPG]]

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

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

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

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

The entry must be constructed as shown below:
Universe.DMX start channel

The DMX512 standard only supports 512 address (also called channels). If more than 512 are needed, people will start a new set of DMX network connections and cabling. Each of these is called a "DMX Universe". Your DMX control device may support multiple DMX universes.

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

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

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

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

__NOTOC__
__NOTITLE__

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

[[category:DMXControl 3]]

[[de:Lektion 6]]

Lesson 5 Tut3

2013-04-17T12:02:14Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_4_Tut3
| TextBackwards = Lesson 4
| LinkForwards = Lesson_6_Tut3
| TextForwards = Lesson 6
}}
==Overview==
In this lesson we explain how to control the properties of devices by several property panels. DMXControl 3 provides an very powerful abstraction level for properties, allowing to handle different devices in the same way.

==Lecture 5: Setting properties of fixtures ==

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

In the animation of the icons in the '''Stage View''' you can see the results of your changes, especially for the moving lights.

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

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

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

Some remarks to the intensity panel:

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

[[File:DMXC3L05 propertyTS.JPG]]

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

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

[[File:DMXC3L05 propertyRGBParColor.jpg]]

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

[[File:DMXC3L05 propertyMix.JPG]]

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

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

[[File:DMXC3L05 PropertyGroupHandling.jpg]]

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

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_4_Tut3
| TextBackwards = Lesson 4
| LinkForwards = Lesson_6_Tut3
| TextForwards = Lesson 6
}}

[[category:DMXControl 3]]

[[de:Lektion 5]]

Lesson 4 Tut3

2013-04-17T12:01:52Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_3_Tut3
| TextBackwards = Lesson 3
| LinkForwards = Lesson_5_Tut3
| TextForwards = Lesson 5
}}
===Overview===
This lesson introduces into the stage view panel - a minimal 2D visualization tool which offers valuable support for programming your show.

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

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

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

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

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

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

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

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

[[File:DMXC3L04 liveView groups.jpg]]

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

{| class="wikitable"
|-
! key !! action !! result
|-
| M ("Matrix") || press key M and drag mouse || a matrix is created from the selected icons
|-
| F ("Fanning") || press key F and drag mouse || icons are proportionally aligned (e.g. in a row)
|-
| C ("Circle") || press key C and drag mouse || icons are aligned in shape of circle
|}

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

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

__NOTOC__
__NOTITLE__
{{NavigationTop-Tut3
| LinkBackwards = Lesson_3_Tut3
| TextBackwards = Lesson 3
| LinkForwards = Lesson_5_Tut3
| TextForwards = Lesson 5
}}

[[category:DMXControl 3]]

[[de:Lektion_4_Tut3]]

Lesson 3 Tut3

2013-04-17T12:01:20Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_2_Tut3
| TextBackwards = Lesson 2
| LinkForwards = Lesson_4_Tut3
| TextForwards = Lesson 4
}}
===Overview===
In this lesson we introduce the Project Explorer. This lesson helps you to understand how to create and patch your fixtures (devices) in DMXControl 3. We will also show you how groups of devices are created (automatically).

===Lecture 3: Creating and patching fixtures===

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

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

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

{{Picture_with_subtitle|DMXC3L03 projectExplorer.JPG|1|The project explorer|center|600px}}

==Add Devices==
As an example, in the following step we will create 4 moving lights of type "TS-255".

Click either on the button '''Device Manager''' in the menu bar of the Project Explorer or choose in the left pane of the Project Explorer the folder '''Devices''' and do a right mouse click into the right pane and select '''device manager''' (pic.2).
Select your devices and fill in the requested data. Please pay attention to define the correct start addresses. Fill out the fields in the window named "Add new device" as follows;
* Number of Devices; 4
* Device Name; TS-255
* DMX Start Address; 200
* DMX Space; 4
* Select the check-box marked "Autogenerate Group".
* Group Name; TS-255 Group 2
* Repeat; 1

{{Picture_with_subtitle|DMXC3L03 createDevice.JPG|2|The device manager, create device|center|600px}}

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

{{Picture_with_subtitle|DMXC3L03 createDeviceGroup.JPG|3|Create device groups|center|600px}}

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

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

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

===Additional Links and References===
*

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_2_Tut3
| TextBackwards = Lesson 2
| LinkForwards = Lesson_4_Tut3
| TextForwards = Lesson 4
}}

[[Category: DMXControl 3]]

[[de:Lektion_3_Tut3]]

Lesson 2 Tut3

2013-04-17T12:00:34Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| LinkBackwards = Lesson_1_Tut3
| TextBackwards = Lesson 1
| LinkForwards = Lesson_3_Tut3
| TextForwards = Lesson 3
}}
===Overview===
In this lessons you will learn how to operate with the panel system of DMXControl 3.0. You can assign your panels in a flexible way and save and restore your favorite configurations.

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

DMXControl 3 provides a lot of tools and windows. For different usage situations, different designs will be in focus. Therefore DMXControl uses a very flexible panel mechanism. You can create your own individual panel configurations.
The forms in the program can be unlocked to float above the main window or can be docked to the top, bottom, left or right margins. This versatility gives you the power to build screens that are easy to use and tailored to your personal preference and to move panels to several monitors. You can drag a window by grabbing its header bar. It will turn transparent, and small icons will appear on the screen to show where you can dock the window. A panel can also be set to occupy the left-over space in the middle (pic.1).

{{Picture_with_subtitle|DMXC3L02 PanelAssignment.jpg|1|Panel assignment|center|650px}}

Some important explanations:

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

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

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

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

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

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

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

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

==Hideaway Forms==
When you click the push-pin at the top of the forms next to the close-down ‘X’, it falls over.
The form becomes ‘unpinned’ and appears to slide off the edge of the screen. The remaining screen re-arranges itself and the space previously taken by the hideaway form is shared with the nearby forms (pic.2.

{{BoxHint
| Text=The push-pin applies to the PANE, not to a single window in it. When forms are sharing a pane they are hidden or revealed together.
}}

{{Picture_with_subtitle|DMXC3L02 WindowsManager.JPG|2|Unpinned window|center|650px}}

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

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

==Save/Restore Layout settings==
You can save and restore your individual layout setting by menu ''Settings->Layout''.

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

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

===Additional Links and References===
*

[[de:Lektion 2]]

__NOTOC__
__NOTITLE__

{{NavigationTop-Tut3
| LinkBackwards = Lesson_1_Tut3
| TextBackwards = Lesson 1
| LinkForwards = Lesson_3_Tut3
| TextForwards = Lesson 3
}}

[[Category: DMXControl 3]]

Lesson 1 Tut3

2013-04-17T12:00:06Z

Jmintenbeck:

{{Maintitle
| logo = Im-aim.png
| maintitle = First Steps: {{PAGENAME}}
}}
{{NavigationTop-Tut3
| upwards = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| LinkForwards = Lesson_2_Tut3
| TextForwards = Lesson 2
}}
===Overview===
Because the operating concept changed completely compared to DMXControl 2 it is necessary to nearly start all over again for the use of DMXControl 3. These lessons will help you to become familiar with this concept and provide you the skills necessary for the basic characteristics of the new user interface. First of a small glimpse of what is waiting for you (pic.1):

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

This lesson is an introduction to the distributed architecture of DMXControl 3.0. You will learn some facts about the client and server communication and how to operate the kernel.

===Lecture: Installation and Configuration===

DMXControl 3 is installed with the help of a setup wizard. It verifies that the required software is installed on the PC (see below) and offers to install it if necessary. Optionally, EasyView (a visualizer) can be selected.

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

DMXControl 3.0 consists of two programs. One acts as server, the other one as client. The server (hereafter referred to as kernel) manages all information related to the project, such as the list of lighting instruments, and the cue list, etc. The kernel runs on the Windows operating system, but can also be launched on Linux (with Mono). The client acts as an interface between the server and the user.

''Advanced note; One or more clients can run on several systems (PCs) in parallel. This structure enables you to work in teams for building and performing your show. DMXControl 3.0 also supports cooperation during the life cycle, i.e. you can execute scene lists during someone else is still programming the missing cues!

''The separation of the server and the client has following advantages: 
* ''if the client (user interface) fails, the kernel (server) continues including sending DMX output
* ''several users can share the kernel to work in a team
* ''kernel and user interface could run on different computers

==The kernel==

At first, lets start the kernel that is the DMXControl server. Currently this application is called "DMXControl 3 Kernel" or "Lumos.exe" (pic.2).

{{BoxHint
| Text=In the beta version you have to start the kernel as administrator when you used the standard installation.
}}

In future a default user don't have to be aware about the kernel process. It will be automatically started with DMXControl and is (hopefully) continuously running.

{{Picture_with_subtitle|DMXC3L01 kernel.JPG|2|Kernel window with miscellaneous information|center|600px}}

During the start-up process of the kernel you can observe what is loaded by DMXControl. The kernel is the central master of all information about devices, cues, projects etc. that can be accessed by the clients. And it provides the DMX mixer engine and output system.

The kernel provides a command shell (pic.3). By typing "help" you get an overview about all supported commands.

{{Picture_with_subtitle|DMXC3L01 konsole.JPG|3|Kernel window with command shell "help" overview|center|600px}}

Here are a few command line options to get more detailed information about the status of the kernel:
*shutdown: Ends the kernel
*status: Displays status information
*menu: menu-access control?
*clear: Clears the console
*notification xxx: Sends a notification to all clients
*width xxx: Specifies the width of the console (number of characters)
*load xxx: Loading a project
*save xxx: Saves the current project
*dmxout [channel, val] +: Sets DMX Out Values
*DMXin [channel, val] +: Sets DMX In Values
*help: help menu (also accessible via '?')

For further details on ''menu'' and ''status'' see Appendix 2.

==The client / user interface==

In the next step you should start the windows-based user interface (currently called "DMXControl 3 GUI" or LumosGUI.exe"), which is located in the sub-folder "GUI" in the program directory. This client is explained in more detail in the next lessons.
First, however, the communication between kernel and client is initiated automatically. When you start the client a connection window opens. You can also select the Menu ''Connection-->Connect'' in order to connect with the server. In the lower right corner of the DMXControl window there is a small blue/grey server-icon that shows a small cross in red if no connection exists. The connection window also opens if you click on that icon (pic.4).

{{Picture_with_subtitle|DMXC3L01 connect.JPG|4|Lumos GUI "Connect to DMXControl Server" window|center|450px}}

If you have installed a firewall you have to grant the communication between client and server(pic.5).

{{Picture_with_subtitle|700px-DMXC3 Tutorial Lektion1 Firewall.png|5|Firewall setup|center|650px}}

After establishing the connection you should see a small blue icon in the lower line of the DMXControl main window indicating the existing connection. A red cross indicates that the connection failed.

{{BoxHint
|Text=If you execute the "LumosGUI.exe" with the parameter "-nonetwork", the kernel will automatically start up a client and connect it directly to the kernel. Thereby you do not have to connect the client manually and the system is ready to go. '''After installation you will find an entry in your start-menu called "DMXControl 3". This option includes this parameter.'''
}}

==Project Management==

To start a new project, choose '''File => New Project'''. If you want to save the current project, click on '''File => Save Project''' or '''File => Save Project As...'''. All project files are saved in a zip-file. You can load saved files with '''File => Load Project'''.

The name of current project is indicated in the top line of DMXControl window.
.

===Exercise===

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

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

3) Try it: exit your DMXControl GUI by task manager and start again: The kernel continues running.

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

===Assumptions for installation===

DMXControl 3.0 requires following software to be installed:

* DirectX 9.0c
* .NET Framework 3.5 SP1 or higher
* XNA Framework 3.0(xnafx30_redist.msi)

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

{{NavigationTop-Tut3
| upwards = [[Tutorials DMXControl 3|Inhaltsverzeichnis]]
| LinkForwards = Lesson_2_Tut3
| TextForwards = Lesson 2
}}

[[de:Lektion 1]]

__NOTOC__
__NOTITLE__

[[Category: DMXControl 3]]

Tutorials DMXControl 3

2013-04-17T11:59:25Z

Jmintenbeck:

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

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

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

This tutorial is split into three parts:

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

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

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

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

Now have fun in learning DMXControl 3!

= Table of content =

{| width=100%
| width="50%" valign=top |
[[Lesson_1_Tut3|Lesson 1: Installation and configuration]] 
[[Lesson_2_Tut3|Lesson 2: The Panel concept of DMXControl 3 GUI]] 
[[Lesson_3_Tut3|Lesson 3: The Project Explorer]] 
[[Lesson_4_Tut3|Lesson 4: The Stage view ]] 
[[Lesson_5_Tut3|Lesson 5: Device properties and its control ]] 
[[Lesson_6_Tut3|Lesson 6: Configuration of output plugins ]] 
[[Lesson_7_Tut3|Lesson 7: Summary and some more details of setup ]] 
[[Lesson_8_Tut3|Lesson 8: Cues and cue lists ]] 
[[Lesson_9_Tut3|Lesson 9: Fanning, Chasers and other effects ]] 
[[Lesson_10_Tut3|Lesson 10: The Programmer view ]] 
[[Lesson_11_Tut3|Lesson 11: Triggers in cue lists ]] 
[[Lesson_12_Tut3|Lesson 12: Editing Cues and cue lists ]] 
[[Lesson_13_Tut3|Lesson 13: Presets ]] 
|valign=top |
[[Lesson_14_Tut3|Lesson 14: Summary and details - Programming ]] 
[[Lesson_15_Tut3|Lesson 15: Executors and use of cue lists ]] 
[[Lesson_16_Tut3|Lesson 16: SoftDesk ]] 
[[Lesson_17_Tut3|Lesson 17: Audio analyzer ]] 
[[Lesson_18_Tut3|Lesson 18: Beamer Tool ]] 
[[Lesson_19_Tut3|Lesson 19: Other DMX Clients ]] 
[[Lesson_20_Tut3|Lesson 20: Create new device definitions ]] 
[[Lesson_21_Tut3|Lesson 21: Summary and details for Execution ]] 
[[Lesson_22_Tut3|Lesson 22: Input Assignment ]] 
[[Lesson_23_Tut3|Lesson 23: Create a RGB Matrix]] 
[[Lesson_24_Tut3|Lesson 24: Transfer DMX values via ArtNet to DMXControl 2]] 
[[Appendix_1_Tut3|Appendix 1: Commands and Shortcuts]] 
[[Appendix_2_Tut3|Appendix 2: Tips for testing and behavior in case of error]] 
|}

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

Thanks for using DMXControl and working with this tutorial.

www.dmxcontrol.org

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

__NOTOC__
__NOTITLE__

[[Category: DMXControl 3]]

[[de:Tutorials DMXControl 3]]

Main Page

2013-04-17T11:58:59Z

Jmintenbeck:

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

{{Portalhead|ff0000|Welcome}}
DMXControl welcomes you in this Wiki warmly. In addition to the information on the [http://www.dmxcontrol.org/ project homepage] and the [http://www.dmxcontrol.org/forum/ forum] we want to give a support and complement to the free software DMXControl including all partner projects hereby.

{{Portalhead|ff0000|Recently Updated in DMXcontrol 2}}
<DynamicPageList>
category = DMXControl_2
count = 5
ordermethod = lastedit
</DynamicPageList>

{{Portalhead|ff0000|Recently Updated in DMXcontrol 3}}
<DynamicPageList>
category = DMXControl_3
count = 5
ordermethod = lastedit
</DynamicPageList>

{{Portalhead|ff0000|Latest User Reports}}
<DynamicPageList>
category = User_Reports
count = 3
ordermethod = lastedit
suppresserrors = true
</DynamicPageList>
<DynamicPageList>
category = Reports_General
count = 2
ordermethod = lastedit
suppresserrors = true
</DynamicPageList>

| width="35%" valign="top" |
{{Portalhead|ff0000|Newest Articles}}
<DynamicPageList>
namespace=main
notcategory = Internal
count = 5
</DynamicPageList>

{{Portalhead|ff0000|Recently Updated Articles}}
<DynamicPageList>
namespace=main
notcategory = Internal
ordermethod = lastedit
count = 5
</DynamicPageList>

|}

[[de:Hauptseite]]

__NOTOC__ __NOEDITSECTION__ __NOTITLE__

Tutorials DMXControl 3

2013-04-11T23:10:53Z

Jmintenbeck: fixed wrong interwiki links -> end of wiki-article