The workspaces

Node:Cue is organized around three workspaces: Cuelist, Pads and Playlist. Each provides content organization, controls and settings suited to its purpose.

Play a file

To get started, create a project with File → New Session, then save it with File → Save As. The .ncue file stores your preparation.

Open Preferences with Ctrl + P. In Local Preferences → Audio, choose the Cuelist bus output, then click Apply and Close.

In the Cuelist view, drop an audio file from Windows File Explorer. Select the Cue that was created, then click Go to play it.

Before the show

Show mode protects your preparation from accidental changes while keeping playback controls available. Enable it in the status bar when your project is ready.

Before the show, check the files in File → Project Health and test the audio outputs and controls you will use.

Main areas

The Cuelist, Pads and Playlist buttons in the title bar choose the player displayed in the main view. The Flow button opens the transition settings between these players.

• Control Bar: contains the playback controls and shows the element that Go will launch.
• Player content: displays the Cues, Pads or tracks in the active player.
• Sidebar: brings together the playback overview, compact player views, buses and Project Browser. Tab shows or hides it.
• Lower Panel: displays the selected element's properties, waveform, processing and Timecode settings. Ctrl + Tab shows or hides it.
• Status bar: provides access to preferences, the theme, Edit and Show modes, global Pad hotkeys, MIDI Map, Sync, Logs and detached windows.

When the Sidebar is wide enough, its split mode can display two views side by side. Each column can be resized. The playback overview and Project Browser can occupy both columns or just one.

A compact player's controls act on that player even when another view occupies the main window.

Edit and Show

Edit mode lets you import files, organize the project and change element properties.

Show mode locks these editing operations. Playback controls, transport settings, waveform navigation and bypass controls remain available. Switching modes does not affect ongoing playback.

Save and move a project

When first saving, Node:Cue creates a folder named after the project. By default, it is in the NodeCue folder in your Windows Documents. File → Save saves project changes. Save As saves it under another name or in another folder.

In File → Project Health, Missing indicates a file that cannot be found and External indicates media outside the project folder. Collect Project Media gathers media into that folder to make moving it easier.

To use the project on another computer, copy the entire folder, then open the .ncue file with File → Open Project. Save As does not copy media: after changing folders, use Collect Project Media to gather it in the new location.

Node:Cue accepts WAV, MP3, FLAC, OGG/OGA, AAC, M4A/MP4 and AIFF/AIF/AIFC files.

Manage multiple lists

Node:Cue can manage multiple Cuelists, Pad Sets and Playlists in one project. Project Browser lets you create these additional lists and switch between them.

You can also duplicate, rename or reorder lists in Project Browser. These operations are also available in File → Project Properties → Lists.

You can add a comment to each list in the Notes column of Project Properties → Lists. This comment then appears in Project Browser. The prefixes CL (Cuelist), PS (Pad Set) and PL (Playlist) distinguish the three list types; their number can range from 1 to 99.

Project setting or local preference?

Project Properties contains settings for the open project: its name, lists, MIDI/OSC patch points and playback options.

Local Preferences contains settings specific to the computer: audio outputs, MIDI devices, OSC endpoints, Timecode input, Sync connection, general hotkeys and display preferences. Local patch point assignments must also be adapted on each computer.

Restore an earlier state

Backups retain earlier project states and provide extra protection when Ctrl + Z can no longer undo a change. File → Backups lets you choose a backup to restore. Restoring replaces the current project state: first save any changes you want to keep. If the project folder is no longer available, use Save As to save the recovered project elsewhere.

Open last project on startup, in Local Preferences → Config → General, restores the session when Node:Cue opens, including unsaved changes, using automatic backups.

Basic controls

Go Enter launches the element shown in the Control Bar. For an audio element, playback starts at the position set manually in the waveform, or at the Start marker if the playhead has not been moved manually.

Pause / Resume Space pauses the relevant playback, then resumes it from the same position. Waits (Pre-wait and Post-wait) are also paused.

Stop Esc stops playback. Fade Out Backspace gradually lowers its level until it stops. These commands also cancel associated waits and delayed starts.

Stop all Esc × 2 stops all players and previews.

Set the scope of controls

In Project Properties → Project → Transport button scope, the scope options choose whether Pause Space, Stop Esc and Fade Out Backspace affect their player or all players.

