I wonder what “doesn’t work” actually means. Do the VSTs not work at all? Or are there other problems with current official wine builds? For me, the VSTs do work, but I don’t get a GUI, only empty windows. The generic controls do work. But this happens with every wine version. I’m on Manjaro Linux and aware that there are some library issues there, but I would like to know the kind of issues other users have?
there are not wine-hq-staging 9.* for ubuntu (>=25.04). Only wine 10.
Any way, as i said in the topic this is not the problem…
I can use the plugins with yabridge (and wine10) with carla… the problem is when i tried to load it in ardour.
I would like to debug the scan plugins process to detect what is the problema exactly
@Vudone
Ever since the wine 9.22+ / yabridge issue appeared, I did not want to spend time trying things out, debugging, etc. The issue is still here after a whole year! I reverted straight to wine 9.21 and left it at that. One day it will be resolved but apart from occasional checks in the yabridge repo for new developments around these issues, I won’t bump up my wine version.
The problem with Wine 9.22+ lies in the graphical interface; there are errors in calculating mouse position.
In my case, some plugins work with Wine 10 and Yabridge in Carla, so they are functional. The problem is that Ardour cannot scan them; this is a separate issue.
And in my case… I’m on Ardour 25.04… and I’d like to upgrade to version 25.10… one option is to reinstall and revert to a previous version… but…I’d rather debug this. 
Using Wine Staging 9.1 on Kubuntu 22.04.5 LTS, I can utilize Superior Drummer 3 and the excellent VST2 plugin PG-8X, a Roland JX-8P emulator, on Linux. This combination has worked flawlessly for me for years, allowing me to use my favorite operating system almost all the time.
I only wish I could run Melodyne with the help of Wine as well, but thankfully, it’s so seldom I use it that I can live with using Windows when needed. So 9.21 is the latest known working Wine version? Then I might test it and test Melodyne again.
Melodyne worked for me some months ago with wine 9.21 before my ubuntu update.
It doesn’t work here, I’m afraid. I tested Melodyne 5 studio 5.4.2 with Wine 9.21. Superior Drummer 3 and PG-8X still work, so I keep 9.21.
Thank you for the Konsole approach with Debian Trixie and Wine 9.21… i stay with debian 12 but it’s good to know it.
If you want to debug, you will need:
- Set up your yabridge with debugging (instructions in the README)
- (possibly) debug version of ardour
- (possibly) debug version of wine
- Another thing you can do is edit the yabridge shell script wrappers (yabridge-host.exe) and edit the first line to: #!/bin/sh -x
This might show some other relevant info.
Run it all from a terminal.
Keep in mind because of the way yabridge installs the plugin and wrapper, Ardour will scan twice: once for the wrapper, and a second time with the vst3. The vst3 will always show that it can not be scanned, because it is the raw windows plugin. Check in the text output of the Ardour plugin manager. If it says something like “Cannot scan xxx.vst3”, then that is ok, and can be ignored. You need to look for the scan that says “Scanning xxx.so”.
1 Like
I launched YaBridge with debug mode last weekend. It generated the debug file, but it didn’t even load a single line… it’s like it never even launched. So what I wanted to do was replicate what Ardour does when it scans plugins…
I tried using the ardour-vst3-scan binary, and it did scan them. The plugins appeared in Ardour, but Ardour crashed when I tried to activate them.
I dont know if internally ardour launchs ardour-vst3-scan .
Yes, to scan for plugins in the background.
What do you mean wit activate?
Load the plugin to a strip? Show the plugin GUI? Activate an online license of the plugin?
Does disabling Preferences > Plugins > GUI > Automatically open the plugin GUI when adding a new plugin allow to instantiate it?
In any case… please see Debugging Ardour | Ardour DAW
I believe that plugins that depend in iLok do not run under wine at all.
Each to their own choices…
It seems to me time and time again that you can have a great workstation on an LTS Platform OR you can have the very latest DE, or Compositor, or Audio Server and have to make choices that affect production. It doesn’t happen all the time but it happens often enough… We have people here running Arch, Ubuntu 25 and various Distros with Wayland and there are ‘some’ issues with the allowance that some people have no issues on bleeding edge systems…
I don’t think at this point in time you could really go ‘wrong’ on a Ubuntu LTS, or Debian Stable using X11. I don’t know Fedora or openSUSE well enough to say what a similar paradigm on that would be, but I’m sure they have LTS-like products as well.
Do you want to make music or do a bug hunt? Seems an easy choice to me…
2 Likes
Fedora does not, latest and latest-1 release get updates, anything older than that gets no more updates (none, including security), and updates to later releases are not guaranteed to work if you attempt more than release + 2 (so if you decided you didn’t care about security updates and stuck to a release for longer than it was supported, you might have to do step upgrades when you did finally want to upgrade to a later release, rather than jumping to the latest).
If you want stable LTS in a Red Hat adjacent release then you want one of the Red Hat Enterprise clones like Rocky or Alma.
1 Like
Yep, I believe my install of Fedora 41 goes EOL after today, so time to upgrade to F42 soon.
In case anyone else is experiencing the same issue…
After running the DBG and debugging the internal startup processes, I discovered that the problem occurred when accessing libwine.
When Ardour tried to search for VST plugins or add a plugin to the track, Yabridge couldn’t find libwine and Ardour was left waiting…
I spent some time troubleshooting and ended up uninstalling all the WineHQ packages and reinstalling libwine from Ubuntu. Now I have all the packages in version 9.0~repack-4build3 of Ubuntu 25.04.
I no longer experience the crashes or waiting times I had before. However, the Windows VSTs have stopped working… but the problem I was having is solved.
Tomorrow I will update WineHQ again and check if libwine is corrupted when installing WineHQ. I’ll see if that allows me to load the Windows VSTs again.
FYI iLok is an option with Melodyne, not a necessity. There was a period of time around Melo 4 when Melodyne would fail to activate.
Also, software iLok should work. I registered a number of plugins that way around 2015/2016. They still work fine. Maybe I’m lucky?
When you have a spare afternoon, try Melo 5 with LinVst, and put it in it’s own wine prefix. So long as you didn’t transfer the authorization to HW iLok key, it should work well. This year I’ve been running wine 9.21-TKG with no Melodyne problems. Quickly checked on the weekend with 10.18, loaded fine, but didn’t test it in a mix. This on Kubuntu 24/X11.
Ubuntu 25.04
Official wine ubuntu version: 9.0~repack-4build3
Yabridge 5.1.1.
I removed all winehq packages and files (except ~/.wine wineprefix).
I installed the Ubuntu version of Wine.
I configured winecfg with the desktop option enabled for graphics (this fixes mouse position errors).
I reinstalled the Visual Studio C++ libraries in Wine.
I removed the ~/.vst3/yabridge directories and rescanned with yabridgectl sync.
At this point, using GDB, I saw this message:
__GI___getrlimit64 (resource=resource@entry=RLIMIT_NOFILE, …)
It seems like ardour with yabridge opens more files than default conf allow.
Then, I ran Ardour, changing the value of ulimit:
ulimit -n 8192 && Ardour
And it works. These screenshots show the Melodyne and LALA plugins working in Ardour.
I need to do more testing, but it seems the plugins work on Ubuntu 25.04.
2 Likes
In my case, most of the plugins activated by iLok were working like a charm… until I upgraded to Ubuntu 25.10.
Now they run into the problem described above: the scanning process runs indefinitely.
I’ve tried to upgrade the iLok app, but couldn’t because of problems with some dependencies (PACE, I think).
It’s a shame. I love Nembrini’s Voice DC30 amp sim. Will be dearly missed.