Chapter 16
Plugin hosting
Scan VST3 plugins #
Open the Libraries & Plug-ins settings tab, use Add Path... for a custom plugin folder, then choose Rescan before looking for a new VST3 instrument or effect. A plugin must be installed for the current operating system and compatible architecture. Scanning another platform plugin folder does not make those binaries usable.
The hosting mode choices are In DonutStudio and Separate process (crash protection). The separate process isolates the plugin from the main application process. It does not guarantee compatibility with every plugin. Check state recall and playback after changing the hosting mode.
The instrument browser lists scanned instruments; the effect browser lists scanned effects. Names, manufacturers, presets, and availability come from scan results and installed plugins. There is no fixed bundled VST3 catalog. Recheck the scan result when a plugin is absent.
These steps document VST3 hosting. Do not infer VST2 compatibility from a legacy category or an internal identifier. Support can depend on how the application was built, and each plugin needs its own compatibility check.
Load and edit a plugin #
Select the target track, open its instrument tile, and choose the scanned VST3 instrument. For an effect, use the track effect browser and choose the VST3 effect. Choose Open Editor in the device menu to use the plugin interface.
DonutStudio stores plugin state for project recall. The installed plugin still has to be available when the project reopens. If a device reports recovery or unavailable state, restore the intended plugin before treating the project as ready to render.
Hosted effects share the ordered track effect chain with built-in effects. Check whether you are editing an instrument or an effect before changing parameters or assigning automation.
Route keys from a plugin editor #
Open the hosted instrument or effect device menu and choose Key-press passthrough. Plugin only sends keys to the plugin editor. DAW only routes them to DonutStudio. Plugin and DAW (default) lets the plugin receive them and forwards applicable shortcuts to DonutStudio.
The default is the combined mode. DonutStudio remembers the choice per plugin, so another instance of that plugin can reopen with the remembered setting. Check it when text entry or a shortcut unexpectedly affects the project.
Use Plugin only while entering plugin text if the same key also triggers a DonutStudio command. Use DAW only when the plugin editor is open but you want project shortcuts. The combined mode can affect both the editor and project; test a harmless shortcut before using destructive commands.
Third-party plugin editors can handle keys differently across platforms. Check the actual editor with your chosen mode.
Tuning and plugin compatibility #
Plugins vary in support for per-note tuning, pitch bend, MPE, and VST3 tuning messages. DonutStudio can show capability badges and tuning choices for a detected plugin. Choose a route the plugin actually supports and compare a short chord before arranging an entire tuned part.
A listed capability or opened editor does not prove audible tuning, latency compensation, preset recall, or offline-render compatibility. Check the actual plugin with the phrase and export workflow you intend to use.
DonutStudio inside another DAW #
When another DAW hosts DonutStudio, that host controls the outer audio/MIDI route and playback clock. Enable the plugin input and output in the host and test one note before diagnosing the inner project.
Standalone audio export is unavailable in the hosted wrapper. Render the outer plugin output with the DAW. Keyboard passthrough for plugins hosted inside DonutStudio is a separate setting from keyboard focus or shortcut routing in the outer DAW.
Native and generic plug-in editors #
Choose Open Editor in the hosted device menu. In Settings > Graphics > Plugin Windows, turn on Use generic hosted plug-in editors to show generic parameter sliders instead of the native editor when hosting mode is In DonutStudio; turn it off to request the plugin's editor. Close and reopen an editor after changing this setting. In Settings > Libraries & Plug-ins, Separate process (crash protection) opens the editor supplied by the plugin and does not use the generic-editor preference; a plugin without an editor has no generic fallback in that mode.
These editor instructions have been checked against source. A native app walkthrough across platforms remains unverified.