When Fade Out affects all players, they share one fade duration. Otherwise, each player keeps its own duration.

Navigate

In Cuelist, Previous ↑ and Next ↓ select another Cue without launching it.

In Playlist, Previous and Next select another track when playback is stopped. During playback, they transition to the previous or next track. If Playlist is paused, they stop the paused track and select the adjacent track without starting audio.

Prepare and launch a Cue

In Edit mode, drop an audio file into Cuelist or use Add audio cue. Selecting a Cue displays its properties in the Lower Panel.

The name and ID identify the Cue in the show sequence. The waveform lets you view the sound and adjust the Start, End, Fade In and Fade Out markers. Go launches the Cue shown in the Control Bar.

In Local Preferences → Config → Cuelist, Advance selected cue on Go automatically selects the next Cue after a launch. Keep editor on launched cue keeps the Lower Panel on the launched Cue to follow its playback, then automatically displays the next Cue when playback ends.

A Cue set to Off stays in the project with its settings, but cannot be launched and is skipped during automatic playback.

Audio Cue Properties

The Properties tab in the Lower Panel contains the selected Cue's settings. The following table describes the fields and controls for an audio Cue.

Program automatic playback

Pre-wait adds a wait before the Cue's first launch. Post-wait adds a wait after it has run.

Play Count sets the total number of plays. Infinite play repeats playback until interrupted. When Play Next is enabled, the next Cue launches after the configured repeats and waits.

Overlap starts the next Cue before the current step ends. The value in this field brings the next Cue's launch forward by that amount.

Control Cues

Add stop cue adds a Stop Cue to Cuelist to include stopping another Cue in the show sequence.

In its properties, choose the Cue to stop in Target. Fade out chooses how it stops:

• Target fade uses the Fade Out configured in the target Cue's properties.
• Custom fade lets you set a different fade duration for this stop.
• Disabling Fade out stops the target Cue without a fade.

Add MIDI cue and Add OSC cue add command Cues. Their destination and message are set in their properties. The MIDI and OSC chapters explain output configuration.

These Control Cues can also trigger Playback Flow transitions when the corresponding option is enabled.

Group Cues bring several Cues together in a single step.

Create a group

In Cuelist, Create empty group creates an empty group. To add Cues, select them, right-click the selection, then choose Move to group from the menu.

Group selected cues Ctrl + G groups at least two adjacent Cues directly.

Ungroup removes the group while keeping its child Cues.

Select the Group Cue to choose its Mode in the properties. Its On/Off button makes the entire group available or unavailable without changing the individual state of its child Cues.

Playback mode

In Group Play mode, Go on the Group Cue launches all child Cues simultaneously. Each child Cue keeps its waits and repeats, but its Play Next and Overlap settings are not used.

The group can repeat: the next repeat starts once all child Cues have finished, including Post-wait. The group's Post-wait is added if set.

Sublist mode is mainly used to organize Cuelist by grouping Cues from the same part of the show. Child Cues keep their usual behavior, launched by the operator's Go commands or their own Play Next and Overlap settings. Go on the Group Cue launches the first available child Cue. The Group Cue's repeats, Post-wait and Play Next are inactive.

When a Group Cue is in Sequence mode, the Sequence manager appears in the Lower Panel. Child Cues play automatically in order. Overlaps are set in this manager; the child Cues' individual Play Next and Overlap settings are not used.

A child Cue can always be launched directly with Go on that Cue. It then behaves like any other Cue, independently of the Group Cue's mode.

The Group Cue's Gain is added to its child audio Cues' gain, including when they are launched individually. It does not replace their gain settings.

Prepare and launch a Pad

In Edit mode, drop an audio file onto an empty cell to create a Pad. Dropping another file onto an existing Pad replaces its media.

The Pad's edit button opens its Properties without launching it. You can change its name, audio settings, color, text color and image there.

The waveform lets you view the sound and adjust the Start, End, Fade In and Fade Out markers.

Click the Pad to launch it, or double-click if Double click mode is active.

Pad Properties

The Properties tab in the Lower Panel contains the selected Pad's settings. The following table describes its fields and controls.

Colors and images

