WINE 10.3 LinVST Still Working

[Glennbo]

I just let Manjaro XFCE update WINE 10.0-1 to WINE 10.2 (now 10.3-1) and all is still well with my Windows plugins. Dunno what changed in WINE, but all my Windows plugins are still happy.

[mjolnir]

yeah, but what about VST3?
if I remember correctly, I thought you were mostly running a firmly weeded out collection of VSTs on LinVST and no VST3's or CLAPs?

And what about all of these? are any of these "closed"/SOLVED?:
https://bugs.winehq.org/buglist.cgi?quicksearch=VST

[Glennbo]

Originally Posted by mjolnir

yeah, but what about VST3?
if I remember correctly, I thought you were mostly running a firmly weeded out collection of VSTs on LinVST and no VST3's or CLAPs?

Yeah, I'm running the exact set of Windows plugins I was running when I had Windows 7 on my DAW machine, and in Windows 7, I only had the VST2 versions of those plugins installed, because in 2018, VST3 was real buggy. When I switched to Linux, and first setup my Windows plugins in WINE, I installed only the VST2 versions just like I had done in Windows 7.

That said, if I'm missing something by not having the VST3 version of those plugins, I don't know what it might be. They all function as virtual midi instruments, which is what I expect from them, and even though I have some Windows audio plugins, I don't use any of them, and only use the virtual instruments like Kontakt, B4 Organ, Superior Drummer, Arturia MiniMoog V, and a few others.

And what about all of these? are any of these "closed"/SOLVED?:
https://bugs.winehq.org/buglist.cgi?quicksearch=VST

I have no idea what might be going on with any of those. I just wasn't afraid to allow WINE 10.2 install last night, and right after checked to see, and all the Windows instrument plugins I use are still working, so I posted notice of it.

[mjolnir]

cool. thanks for the clarification.
i apologize for sounding rude.
i'm so anxious about the WINE bugs being fixed by the WINE devs, hopefully.
i come accross rude sometimes. sorry for that.
i'm glad your stuff is working out.

[Glennbo]

Originally Posted by mjolnir

cool. thanks for the clarification.
i apologize for sounding rude.
i'm so anxious about the WINE bugs being fixed by the WINE devs, hopefully.
i come accross rude sometimes. sorry for that.
i'm glad your stuff is working out.

No worries. I know about being anxious with WINE. Last night was the first time in a month or more that I wasn't on edge letting a Manjaro update install a new version of WINE.

[mjolnir]

I think that there's more than one WINE bug historically speaking, and a bunch of them are from the alpha introduction of Wayland. As far as I know, they haven't been solved yet.

But like any bugs, they vary from user to user.
Just because something is broken for one user doesn't mean it's broken for other users. And likewise, sometimes a fix for one user doesn't affect a different set of users who still have software not working right (different bugs per user(s)).

[Glennbo]

Originally Posted by mjolnir

I think that there's more than one WINE bug historically speaking, and a bunch of them are from the alpha introduction of Wayland. As far as I know, they haven't been solved yet.

But like any bugs, they vary from user to user.
Just because something is broken for one user doesn't mean it's broken for other users. And likewise, sometimes a fix for one user doesn't affect a different set of users who still have software not working right (different bugs per user(s)).

Wayland support is the root of most problems with WINE currently.

[mjolnir]

Originally Posted by Glennbo

Wayland support is the root of most problems with WINE currently.

Yeah, I know; that's what I've been saying on a variety of posts. I don't know it like a programmer would know it, but even the Yabridge developer seemed to weigh in on the topic and it seemed like that. I read his github page and I try to peek at the bugzilla on WineHQ

But I keep forgetting that you're using LinVST and not Yabridge. And of course they are different from each other.

Somebody did mention somewhere on the web, though, that some of the WINE bugs with VST's and/or CLAP's might not be there if you run REAPER for Windows (on WINE) and just load up the Windows plugins from within that.

I used to do that all the time, before the Linux REAPER project was fully up and running. It took more Linux optimization tweaks to get it to work stable, but I was able to do it.

I was even planning on sharing some of the successful tweaks I'd learned from others, such as how to configure PulseAudio for pro audio (yes, it's possible) with the "tsched=0" trick and other things. But then PulseAudio became negligeable when PipeWire became mainstream, so I never followed through.

And then, of course, I keep jumping from DAW to DAW (almost like distro hopping) so I'm not as focussed on REAPER as other REAPER users. Other REAPER users, for example know a lot about scripting and I sure don't.

