VST3 Host for Praat — User Guide

A two-mode bridge between Praat and installed VST3 plugins: process a selected Sound through a VST3 effect, or render a selected MusicXML Strings object through a VST3 instrument.

Author: Shai Cohen Affiliation: Department of Music, Bar-Ilan University, Israel Version: 1.9.2 (2026) License: MIT License Repo: GitHub
Contents:

What this does

VST3 Host for Praat extends Praat AudioTools beyond audio effects. The same Praat command now detects the selected object and launches the appropriate backend automatically.

Sound → Pedalboard → VST3 effect → Sound
MusicXML Strings → parser → DawDreamer RenderEngine → VST3 instrument → Sound
Release architecture in v1.9.2:
  • Pedalboard is used only for conventional audio-effect processing.
  • DawDreamer is used for MusicXML-to-instrument rendering, instrument audition, native editor state, and instrument parameter access.
  • The experimental v1.8 VSTi probe/retry/chunk/part/note fallback paths have been removed.
  • The canonical Python backend filename is permanently host_vst.py; release numbers live inside the code, not in the filename.

Two operating modes

Effect mode

Selection: exactly one Praat Sound.

The Sound is written to a temporary WAV, processed offline by a VST3 effect through Pedalboard, and returned to Praat as:

<original_name>_vst

A mono Sound is automatically duplicated to stereo if the selected effect requires stereo input.

Instrument mode

Selection: exactly one Praat Strings object containing MusicXML.

The score is parsed into note events and scheduled directly on a DawDreamer VST3 instrument timeline. The rendered stereo result returns to Praat as:

<score_name>_vsti

All MusicXML parts are merged onto one selected instrument. Polyphony and the original note timing are preserved.

Quick start

  1. Install Python dependencies once:
    python -m pip install pedalboard soundfile dawdreamer
  2. Place VST_Effect_from_Praat.praat and host_vst.py in plugin_AudioTools/py/.
  3. In Praat, select exactly one object:
    • a Sound for effect processing, or
    • a Strings object containing <score-partwise> MusicXML for instrument rendering.
  4. Run VST_Effect_from_Praat... and choose Open host.
  5. In the host window, choose a plugin from the VST3 list or click Browse....
  6. Optionally click Open Plugin Editor and adjust the plugin in its own native interface.
  7. Use Audition 8 s to hear a preview.
  8. Click Process in Effect mode or Render in Instrument mode.
  9. When processing finishes, Praat imports the resulting Sound automatically.
Object type determines the mode. You no longer choose “effect” or “instrument” manually. One selected Sound opens Effect mode; one selected MusicXML Strings object opens Instrument mode.

The host window

The v1.9 interface is intentionally compact. The plugin's own editor remains the primary place for sound design; the host itself shows only controls needed for selection, audition and rendering.

VST HOST INSTRUMENT · MusicXML
[ Pianoteq 6 Stage                         ] [Browse...] [Rescan]
C:\Program Files\Common Files\VST3\Pianoteq 6 STAGE.vst3
Score: 4 parts · 32 notes · 15.8 s · 60 bpm

[Open Plugin Editor] [Audition 8 s] [Stop]            [Cancel] [Render]

Ready

▸ Advanced      ▸ Log
    

Primary controls

Advanced

Processing architecture

Praat side

Effect backend

Praat Sound → temporary WAV → Pedalboard → VST3 effect → output WAV → Praat

Effect processing remains the mature Pedalboard path used by earlier versions of the tool.

Instrument backend

MusicXML → note parser → add_midi_note() → DawDreamer graph → engine.render() → output WAV → Praat

DawDreamer owns the entire score timeline. Each parsed note is scheduled with pitch, velocity, onset and duration; the score is then rendered through one VST3 instrument graph.

Responsive final render: the final DawDreamer RenderEngine.render() call runs in a separate worker process. The Tk window remains responsive, reports elapsed time, keeps Cancel available, and terminates a genuinely hung VSTi after a watchdog timeout.

MusicXML rendering

Instrument mode accepts a Praat Strings object containing score-partwise MusicXML. The parser uses Python's standard XML library; no music21 or intermediate MIDI file is required.