The Text color and Pad color palettes apply the selected color immediately. Cancel undoes changes made since opening the palette for the affected Pads. Save as Default saves a color for new Pads; choosing Auto and saving it as the default restores automatic colors.

In presets, Auto uses the automatic background or text color. Automatic text color adapts to the Pad background for the best contrast.

Default recalls the saved default color so you can reapply it to the Pad. Image, Expand image / Adapt image and Clear image manage its background image.

Click and Re-click

Pad launch interaction, in Local Preferences → Config → Pads, chooses Single click or Double click triggering. The corresponding button in the main view and Sidebar also changes this mode.

When a Pad is already active, triggering it again applies its Re-click action: Stop, Restart or Pause / Resume. Direct clicks and the Pad's own hotkeys use this behavior.

Default re-click action, in Local Preferences → Config → Pads, sets the action for new Pads. Existing Pads keep their setting.

Go Enter launches or relaunches the selected Pad from the position set manually in the waveform, or from Start if the playhead has not been moved manually. It does not apply the Re-click action.

Grid pages

The Pad grid can be set from 3 × 3 to 5 × 5, independently for each page.

Reducing the number of rows or columns does not delete hidden Pads, but makes them inaccessible. The status bar indicates hidden Pads.

The mouse wheel, Page Up and Page Down change pages; Home returns to the first.

Repeats and exclusivity

Play Count, in the properties, sets the Pad's number of plays. Infinite play repeats its playback until interrupted.

Multi mode lets several Pads play together. In Single mode, a new launch interrupts the other Pads using the configured transition. Switching from Multi to Single does not itself stop ongoing playback.

Modes and transitions are described in Play Mode.

Prepare and launch a track

In Edit mode, drop audio files into Playlist. Drag rows to change their order. Selecting a track displays its audio properties in the Lower Panel.

The waveform lets you view the sound and adjust the Start, End, Fade In and Fade Out markers.

Select the starting track, then click Go Enter. Playlist continues with the following tracks according to the transition and loop settings.

A track's ID corresponds to its position in the list. Outside Random mode, moving a track automatically reassigns IDs.

Track Properties

The Properties tab in the Lower Panel contains the selected track's settings. The following table describes its fields and controls.

Trims and transitions

Auto Trim automatically sets each track's Start and End parameters to remove silence at the beginning and end of the file.

Setting Start or End manually on a track makes that parameter independent of Auto Trim. The manual setting is preserved even if you disable and then enable Auto Trim again.

To let Auto Trim set that parameter again, click M or Switch to Auto Trim on the corresponding marker.

Overlap automates crossfades between two tracks. Crossfade duration sets their transition duration.

You can apply a fade-in automatically to every Playlist Go launch. In Project Properties → Project → Go mode, choose Fade In and set its duration.

Loops and random order

The Loop button has three states.

• Off: playback stops at the end of the last track in the list.
• Loop playlist: at the end of the last track, playback continues from the start of the list.
• Single track: repeats only the current track.

At the top of Playlist, Random switches to random playback. Shuffle reshuffles Playlist in Random mode. Auto automatically triggers a Shuffle at each end of Playlist in Random mode.

Resume after stopping

Pause / Resume Space resumes a track where playback was paused.

After Stop Esc, Stopped at and Resume let you restart from the position retained in the session. A new launch replaces this resume point.

Last played track shows the last track that finished naturally.

Configure the input

The auxiliary menu in the Playlist view's Control Bar selects the auxiliary input device.

To receive audio from another application, assign that application an output to a virtual audio cable in Windows settings. We recommend VB-Audio VB-CABLE. In Node:Cue, select the virtual device corresponding to that output as the AUX input source.

To play the auxiliary source, select the AUX row in Playlist's content area, then use Go to open its audio feed to the Playlist bus.

AUX / Playlist transition sets the transition between the input and tracks.

Switch from music to AUX

Launching AUX interrupts Playlist tracks and their automatic starts. Launching or resuming a track closes AUX using the configured transition.

Stop Playlist and Fade Out close the AUX audio feed. The source stays selected and can be reopened with another Go. When the target is AUX, Pause, Previous, Next and Loop are unavailable.

AUX meters show the input level even when its audio feed is closed.

In the active playback panel, the AUX input display shows whether its audio feed is open, even when the source is silent.

