Most VST3s have strange behavior after Wine Staging update #382
Comments
|
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. |
|
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: ***@***.***>
|
|
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. |
|
This perhaps due Wine in 9.22 going into Wayland by default. I have the same problem, but instead i can interact with the VST with wrong scaling? (i guess) 9.21 doesn't have this problem. |
|
Here are some video preview of what happened in my computer. My system is Fedora 41 using Wine 9.22 copr build from patrickl 2024-11-26.14-48-38.mp4 |
|
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.
yabridge has been unsetting
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. |
|
I have same problem on wine 9.22, downgrading wine to 9.21 fixes it. |
Yes i'm using yabridge 5.1.1 compiled from patrickl COPR when im testing this. |
|
For me, this also affects older wine versions. This started happening to me when I upgraded to Btw this is on Arch running the official packages for both yabridge and wine (switched to wine-staging to install |
|
I'm experiencing the same problem. Downgrading to 9.21 fixed it for me too. |
|
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 The |
|
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 |
Or alternatively just use the official Fedora 41 repo and install wine 9.15 which is apparently based off wine-staging. |
|
Side question about the Wayland: Is there Wayland support planned for Yabridge? I wonder if this could make the proper plugin GUI available in Presonus Studio One.... Thanks! |
|
same here Bitwig 5.2.7 linux mint .debian |
|
Still issues after Wine 10. For lazy people on Debian Bookworm: sudo apt install --allow-downgrades 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 && sudo apt-mark hold winehq-staging wine-staging wine-staging-amd64 wine-staging-i386To reiterate, 9.21 is the last working version. |
|
i think this is possibly related to a much older bug report made about neuralnote running through yabridge, not certain however https://bugs.winehq.org/show_bug.cgi?id=56774 |
|
Confirmed same issue and downgrade to 9.21 and a reboot fixed it for me. |
|
@robbert-vdh any ideas how much effort it would be to work around this from the yabridge side? I'd prefer not to downgrade wine, and while moving all plugin windows to 0,0 works for now it's not exactly convenient 😄 |
|
@cnschn That probably won't possible do to in a way that keeps the old behavior, and that won't break immediately again after the next Wine release. I briefly checked if I could get something to work by moving the window's position around and then compensating with negative translations but that didn't really work and is super janky. I don't think the Wine people are going to change something on their side that would make this work again anytime soon though. Maybe they'll accept a patch from me that would make this work properly without any hacks, but I currently also don't really have the time to work on that. |
|
That's unfortunate, but understandable. I really don't want to downgrade/pin wine to an older version, does anyone have any recommendations on how to manage prefixes using non-system versions of wine (on arch in my case)? I'm using Lutris for some games/applications already, maybe setting up a fixed version prefix for VSTs using that could be an option? |
|
Experiencing same issue on arch with 9.22 - does anyone know if there is an open issue in wine to address this? |
|
It is a known issue with 9.22 please downgrade to 9.21 - afaik no fix in
wine for this. @robbert-vdh/yabridge ***@***.***> was
trying to get a workaround in place but if I remember correctly this is WiP
at best - due to lack of time...
Very Best Regards,
Szymon Kosecki
…On Sun, 22 Dec 2024 at 13:07, Craig Dunford ***@***.***> wrote:
Experiencing same issue on arch with 9.22 - does anyone know if there is
an open issue in wine to address this?
—
Reply to this email directly, view it on GitHub
<#382 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ6NUQZCOEHAQMQSY5QYZT2G22QZAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ2TANZTHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Yeah I'll see about downgrading - that's always a bit of a headache on arch. Would be stellar if someone was able to fix this at some point. |
|
you can probably go to /var/cache/pacman/pkg folder and install older
package from there if it has not been emptied by yourself already.
Very Best Regards,
Szymon Kosecki
…On Sun, 22 Dec 2024 at 15:08, Craig Dunford ***@***.***> wrote:
Yeah I'll see about downgrading - that's always a bit of a headache on
arch. Would be stellar if someone was able to fix this at some point.
—
Reply to this email directly, view it on GitHub
<#382 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ6NUQ4NBS43MVFXM74YO32G3IWXAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ4DMNRWGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Ah, and do not forget to mask wine in /etc/pacman.conf with Ignore-pkg =
wine . you can google doing it for just a specific version if you want.
Very Best Regards,
Szymon Kosecki
…On Sun, 22 Dec 2024 at 15:38, Szymon Kosecki ***@***.***> wrote:
you can probably go to /var/cache/pacman/pkg folder and install older
package from there if it has not been emptied by yourself already.
Very Best Regards,
Szymon Kosecki
On Sun, 22 Dec 2024 at 15:08, Craig Dunford ***@***.***>
wrote:
> Yeah I'll see about downgrading - that's always a bit of a headache on
> arch. Would be stellar if someone was able to fix this at some point.
>
> —
> Reply to this email directly, view it on GitHub
> <#382 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAQ6NUQ4NBS43MVFXM74YO32G3IWXAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ4DMNRWGQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
I think this problem with 9.22 is wider than just yabridge. Carla fails too plus the plugins in Photoshop CS2 (which was the last Adobe product I ever bought...think on Adobe! ) All fail to respond to mouse, or at least not know the coordinates of the pointer. |
|
@Lord-Formaldahyde-Brick maybe let them know about this. The more software is affected by this change, the more likely it is for them to reconsider. Merge request is here: https://gitlab.winehq.org/wine/wine/-/merge_requests/6569 |
|
I filed a bug report on: https://bugs.winehq.org/show_bug.cgi?id=57603 |
|
Short confirmation for Manjaro Linux, KDE flavor: Currently no RT kernel in use; I think the issue independent of the kernel version. Tested with some (free) 64-bit VSTi2, VSTi3 & CLAPi plugins on Rapper + Carla.
Like for most of the others here, I was able to temporarily solve that issue by downgrading Wine-Staging from version 9.22 to 9.21. BTW:
|
|
Thanks everyone for the feedback, Thanks to @robbert-vdh I'm not worried. Still with downgraded winehq-staging at version 9.21 and everything continue to works perfectly. I'm aware we already have winehq-staging 10.0~rc3 but I'm not rushing the latest updates over functionality. |
|
Ive downgraded to wine 9.21 (tkg build). VSTs are rendering (not frozen either) (9.22+ gave me a black screen), but mouse and keyboard interactions does not work. dxvk is installed. |
|
Hey folks, I just wanted to suggest a way to work around this which might help some of you. I am on OpenSUSE and downgrading Wine is not trivial, and not worth the effort for me personally. Instead, I noticed that Wine seems to be registering the mouse clicks using my absolute screen coordinates, as if the left-most top-most pixel of the VST display were exactly at pixel position 0,0 on the screen. I noticed this because the mouseclicks in EZdrummer were always registering down and to the right of where I intended them. In other words, the further your VST window happens to be positioned away from the top-left corner of the screen, the further your mouse clicks will be from where you intended. So to work around it, I am having success simply by right clicking the title bar of my VST and clicking move, and then position the VST window so that it is where Wine apparently thinks it is, with the top-left most corner of the VST display aligned with the top-left most corner of the monitor. You will have to push the title bar off the screen if you want your clicks to be exact, which is why I rightclick the title bar and move that way instead of dragging the title bar as you would usually do. This works in Reaper with KDE... methods may be different in other desktop environments and DAWs. |
|
I have same mouse shifting problem on Endeavour OS, I fixed it by downgrading from 9.22 to 9.21: wget https://archive.archlinux.org/packages/w/wine-staging/wine-staging-9.21-1-x86_64.pkg.tar.zst
sudo pacman -U wine-staging-9.21-1-x86_64.pkg.tar.zst |
By default in KDE Plasma, you can also hold down the left Windows key and drag a window by clicking anywhere within the window. It might be Left Alt instead if you have upgraded from an older Plasma version. |
I take it I would need to install Wine-9-21 from archive too as it needs to remove it when pacman downgrades staging? |
and others
Thanks for giving yabridge a shot!
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 syncEverything 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-1Until 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
The text was updated successfully, but these errors were encountered: