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

Mention that VST3 plugins usually outperform VST2

Browse Source
This commit is contained in:
Robbert van der Helm
2021-02-28 15:47:15 +01:00
parent bf2f60e744
commit cf17e530f3
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11
View File
@@ -501,6 +501,17 @@ these negative side effects:
If anyone knows a good way to install an fsync patched version of Wine on If anyone knows a good way to install an fsync patched version of Wine on
other distros, then please let me know! other distros, then please let me know!
- If you have the choice, the VST3 version of a plugin usually performs better
than the VST2 version. This is because with VST2 a typical audio processing
cycle requires _at least_ two function calls plus another function call for
every parameter change and MIDI event. With VST3 all of that gets wrapped up
in a single function call. That significantly reduces the amount of
back-and-forth communication needed, and thus the potential overhead of
bridging. VST3 plugins also allow the host do some optimizations for plugins
that are not actively processing sound, which potentially reduces the overall
DSP load even further in a large project where there may be many tracks that
are not actively being used during most of the project.
- [Plugin groups](#plugin-groups) can also greatly improve performance when - [Plugin groups](#plugin-groups) can also greatly improve performance when
using many instances of the same VST2 plugin. _VST3 plugins have similar using many instances of the same VST2 plugin. _VST3 plugins have similar
functionality built in by design_. Some plugins, like the BBC Spitfire functionality built in by design_. Some plugins, like the BBC Spitfire