Configure AUX on Backup with Sync

When using Sync, the AUX device is selected separately on Primary and Backup. Sync does not carry this input's audio signal.

For the AUX input to be available on Backup, the audio source must also reach that computer. Configure its AUX input and check its audio routing before enabling synchronization.

Configure Cuelist and Pads

Cuelist and Pads each keep their own Play Mode settings and transitions. Interruptions between players are configured in Playback Flow.

Open Playback Flow

Flow is available in the title bar of Node:Cue's three main views. Click Flow to open the transition settings menu between players.

Playback Flow assigns two separate transitions to each scenario: the main transition and the Alternative Transition.

Read the menu

Read the menu from left to right. Its default configuration uses these scenarios:

• When a Cue is launched: Playlist stops with a 3-second Fade Out. With Alternative Transition, Playlist also stops with a 3-second Fade Out before the Cue actually launches.
• When a Pad is launched: Playlist stops with a 3-second Fade Out. With Alternative Transition, Playlist also stops with a 3-second Fade Out before the Pad actually launches.
• When a Playlist track is launched: Cuelist and Pads stop with a 3-second Crossfade. With Alternative Transition, Cuelist and Pads stop with a 3-second Fade Out before the track actually launches.

Pause Playlist

Enabling Pause Playlist when interrupted pauses the current track instead of stopping it.

Apply Playback Flow to Control Cues

Apply Flow to Stop, MIDI, and OSC cues chooses whether Control Cues trigger the configured transitions.

If disabled, launching a Control Cue does not stop playback in Pads or Playlist.

Save the default configuration

Click Use as new-project default to save the Flow configuration as the default for new projects.

Configure the alternative transition

Configure Alternative Transition in the Flow window for the relevant Playback Flow row or Single Play mode. This configuration is used only when Alt Go is requested; normal starts still use the main transition.

If no alternative transition is configured, Alt Go has the same effect as a normal Go.

Trigger Alt Go

• press Alt + Enter in the active view;
• hold Alt while clicking Go or a Pad;
• click Alt Go when it is displayed because the option is enabled.

Alt Go respects the element's own Pre-wait and fades.

Assign outputs

In Local Preferences → Audio, the Driver choice determines the available devices and channels. In WASAPI, each bus can use its own device; in ASIO, buses use the selected driver's channels.

Bus routing assigns Cuelist, Pads and Playlist buses to Mono or Stereo outputs. Several buses can share an output. Their faders and Mute buttons remain independent.

When a configured device is lost, an alert identifies the affected buses. Audio unavailable in the status bar or on a bus opens audio preferences. If the same device becomes available again, Node:Cue attempts to restore its output without changing the selected assignment.

Adjust an audio element

Selecting an audio Cue, Pad or track displays its settings in the Lower Panel.

• Gain adjusts the element's level. Normalize applies the correction from the file's normalization analysis.
• Start and End define the part of the file to play.
• Fade In and Fade Out set the element's gradual fade-in and fade-out.
• BAL adjusts the balance.
• Equalizer and Compressor adjust the spectrum and dynamics before mixing into the bus.

For audio Cues and Pads, Play Count sets the total number of plays, from 1 to 999. Infinite play keeps repeating until interrupted.

Choose repeat fades

Repeat fades determines which plays receive fades when an audio element repeats. The first value is for Fade In and the second for Fade Out.

• First / Last: Fade In on the first play and Fade Out on the last.
• Every / Every: both fades on every play.
• Every / Last: Fade In on every play and Fade Out on the last.
• First / Every: Fade In on the first play and Fade Out on every play.

Infinite playback has no natural last play. These settings do not replace transport stop fades or transitions between players.

Use the waveform

The waveform displays the file and lets you move the Start, End, Fade In and Fade Out markers. Click in the waveform to position the playhead. During playback, this also changes the playback position.

When gain is too high, red lines appear in the waveform where peaks reach or exceed 0 dBFS with the applied gain. They indicate a clipping risk: reduce the affected element's gain.

The mouse wheel adjusts zoom. Shift + mouse wheel moves the visible area. The overview below lets you move or resize that area. Compact / L/R chooses a combined display or separate channels.

Follow playhead, to the left of Compact/L/R, enables automatic playhead tracking when the waveform is zoomed in. Disable it to keep the displayed area while working on a passage without stopping playback.