But I have a stable Manjaro XFCE/MATE Linux and I'm happy abou that.
And for that matter, my REAPER is stable too. As long as I get some music done, I'm happy.

Lately, I'm not sure which plugins are buggy or not because I got rid of all of them on my system which were incompatible with WINE's bugs. ...All of them, except for MaxSynths Bass Module. That one seems stable lately and my system is pinned (held) at WINE-Staging v9.22

I'm not going to unpin WINE-Staging until the WINE devs claim to have fixed the VST GUI bugs on the WINE HQ website. Or, until a bunch of the audio guys at this site and LinuxMusicians claim that the bugs are totally fixed.

Overall, the progress is slow, but I don't think that there are very many developers anyhow. Aren't they understaffed, right? And it's not like they're getting paid. So we're lucky to have anything that works.

[Glennbo]

I just went down a long and unpleasant trip after updating my DAW machine with a big Manjaro update. I think the mirrors around the world were out of sync for a while or something, because I saw it on two machines, but two others were fine updating a day later.

My DAW got into a catch 22 loop where trying to install or uninstall anything would throw out three errors about removing blah blah blah library can't be done because blah blah blah is dependent on it. After many attempts down different paths, and starting again after a TimeShift restore, the fix was to switch mirrors to Global, refresh the mirrors list, and then run the update from a terminal.

Now I can add or remove again using the GUI method, and just added SpeedCrunch using the GUI interface. It was sort of funny too, because after all that, I got a notification that WINE 10.2 was available to install as an update, because TimeShift had rolled me back to WINE 10.0-1 evidently.

[mjolnir]

@GlennBo: that does sound like true DLL Hell, as they say.

somebody somewhere taught me "sudo pacman -Rndd" (<junk-to-remove>),
so I use that quite alot to get rid of installs without them complaining about forced removals of other things. maybe that will come in handy for you?

[Glennbo]

Originally Posted by mjolnir

@GlennBo: that does sound like true DLL Hell, as they say.

somebody somewhere taught me "sudo pacman -Rndd" (<junk-to-remove>),
so I use that quite alot to get rid of installs without them complaining about forced removals of other things. maybe that will come in handy for you?

Thanks! All is well right now, but that command might come in handy sometime in the future.

[fabio77]

Originally Posted by Glennbo

I just let Manjaro XFCE update WINE 10.0-1 to WINE 10.2 and all is still well with my Windows plugins. Dunno what changed in WINE, but all my Windows plugins are still happy.

Did you get the update to wine 10.3 yet?

I got it today. And it did mess up again. The plugin interface doesn't show up entirely. I think you reported such behaviour before. And I know this too. But until now resizing the window helped me with this. Not anymore

[Glennbo]

Originally Posted by fabio77

Did you get the update to wine 10.3 yet?

I got it today. And it did mess up again. The plugin interface doesn't show up entirely. I think you reported such behaviour before. And I know this too. But until now resizing the window helped me with this. Not anymore

I just checked and I'm running WINE 10.2-2 and so far the Manjaro repository isn't yet showing 10.3 for stable or staging. I stopped using staging about a month ago, and so far see no reason to switch back to it.

I never had any graphical issues with any version of WINE, but before OSXmidi made the fixes for 9.22 - 10.0, I was getting errors and none of my plugins worked at all. I was also getting errors on a stock ticker I wrote in a Windows programming language, and on a Windows programming editor I still use. The stock ticker and editor would load after popping up several error messages, but none of my Windows plugins in REAPER would.

With the LinVST fixes OSXmidi made, all my Windows plugins work in 9.22, 10.0, 10.0-1, 10.2, and 10.2-2. Manjaro doesn't yet have 10.3 in the repository, but maybe it will show up soon and I can find out how LinVST deals with it.

I see that OSXmidi has a new 4.9 release of LinVST here,

https://github.com/osxmidi/LinVst/releases/tag/4.9

that says "yesterday". I compared the file size of one of the server files, and it was different from the original v4.9 fix that was posted a while back. I'm just holding it for now, until I see what happens with WINE 10.3 when I get it.

[fabio77]

Originally Posted by Glennbo

I stopped using staging about a month ago, and so far see no reason to switch back to it.

I did switch to normal wine also, around the time 9.22 was released on us

Originally Posted by Glennbo

I see that OSXmidi has a new 4.9 release of LinVST here,

https://github.com/osxmidi/LinVst/releases/tag/4.9

that says "yesterday". I compared the file size of one of the server files, and it was different from the original v4.9 fix that was posted a while back.

