Lesson 1 Tut3

DMXControl 3 lessons

Overview

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

Lecture: Installation and Configuration

DMXControl 3.0 provides a distributed architecture, i.e. there is a kernel that can communicate with several clients. The kernel runs basically on Windows operating system, but can also be launched on Linux (with Mono).

One or multiple clients can be started on different systems (Windows, iOS, Android). Thus, you can even work in teams for implementing and performing your show. DMXControl 3.0 supports also cooperation during the life cycle, i.e. you can execute scene lists during your mate is still programming the missing cues!

The separation of server and clients provides some benefits:

• the kernel continues in case of malfunction in the user interface and continues DMX output
• several users can share the kernel to work in a team
• kernel and user interface could run on different computers

The kernel

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

600px

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

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

600px

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

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

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

The client

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

Datei:DMXC3L01 connect.JPG

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

600px

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

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

topics to be added (by beta testers)

• how to save a project

Excercise

1) Please try following commands in command shell:

• menue
• status
• shutdown -> uups!

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

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

Assumptions for installation

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

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

Additional links and references

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 have understood the topics of this lecture and want to continue with next course: Lecture2: The panel concept

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

}}

Language:

Deutsch