From 0df900647cc1371b05ed1906d2f7dc20155c382c Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Fri, 14 May 2021 18:39:32 +0200 Subject: [PATCH] Add back the recommendation for preferring VST3 This was removed in 4a92034620ae1090a0b45b1e9b548cce05847cfe 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). --- README.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 2a35f1fe..f254edf0 100644 --- a/README.md +++ b/README.md @@ -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