MusicXML featurev1.9.2 behaviour
Pitch: step / alter / octaveConverted to MIDI note numbers. Microtonal values are rounded to the nearest semitone and reported in the Log.
Duration / divisionsConverted to quarter-note positions and then seconds.
Tempo<sound tempo="..."> is supported, including tempo changes. If no tempo is present, 120 bpm is used.
RestsAdvance the score timeline but generate no note.
TiesAdjacent tied notes of the same voice/pitch are merged into one sounding note.
Chord / backup / forwardHandled for polyphonic score positioning.
DynamicsMusicXML note or <sound dynamics> values are converted to note velocity; otherwise the host Velocity setting is used.
Grace / cue notesCurrently skipped and reported.
Pedal directionsDetected by the parser and reported, but v1.9.2 currently schedules notes only; sustain-pedal CC64 is not yet sent to DawDreamer.
One instrument per render: all score parts are merged into one VST3 instrument. Separate orchestration of different MusicXML parts to different VST instruments is not part of v1.9.2.

Parameters, state & presets

Native instrument state

In Instrument mode, closing the plugin's native editor saves its DawDreamer state under:

~/.vst_host/dawdreamer_states/

The next audition or render loads that state automatically. This is how a selected Pianoteq model, Kontakt instrument, or other plugin setup survives between host sessions.

Host presets

Host presets are stored as JSON files in:

~/.vst_host/presets/

They can include plugin path, tail, buffer size, text parameters and — for Instrument mode — velocity and sample rate. Native VST instrument state is stored separately as described above.

Text parameter syntax

name=0.6, another_parameter=0.9

Persistent configuration

General host settings and the VST3 scan cache are stored under ~/.vst_host/. Praat also keeps separate plain-text last-plugin preferences for effects and instruments.

Installation & dependencies

Files

Recommended location:

Praat/plugin_AudioTools/py/

Python packages

python -m pip install pedalboard soundfile dawdreamer

Effect mode requires Pedalboard. Instrument mode additionally requires DawDreamer and SoundFile. The Praat launcher probes available Python commands and now reports the exact missing package(s) rather than incorrectly saying that Python itself is missing.

Windows: if several Python installations exist, install the packages into the same interpreter that Praat finds. A useful check is:
py -3 -c "import pedalboard, soundfile, dawdreamer; print('ALL OK')"

VST3 discovery

The host scans standard VST3 locations and caches the catalogue in ~/.vst_host/vst_plugins.json. Use Rescan after installing a new plugin.

FAQ / troubleshooting

“Python was found, but ... is missing required package(s)”

The interpreter is valid, but one or more dependencies are missing from that specific Python installation. Install the package named in the message with python -m pip install ....

Instrument render takes a long time

The status line shows elapsed time while DawDreamer renders in a worker process. Cancel remains active. A watchdog is calculated from score duration (minimum 60 s, maximum 300 s); a VSTi that never returns is terminated with an explicit error rather than freezing the host indefinitely.

DawDreamer rendered silence

The MusicXML was parsed and notes were scheduled, but the selected VSTi returned zero audio. Open Plugin Editor, confirm that the desired instrument/preset is loaded and that its main stereo output is active, close the editor so its state is saved, then render again.

The Strings object is rejected

Instrument mode currently requires <score-partwise> MusicXML. <score-timewise> is explicitly rejected. The root element must appear near the top of the Strings object.

My instrument does not appear in the list

Click Rescan. If the automatic effect/instrument classifier cannot identify it, open Advanced and enable List every plugin, or use Browse... to select the .vst3 directly.

Parameter changes have no effect

Prefer the plugin's own native editor. For text parameters, use List parameters first and copy the exact exposed name or index.

Sentinel mechanism: Praat waits for a small completion file written by the Python host. The host writes it on success, cancellation or controlled exit so Praat's polling loop can stop cleanly.

Command-line usage

The same backend can also be called without the Praat GUI:

py host_vst.py input.wav output.wav plugin.vst3 [tail] [buf] [params] [dump]
py host_vst.py --instrument score.musicxml output.wav plugin.vst3 [tail] [buf] [params] [velocity] [sample_rate]