- dot2 User Manual
- dot2 Quick Start Guide
- 1 - Introduction
- 2 - Physical setup and layout
- 3 - Create a new empty show
- 4 - Adding and patching dimmers
- 5 - Controlling dimmers
- 6 - Fixture view
- 7 - The programmer
- 8 - Making and working with groups
- 9 - Store a cue and play it back
- 10 - Making more cues in the cue list
- 11 - Adding LED fixtures
- 12 - Working with colors
- 13 - Creating presets
- 14 - External screen
- 15 - Adding moving lights
- 16 - Controlling moving lights
- 17 - Making more groups and Presets
- 18 - More about cues and playback
- 19 - A look at Blind, Preview and DMX tester
- 20 - Fun with macros
- 21 - Building chasers
- 22 - Building dynamic effects
- 23 - Connect to onPC, 3D, Wings and Nodes
- 24 - Happy programming
- dot2 3D
- dot2 Release Notes
Getting Started Guide - Introduction
Table of contents of this topic
- Douglas Adams, The Hitchhiker's Guide to the Galaxy
Welcome to this guide through the dot2.
We are going to have a look at most of the functions of the dot2 console.
It's a learning curve and we suggest that you follow the steps in this guide precisely and then might experiment on your own afterwards.
It's also recommended that you read this guide from the beginning to the end. It doesn't make much sense if you jump around between the chapters.
The design and idea behind the console is that it should be easy to use and easy to understand.
When you are presented with different possibilities on the console, then you also see a short explanation of the options on the console. In this guide we are going to explain it a bit further and explore some of the differences.
This guide is written as if you are sitting at a physical console. I'll suggest you use an external USB keyboard and an external screen - preferably a touch screen, if you don't have a touch screen, then you'll also be happy with a USB mouse.
You can follow this guide using just a console, but you get a better experience with an external screen. There's more about connecting these external devices in the next chapter.
The different markup in this guide
Throughout this guide I'll use some different markings in the text.
If you need to press a key or I'm just referring to a key on the console it'll look like this: Help
Some keys have symbols and when we need to talk about them, I'll show you the key and also introduce the written word for those keys.
You also need to tap areas on the screen. It will look like this: System Clock.
If I need you to write something on the keyboard, I'll write it like this: f 42 at full I might also use this for a quick demonstration of syntax and commands.
If you need to enter text into the command line using a keyboard (I know you might not know yet what the command line is) or just look at the actual command the console is about to execute, it'll look like this:
And the response from the console would look like this:
Please follow the step of this guide and I hope you'll have a great experience with the dot2.
That's it! We should be ready to move on to the next chapter.