When the element is not playing, markers close to the playhead automatically snap to its position. Hold Shift while dragging to bypass snapping.

The four bypass buttons independently bypass trims and fades without erasing their values. A red cross indicates an active bypass. Right-clicking a marker changes the same state. W returns the playhead to the element's effective start without changing its playing or paused state.

Choose the output

In Local Preferences → Audio → Monitor, Enable Monitor enables the monitoring circuit. Assign the device and channels used by your monitoring system.

Monitor can use a dedicated output or share an output with a show bus. With a shared output, Bus Monitoring is unavailable. Preview remains available when show playback is stopped.

This setup can be used to prepare or rehearse a show sequence: Skip waits bypasses Pre-wait and Post-wait.

Preview an element

Single item mode previews the selected element once, ignoring automation such as repeats and Play Next automatic playback.

Show simulation mode reproduces transitions, groups and automatic playback in a show sequence. To preview a Group Cue, enable Show simulation mode.

Timing has two options: Skip waits bypasses Pre-wait and Post-wait; Follow timing respects them.

Select the element, then hold Ctrl while clicking the large Go button, which becomes PFL Go. On a Pad, Ctrl reveals Select and Preview areas. To stop previews, hold Ctrl and use Stop All PFL.

Send MIDI / OSC, available in Show simulation mode, allows real MIDI or OSC messages to be sent to the configured destinations. Leave it disabled to preview without sending MIDI or OSC messages.

Listen to the show

Bus Monitoring lets you listen to a Cuelist, Pads or Playlist bus, or all of them with All buses.

AFL mode follows the bus fader and Mute. PFL mode listens before those controls. Bus Level and the Monitor fader adjust the listening level.

Monitor and previews are unavailable on a Backup following Primary.

Configure local devices

In Local Preferences → Control → MIDI, MIDI input selects the devices from which Node:Cue receives messages. MIDI output selects the outputs used to send messages.

+ adds an input or output. Refresh devices updates the list of available devices after a connection.

These choices are specific to the computer. Assignments that determine what received messages trigger are saved in the project using MIDI Map.

Configure the project's MIDI patch

MIDI Cues use destinations defined in the project patch. Each destination must be linked to a local MIDI output device.

1. Open Project Properties → MIDI Patch and use + to add a patch point.
2. In the Patch point column, give it a name corresponding to its role in the show.
3. In Local MIDI Output, choose the output declared in local preferences.

This makes the project portable: the patch stays the same between computers. Only the local devices assigned to patch points may change, without modifying MIDI Cues.

Renaming a point preserves its Cue assignments. To delete a point in use, first reassign the affected Cues. An Unassigned point has no output assigned yet; an Unavailable output should be checked before sending.

Assign commands with MIDI Map

MIDI Map (in the status bar) assigns a received MIDI message to a Node:Cue command, such as Go, launching a Pad or adjusting a bus level. MIDI Learn learns the message sent by your controller.

1. First choose the MIDI input in local preferences, then open MIDI Map from the status bar.
2. In the assignment panel, click + and choose the command to control in Target.
3. Click MIDI Learn, then move or press your controller's button, fader or knob. The form captures the message type, channel and number.
4. Click Assign to save the assignment in the project.
5. Exit MIDI Map mode, then use the controller again to operate the assigned command.

You can also enter the message type, channel and number manually in the form. Double-click an existing assignment to edit it; Save then saves the changes.

During MIDI learning, use a fader or knob sending an absolute CC, a level value from 0 to 127, to assign a level command. Move it over a sufficient range for Node:Cue to recognize this continuous control.

Send a message with a MIDI Cue

A MIDI Cue sends a MIDI message from Cuelist. It uses a destination defined in the project's MIDI patch.

1. In Edit mode, use Add MIDI cue to add the Cue.
2. Select it and open its Properties in the Lower Panel.
3. In Destination, choose the MIDI patch point you want.
4. Enter the message type, channel and data, then launch the Cue with Go.

A Note message uses a note, velocity and duration. A Control Change uses a controller number and value. A Program Change uses a program number.

Use MIDI with Sync

Sync transfers project patch points and MIDI Map assignments. MIDI inputs, MIDI outputs and each patch point's local assignment are specific to each computer.

