You've met every building block this course covers. This section puts them together, then checks everything in one final quiz.
The whole picture#
Take one example through the whole system. A sound operator wants a button that mutes the presenter's microphone, turns red while muted, and shows the current level:
- The audio mixer is a connection, added under Connect. Its module supplies the mute action, a mute feedback and a level variable.
- The sound operator has a position, built under Position. It's their workspace, separate from the graphics operator's.
- The position has two surfaces: a Stream Deck beside the mixer and an iPad. Both show the same button, because they're two ways into the same position.
- The button runs the mute action when pressed. The feedback turns it red while the mute is on. A variable shows the level as text.
- It's a button, not a Cuelist or a workflow, because one control doing one job is enough.
If the same studio also needs its camera routes put back before every show, that's routing: a routing Preset that recalls the routes in one press, taken with care because it changes real signals.
Key points to remember#
- A connection is one device. A position is one person. A surface is one way in.
- A variable is a value. A feedback changes how a button looks.
- Routing changes real signals. Stage, check, then take, and trust the state the device reports.
- Check where you are and what a change does before you make it.
- Use the simplest control method that does the job.