Most VST3s have strange behavior after Wine Staging update

[cobe571]

Thanks for giving yabridge a shot!

• I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

Hello everyone,
Today I update my Debian 12 (bookworm) with yabridge 5.1.1 to Kernel Linux 6.1.0-28-rt-amd64 x86_64 and Wine Staging 9.22

Just to be sure everything works fine in the end I follow these steps:

I delete the file:
/home/patrizio/.config/yabridgectl/config.toml

And the two directories:
/home/patrizio/.vst/yabridge/
/home/patrizio/.vst3/yabridge/

As usual I gave the commands:

:~$ /home/patrizio/.local/share/yabridge/yabridgectl add /home/patrizio/.vst/

:~$ /home/patrizio/.local/share/yabridge/yabridgectl add "$HOME/.wine/drive_c/Program Files/Common Files/VST3"

:~$ /home/patrizio/.local/share/yabridge/yabridgectl sync

Everything works fine! But...

All of the programs I use i.e. Carla Audio Plugin Host; Reaper and Ardour DAW recognize the plugins but when I open it in most cases they have a really strange behavior. Most of them don't show their GUI with controls and many others don't works at all.

I downgrade winehq-staging to version 9.21 and now everything works perfectly.

Note to remember. To downgrade Wine Staging version, all the files needed for the downgrade must be listed in the installation command:

:~$ sudo apt install winehq-staging=9.21~bookworm-1 wine-staging=9.21~bookworm-1 wine-staging-amd64=9.21~bookworm-1 wine-staging-i386=9.21~bookworm-1

Until it will be fixed I marked Wine Staging as blocked with:

:~$ sudo apt-mark hold winehq-staging

**

Hope it will be fixed very soon, cause I really like yabridge and I appreciate so very much I can finally use a full set of windows plugins into my Linux computers.

Thanks for the effort and please keep up with the good job!

~Patrizio.

What did you expect to happen?

That everything works as expected

What actually happened?

Loading plugins was a faliure: No GUI and most of the plugins not working at all

Operating system

Debian GNU/Linux 12 (bookworm)

How did you install yabridge?

github

yabridge version

5.1.1

yabridgectl version

5.1.1

Wine version

9.22

Plugin

Almost all of them

Plugin type

both VST2 and VST3

Plugin architecture

64-bit

Host

Carla; Reaper; Ardour 7

Desktop environment or WM

XFCE 4.18

GPU model

AMD PALM

GPU drivers and kernel

Mesa 22.3.6 on Kernel 6.1.0-28-rt-amd64

Debug log

No response

Anything else?

No response

[Abso793]

Hello. I have this problem too. With wine-staging 9.22 i can't interact with the gui of the plugins. I have seen people mention this issue on winehq forum and on reddit too.

[siborg]

I reverted to 9.19 and the issues were resolved so there must be some regression or incompatibility in wine 9.22. It happens every now and then. Very Best Regards, Szymon Kosecki

…

On Mon, 25 Nov 2024 at 19:08, Abso793 ***@***.***> wrote: Hello. I have this problem too. With wine-staging 9.22 i can't interact with the gui of the plugins. I have seen people mention this issue on winehq forum and on reddit too. — Reply to this email directly, view it on GitHub <#382 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ6NUWJ4GMRMKYSKCLOG732CNYRBAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYHAZDCOJXGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[pablo-888]

Same. I thought it was a wine-tkg problem so I switched to vanilla but then I noticed Arch was actually a couple of wine versions behind so that explains it. I couldn't interact with Melodyne.

[sandycorzeta]

This perhaps due Wine in 9.22 going into Wayland by default.
https://www.phoronix.com/news/Wine-9.22-Released

I have the same problem, but instead i can interact with the VST with wrong scaling? (i guess)
i use 1360x768 on my native resolution, but the VST seems going into over more than my native resolution in 9.22. So i have the button pressed wrong location.

9.21 doesn't have this problem.

[sandycorzeta]

Here are some video preview of what happened in my computer.
It looks like the window coordinate initialization is not properly configured when the plugin being launched.
Perhaps almost looks like the same bug from #368 .

My system is Fedora 41 using Wine 9.22 copr build from patrickl

2024-11-26.14-48-38.mp4

[robbert-vdh]

Thanks for letting me know about this! I'll probably need to dive into what actually changed between Wine 9.21 and 9.22 to figure out what's happening here. I'll try to find time for that this weekend. For now you'll have to downgrade to an earlier version of Wine.

This perhaps due Wine in 9.22 going into Wayland by default.

yabridge has been unsetting WAYLAND_DISPLAY since early 2023 in anticipation for that on its own should not be causing any problems

I have the same problem, but instead i can interact with the VST with wrong scaling? (i guess)
i use 1360x768 on my native resolution, but the VST seems going into over more than my native resolution in 9.22. So i have the button pressed wrong location.

Are you using yabridge 5.1.1? Wine 9.17 changed how it handles DPI scaling, which did cause issues like this. Yabridge 5.1.1 should scale fine with all current Wine versions.

[bsedin]

I have same problem on wine 9.22, downgrading wine to 9.21 fixes it.
yabridge compiled from a82bd51 (with DPI scaling fix). I will try to test on latest master branch

[sandycorzeta]

Are you using yabridge 5.1.1? Wine 9.17 changed how it handles DPI scaling, which did cause issues like this. Yabridge 5.1.1 should scale fine with all current Wine versions.

Yes i'm using yabridge 5.1.1 compiled from patrickl COPR when im testing this.

[ArtikusHG]

For me, this also affects older wine versions. This started happening to me when I upgraded to 9.20. Downgrading to 9.17 only partially fixed it - on 9.20 I couldn't use the mouse to interact with the GUI at all, on 9.17 it would work on some plugins, but not others (Melodyne was still broken). The only version that works without issues currently for me is 9.21 (even with Melodyne).

Btw this is on Arch running the official packages for both yabridge and wine (switched to wine-staging to install 9.21 though). Don't think it matters, but just in case, my DAW is Reaper, my DE is GNOME on Wayland and I'm running it all through distrobox on Fedora Silverblue.

[Nekkowe]

I'm experiencing the same problem.
Linux Mint, X11, Reaper, wine-devel 9.22, yabridgectl 5.1.1
The plugin UIs do not react to the mouse in any way whatsoever, every one I've tried appears completely frozen.

Downgrading to 9.21 fixed it for me too.

[robbert-vdh]

I don't know if I still have the time to cook up a yabridge-side workaround for this today (and if that's possible to do in a reasonably sane manner) but for context, this is the Wine commit that introduced this issue's specific regression where GUI interaction just no longer works:

Patch: https://gitlab.winehq.org/wine/wine/-/merge_requests/6569
Specific commit causing the problem (through interaction with an earlier commit): wine-mirror/wine@d8b5a3a

The ConfigureNotify events sent by yabridge are being ignored because of those new checks. These events are what tells Wine where on the screen the window actually is. You'll notice that if you move a plugin window around to align with the very top left corner of your screen, mouse interaction still works as expected with Wine 9.22. The same PR added the following line, which causes that wm_state_serial flag to no longer be cleared, causing the problem:

https://github.com/robbert-vdh/wine/blob/d8b5a3ae129e0971e71fcf6e95387d8d1e35e646/dlls/winex11.drv/window.c#L1442-L1443

[PennRobotics]

Because the problem is already bisected, I imagine a fix is coming in the next release. Nonetheless, Fedora users can use:

sudo dnf install --allow-downgrade winehq-staging-9.21
sudo dnf versionlock add winehq-staging