Prepare Backup devices and destinations on that computer. These local settings remain accessible while it follows Primary. While following, Backup ignores received MIDI commands and does not send MIDI Cue messages. Its local destinations are used when it operates in Standalone mode.

Configure local OSC connections

In Local Preferences → Control → OSC, + adds a named connection, called an endpoint in the application. Each connection has a name, mode, address or interface, and UDP port.

To communicate in both directions, create a Receive connection and a Send connection. These connections are local to the computer; they are not saved in the project.

For reception, the sender must send messages to the Node:Cue computer's IP address and chosen port. Also check that Windows Firewall allows this communication. Two Receive connections must not use the same interface and port.

Configure the project's OSC patch

OSC Cues use destinations defined in the project patch. Each destination must be linked to a local OSC connection in Send mode.

1. First create a Send endpoint in local preferences.
2. Open Project Properties → OSC Patch, then use + to add a patch point.
3. Give it a name in Patch point and choose its connection in Local OSC Endpoint.

This makes the project portable: the patch stays the same between computers. Only the local connections assigned to patch points may change, without modifying OSC Cues.

Renaming a patch point preserves its use by Cues. A point still in use cannot be deleted: first reassign the affected Cues.

The OSC patch is used only for outgoing OSC messages sent by Cues. Incoming messages that control Node:Cue use Receive endpoints without passing through the project patch.

Control Node:Cue by OSC

A Receive connection lets you control Node:Cue from an application or device capable of sending OSC messages.

All commands are listed in the OSC command reference.

The commands in the OSC reference’s Active View section control only the active view, like its playback controls.

The general /nodecue/cuelist/go command launches the Cue shown in the Control Bar. To choose a Cue by ID, use an explicit address such as /nodecue/cuelist/go/12.5. Adding an argument to the general Go address does not select another Cue.

Each player has its own open list. That player's OSC commands act on this list even when another view is displayed. Use /nodecue/cuelist/open/CL2, /nodecue/pads/open/PS3 or /nodecue/playlist/open/PL2 to change lists. This does not launch playback or stop playback from the previous list.

OSC bus IDs are 1 for Cuelist, 2 for Pads, 3 for Playlist and 4 for Monitor. For example, /nodecue/bus/leveldb/4 with the numeric argument -6 sets Monitor to -6 dB. /nodecue/aux/leveldb sets AUX in the same way. 0 means 0 dB and the text -inf means silence. The level commands keep their 0 to 1 scale. Cuelist, Pads, Playlist and AUX Fade Out commands, and global Fade Out, accept a duration from 0 to 60,000 milliseconds (60 seconds). Without a duration argument, they use the configured fade setting, capped at 60 seconds.

The rewind command, for example /nodecue/playlist/rewind, returns the selected audio element to its effective start while preserving its playing or paused state. /nodecue/stopall and /nodecue/fadeoutall affect all playback in the project, including previously opened lists.

Send a message with an OSC Cue

An OSC Cue sends an OSC message from Cuelist. It uses a destination defined in the project's OSC patch.

1. In Edit mode, use Add OSC cue to add the Cue.
2. Select it and open its Properties in the Lower Panel.
3. In Destination, choose the OSC patch point you want.
4. Enter the OSC address and arguments expected by that recipient, then launch the Cue with Go.

The OSC address starts with /. It identifies a command on the recipient, while the Send connection's IP address and port identify where to send the message. The address and arguments remain specific to the Cue when you change the connection assigned to the patch point.

Use OSC with Sync

Sync transfers project patch points and OSC Cues. OSC connections and their local patch point assignments are specific to each computer.

Prepare Backup connections and destinations on that computer. These local settings remain accessible while it follows Primary. While following, Backup does not execute received OSC commands or send its OSC Cue messages. Its local connections are used when it operates in Standalone mode.

Default shortcuts

Local Preferences → Hotkeys lets you view and edit general hotkeys. Commands marked Fixed cannot be changed, and an assigned combination cannot be reused.

Playback and preview

Project and interface

Selection and editing

Player navigation

When Node:Cue is not in the foreground, general hotkeys do not control playback. The crossed-out keyboard in the Control Bar indicates this state. Click in the playback control area to restore this function.

