VST instrument UI not responding on mouse clicks

[habernal]

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

Clean install of wine staging, clean install of yabridge, cleaned up Ardour. After installing a VST 2 plugin/instrument (tried both 32 bit and 64 bit versions), it produces sound, but its UI is not clickable. It worked on some previous versions of Ardour/Wine/yabridge without problems.

I tested it with several VST plugins (one example listed below) with the same result. All of them worked previously.

What did you expect to happen?

Being able to interact with the VST plugin

What actually happened?

Default sound works (so the plugin actually works) but its UI does not respond on mouse clicks.

Operating system

Xubuntu 24.04 (latest)

How did you install yabridge?

from releases

yabridge version

5.1.1

yabridgectl version

5.1.1

Wine version

wine-10.0-rc5 (Staging)

Plugin

Iowa Alto Sax (WIN 64 bit; but the same result on 32 bit) https://plugins4free.com/plugin/2513/

Plugin type

VST2

Plugin architecture

64-bit

Host

Ardour 8.10.0 "Sonora Portraits" (rev 8.10) Intel 64-bit

Desktop environment or WM

Xubuntu default (Xfce I guess)

GPU model

NVIDIA GeForce RTX 4060 Ti (but the same problem also on previous AMD graphics card)

GPU drivers and kernel

No response

Debug log

yabridge.log

Anything else?

No response

[NotGena]

Hey you need to install dxvk for wine that should solve your problem

[QXR9]

Same problem. I fixed it partially, I stick the plugin window to the top left corner of screen and that solves problem for me. But it is still annoying. Waveform13.2

[NotGena]

do winetricks dxvk in your terminal

[NotGena]

And downgrade your wine to 9.0 Newer versions be... not so good well there buggy with you, so wine stable is the best to use.

[QXR9]

do winetricks dxvk in your terminal

Tried both manually installed and with command "winetricks dxvk". Did not work. Downgrading is annoying too, do yabridge working with wine stable? Is not staging required?

[NotGena]

staging isnt required. im using 9.0 currently. Can u show the log when you did winetricks dxvk and downgrading? It's not too bad; it wont delete your wine prefix If u have syntapic package Manager, it also makes it easier

[QXR9]

staging isnt required. im using 9.0 currently. Can u show the log when you did winetricks dxvk and downgrading? It's not too bad; it wont delete your wine prefix If u have syntapic package Manager, it also makes it easier

Thanks, I still did not the downgrade but it seems it is going to work perfectly. There's another issue that explains about it. It is all about wine 9.21 and wine 9.22. 9.21 is the last version that works perfectly. Then I'll just go and use the stable version but in Fedora I don't know how to switch to stable. I'll research.

Also, developer does not have much time to fix it. So it is incompatible with wine newer versions, it seems. I'd want to keep project up to date but neither I have time too.

[NotGena]

i havent used fedora before so i cant suggest how but i did downgrade today because i was doing some testing sudo apt-get remove --auto-remove winehq-stable
this is to remove stable but since you got staging i guess u change stable to staging lol and see how that works then install sudo apt install --install-recommends winehq-stable

[habernal]

do winetricks dxvk in your terminal

Appreciate all your suggestions. However, I'd expect a much more technical discussion here at GitHub (if the devs don't address the issues themselves).

• Why is Direct3D with Vulkan relevant to this issue? I didn't have this installed on previous versions of yabridge/Wine/Ardour and everything worked.

• Why winetricks and not just pure Wine? Does Winetricks solve the problem or it's just a workaround for some other issues?

• Which version of Wine do you use exactly, from which source, on which distribution, how do you downgrade it, etc?

Thanks!

[habernal]

Looks like the same problem in #390 . Will keep this issue open, though.

[habernal]

Also noticed in other issues, might be the same problem: #382 (comment)

[habernal]

I gave it another try and installed Ample Bass P Lite v2.31 (https://www.amplesound.net/en/download.asp) first in Wine with its standalone host:

~/.wine/drive_c/ABPL_2_3_1_Complete_Installer$ ls
'ABPL Library'   ABPL_2_3_1_Complete_Installer.exe   Non-Admin_Fix.exe   vcredist
# install in Wine; click all to default
$ wine "ABPL_2_3_1_Complete_Installer.exe" 
# ....
# it also installs some C++ libraries, just accept everything
# ...
~/.wine/drive_c/Program Files/Ample Sound$ ls
'ABPL Library'   ABPL2x86.dll           'Ample Bass Manual.pdf'   ASHost_x86.exe   unins000.dat
 ABPL2.dll       ActivationManager.exe   ASHost.exe               configs.lnk      unins000.exe
# Run ASHost
$ wine ASHost.exe 

It works well, plays the sound, UI interacts, etc.

Then I synced the VST plugin in yabridge and added to Ardour and found out that the UI is clickable but the clicks are some pixels off, see the screenshot below:

Here the clicks are performed at the position of the mouse cursor, but actually the note C plays as shown.

However, this might be a different issue as with the other plugin mentioned above (Iowa Alto Sax), no such offset works.

[nikdavis]

Same problem. I fixed it partially, I stick the plugin window to the top left corner of screen and that solves problem for me. But it is still annoying. Waveform13.2

Yes same for me. Weird that this works. Works for plugins like MTuner, Scaler2 (using Bitwig). If you move the window to the top left and then remove the window control bar the mouse aligns & clicks perfectly.

This is happening to all the windows vsts I tested.

Installed fresh from Wine staging yesterday (will have to check version).