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

Reword changelog, again

Browse Source
This commit is contained in:
Robbert van der Helm
2021-07-14 19:37:16 +02:00
parent 0c816b0046
commit 0250d62173
1 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+15 -15
View File
@@ -14,7 +14,7 @@ Versioning](https://semver.org/spec/v2.0.0.html).
this gets released this gets released
- Added support for drag-and-drop from Windows plugins running under yabridge to - Added support for drag-and-drop from Windows plugins running under yabridge to
native applications such as your DAW. This makes it much more convenient to native applications, such as your DAW. This makes it much more convenient to
use plugins like _Scaler 2_ that generate audio or MIDI files. Because of the use plugins like _Scaler 2_ that generate audio or MIDI files. Because of the
way this is implemented this feature will work with any Wine version. way this is implemented this feature will work with any Wine version.
- When a plugin fails to load or when the Wine plugin host process fails to - When a plugin fails to load or when the Wine plugin host process fails to
@@ -37,9 +37,9 @@ Versioning](https://semver.org/spec/v2.0.0.html).
allows the above mentioned 32-bit version of yabridge to be used in allows the above mentioned 32-bit version of yabridge to be used in
**EnergyXT**, allowing you to use both 32-bit and 64-bit Windows VST2 plugins **EnergyXT**, allowing you to use both 32-bit and 64-bit Windows VST2 plugins
there. there.
- Added an environment variable to disable the watchdog timer. This is needed - Added an environment variable to disable the watchdog timer. This is only
when running the Wine process under a separate namespace. If you don't know needed when running the Wine process under a separate namespace. If you don't
that you need this, then you probably don't need this! know that you need this, then you probably don't need this!
### Changed ### Changed
@@ -77,12 +77,12 @@ Versioning](https://semver.org/spec/v2.0.0.html).
the Smart Ops panel after having used it once. To fix this, yabridge's the Smart Ops panel after having used it once. To fix this, yabridge's
Wine-side VST3 mutual recursion mechanism now only operates when invoked from Wine-side VST3 mutual recursion mechanism now only operates when invoked from
the GUI thread. the GUI thread.
- Fixed missing transport information for VST2 plugins in **Ardour**, breaking - Fixed VST2 plugins in **Ardour** not receiving all transport information,
host sync and LFOs in certain plugins. This was a regression from yabridge breaking host sync and LFOs in certain plugins. This was a regression from
3.2.0. yabridge 3.2.0.
- Fixed _Insert Piz Here_'s _midiLooper_ crashing in **REAPER** when the plugin - Fixed _Insert Piz Here_'s _midiLooper_ crashing in **REAPER** when the plugin
tries to use REAPER's [host function tries to use REAPER's [host function
API](https://www.reaper.fm/sdk/vst/vst_ext.php#vst_host) which currently isn't API](https://www.reaper.fm/sdk/vst/vst_ext.php#vst_host). This currently isn't
supported by yabridge. We now explicitly ignore these requests. supported by yabridge. We now explicitly ignore these requests.
- Fixed yabridge's logging seeking the STDERR stream to position 0 every time it - Fixed yabridge's logging seeking the STDERR stream to position 0 every time it
writes a log message. This would be noticeable when piping the host's STDERR writes a log message. This would be noticeable when piping the host's STDERR
@@ -90,9 +90,9 @@ Versioning](https://semver.org/spec/v2.0.0.html).
- When printing the Wine version during initialization, the Wine process used - When printing the Wine version during initialization, the Wine process used
for this is now run under the same environment that the Wine plugin host for this is now run under the same environment that the Wine plugin host
process will be run under. This means that if you use a custom `WINELOADER` process will be run under. This means that if you use a custom `WINELOADER`
script to use different Wine binaries depending on the prefix, the script to use different Wine versions depending on the prefix,
`wine version:` line in the initialization message will now always match the the `wine version:` line in the initialization message will now always match
version of Wine the plugin is going to be run under. the version of Wine the plugin is going to be run under.
- Fixed the plugin-side watchdog timer that allows a yabridge plugin to - Fixed the plugin-side watchdog timer that allows a yabridge plugin to
terminate when the Wine plugin host application fails to start treating zombie terminate when the Wine plugin host application fails to start treating zombie
processes as still running, active processes. This could cause plugins to hang processes as still running, active processes. This could cause plugins to hang
@@ -118,14 +118,14 @@ Versioning](https://semver.org/spec/v2.0.0.html).
when supported by the file system. This speeds up the file coyping process when supported by the file system. This speeds up the file coyping process
while also reducing the amount of disk space used for yabridge when using while also reducing the amount of disk space used for yabridge when using
Btrfs or XFS. Btrfs or XFS.
- If pruning causes a directory to be empty, then the empty directory will also - If pruning causes a directory to be empty, then the empty directory will now
be removed. This avoids having your plugin directories littered with empty also be removed. This avoids having your plugin directories littered with
directories. empty directories.
- Fixed incorrect new and total plugin counts. These counts are now always - Fixed incorrect new and total plugin counts. These counts are now always
correct, even when using multiple versions of the same VST3 plugin or when correct, even when using multiple versions of the same VST3 plugin or when
multiple plugin directories overlap because of the use of symlinks. multiple plugin directories overlap because of the use of symlinks.
- Aside from pruning only unmanaged VST3 bundles in `~/.vst3/yabridge`, yabridge - Aside from pruning only unmanaged VST3 bundles in `~/.vst3/yabridge`, yabridge
will now also prompt you to prune unmanaged files within a managed VST3 will now also prompt you to prune leftover files from within a managed VST3
bundle. This makes it easy to switch from the 64-bit version of a plugin to bundle. This makes it easy to switch from the 64-bit version of a plugin to
the 32-bit version, or from a 64-bit version of yabridge to the 32-bit the 32-bit version, or from a 64-bit version of yabridge to the 32-bit
version. I don't know why you would want to do either of those things, but now version. I don't know why you would want to do either of those things, but now