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.
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.
- 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:
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:
All MusicXML parts are merged onto one selected instrument. Polyphony and the original note timing are preserved.
Quick start
- Install Python dependencies once:
python -m pip install pedalboard soundfile dawdreamer
- Place
VST_Effect_from_Praat.praatandhost_vst.pyinplugin_AudioTools/py/. - In Praat, select exactly one object:
- a Sound for effect processing, or
- a Strings object containing
<score-partwise>MusicXML for instrument rendering.
- Run VST_Effect_from_Praat... and choose Open host.
- In the host window, choose a plugin from the VST3 list or click Browse....
- Optionally click Open Plugin Editor and adjust the plugin in its own native interface.
- Use Audition 8 s to hear a preview.
- Click Process in Effect mode or Render in Instrument mode.
- When processing finishes, Praat imports the resulting Sound automatically.
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.
[ 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
- Plugin selector – installed VST3 plugins are scanned and classified; Instrument mode prefers instruments, Effect mode prefers effects.
- Browse... – choose a
.vst3directly. - Rescan – refresh the installed VST3 catalogue after installing or removing plugins.
- Open Plugin Editor – opens the VST3's native editor in an isolated worker process.
- Audition 8 s – renders and plays an eight-second preview.
- Process / Render – executes the final operation.
- Cancel – cancels the host. During DawDreamer rendering it can terminate a stuck render worker.
Advanced
- Tail seconds – additional time after the last input/note for reverb and release tails.
- Buffer size – processing block size. Instrument mode defaults to 512; Effect mode keeps its own saved/default setting.
- Velocity – Instrument mode only; used when the MusicXML contains no dynamic value for a note.
- Sample rate – Instrument mode output rate; common choices include 44.1, 48, 88.2 and 96 kHz.
- Text parameters – optional parameter assignments. For most plugins the native editor is preferable.
- List parameters – displays exposed plugin parameters in the Log.
- Presets – save and restore host-side settings.
- List every plugin – bypass the effect/instrument filter when necessary.
Processing architecture
Praat side
- The script determines the mode from the selected object.
- For a Sound, Praat writes a temporary WAV. For a Strings object, it writes the MusicXML lines to a temporary
.musicxmlfile. - Praat launches
host_vst.pyas a detached Python process and polls a sentinel file while the Python host is open. - On success, the rendered WAV is imported back into the Objects window and optionally played.
- Effect and instrument modes remember separate last-used plugin paths.
Effect backend
Effect processing remains the mature Pedalboard path used by earlier versions of the tool.
Instrument backend
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.
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 feature | v1.9.2 behaviour |
|---|---|
| Pitch: step / alter / octave | Converted to MIDI note numbers. Microtonal values are rounded to the nearest semitone and reported in the Log. |
| Duration / divisions | Converted to quarter-note positions and then seconds. |
| Tempo | <sound tempo="..."> is supported, including tempo changes. If no tempo is present, 120 bpm is used. |
| Rests | Advance the score timeline but generate no note. |
| Ties | Adjacent tied notes of the same voice/pitch are merged into one sounding note. |
| Chord / backup / forward | Handled for polyphonic score positioning. |
| Dynamics | MusicXML note or <sound dynamics> values are converted to note velocity; otherwise the host Velocity setting is used. |
| Grace / cue notes | Currently skipped and reported. |
| Pedal directions | Detected by the parser and reported, but v1.9.2 currently schedules notes only; sustain-pedal CC64 is not yet sent to DawDreamer. |
Parameters, state & presets
Native instrument state
In Instrument mode, closing the plugin's native editor saves its DawDreamer state under:
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:
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
- Effect mode uses parameter names exposed by Pedalboard.
- Instrument mode accepts a DawDreamer parameter name or numeric parameter index.
- DawDreamer parameter values are normalized to the range
0.0–1.0. - Use List parameters to inspect names/indices/current values before entering text assignments.
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
VST_Effect_from_Praat.praat– Praat launcher and object-type router.host_vst.py– canonical Python backend. Keep this exact filename.
Recommended location:
Python packages
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.
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
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 ....
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.
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.
Instrument mode currently requires <score-partwise> MusicXML. <score-timewise> is explicitly rejected. The root element must appear near the top of the Strings object.
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.
Prefer the plugin's own native editor. For text parameters, use List parameters first and copy the exact exposed name or index.
Command-line usage
The same backend can also be called without the Praat GUI: