Lesson 1 Tut3

table of content Lesson 1: Installation and configuration Lesson 2: The Panel concept of DMXControl 3 GUI Lesson 3: The Project Explorer Lesson 4: The Stage view Lesson 5: Device properties and its control Lesson 6: Configuration of output plugins Lesson 7: Summary and some more details of setup Lesson 8: Cues and cue lists Lesson 9: Fanning, Chasers and other effects Lesson 10: The Programmer view Lesson 11: Triggers in cue lists Lesson 12: Edit of cues and cue lists Lesson 13: Presets Lesson 14: Summary and details - Programming Lesson 15: Executors and use of cue lists Lesson 16: Softdesk Lesson 17: Audio analyser Lesson 18: Multimedia Support Lesson 19: Other DMX Clients Lesson 20: Create new device definitions Lesson 21: Summary and details for Execution Lesson 22: Input Assignment Lesson 23: Create a RGB Matrix Lesson 24: Transfer DMX values via ArtNet to DMXControl 2 Appendix 1: Commands and Shortcuts Appendix 2: Tips for Testing and behaviot in error case

{{#tree:id=dmxc3|openlevels=1|root=DMXC 3 lessons|

• preamble
• lesson 1: Installation and configuration
• lesson 2: The GUI panel concept
• lesson 3: Creating and patching fixtures
• lesson 4: The live view panel
• lesson 5: Setting properties with property panels
• lesson 6: Output plugins
• lesson 7: Summery and details - Setting
• lesson 8: Scenes (cues) and scene lists
• lesson 9: Fanning, chasers and other effects
• lesson 10: The programmer view
• lesson 11: Trigger concepts
• lesson 12: Editing scenes and scenelists
• lesson 13: Presets
• lesson 14: Summary and details - Programming
• lesson 15: Working with parallel scene lists
• lesson 16: Softpult
• lesson 17: Artnet
• lesson 18: Multi-media: Beamer tool, Matrix etc.
• lesson 19: Other clients and plugins (Android, iOS, ...
• lesson 20: Create new device definitions
• lesson 21: free topic
• lesson 22: Hints for testers and test reporting
• appendix1: Summary of commands ans shortcuts
• appendix2: Kernel menu tree

}}

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:

This lecture introduces into the distributed architecture of DMXControl 3.0. You will learn some facts about the client and server communication and how to operate the kernel.

Lecture: Installation and Configuration

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

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

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

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

The separation of the server and the client has following advantages:

• if the client (user interface) fails, the kernel (server) continues including sending DMX output
• several users can share the kernel to work in a team
• kernel and user interface could run on different computers

The kernel

At first, lets start the kernel that is the DMXControl server. Currently this application is called "DMXControl 3 Kernel" or "Lumos.exe" (hint: in the beta version you have to start the kernel as administrator when you used the standard installation). In future a default user don't have to be aware about the kernel process. It will be automatically started with DMXControl and is (hopefully) continuously running.

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

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

Here are a few command line options to get more detailed information about the status of the kernel:

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

For further details on menu and status see appendix 2.

The client

In the next step you should start the Windows-based user interface (currently called "DMXControl 3 GUI" or LumosGUI.exe"), which is located in the subfolder "GUI" in the program directory. This client is explained in more detail in the next lessons. First, however, the communication between kernel and client is initiated automatically. You can also select the Menu Connection-->Connect in order to connect with the server. When you start the client a connection window opens.

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

Error creating thumbnail: File missing

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

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

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

Project Management

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

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

Excercise

1) Please try following commands in command shell:

• menue
• status
• shutdown -> uups!

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

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

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

Assumptions for installation

DMXControl 3.0 requires following software to be installed:

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

Additional links and references

1. DirectX 9.0c
2. .NET Framework 3.5
3. .NET Framework 3.5 Service Pack 1
4. XNA Framework 3.0 (Has to be installed even if a higher version of XNA framework is already installed)

Certificate

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

table of content Lesson 1: Installation and configuration Lesson 2: The Panel concept of DMXControl 3 GUI Lesson 3: The Project Explorer Lesson 4: The Stage view Lesson 5: Device properties and its control Lesson 6: Configuration of output plugins Lesson 7: Summary and some more details of setup Lesson 8: Cues and cue lists Lesson 9: Fanning, Chasers and other effects Lesson 10: The Programmer view Lesson 11: Triggers in cue lists Lesson 12: Edit of cues and cue lists Lesson 13: Presets Lesson 14: Summary and details - Programming Lesson 15: Executors and use of cue lists Lesson 16: Softdesk Lesson 17: Audio analyser Lesson 18: Multimedia Support Lesson 19: Other DMX Clients Lesson 20: Create new device definitions Lesson 21: Summary and details for Execution Lesson 22: Input Assignment Lesson 23: Create a RGB Matrix Lesson 24: Transfer DMX values via ArtNet to DMXControl 2 Appendix 1: Commands and Shortcuts Appendix 2: Tips for Testing and behaviot in error case

__NOTITLE__