How CUE Player Improves Your Audio Workflow

CUE Player: Ultimate Guide to Features & SetupCUE Player is a flexible cue-management and audio-playback application designed for live events, theatre productions, podcasts, and broadcast workflows. This guide walks through its core features, setup steps, advanced configuration, troubleshooting tips, and practical workflows to help you get the most from the app.

What CUE Player does best

CUE Player focuses on reliable, low-latency playback and precise cue control. Its strengths include:

Robust cue lists for organizing tracks, sound effects, and voiceovers.
Accurate timing and pre-roll so cues trigger exactly when needed.
Multiple output routing to send different sounds to separate speakers or channels.
MIDI and OSC support for external control from consoles, footswitches, or custom controllers.
Cross-platform compatibility (Windows/macOS/Linux) where available.
Safe-play features such as pre-load, fade controls, and emergency mute.

Installation and initial setup

System requirements

Ensure your system meets minimum requirements: modern multi-core CPU, at least 8 GB RAM (16 GB recommended for large sessions), and a low-latency audio interface for live use. SSD storage is strongly recommended for fast sample load times.

Installation steps

Download the correct installer for your OS from the official site or vendor.
Close other audio apps to avoid device conflicts.
Run the installer and follow prompts.
Launch CUE Player and choose your audio device in the initial audio preferences dialog.

First-time configuration

Select your audio driver. Use ASIO (Windows) or Core Audio (macOS) for best latency. On Linux choose the recommended JACK or ALSA settings.
Set sample rate and buffer size. For live cues, aim for buffer sizes that balance stability and latency (e.g., 128–256 samples).
Choose output routing: map stereo or multi-channel outputs to the physical outputs of your interface.

Core features explained

Cue lists and cue types

CUE Player organizes material into cue lists (sometimes called “shows” or “scenes”). Common cue types:

Audio file cue — plays a sound file (mp3, WAV, FLAC, etc.).
MIDI cue — sends MIDI messages.
OSC cue — sends OSC commands to control other networked devices.
Group cue — triggers multiple cues together.
Script cue — runs simple automation scripts or macros.

Playback modes

Manual: operator triggers cues one-by-one.
Auto/Follow: cues advance automatically after set durations.
Triggered by MIDI/OSC: external devices trigger cues.

Pre-roll, fades, and crossfades

CUE Player supports pre-roll (previewing audio through headphones without sending to mains), configurable fade-in/out shapes (linear, logarithmic), and crossfade curves for smooth transitions.

Timecode and synchronization

Supports LTC/MTC timecode input and SMPTE synchronization for aligning with lighting desks or video playback.

Hotkeys, MIDI, and OSC control

Assign keyboard shortcuts, MIDI notes/CCs, or OSC addresses to any cue or control. This enables hands-free triggering from consoles, footswitches, or tablets.

Multi-channel routing and matrix mixing

Map cues to individual outputs or use an internal matrix to route and mix signals to different channels. Useful for in-ear monitors, front-of-house playback, and stage foldback.

Creating a show: step-by-step

Create a new show or cue list and save it immediately.
Import audio files — drag & drop is usually supported. Organize files into folders or groups.
Rename cues clearly (e.g., “Scene 2 — Door Slam”).
Assign outputs and levels for each cue.
Set pre-roll for cues you’ll preview live.
Add fades and set durations for auto-advance where needed.
Map MIDI/OSC triggers for hands-free control.
Test run the show in rehearsal, adjusting buffer sizes, fades, and levels.
Save a backup copy and export cue list if the app supports show packages.

Advanced configuration

Redundancy and backup

Use a secondary machine and sync cue lists via exported show files.
Maintain offline backups of all audio assets on an external drive.
Some setups employ two audio interfaces with mirrored outputs for failover.

Networked playback and remote control

CUE Player can be controlled over a LAN using OSC or a proprietary remote app. Secure the network by using a dedicated switch and avoiding Wi‑Fi for critical shows.

Scripting and macros

Script cues allow conditional logic (if/then), looping, and variable substitution for dynamic shows (e.g., variable countdowns or randomized effects).

Integration with lighting and video

Use timecode or OSC triggers to align audio with lighting cues and video playback. Test synchronization under live load; add timecode offsets if necessary.

Common problems and fixes

Audio stuttering or dropouts: increase buffer size, close background apps, use dedicated audio drivers (ASIO/Core Audio), ensure SSD for assets.
MIDI/OSC triggers not responding: confirm correct IP/port, check firewall settings, verify channel/note mappings.
Latency too high for live needs: lower buffer, use ASIO drivers, reduce system load, disable power-saving CPU features.
Crashes on large shows: update to latest version, increase RAM, split large shows into sublists.

Practical workflows and tips

Rehearsal-first: Always rehearse with the final audio interface and same buffer size you’ll use live.
Naming convention: Use concise, consistent cue names that include scene numbers.
Two-stage triggering: use pre-roll for previewing and a separate “GO” trigger for mains output.
Level checks: include a dedicated silence or calibration cue at the start for quick level setting.
Use groups: group related cues (ambience, SFX, music) for single-button triggering.

Comparison: Basic vs. Advanced usage

Aspect	Basic use (small shows)	Advanced use (theatre/broadcast)
Setup complexity	Low	High
Routing needs	Stereo out	Multi-channel, matrix routing
Control methods	Keyboard/manual	MIDI/OSC, timecode, scripts
Redundancy	Simple backups	Dual machines, mirrored outputs
Synchronization	Manual	LTC/MTC, SMPTE, network sync

Example show checklist (quick)

[ ] Confirm audio interface and driver
[ ] Load show file and verify cue order
[ ] Test each cue’s output and level
[ ] Verify MIDI/OSC mappings
[ ] Rehearse full run with team
[ ] Save backup and export show package

Final notes

CUE Player is built for precision and reliability in live audio playback. The key to success is careful organization, rehearsal with the final hardware, and implementing redundancy for critical productions. With MIDI/OSC control, scripting, and multi-channel routing, it adapts from simple podcast episodes to complex theatrical shows.

If you want, I can: export a sample cue list template, draft MIDI mapping suggestions for common consoles, or walk through setting up a specific audio interface.