Global Pads Hotkeys

The Global Pads Hotkeys switch in the status bar lets you trigger Pad hotkeys while using another application with Node:Cue in the background. It is disabled by default.

This function uses the shortcuts assigned to available Pads in the open Pad Set, across all its pages. Node:Cue's general hotkeys do not become global. This setting is specific to the computer and cannot control a Backup following Primary.

In Local Preferences → Pads, Show floating Global Pads Hotkeys widget displays a small panel above other windows when Node:Cue is in the background. Its switch enables or disables global hotkeys. Closing this panel does not disable hotkeys.

Set up a key

Tools → Install Stream Deck plugin opens the plugin page on Elgato Marketplace. Once installed, add a Node:Cue action in Stream Deck.

Choose the command you want and, for a specific target, enter the requested ID. A general Go action launches the selected element in the player; an action by ID targets the specified element.

The name and state displayed on the key let you check the target. In Playlist, an action targeting a track by ID keeps that target in Random mode. Previous/Next follows the displayed order.

Available commands

The plugin 2.1 catalog contains the following 13 actions. In Stream Deck, choose an action, then set its source, target or mode when those options are available.

ALT action modes

Monitor action commands

Timecode action modes

ALT and PFL Go modifiers apply to Go commands launched from Stream Deck. They are exclusive: enabling one disables the other.

Configure reception

In Local Preferences → Control → Timecode, Enable Timecode displays the associated tools. Choose MTC with its MIDI input, or LTC with its audio input and channel.

Frame rate sets the rate used, in frames per second. Freewheel sets how long Node:Cue can keep advancing timecode if the signal is lost.

The Timecode monitor displays the received value and reception state. Locked means Node:Cue is synchronized with the received signal.

Displaying the tools and arming are separate. Arm allows Cues to trigger.

Program a start

In the Lower Panel, the Timecode tab defines one or more trigger timecodes for a Cue. In Edit mode, select the Cue and use Add trigger to enter a value in HH:MM:SS:FF format: hours, minutes, seconds and frames. Capture current timecode uses the currently received value directly.

After checking the Cue, its trigger timecode and the frame rate, enable Arm timecode. When received timecode reaches the programmed value, Node:Cue triggers the Cue with its transitions and Pre-wait. These settings can delay the start of audio.

Disarm prevents new Timecode triggers without stopping playback already launched.

Shifts and signal handling

Shift Cue by and Shift Cuelist by move a Cue's or Cuelist's trigger timecodes earlier or later, depending on the chosen scope. Enter the shift duration, then use − to bring triggers forward or + to delay them.

If the signal is lost after synchronization, Freewheel lets Node:Cue keep advancing timecode for the configured duration. Cues scheduled during that period can still trigger. If the signal has not returned in time, Node:Cue waits for a synchronized signal again before triggering further Cues.

If timecode jumps forward by several seconds, Cues whose trigger times were passed are not launched automatically.

With Sync, only Primary triggers Cues from Timecode. Backup follows Primary's triggers.

How it works

Primary sends committed project changes and playback commands to Backup. Backup applies these events in the same order and plays audio in parallel, but its local controls and project changes stay locked while it follows Primary.

If Primary becomes unavailable, Backup automatically switches to Standalone mode and becomes available to the operator without interrupting ongoing playback.

Requirements

Before configuring Sync, check the following:

• both computers use the same Node:Cue version;
• both computers are connected by a stable local network, preferably Ethernet;
• the project is saved on Primary;
• project media is available on Backup. Use Collect Project Media to gather audio files and Pad images into the project folder;
• both systems are in a clean state established with Stop all: no playback, pause, wait, fade or delayed action should be active;
• audio outputs, devices and backup paths are configured and tested separately on each computer.

The roles

Standalone

The computer operates alone. This is the normal state before pairing, after Stop Sync and after losing Primary.

Primary

The computer controlled by the operator. It retains authority over project changes and transport commands.

Backup

The backup computer. It follows Primary, keeps audio playing in parallel and becomes available for manual takeover if a failure occurs.

Detailed role configuration and pairing are described in Configure Sync.

Configure Primary

Choose Primary in the role selector. Then configure:

