Bitfocus AS
logo
logo
Bitfocus AS
logo
logo
Sign upSign in

Loading...

Bitfocus

Subscribe to our newsletter

The latest news, articles, and resources, sent to your inbox.

FacebookInstagramGitHubYouTubeLinkedIn

Products

  • Buttons
  • Companion

Integrations

  • Supported Devices
  • Developer Community
  • Connection Development

Support

  • Support Overview
  • Documentation
  • Video Tutorials
  • Community Forum

Sales

  • Resellers & Integrators
  • Buttons Pricing

Updates

  • Case Studies
  • Events & Trade Shows
  • Press Releases
  • Product Updates
  • Webinars

Legal

  • Legal Overview
  • Privacy Policy
  • Buttons EULA
  • Terms & Cookie Policy

Company

  • About us
  • Press kit
  • Careers

© 2026 Bitfocus AS. All rights reserved.

Understand Cuelists
Docs for
Overview
Getting started
What is Bitfocus Buttons?
Install Buttons and get started
Manage your Buttons license
Activate Buttons offline
Find your way around Buttons
Create your first backup
Add an ATEM connection
Choose a control method
Choose an installation path
Install Buttons on Debian or Ubuntu
Understand HA clustering
Kubernetes HA
Update or remove Buttons
Positions
Understand positions
Create a position
Add controls and sections to a position
Create your first button
Use a connection's presets
Build more capable button actions
Add more feedback to a button
Organize controls in a section
Shift Section
Organize controls with a Folder Section
Add a Popover Section
Build and reuse a Shared Section
Build a Router Section
Understand Custom Routers
Custom Router panel
Surfaces
Surface compatibility
Add and attach a surface
Device orientation
Connections
Update a connection's module safely
Monitor and troubleshoot a connection
Router integrations
VideoHub and AJA KUMO
Utah Scientific BPS
Generic SW-P-08
Nevion VideoIPath
Arkona BLADE//runner
Routing
Physical routing
Configure ports and labels
Take a physical route
Understand route status
Topology graph
Routing Presets
Get started with virtual routing
Configure Nested Shapes
Reverse routing
Tielines
Routing Projects
Routing settings
Troubleshoot a route
Tally
Understand the Tally system
Send ATEM tally and labels to a UMD
Interpret Active Tally state
TSL/UMD connections
Diagnose tally problems
NMOS
Understand NMOS in Buttons
Connect Buttons to an NMOS Registry
Built-in Registry Server
Configure NMOS connections
Discover and adopt
Browse the NMOS inventory
Manage NMOS multicast addresses
Diagnose NMOS problems
Understand Cuelists
Build a Cuelist
Read and advance a running Cuelist
Control a Cuelist from a Position
Workflows
Understand workflows
Build your first workflow
Reuse a group of workflow nodes safely
Troubleshoot a workflow
Recipes
Sequence a timed automation
Call an HTTP endpoint from a workflow
REST endpoint
Use variables
Understand variable scope
Understand nested variables
Update expressions for v1.8
Plan and use Tags
Access
Create and manage users
Create roles and assign permissions
Grant access to specific resources
Show different controls by role
Sessions
Set up PIN and NFC sign-in
SSO
Get started with SSO
Connect a generic OIDC provider
Connect LDAP or Active Directory
Map identity claims to roles
Secure a Buttons deployment
Integrations
External control
Connect to Bitfocus Listener
USB Relay
Install USB Relay on Windows
Install USB Relay on macOS
Install USB Relay on Linux
Install USB Relay on a Raspberry Pi
Get started with the Control API
Secure and monitor the Control API
Control API reference
API reference
Administration
Enable and manage installable features
Services and health
Configure and monitor scheduled backups
Restore a backup and verify it
Export or import Buttons configuration
Store and rotate connection secrets
Replace the HTTPS certificate
HA backup and recovery
Settings
Collect support information
Reference
Glossary
Button Inspector reference
Network ports reference
Expressions
Internal actions reference
Routing Presets panel reference
Startup configuration reference
Workflow nodes
Connection workflow nodes
Workflow workflow nodes
Internal workflow nodes
Position workflow nodes
API workflow nodes
Utility workflow nodes

Loading...

Previous
← Diagnose NMOS problems
Next
Build a Cuelist →
Contact support →
You are viewing documentation for Buttons 1.8.See the docs for Buttons 1.6
Buttons/Cuelists/Understand Cuelists

Understand Cuelists

A Cuelist can help you build a determined show order (a rundown of cues to fire in sequence during a live production) or simply act as a compact alternative to many individual buttons, keeping a long list of related actions organized as rows instead of scattered across a canvas. Both uses are the same feature: a list of Cues, each firing a stack of actions when it runs.

The model#

Cuelist
→ Cue (a row, with a name and color)
  → Sub Cues (optional, nested under a parent Cue)
  → Actions (fired together, or one after another with delays)
A Cuelist is its own top-level resource in Buttons: it isn't a section you build inside a Position, and there's no separate control block for it either. Each Cue is one row: a name, a color, and a stack of actions to run when the cue executes.
Cues can be nested as Sub Cues under a parent Cue, letting you group related steps (for example, a set of camera moves that all belong under one segment of a show) without flattening everything into one long list.

Actions inside a cue#

A cue's actions aren't limited to single, independent steps. Selecting + Add Action offers recently used actions plus two structural options:
  • ActionGroup: bundles several actions to run either Sequentially (one after another) or Concurrently (all at once).
  • ActionLogic: runs different actions depending on a condition, using a feedback or an expression as the test: a When true branch fires if the condition holds, an Else branch fires if it doesn't.
You can nest these (an ActionGroup can contain an ActionLogic, and vice versa) to build cues that do more than fire a flat list of commands.

Reading cue state#

While a cuelist is open, each cue shows its own current state as an icon next to its number: whether it's simply next in line, currently selected and ready to run, actively running, or has completed. This state is visible directly in the same view you build the cuelist in: there's no separate "show mode" to switch into.

Why use a Cuelist instead of individual buttons#

  • Determined show order: when steps genuinely need to happen in a specific sequence, a Cuelist keeps that order explicit and lets you move through it deliberately rather than trusting an operator to press the right buttons in the right order.
  • Compact alternative to many buttons: when you have a long list of similar actions, a Cuelist keeps them organized as rows you can scan, search, and reorder, rather than filling a canvas with individual controls.

Where to go next#

  • Build a Cuelist.
  • Read and advance a running Cuelist.
  • Control a Cuelist from a Position.

Was this helpful?

Was this helpful?

0 of 0 users found this page helpful