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

Merge the two prefetching changelog entries

Browse Source
This commit is contained in:
Robbert van der Helm
2021-04-29 12:25:48 +02:00
parent a495f1a67f
commit a0abfed689
1 changed files with 11 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+11 -13
View File
@@ -10,19 +10,17 @@ Versioning](https://semver.org/spec/v2.0.0.html).
### Added
- During VST2 audio processing calls, yabridge will now prefetch the current
transport information and send that to the Wine plugin host along with the
audio buffers. This lets us cache this information during the processing call,
which significantly reduces the overhead of bridging VST2 plugins by avoiding
one otherwise mandatory back and forth function call between yabridge's plugin
and the Wine plugin host. This has an even greater impact on plugins like
_SWAM Cello_ that request this information repeatedly over the course of a
single audio processing cycle. Previously yabridge had a `cache_time_info`
compatibility option to mitigate the performance hit for those plugins, but
this new caching behaviour supercedes that.
- Similarly, yabridge will also prefetch the current process level during audio
processing to reduce bridging overhead for plugins that use this, like the
_Meldaproduction_ plugins.
- During VST2 audio processing, yabridge will now prefetch the current transport
information and the process level before sending the audio buffers to the
Windows VST2 plugin. This lets us cache this information during the audio
processing call, which significantly reduces the overhead of bridging VST2
plugins by avoiding one or more otherwise mandatory back and forth function
call between yabridge's plugin and the Wine plugin host. This has an even
greater impact on plugins like _SWAM Cello_ that request this information
repeatedly over the course of a single audio processing cycle. Previously
yabridge had a `cache_time_info` compatibility option to mitigate the
performance hit for those plugins, but this new caching behaviour supercedes
that.
- We now always force the CPU's flush-to-zero flag to be set when processing
audio. Most plugins will already do this themselves, but plugins like _Kush
Audio REDDI_ and _Expressive E Noisy_ that don't will otherwise suffer from