• Network interface: the local IPv4 interface where Primary accepts Backup's connection. Auto keeps normal system routing; an explicit interface limits listening to that address;
• Sync port: the TCP port used for the Sync connection. It must be identical on both computers;
• Heartbeat interval: how often the connection is checked, from 50 to 5000 milliseconds. The default 100 ms suits a stable wired network.

Save preferences, then use Sync in the status bar and Start Primary to wait for Backup's connection.

Configure Backup

Choose Backup in the role selector. Then configure:

• Network interface: the local interface used to reach Primary;
• Primary IP: the full IPv4 address of Primary's network interface;
• Sync port: the same TCP port configured on Primary;
• Link resilience: tolerance for missed heartbeats. Fast tolerates 5, Balanced 8 and Safe 15. Safe is the best starting point when the network may experience brief interruptions; Fast detects loss of Primary sooner but tolerates less network variation. This setting mainly determines how quickly Backup switches to Standalone if the connection to Primary is lost. A fast setting may cause the two computers to lose synchronization if network jitter is too high.

Prepare Backup controls

Project MIDI and OSC patch points are shared between the computers. Their physical assignments remain local and must be prepared on Backup.

In Project Properties → MIDI Patch, assign each used point to an output on this computer in Local MIDI Output. In OSC Patch, Local OSC Endpoint selects the corresponding local OSC endpoint.

These assignments remain editable on a Backup following Primary without changing project patch points. Confirm them with Apply.

Ready indicates an available destination. Unassigned means a destination is not assigned; Unavailable means it is unavailable. Correct these states and test the affected equipment before relying on Backup to take over the show.

Pair the computers

Pair using Sync in the status bar after saving connection settings on both computers.

1. Save the project on Primary and use Stop all on both computers to end playback and pending actions.
2. On the main computer, open Sync and click Start Primary.
3. On Backup, check Primary's address, then click Connect to Primary.

If Primary's project is not present on Backup, Download project downloads it with its media. This transfer must be requested; importing a file on Primary does not trigger it automatically.

If the project is already present but its settings differ, use Align from Primary. If files are missing after alignment, Restore missing files retrieves them.

Link, Project, Media, Audio, Control and Playback indicators check different aspects of readiness. They do not replace testing each computer's physical outputs.

Modify the project

A change to a Cue, Pad or Playlist element is sent to Backup as long as the relevant media is already present locally. The audio file or image remains specific to each computer: importing on Primary does not trigger an automatic download on Backup.

Adding an audio Cue, Pad or Playlist element therefore requires downloading the new media to Backup with Download project or Restore missing files, then resynchronizing the project. Backup should not be considered ready until resynchronization finishes.

Project changes, Save As and Collect Project Media must be performed after stopping Sync. For other media imports, stopping Sync first remains the recommended procedure so you can prepare the file on Backup before resuming synchronization.

What is synchronized

Primary sends, in particular:

• committed changes to Cues, Pads and Playlist elements;
• playback, transition, fade, wait and loop settings;
• Go, Stop, Pause, Resume, Fade Out, Play next and Stop all commands;
• selections and playback states needed to prepare a consistent takeover.

What stays specific to each computer

Machine-related items remain local:

• the audio device and physical outputs;
• local MIDI interfaces, devices and output assignments;
• local OSC endpoints and their listening interfaces;
• Timecode inputs and their local settings;
• network interfaces and Sync connection settings;
• local media paths when the project is already present on both computers.

Backup remains read-only while following Primary. MIDI and OSC commands are suppressed as external effects during this phase while retaining their synchronized playback state. Project MIDI mappings stay identical, but their physical destinations are adapted to Backup's local outputs. OSC Receive endpoints also stay configured locally for takeover after switching to Standalone.

Monitor the session state

Synced means events are being applied, both instances' projects match and required media is available. Needs Resync, Media missing, Degraded and Diverged indicate that a check or intervention is needed.

Degraded can indicate a non-blocking playback difference. Diverged means an event was rejected or the projects no longer converge. In either case, do not consider Backup ready until the displayed issue is resolved.

After losing Primary

If Primary fails, Backup switches to Standalone mode without interrupting ongoing playback. You can use it to continue the show without interruption.

To restore synchronization, wait until nothing is playing, click Start Primary on the main computer, then click Connect to Primary on the backup computer.