Compare a button, a routing Preset, a Cuelist and a workflow, and choose the simplest one that does the job.
After this section you can:
Say what makes each of the four control methods different.
Choose the right control method for a new scenario and explain why.
Name the limits of a Free installation.
Buttons gives you four ways to make something happen: a button, a routing Preset, a Cuelist and a workflow. All four can "do things", so it's easy to pick the wrong one. In this section you'll learn how to choose.
Use the smallest tool that does the job. If a single button can do it, use a button. Reach for the others only when the task needs something a button can't give you.
The real question is usually not does someone press something? It's where should the task's order, state and logic live?
A button runs its own actions when someone presses it. It can run several actions together or one after another (ActionGroup), choose between actions depending on a condition (ActionLogic), and repeat actions while a condition holds (While). Use a button when one control doing its own job is enough.
A routing Preset is a saved set of routes. It's not a sequence and has no order: it puts a set of routes back to a known configuration in one go. You can build it by hand or capture the routes that are live right now. Any button or router panel can recall it.
A routing Preset is a list of routes with no order. Executing it puts all of them back at once.
A Cuelist is a list of cues that run in a set order. It remembers which cue is next, and it doesn't belong to any one button or position, so several people can control and follow the same list. Use it when steps must happen in a set order, or when many similar actions are easier to manage as rows in one list.
A workflow is the only method that can start without a press: on a schedule, on a timer, on an NFC read, on an incoming network request, or when a connection's state changes. It's also the only one that keeps its own values (workflow variables), available everywhere. Use it for those triggers, for logic that compares or transforms values, or to talk to another system. A workflow can recall a routing Preset or advance a Cuelist, so it can sit on top of the other three.
A small workflow: a timer starts it every 30 seconds, with nobody pressing anything.
People often reach for a workflow for anything that sounds complicated, because it sounds the most powerful. Ask: does this need to start without a press, or keep values over time? If not, it probably isn't a workflow.
The other common mix-up is treating a routing Preset and a Cuelist as the same kind of "saved thing". A Preset is a set of routes with no order. A Cuelist is an ordered sequence that knows where it is.
Open Routing → Presets, Cuelist and Workflow in turn. Each is where one of the methods lives. (Buttons live in positions, which you created in section 2.)
Decide which method fits each scenario best, and why:
Every Wednesday, four camera routes need to go back to the same M/Es for a recurring panel show.
A segment plays three clips and two graphics in a fixed order, and both the director and the technical director need to see what's next.
At 06:00 every day, with nobody in the building, the program feed should switch from a wide shot to a close-up.
An operator needs one control that mutes the presenter's microphone.
Check your answers:
Routing Preset. It's "put these routes back", with no order and no timing. You can capture it from the live routes once they're right.
Cuelist. The steps have a fixed order, and two people need to see what's next.
Workflow, with a schedule. Nobody is there to press anything, and only a workflow can start without a press.
Button. One control doing one job: no order, state or special trigger needed.
Quiz
Answer the questions for this section. You need 80% to move on.