vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-07 03:50:11 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add back the recommendation for preferring VST3

Browse Source 
This was removed in 4a92034620 after the
VST2 callback prefetching from yabridge 3.2.0. Now with the recent VST3
optimizations, VST3 plugins always outperform VST2 plugins on my system
even when using plugin groups for the VST2 version (and not having to
use plugin groups is of course another good reason to prefer VST3).
This commit is contained in:
Robbert van der Helm
2021-05-14 18:39:32 +02:00
parent a9643577fd
commit 0df900647c
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+10 -6
View File
@@ -677,12 +677,16 @@ negative side effects:
You can find a guide to setting these things up on Ubuntu
[here](https://zezic.github.io/yabridge-benchmark/).
- [Plugin groups](#plugin-groups) can also greatly improve performance when
using many instances of the same VST2 plugin. _VST3 plugins have similar
functionality built in by design_. Some plugins, like the BBC Spitfire
plugins, can share a lot of resources between different instances of the
plugin. Hosting all instances of the same plugin in a single process can in
those cases greatly reduce overall CPU usage and get rid of latency spikes.
- If you have the choice, the VST3 version of a plugin will likely perform
better than the VST2 version.
- If the plugin doesn't have a VST3 version, then [plugin
groups](#plugin-groups) can also greatly improve performance when many
instances of same VST2 plugin. _VST3 plugins have similar functionality built
in by design_. Some plugins, like the BBC Spitfire plugins, can share a lot of
resources between different instances of the plugin. Hosting all instances of
the same plugin in a single process can in those cases greatly reduce overall
CPU usage and get rid of latency spikes.
## Building