Oh, interesting. I will try that too.

Originally Posted by Glennbo

With the LinVST fixes OSXmidi made, all my Windows plugins work in 9.22, 10.0, 10.0-1, 10.2, and 10.2-2. Manjaro doesn't yet have 10.3 in the repository, but maybe it will show up soon and I can find out how LinVST deals with it.

Yes, that worked for me too, until wine-10.3. I just downgraded wine to 9.21 again. And for now I'm using the vst2 versions of my plugins with LinVST.

[Glennbo]

Originally Posted by fabio77

Yes, that worked for me too, until wine-10.3. I just downgraded wine to 9.21 again. And for now I'm using the vst2 versions of my plugins with LinVST.

So were you having graphic problems with WINE 10.3 and LinVST?

If so, is your desktop running Wayland or X11? Mine is X11, since it's XFCE.

[fabio77]

Originally Posted by Glennbo

So were you having graphic problems with WINE 10.3 and LinVST?

If so, is your desktop running Wayland or X11? Mine is X11, since it's XFCE.

Yes, wine-10.3 and LinVST, but on wayland. I could try x11 also, but tomorrow on my laptop. There I have still wine-10.3 running.

[Glennbo]

Originally Posted by fabio77

Yes, wine-10.3 and LinVST, but on wayland. I could try x11 also, but tomorrow on my laptop. There I have still wine-10.3 running.

It might make a difference. If you get a chance to try it, I'd be interested to know what you find out.

[mjolnir]

from what I read on the internet, XFCE doesn't (yet) support wayland.

On my XFCE/MATE Manjaro system, I tried to install all of the wayland files in advance and when I log in there's an option for XFCE with Wayland instead of XFCE (or MATE). However, if I select that option, nothing happens. I have to choose either XFCE or MATE.

again, from what I've read XFCE doesn't (yet) support wayland, even though other things do.

so it's a waiting game.
(during which i might switch back to MS Windows for compatibility reasons)

[fabio77]

Originally Posted by Glennbo

It might make a difference. If you get a chance to try it, I'd be interested to know what you find out.

It is the same on x11 here (kde plasma).

[Glennbo]

Originally Posted by fabio77

It is the same on x11 here (kde plasma).

Hmmm. Did you get WINE 10.3 as an update from your distro, or are you getting it from WineHQ? Manjaro still doesn't have it in their repository.

[fabio77]

Originally Posted by Glennbo

Hmmm. Did you get WINE 10.3 as an update from your distro, or are you getting it from WineHQ? Manjaro still doesn't have it in their repository.

From my distro. I'm actually running EndeavourOS (switched to it from Fedora this month). Yeah, Manjaro has a little delay.

[osxmidi]

Originally Posted by fabio77

Yes, wine-10.3 and LinVST, but on wayland. I could try x11 also, but tomorrow on my laptop. There I have still wine-10.3 running.

I'm getting the same thing with wine 10.3.

They (wine) have done something somewhere (again).

[fabio77]

Originally Posted by osxmidi

I'm getting the same thing with wine 10.3.

They (wine) have done something somewhere (again).

Yes, it seems they did. I hoped they did their change and move to wayland and this was it, but somehow they're not done yet.

Luckily it's easy to downgrade wine

As I mentioned above I downgraded right to 9.21, but now I think about it 10.2 would work also. I just did that, so that I could work on older projects, where all my plugins are vst3 versions. I should migrate some custom presets to vst2, that will be my go for in future projects.

[Glennbo]

Originally Posted by osxmidi

I'm getting the same thing with wine 10.3.

They (wine) have done something somewhere (again).

When Manjaro tells me it's available as an update, I'll give it try, and if it does what you are seeing, I'll downgrade to 10.2-2, which is working great currently.

Originally Posted by fabio77

Yes, it seems they did. I hoped they did their change and move to wayland and this was it, but somehow they're not done yet.

Luckily it's easy to downgrade wine

As I mentioned above I downgraded right to 9.21, but now I think about it 10.2 would work also. I just did that, so that I could work on older projects, where all my plugins are vst3 versions. I should migrate some custom presets to vst2, that will be my go for in future projects.

I have to wonder if the WINE developers are testing anything but games running on Wayland before they release these new versions. My kid, who is a big time gamer says a lot of this push is coming from Steam.

[fabio77]

Originally Posted by Glennbo

I have to wonder if the WINE developers are testing anything but games running on Wayland before they release these new versions. My kid, who is a big time gamer says a lot of this push is coming from Steam.

