- dot2 User Manual
- New in the Manual
- Introduction
- Intended Use
- System Requirements dot2 onPC
- Installation of dot2 onPC
- What are...
- System Colors
- Command History
- Executor
- Values
- Background
- Programmer
- Groups
- Presets
- Tracking
- Cues
- Executors
- Chasers
- Effects
- Preview and Blind
- Network
- IPv6
- DMX Tester
- System Colors
- How to...
- Turn the console on and off
- Update the console
- Add, patch, change, and delete fixtures
- Save and load your show
- Use the command line
- Use Encoders in the onPC
- Work with groups
- Work with presets
- Work with cues
- Work with chasers
- Work with effects
- Connect nodes, wings, 3D and onPC
- Use external input triggers
- Use MIDI and MIDI Show Control (MSC)
- Use the external screen
- Use web remote
- Reset the console
- Keys
- Align
- At
- Backup
- Blind
- B.O.
- Clear
- Copy
- Cue
- Delete
- DMX
- [dot]
- Down
- Edit
- Effect
- [Encoder]
- Esc
- Exec (Executor)
- [Exec Flash]
- [Exec Go]
- Fix
- Fixture
- Flash
- Full
- Go-
- Go- (Large)
- Go+
- Go+ (Large)
- [GoFastBack] <<<
- [GoFastForward] >>>
- Goto
- Group
- Help
- Highlt (Highlight)
- Label
- If
- MA
- Macro
- Magic
- [Minus] -
- Move
- Next
- [Numeric keys]
- Off
- On
- Oops
- Page
- Page+
- Page-
- Pause
- Pause (Large)
- Please
- [Plus] +
- Preset
- Prev (Previous)
- Prvw (Preview)
- Select
- Set
- Setup
- Speed
- Store
- Thru
- Time
- Toggle
- Tools
- Up
- Update
- View [Eye]
- Views & Windows
- Control Elements
- Command Line
- Encoder Bar
- Executor Bar
- Preset Type Bar
- Title Bar
- View Bar
- Icons
- Add New Fixtures
- Backup
- Beam Preset Type
- Calculator
- Calibrate Screens
- Change Functions of Executor
- Choose Clone Method
- Choose Copy Method
- Choose Delete Method
- Choose Store Method
- Choose Update Method
- Clock
- Color Preset Type
- Command Line
- Configure Slot
- Control Preset Type
- Cues
- Dimmer Preset Type
- DMX
- Edit Cue Number(s)
- Effects
- Empty Executor
- Enter Name for
- Executor Bar
- Executor Pool
- Fixtures
- Fixture Schedule Overview
- Focus Preset Type
- Gobo Preset Type
- Global Settings
- Groups
- Help
- Import Fixture Type
- Key Backlight
- Leaving Patch & Fixture Schedule...
- Load Show
- Macros Pool
- Magic Speeds
- MIDI Configuration
- MIDI Monitor
- MIDI Show Control
- Network Interface
- Network Protocols Configuration
- Network Setup
- New Show
- Off...
- Oops
- Page Pool
- Patch and Fixture Schedule
- Position Preset Type
- Presets Pools
- Remote Inputs Configuration
- Save Show As...
- Select DMX Address...
- Select DMX Ports
- Select Fixtures ID(s)
- Select Fixture Type...
- Select Function for Remote Inputs Configuration
- Select Function of Executor
- Select Language...
- Select Session Number
- Select Station...
- Select Trig
- Select Type
- Select View
- Select View for External Screen
- Select Wing...
- Session Collision
- Settings of Executor
- Setup
- Shapers Preset Type
- Software Update via USB
- Sound Input Configuration
- Status and Messages
- System Clock
- System Information
- Time defaults
- Timecode Configuration
- Tools
- Video Preset Type
- Virtual Playbacks
- Window Settings
- Wings
- Wings & Nodes Diagnosis
- Control Elements
- Commands
- >>> [GoFastForward]
- <<< [GoFastBack]
- - [Minus]
- + [Plus]
- Assign
- At
- Black
- Blind
- Call
- Clone
- Copy
- Cue
- Default
- Delay
- Delete
- Dmx
- DmxUniverse
- Edit
- Effect
- Executor
- Fade
- Fix
- Fixture
- Flash
- Full
- FullHighlight
- Go
- GoBack
- Goto
- Group
- Help
- If
- IfOutput
- Invert
- Label
- Learn
- Macro
- MidiNote
- Move
- Off
- On
- OutDelay
- OutFade
- Page
- Park
- Pause
- Preset
- PresetType
- Preview
- Rate
- Record
- Release
- Remove
- Replace
- Select
- Selection
- SetIP
- SnapPercent
- Solo
- Stomp
- Store
- StoreLook
- SyncEffects
- Temp
- Thru
- Toggle
- Top
- Unpark
- Update
- View [Eye]
- Zero
- Hints for Operating
- Error Handling
- CrashLogCopy
- CrashLogDelete
- CrashLogList
- Error Messages
- Glossary
- dot2 Quick Start Guide
- dot2 3D
- dot2 Release Notes
What are cues
Cues are where we store the active values for our fixtures. This is very useful if we want to play it back later.
Cues are like a container where we can put values from our programmer. It then remembers the values. Cues are often stacked in a cue list.
The cues and the cue lists are stored to Executors and can only exist on executors. You can't have cues outside the executors. You can, of course, have values in your programmer without storing them in cues.
This can sound a little complicated, but the console usually does this for you. If you have active values and press store and then a key associated with an Executor then it will store a cue. If it doesn't know what you want to do, then it might ask you.
Cue also keeps the information about how we enter the cue. That's information like the fade times and delay and what triggers the cue (could be a Go key or something else).
Read the links below to understand more about executors or learn how to work with cues.