ASCENSION CUEBOARD

Run the show by moments—not by timestamps.

Not every production runs to a clock. CueBoard is Ascension's operator-driven playback environment for the moments that happen when the show caller says GO. Build complete show states as cue columns, route rows to the outputs and layers that need them, and execute coordinated media, transitions, layer looks and external control without forcing a live show into a timeline.

Ascension CueBoard showing routed rows and coordinated cue columns

Operator-driven show control

One column can represent the entire next moment.

Rows describe destinations. Columns describe cue moments. When a column fires, Ascension coordinates the programmed change across the rows that participate in that cue.

01

Destination-driven rows

Route each row to the required Ascension node, output channel and user layer. Assets dropped into that row inherit the destination.

02

Coordinated cue columns

Combine multiple assets and destinations into one operator action instead of firing unrelated playback commands one at a time.

03

Multiple CueBoard decks

Separate acts, rooms, operating responsibilities or alternate sequences into focused decks inside the same Event.

04

Live engine status

Follow the active column, media progress, loop state and elapsed or remaining timing from the state reported by the running server.

05

Persistent spans

Keep backgrounds, ambience, live sources or music active across multiple cue positions while other rows continue to advance.

06

External actions

Send supported network-control commands as part of the same cue that changes media and visual state.

CueBoard deck tabs, transport clocks, rows and cue controls

A grid that reads like the show

Keep live programming immediate.

Drag media, Inputs, NDI sources, Templates and URLs from the Ascension Library into the grid. Move an asset horizontally to change its cue position or vertically to change its destination with the row. Replace sources directly in-place without rebuilding the surrounding show structure.

  • Next, Previous, direct-column play and stop controls
  • Named decks and cue columns for operator clarity
  • Row locking to protect finished programming
  • Primary timing asset with elapsed and remaining clocks
  • Intentionally empty columns can create a clean clear/black state

Cue-specific behavior

The source stays intact. The cue gets the behavior.

Playback choices belong to the CueBoard instance rather than the original media. Trim, route, transition and shape the cue for the job it has to do in this show.

CueBoard asset properties with playback, routing and transition controls
ASSET OPTIONS

Route and play it the way this cue needs.

Set volume, playback rate, looping, clone routes, node/output destinations, cue delay and independent Transition In / Transition Out behavior.

Ascension nondestructive trim editor
NONDESTRUCTIVE TRIM

Use exactly the part of the media you need.

Set trim-in and trim-out points against a visual preview while keeping the original source untouched.

Ascension Stinger Transition properties
STINGER TRANSITIONS

Cover the complete state change.

Assign Stinger media to an incoming cue, choose its cut point, destination, level and geometry, then let Ascension take the new CueBoard state underneath the transition.

Desired Layer Configurations

Recall a different visual look for an individual cue.

A CueBoard asset can carry the layer appearance it should recall when that cue is played. One item can be full-screen, the next a PIP, and another can recall crop, zoom, rotation, opacity, keying, border or treatment settings without changing the normal Layer Default.

The Desired Layer Configuration belongs to that CueBoard asset. Edit it with Ascension's normal Output Space and Layer Controls, save it back to the cue, and the programmed look returns whenever that item is taken.

GeometryZoom + PanCropRotationOpacityKeyingTreatment
Ascension Layer Controls used to build per-cue visual configurations
Ascension Remote Command Options for timed network control

External control inside the cue

A GO can change more than the media server.

Attach external control to the same CueBoard column that advances the show. Ascension can send supported Companion, AV-Key, Custom UDP, OSC and Art-Net DMX actions, including a programmed millisecond delay when the device action should occur after the cue begins.

A column does not need media to be useful. It can exist purely as a device-control moment inside the operator's CueBoard sequence.

COMPANIONAV-KEYUDPOSCART-NET DMX

Stream Deck + Virtual Console

Build the control surface once. Put it wherever the operator needs it.

Ascension includes its own Stream Deck control system rather than treating the hardware as a collection of fixed hotkeys. Design consoles inside the show, build button actions from Ascension functions, and use the same control surface from connected Stream Deck hardware or the browser-based Virtual Console.

Ascension Stream Deck Setup editor showing button layout, cue stack, node target, function selection and live status

Control-surface editor

Program buttons as show actions—not keyboard shortcuts.

Each button can execute a single command or a stack of cues. Add actions, insert or reorder them, target local or remote nodes, apply millisecond delays, and select the cue that defines the button's icon, automatic text and live-status color.

CueBoardTimelineBackgroundsPixel Space + TrackPGM ScreensClear LayersAV-KeyCustom UDP

Ascension Redundancy Control · ARC

Keep the operator connected even when Main fails.

Ascension Redundancy Control (ARC) brings remote Stream Deck control and the Ascension browser workspace together on a Windows, macOS or Linux operator workstation. Connect the deck by USB, launch ARC, and operate a single Ascension server or a configured Main / Backup pair.

For redundancy, run ARC and the attached decks on a separate third workstation, independent of both media servers. With protection armed, ARC confirms configured Main faults and checks Backup readiness before transferring control. The browser view and Stream Deck commands follow the selected server, keeping the operator connected through the takeover.

The handover can also coordinate the rest of the production. ARC can automatically send configured TCP or UDP command strings to compatible switchers, routers or automation systems when transferring to Backup or returning to Main.

STREAM DECKUSBARC WORKSTATIONLANMAIN / BACKUP
  • Remote Stream Deck control for a single server or a redundant pair
  • Selected shared commands coordinate operation across Main and Backup
  • Multiple attached decks retain their configured button faces and live status
  • After failover, stay on Backup until the operator chooses to return to Main
  • Windows, macOS and Linux ARC packages are available from the Ascension interface

Using a Stream Deck directly on the Ascension server? Enable it through Settings > Stream Deck to use the installed local bridge. ARC is the recommended client for remote operation and independent redundancy control.

Explore ARC protection and external actions
Ascension Redundancy Control download dialog with single-server and Main / Backup guidance, Windows, macOS and Linux packages, and installation instructions
Ascension Virtual Console in a desktop browser mirroring a configured Stream Deck surface
DESKTOP VIRTUAL CONSOLE

The console is not tied to the hardware.

Open the Virtual Console in a browser and operate the configured surface with the same pages, button identities and live state. Select the console, choose a page, scale the surface to the display and keep show control separate from the main programming workspace.

Ascension Virtual Console running responsively in a phone browser
MOBILE VIRTUAL CONSOLE

Put real show control in a phone browser.

The same surface adapts to a mobile display for roaming operation, backup control or a compact operator station—without creating a second set of commands.

Operator-driven or clock-driven

CueBoard and Timeline belong in the same production.

Use CueBoard when the next moment happens when the room is ready. Use Timeline when media and control must follow a programmed clock. Ascension Events can use both.