vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-09 20:29:10 +02:00
Code Issues Packages Projects Releases Wiki Activity

Mention that VST3 modules might not be unloaded

Browse Source 
In certain hosts.
This commit is contained in:
Robbert van der Helm
2021-02-14 11:28:45 +01:00
parent 9f756b4881
commit 6165e46ec8
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6
View File
@@ -548,6 +548,12 @@ include:
section for instructions on how to set this up. This is not necessary for VST3 section for instructions on how to set this up. This is not necessary for VST3
plugins, as multiple instances of those plugins will always be hosted in a plugins, as multiple instances of those plugins will always be hosted in a
single process by design. single process by design.
- Some hosts, particularly _Ardour_, _REAPER_, _Qtractor_, will by default not
unload VST3 modules after you close the last plugin. This means that the
associated `yabridge-host.exe` process will keep running until you close the
project. For REAPER there's an option called
`Allow complete unload of VST plug-ins` in the `VST` tab of the settings
dialog to disable this behaviour.
- **Drag-and-drop** from applications running under Wine to X11 does not yet - **Drag-and-drop** from applications running under Wine to X11 does not yet
work, so you won't be able to drag samples and MIDI files from a plugin to the work, so you won't be able to drag samples and MIDI files from a plugin to the
host. At least, not directly. Because Windows applications have to create host. At least, not directly. Because Windows applications have to create