Pianoteq STAGE vs. Other Virtual Pianos: Which Should You Choose?

Installing and Optimizing Pianoteq STAGE for Live Performance

OS: Windows ⁄₁₁ (64-bit) or macOS 10.14+ — use the latest stable updates and audio drivers.
CPU/RAM: Modern multi-core CPU and at least 8 GB RAM (16 GB recommended for large sessions).
Disk: SSD for faster load times.
Audio interface: Low-latency USB/Thunderbolt interface with up-to-date drivers (ASIO on Windows).
MIDI controller: Fully functional keyboard with MIDI over USB or DIN.
Backups: Export your presets and save Pianoteq license file to an external drive or cloud.

Download the Pianoteq STAGE installer from the official site.
Run the installer and follow prompts (choose 64-bit plugin locations if offered).
Authorize with your license (serial key or Studio/Modartt account).
Install any included sound packs/presets you need for the show.
Verify plugin and standalone launch: test standalone first, then in your DAW or host.

Prefer standalone mode for simplest routing and lowest latency.
Set audio device to your interface and select the correct sample rate (44.1 or 48 kHz).
Choose ASIO driver on Windows; enable Core Audio on macOS.
Set buffer size to balance latency vs. stability: 64–128 samples is typical for live if CPU allows.
Map your MIDI controller channel and enable MIDI through/OMNI as needed.
Route output to your mixing console: use stereo out or separate outs if you need parallel processing/monitor mixes.

Lower buffer size until you hear stable audio without dropouts; if glitches occur, raise buffer or freeze other processes.
Disable background apps (cloud sync, antivirus scans) before performance.
Use 64-bit standalone and minimize plugin instances.
Freeze or bounce any additional virtual instruments in your host; keep Pianoteq as the active live instrument.
Enable multithreading in your host if available; Pianoteq is efficient but benefits from CPU cores.
Consider increasing the audio buffer during patch changes or CPU-heavy passages.

Create a “Live” bank with only the patches needed for the gig.
Name presets with short, clear labels and use numeric ordering matching setlist order.
Save variations for different venue sizes (e.g., “Club,” “Theater,” “Cathedral”) adjusting reverb and EQ.
Use the built-in EQ, hammer, and voicing controls to tailor brightness and presence to the room.
Pre-test patches on the venue PA to adjust brightness/low end for stage bleed and FOH.

Send a dry/stage monitor mix to your monitor engineer if they prefer natural piano sound.
Provide FOH either a slightly brighter/tighter sound and a DI (stereo or L/R) feed; consider a separate aux output for reverb or stereo FX.
If using DI to PA, set output level conservatively to avoid clipping; leave headroom for FOH processing.
If running through a stage piano amp for monitoring, check phase and avoid duplicate reverb or heavy FX in both amp and FOH.

Map program changes or bank switches to a MIDI foot controller for hands-free patch changes.
Assign sustain, soft pedal, and any expression CCs to foot pedals.
Use expression mappings to control virtual pedal noise, release, or sympathetic resonance if needed for realism.

Have a backup laptop or a lightweight hardware keyboard patch exported (WAV) if Pianoteq fails.
Keep a second audio interface or USB hub available; test all cables and MIDI leads beforehand.
Create a short checklist for soundcheck: audio device, MIDI input, buffer size, preset order, output routing.

If you’d like, I can produce a sample “Live bank” preset list named and ordered to match a typical 10-song set.