I think so too.

Altough, I'm not a programmer, but I doesn't understand this kind of regression. Or I think there could be at least a little bit more transparency or explanation what they are doing, so that such regressions could be worked around without guessing. Maybe there is transparency somewhere, but from googleing there don't seems much of a discussion about it.
But I also don't know how big their team actually is. Maybe they don't even have the time to read all the bug reports I'm happy that it exists, and more so, that I can decide myself wich version I want to use.

[Glennbo]

Originally Posted by fabio77

I think so too.

Altough, I'm not a programmer, but I doesn't understand this kind of regression. Or I think there could be at least a little bit more transparency or explanation what they are doing, so that such regressions could be worked around without guessing. Maybe there is transparency somewhere, but from googleing there don't seems much of a discussion about it.
But I also don't know how big their team actually is. Maybe they don't even have the time to read all the bug reports I'm happy that it exists, and more so, that I can decide myself wich version I want to use.

Still no WINE 10.3 in the Manjaro repository. Normal WINE like I'm running is still at 10.2-2 and wine-staging is at 10.2-1, so maybe I'll get WINE 10.3-2 or something with a fix when it drops.

I wonder how easy it would be to create an auto-bot mailer to send the WINE-Os twenty or so messages per day, with randomly generated "From" addresses, and randomly generated Linux DAW and plugins reports.

Something like this.

Hey WINE-Os, it's <random email address> again, I was just emailing you guys to remind you that <random Windows Plugin> is exhibing GUI issues with <random Linux DAW>! Please fix this ASAP.

Thanks in advance! <random email address>

[fabio77]

Originally Posted by Glennbo

I wonder how easy it would be to create an auto-bot mailer to send the WINE-Os 20 angry messages per day, with randomly generated "From" addresses, and randomly generated Linux DAW and plugins reports. Something like this.

Haha But I don't know if this would benefit or rather harm the relationship between the wine people and linux musicians.

But since it's open source, I would like to see some explanation about what they changed, that might cause these regressions. That would maybe help to work around it or even realign to their new concept of .. I don't know, window drawing and pointing to coordinates, through this new "crosseyed" wine targeting

[Glennbo]

Originally Posted by osxmidi

Try this one for Wine 10.3

I still don't have WINE 10.3, but can confirm that this newest patch still works fine in 10.2-2.

Thanks OSXmidi for jumping right into the middle of these changes in recent WINE versions. I'm now waiting for 10.3 to drop in Manjaro so I can check it out.

BTW, anybody running Manjaro and having issues or error messages updating, it might be related to your /etc/pacman.conf file. Up until recently it would still honor the file if it had an entry for [community] because they were using a blank entry in their database so it wouldn't error out. Now that is no longer the case and if you do have a [community] section, you will get errors and not be able to update. I just commented mine out like this,

# [community]
# SigLevel = PackageRequired
# Include = /etc/pacman.d/mirrorlist

and all is cool again. Three of the four machines I have running Manjaro needed these lines commented out. What used to be in [community] has been merged with [extra] and the [community] entry is now invalid.

Also, you will need to refresh the mirrors if you comment those lines out.

[fabio77]

Originally Posted by osxmidi

Try this one for Wine 10.3

Yes, it works Thank you!

[osxmidi]

Originally Posted by Glennbo

I still don't have WINE 10.3, but can confirm that this newest patch still works fine in 10.2-2.

Thanks OSXmidi for jumping right into the middle of these changes in recent WINE versions. I'm now waiting for 10.3 to drop in Manjaro so I can check it out.

BTW, anybody running Manjaro and having issues or error messages updating, it might be related to your /etc/pacman.conf file. Up until recently it would still honor the file if it had an entry for [community] because they were using a blank entry in their database so it wouldn't error out. Now that is no longer the case and if you do have a [community] section, you will get errors and not be able to update. I just commented mine out like this,

# [community]
# SigLevel = PackageRequired
# Include = /etc/pacman.d/mirrorlist

and all is cool again. Three of the four machines I have running Manjaro needed these lines commented out. What used to be in [community] has been merged with [extra] and the [community] entry is now invalid.

Also, you will need to refresh the mirrors if you comment those lines out.

Thanks for letting me know that it works, it helps in getting a version that runs regardless of wine version and that hopefully will be future (wine) proof.

[osxmidi]

Originally Posted by fabio77

Yes, it works Thank you!

Thanks for trying it out, it also helps to hear that it works on various different systems.

