Performance Launcher — Real-Time Multichannel Audio & MIDI Cue Player
Turn selected Praat Sound objects into a multichannel performance set, triggered from the computer keyboard, a MIDI keyboard, or on-screen controls. Shape cue levels, fades, routing, and MIDI mappings in a dedicated live-performance GUI.
What this does
Select one or more Sound objects in Praat and launch them in a dedicated real-time audio engine. Every Sound becomes an independent cue that can be triggered via computer keyboard, MIDI note, or GUI play button. The interface provides per-cue gain, fade-in/out, channel offset, progress, and remaining time. Audio is loaded into RAM in advance for responsive triggering.
Key Features:
- Three triggering methods — MIDI keyboard, computer keyboard, and on-screen cue buttons
- MIDI note mapping — per-cue MIDI Learn, quick “Map from key…” assignment, and a dedicated MIDI Stop key
- Chromatic / Diatonic layouts — consecutive semitones or white keys only
- MIDI performance options — selectable input port and channel, optional note-off gate and velocity-sensitive gain
- Multichannel routing — selectable output interface/channel count and per-cue channel offsets; Windows ASIO support
- Real-time mixing — overlapping cues or exclusive playback, individual gain and fades, master gain
- Visual feedback — cue progress/countdown, MIDI activity/ignored-note feedback, status reporting
- Persistent settings — audio and MIDI port preferences, mappings, cue settings, and performance options restored across runs
- Optional MIDI dependency — the program still works without python-rtmidi
sounddevice for low-latency audio output, soundfile for reading WAVs, numpy for audio mixing, and tkinter for the GUI. The engine runs a real-time callback thread that mixes all active cues sample-accurately with fade-in/out and channel routing.
Quick start
- In Praat, select one or more Sound objects and run
PerformanceLauncher.praat. - Choose an Output Device and the required number of output channels.
- For MIDI performance, connect your controller, choose its port in MIDI In, and select the appropriate Ch (or Omni). Use the refresh button if needed.
- Play cues using their default MIDI notes (starting at C3 / note 48), computer keys, or GUI buttons.
- To reposition the set on your keyboard, select Chromatic or Diatonic, click Map from key…, and press the note for cue 1. To customize a single cue, click its note button and press a MIDI key.
- Optionally enable Note-off stops and Velocity. Adjust individual gains, fades, channel offsets, and master gain.
- Stop playback with the red MIDI Stop note, GUI Stop All, or Esc. Close the launcher to save settings and clean up temporary audio files.
python -m pip install sounddevice soundfile numpy. MIDI input additionally requires python -m pip install python-rtmidi in the same Python environment used by Praat AudioTools. Tkinter is also required. Without python-rtmidi, keyboard/mouse audio triggering remains available.Workflow: Praat → Performance Launcher
1 · Prepare in Praat
Edit, synthesize, or process Sound objects. Select the sounds to perform; their selection order determines the initial cue order.
2 · Export and launch
The Praat front end resamples exported copies to the highest selected sample rate, writes temporary WAV files and a JSON manifest, then opens the Python GUI. Original Praat objects are unchanged.
3 · Configure audio and MIDI
Choose the audio interface, channel count, master gain and exclusive mode. If using a MIDI controller, select its MIDI input port, channel, layout, and optional gate/velocity behavior.
4 · Map and perform
Use default mappings or MIDI Learn. Trigger cues, control per-cue gain/fades/routing, and follow their progress and remaining time. The MIDI Stop key and Stop All control fade out active cues.
5 · Save and close
On close, performance settings are saved for future sessions; temporary WAVs and manifest are cleaned up.
MIDI performance
Connect a MIDI keyboard to trigger Praat sounds as playable cues. MIDI Note On initiates a cue directly in the audio engine; the interface updates independently to show the received note, velocity and cue name.
Input and expressive controls
| Control | What it does |
|---|---|
| MIDI In | Select the connected MIDI input device; refresh the list after connecting a controller. The previously selected port is restored by name when available. |
| Ch | Listen to Omni (all channels) or one MIDI channel (1–16). |
| Note-off stops | Gate mode: releasing a mapped key starts that cue’s fade-out; with this off, notes trigger independently of key release. |
| Velocity | Use note velocity to scale each new cue’s amplitude as (velocity / 127)². Disable it for a fixed trigger level. |
| MIDI activity | Indicates incoming notes, mapped cues, unmapped notes and events excluded by the channel filter. |
Mapping notes to cues
| Action | Result |
|---|---|
| Default mapping | Cue 1 = C3 (note 48), then upward according to the chosen layout. |
| Chromatic | Every successive MIDI semitone triggers the next cue. |
| Diatonic | Only white keys are used. A starting black key is moved up to the next white key. |
| Map from key… | Press the desired starting MIDI note: cue 1 is assigned there and all following cues are laid out in sequence. The MIDI Stop key follows the last cue. |
| Click a cue’s note button | Learn one note from the next MIDI keypress. Right-click the button to clear its mapping. |
| Red ■ Stop note button | The next layout key after the final cue is assigned to Stop All by default. Click to learn another Stop note; right-click to clear. |
GUI Features
Main window layout
| Section | Controls | Description |
|---|---|---|
| Top bar | Stop All button, window title | Stop all currently playing cues with fade-out. |
| MIDI controls | MIDI In, refresh, Ch, Note-off stops, Velocity, layout, Map from key…, MIDI Stop | Choose your controller, assign notes, and configure expressive triggering. Available when python-rtmidi is installed. |
| Master controls | Master gain slider, Exclusive mode toggle | Global output level. Exclusive mode = new cue stops all others. |
| Device selector | Output device dropdown, Channels spinbox | Select the audio interface and output channel count (1–32, subject to device capabilities). Device labels identify their host API, including ASIO on Windows. |
| Cue grid | Scrollable list of cues. Each row contains:
Also: a MIDI note button (click to learn; right-click to clear), and editable fade-in/fade-out times in seconds. | |
| Status bar | Shows current action, device status, or error messages. | |
Playback modes
Restart mode (default)
If the same cue is triggered while playing, it stops (with fade-out) and restarts from the beginning. Ideal for drum hits or short phrases.
Overlap mode
Multiple instances of the same cue can play simultaneously (configured via manifest). Useful for layers and polyphonic textures.
Keyboard shortcuts
| 1–0 | Cues 1–10 |
| q–p | Cues 11–20 |
| a–l | Cues 21–29 |
| z–m | Cues 30–36 |
Global controls: Esc stops all cues (or cancels MIDI Learn); ↑/↓ adjust master gain by ±1 dB and →/← by ±0.1 dB.
Click a cue’s computer-key badge to customize the keyboard shortcut. MIDI assignments are configured separately in the MIDI note button.
Applications
Live electronic music performance
Trigger prepared loops, one-shots, sound layers, or longer passages from the computer keyboard or directly from a MIDI controller.
Workflow: Prepare sounds in Praat (filtering, spectral processing, granulation), select them, launch Performance Launcher, and perform using keyboard or MIDI (directly, with note learn and chromatic/diatonic layouts).
Sound installation / gallery
Use case: Autonomous or interactive playback of multiple sound files with individual level and pan control.
Workflow: Load ambient textures, field recordings, or spoken word cues. Use exclusive mode to ensure only one sound plays at a time. Connect to a multichannel speaker array using channel offset.
Theatre / dance production
Use case: Cue-to-cue playback with precise fade control.
Workflow: Each cue has its own gain and fade-out time. The stage manager triggers cues via keyboard. Progress bars show remaining time for each sound — essential for cueing next elements.
Rehearsal / practice tool
Use case: Quickly audition multiple versions of a processed sound.
Workflow: In Praat, generate several variations (different filters, pitch shifts, delays), select all, launch Performance Launcher, and trigger each version with a single key press for A/B comparison.
Workflow: Multi-track stem playback
Source: 8 stereo stems (drums, bass, pads, leads, etc.) prepared in Praat.
Settings: Output channels = 16 (or 8 stereo pairs). Set Ch+ offset for each cue to route to different speaker pairs.
Result: Independent level and mute control over each stem via the GUI, all synchronised by triggering simultaneously.
Workflow: A/B comparison for mastering
Source: Same audio file processed with different settings (e.g., different compressor thresholds).
Settings: Exclusive mode on. Assign neighbouring keys (e.g., '1' and '2').
Result: Quick switching between versions for blind listening tests.
- No MIDI input: Install
python-rtmidiin the interpreter chosen by the Praat launcher, connect the keyboard, refresh MIDI In, and select its port. - Notes are ignored: Set Ch to Omni to test; check the MIDI activity indicator for a filtered channel or unmapped note.
- MIDI port does not open: Another application (such as Live or Max) may already own it, especially on Windows.
- No audio: Choose the correct output device and channel count. For ASIO, match the hardware sample rate; changing devices can interrupt playback.
- Too many cue channels: A cue requiring more channels than the selected stream will be blocked rather than silently folded down.
- Computer keys do not trigger: Click the launcher window to focus it; text-editing fields suppress cue shortcuts while you type.
Configuration persistence
sounddevice.OutputStream callback (512-frame block size). The MIDI listener uses python-rtmidi and triggers the lock-protected engine without waiting for Tk GUI updates. Actual audible latency still depends on audio hardware, drivers, and buffer scheduling. Routing and fades occur in the audio callback.