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

Update the changelog for VST3 support

Browse Source
This commit is contained in:
Robbert van der Helm
2020-12-26 13:44:23 +01:00
parent 38f34f91f2
commit d32e566446
2 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+12 -4
View File
@@ -13,8 +13,16 @@ version from the readme
### Added ### Added
TODO: Add the relevant entries here for yabridge's VST3 support - Yabridge 3.0 introduces the first ever Wine VST3 bridge, allowing you to use
Windows VST3 plugins in Linux VST3 hosts with full VST 3.7.1 compatibility.
Simply tell yabridgectl to look for plugins in
`$HOME/.wine/drive_c/Program Files/Common Files/VST3`, run `yabridgectl sync`,
and your VST3 compatible DAW will pick up the new plugins in
`~/.vst3/yabridge` automatically. Even though this feature has been tested
extensively with a variety of VST3 plugins and hosts, there's still a large
part of the VST 3.7.1 specification that none of the hosts or plugins we can
across actually used, so please let me know if you run into any weird
behaviour!
- Added the `with-vst3` compile time option to control whether yabridge should - Added the `with-vst3` compile time option to control whether yabridge should
be built with VST3 support. This is enabled by default. be built with VST3 support. This is enabled by default.
- Added an - Added an
@@ -26,8 +34,8 @@ TODO: Add the relevant entries here for yabridge's VST3 support
### Changed ### Changed
- `libyabridge.so` is now called `libyabridge-vst2.so`. If you're using - `libyabridge.so` is now called `libyabridge-vst2.so`. If you're using
yabridgectl then nothing changes here. To avoid any confusion in the future yabridgectl then nothing changes here. **To avoid any confusion in the future,
it's adviced to remove the old `libyabridge.so` file when upgrading. please remove the old `libyabridge.so` file before upgrading.**
- VST2 editor idle events are now handled slightly differently. This should - VST2 editor idle events are now handled slightly differently. This should
result in even more responsive GUIs and I have not come across any plugins result in even more responsive GUIs and I have not come across any plugins
where this caused issues, but please let me know if it does break anything for where this caused issues, but please let me know if it does break anything for
README.md
-5
View File
@@ -23,11 +23,6 @@ incomplete list of things that still have to be done before this can be used:
- All interfaces introduced after that - All interfaces introduced after that
- Fully implemented: see [this - Fully implemented: see [this
document](https://github.com/robbert-vdh/yabridge/tree/feature/vst3/src/common/serialization/vst3/README.md) document](https://github.com/robbert-vdh/yabridge/tree/feature/vst3/src/common/serialization/vst3/README.md)
- Mention that this update will break all existing symlinks and that the old
`libyabridge.so` file should be removed when upgrading.
- Pay close attention when updating the plugin groups section of the readme,
since VST3 plugins by design cannot be hosted completely individually (as in,
each plugin is basically in its own group).
- Update all the AUR packages for the `libyabridge-vst{2,3}.so` changes. - Update all the AUR packages for the `libyabridge-vst{2,3}.so` changes.
- Test the binaries built on GitHub on plain Ubuntu 18.04, are we missing any - Test the binaries built on GitHub on plain Ubuntu 18.04, are we missing any
static linking? static linking?