[fabio77]

Originally Posted by osxmidi

Thanks for trying it out, it also helps to hear that it works on various different systems.

I have an old laptop, wich I only use for testing reasons. It has actually Debian, EndeavourOS, Fedora 41 and OpenSuse Tumbleweed installed.
If it would help, I could install some vst for testing with LinVST on each of it.


EDIT: On Debian I was not able to install wine correctly, and couldn't install any plugin

On EndeavourOS I recently have installed wine-9.20 on my pc and wine-10.3 on my laptop: both work fine.

Fedora also has wine-10.3 so I didn't test and assume it's the same as on Endeavour.

My OpenSuse installation has wine-7.12 and installing TDR-Nova and converting it with LinVST worked also fine.

But I realized some minor things:
When I close the plugin window I have a delay of about 2 seconds, before it really closes.
Sometimes, when I open up the plugin window, the plugin interface is black, but after hoovering over it the interface appears.

[Glennbo]

Originally Posted by osxmidi

Thanks for letting me know that it works, it helps in getting a version that runs regardless of wine version and that hopefully will be future (wine) proof.

Still no WINE 10.3 in Manjaro XFCE. I keep checking several times a day to see if it has dropped yet, but so far it hasn't shown up.

The latest LinVST is still working fine in WINE 10.2-2, with no unexpected side effects.

[fabio77]

Originally Posted by osxmidi

I've got a beta version you could try which has some new ways of doing things and enables the use of the space bar (press shift to bypass the space bar key going to the plugin).

This works on wine-10.3! No more delay on closing windows and no hidden interface. You really seem to know what the problems are and how to work around

I will test on the other wine versions later.

Originally Posted by osxmidi

Fabfilter seems to have some problems with wine, sometimes the display is ok and sometimes not, it even does it in Ardour which has a different way of opening and closing the vst's display (it just opens the vst display at the start and then toggles the window on and off without reopening and closing the display).

I really like the fabfilter plugins. They are at least buggy through wine from all the paid ones I have. All others either stopped to work at some point or were unable to register. The sonible plugins are ok also, but only if you don't reinstall your system often. Because they have limited register slots, and every new installation seems to be considered as a new machine.
There should be a way to deregister them as long you are on the old installation, but if you forget before reinstalling the system there is no way around, but to contact the support and ask for some new slots (what they did for me).
So, when I stopped to buy any other windows vsts, the fabfilter plugins were the only ones I still paid for, because they are great

But that's another topic. So thank you for the patch!

[Glennbo]

Originally Posted by fabio77

This works on wine-10.3! No more delay on closing windows and no hidden interface. You really seem to know what the problems are and how to work around

I will test on the other wine versions later.

I briefly tried the Beta, but the first plugin I tried loading, which was Superior Drummer 2, didn't work, so then I rolled back to the first version for 10.3 and it still didn't work.

Then I noticed that it was saying it couldn't find the drum libraries, so I pointed Superior to the seven drum libraries I have, and it worked again. I haven't yet tried the Beta, but I'm pretty sure it would work okay as well.

I was messing last night with trying to add Proteus-X presets that someone posted in another thread, and the install of those likely broke the paths for Superior, which I never tried after giving up on trying to make the Proteus-X patches work in Proteus-VX.

I'm still waiting for Manjaro to drop WINE 10.3, which I'm now surprised has not happened yet.

I really like the fabfilter plugins. They are at least buggy through wine from all the paid ones I have. All others either stopped to work at some point or were unable to register. The sonible plugins are ok also, but only if you don't reinstall your system often. Because they have limited register slots, and every new installation seems to be considered as a new machine.
There should be a way to deregister them as long you are on the old installation, but if you forget before reinstalling the system there is no way around, but to contact the support and ask for some new slots (what they did for me).
So, when I stopped to buy any other windows vsts, the fabfilter plugins were the only ones I still paid for, because they are great

But that's another topic. So thank you for the patch!

I've always been leery of reinstalling any of my Windows plugins, because of the number of slots thing. Superior Drummer 2, EZ-Drummer 1, and EZ-Keys 1 are all like that. I'm still using the very same .wine folder that I setup way back in 2018, and have never reinstalled any of my Windows plugins since then. That's been the same .wine folder through three installs of Xubuntu and three installs of Manjaro. The other thing I worry about is that companies like Native Instruments like to change what software you have to run to install their plugins. I have both Native Access, and Service Center from 2018, but would either of those even work at this point?

[michael diemer]

