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

No longer zero out VST3 audio buffers

Browse Source 
Apparently we also never did this for VST2 plugins, so this should be
safe. Filling the vectors with zeroes here had a non-negligible
performance impact according to perf.
This commit is contained in:
Robbert van der Helm
2021-05-23 15:55:29 +02:00
parent 8429919dfe
commit d2965e048d
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+4
View File
@@ -39,6 +39,10 @@ Versioning](https://semver.org/spec/v2.0.0.html).
unions yabridge uses to differentiate between single and double precision
floating point audio buffers, undoing all of our efforts at reusing objects
and preventing memory allocations in the process.
- VST3 output audio buffers are no longer zeroed out for the plugin. We did this
for VST3 plugins, but not for VST2 plugins. Since not doing this never caused
any issues with VST2 plugins it should also be safe to do the same thing for
VST3 plugins. This further reduces the overhead of VST3 audio processing.
- Further optimized VST3 audio processing by preallocating small vectors for
event and parameter change queues.
- VST2 audio processing also received the same small vector optimization to get