Remove mentions of broken Wine 7.21, 7.22, 8.0-rc1

With yabridge 5.0.3's release.
This commit is contained in:
Robbert van der Helm
2022-12-23 21:13:37 +01:00
parent ab7012c8c9
commit 6a7e07e222
2 changed files with 14 additions and 20 deletions
+9
View File
@@ -8,6 +8,15 @@ Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased] ## [Unreleased]
# Changed
- The yabridge 5.0.3 binaries up on the GitHub releases page (and in the
[`yabridge-bin`](https://aur.archlinux.org/packages/yabridge-bin) AUR package)
now work again with every Wine version after Wine 5.7, including 7.21, 7.22,
and the 8.0 release candidates. All workarounds for Wine 7.21 and 7.22 have
been reverted. See Wine bug
[#53912](https://bugs.winehq.org/show_bug.cgi?id=53912) for more information.
### Packaging notes ### Packaging notes
- The VST3 dependency has been updated to target version 3.7.7 with tag - The VST3 dependency has been updated to target version 3.7.7 with tag
+5 -20
View File
@@ -39,15 +39,7 @@ while also staying easy to debug and maintain.
## Tested with ## Tested with
Yabridge has been tested under the following hosts using Wine Staging **7.20**. Yabridge has been tested under the following hosts using Wine Staging 8.0-rc2.
Wine 7.21 and 7.22 contain a major regression
[#53912](https://bugs.winehq.org/show_bug.cgi?id=53912) that breaks yabridge.
The current yabridge 5.0.2 build up on GitHub contains several workarounds to
still be able to use the latest version of Wine with yabridge. But if you're
getting crashes or freezes, do consider [downgrading](#downgrading-wine) back to
Wine Staging 7.20.
Wine **8.0-rc1** completely breaks yabridge, and it should be avoided.
| Host | VST2 | VST3 | CLAP | | Host | VST2 | VST3 | CLAP |
| --------------------- | ------------------ | -------------------------------------------------------------------- | ---------------------------------------------------- | | --------------------- | ------------------ | -------------------------------------------------------------------- | ---------------------------------------------------- |
@@ -79,11 +71,6 @@ Please let me know if there are any issues with other hosts.
check out Wine's [user check out Wine's [user
guide](https://wiki.winehq.org/Wine_User%27s_Guide#Using_Wine). guide](https://wiki.winehq.org/Wine_User%27s_Guide#Using_Wine).
**As mentioned above, Wine (Staging) 7.21 and 7.22 may not work correctly
with yabridge, and Wine 8.0-rc1 will not work with yabridge at all.** See
below for [downgrading instructions](#downgrading-wine) if yabridge
immediately crashes or freezes for you.
1. Depending on your distro you can install yabridge and its yabridgectl 1. Depending on your distro you can install yabridge and its yabridgectl
companion utility through your distro's package manager or by using companion utility through your distro's package manager or by using
a binary archive from the GitHub releases page. Keep in mind that the distro a binary archive from the GitHub releases page. Keep in mind that the distro
@@ -599,12 +586,10 @@ the yabridge [Discord](https://discord.gg/pyNeweqadf). Also check the [known
issues and fixes](#known-issues-and-fixes) section above for help with issues and fixes](#known-issues-and-fixes) section above for help with
plugin-specific issues. plugin-specific issues.
- Yabridge may not work correctly with Wine 7.21 and 7.22 depending on how - Old versions of yabridge may not work correctly with Wine 7.21, 7.22, and
yabridge was built because of Wine bug 8.0-rc1 because of Wine bug
[#53912](https://bugs.winehq.org/show_bug.cgi?id=53912). If you experience [#53912](https://bugs.winehq.org/show_bug.cgi?id=53912). Either update to
crashes or freezes, you may want to stick with Wine Staging 7.20. See above yabridge 5.0.3, or [downgrade to Wine Staging 7.20](#downgrading-wine).
for [downgrading instructions](#downgrading-wine). Wine 8.0-rc1 will not work
with yabridge at all.
- Both yabridgectl and yabridge try to diagnose many common issues for you. If - Both yabridgectl and yabridge try to diagnose many common issues for you. If
you're running into crashes or other issues, then try launching your DAW from you're running into crashes or other issues, then try launching your DAW from