Originally Posted by Glennbo

I briefly tried the Beta, but the first plugin I tried loading, which was Superior Drummer 2, didn't work, so then I rolled back to the first version for 10.3 and it still didn't work.

Then I noticed that it was saying it couldn't find the drum libraries, so I pointed Superior to the seven drum libraries I have, and it worked again. I haven't yet tried the Beta, but I'm pretty sure it would work okay as well.

I was messing last night with trying to add Proteus-X presets that someone posted in another thread, and the install of those likely broke the paths for Superior, which I never tried after giving up on trying to make the Proteus-X patches work in Proteus-VX.

I'm still waiting for Manjaro to drop WINE 10.3, which I'm now surprised has not happened yet.



I've always been leery of reinstalling any of my Windows plugins, because of the number of slots thing. Superior Drummer 2, EZ-Drummer 1, and EZ-Keys 1 are all like that. I'm still using the very same .wine folder that I setup way back in 2018, and have never reinstalled any of my Windows plugins since then. That's been the same .wine folder through three installs of Xubuntu and three installs of Manjaro. The other thing I worry about is that companies like Native Instruments like to change what software you have to run to install their plugins. I have both Native Access, and Service Center from 2018, but would either of those even work at this point?

Service Center would definitely not work, as NI abandoned it several years ago. to my knowledge, only Native Access 1.x works on Wine. Supposedly 2.x works with considerable tweaking (something involving a daemon, but I try to stay away from those ).

[Glennbo]

Originally Posted by michael diemer

Service Center would definitely not work, as NI abandoned it several years ago. to my knowledge, only Native Access 1.x works on Wine. Supposedly 2.x works with considerable tweaking (something involving a daemon, but I try to stay away from those ).

So far, I haven't needed to mess with installing Kontakt, or any of my other Windows plugins again since 2018, and I have multiple backups of my .wine folder with everything installed, so if something were to get corrupted, I have several rabbits I could pull out of the hat.

I also will *never* install another Windows plugin (even the free ones), because I don't support developers who don't support Linux. All the Windows plugins I have were *all* purchased when I was still running Windows.

That said, I am only moments away from sending $140 US to Modartt for Pianoteq. I just have to decide for sure on what the second piano I want will be. It's a toss up between the U4 upright or the Kawai. I'm definitely getting the Steinway Model D New York and either the U4 or Kawai as the second one. Anyway, another Linux developer will get my money, and not some Windows and Mac only developer.

[fabio77]

I just tested the beta on wine-9.21. And first it seemed to work fine, but then I realized, that I got the delay on closing windows again, when I loaded any other plugins than fabfilter ones.
And after that I got the delay even with the fabfilter plugins.

Maybe tomorrow I test again with wine-10.3. It could be that I the first test just wasn't long enough.

But the main thing is, that the plugins are usable.

[osxmidi]

Originally Posted by fabio77

I just tested the beta on wine-9.21. And first it seemed to work fine, but then I realized, that I got the delay on closing windows again, when I loaded any other plugins than fabfilter ones.
And after that I got the delay even with the fabfilter plugins.

Maybe tomorrow I test again with wine-10.3. It could be that I the first test just wasn't long enough.

But the main thing is, that the plugins are usable.

Delays could be anything, maybe the state of the wine prefix, overrides, what was previously installed interfering somehow, who knows, maybe Wayland issues or just wine issues, and some plugins might result in it, and maybe display cards/drivers.

I don't think it's LinVst itself, because I've tested it on Ubuntu Wayland/Mutter and EndeavourOS/xfce and MX Linux/xfce and I havn't encountered delays like you describe, but I could be wrong.

I havn't tested using KDE at all.

When I test, I've often got a clean new wine prefix, because I often delete the wine prefix to stop possible accumulated errors happening (possible dll conflicts or override conflicts or config conflicts etc) from other vst installs happening when I'm testing some vst's,

[fabio77]

Originally Posted by osxmidi

Delays could be anything, ...

I don't think it's LinVst itself

I didn't think that either. I only can imagine the amount of possibilities for issues, in that process.

Originally Posted by osxmidi

I've tested it on Ubuntu Wayland/Mutter and EndeavourOS/xfce and MX Linux/xfce and I havn't encountered delays like you describe, but I could be wrong.

I havn't tested using KDE at all.

Oh, so there are no delays on XFCE. I know that kwin sometimes can do weird stuff too.

But as I said, this doesn't effect the functionality of the plugins, what's most important. I don't think I will switch to XFCE