Suggestion for Linux VST

• Jul 21, 2023 - 18:53

Would any developers or volunteers be interested in this? The program supports VST through Wine.

Here is a link to the LMMS page:

It doesn't seem to be in active development, but someone might be interested in examining the source.

Thank you!


Thanks for the pointer! I kind of doubt going through Wine would really be an acceptable option to most Linux users, but it's good to know that's at least potentially an option.

FWIW, supporting the VST itself is "easy" and already implemented. The part causing trouble, apparently, is getting the window for the VST to display and function correctly, apparently because of differences in how Linux handles windows and processes. At this point, I'm really just summarizing I read but didn't really understand, but anyhow - if someone wants to help work on this, I think the upshot is, you need expxperience in process and window management more so than in audio.

In reply to by Chuck Bermingham

It has always been possible in a VST enabled Linux Musescore 4 build to use Windows VST3 audio plugins with wine + yabridge -- if the plugin can run with wine at all: some will not work, e.g. because of missing cryptographic modules in Wine, or because of ilok, and so on..
in the middle (May 23, 2022)
yabridge ( plugins are already working. yabridge provides the gui event loop so just compiling with the flag to enable the editor to open is enough to have most of my plugins working.

For the use of Wine on Linux: if you don't want to use Wine for orchestral music, you eliminate almost all commercial products (with the exception of Librewave )
There are currently only 4 complete orchestras in a format that can be used by Linux apps (all in sfz format) - all others are either Kontakt or Windows format VST
1) SonatIna
2) Versilian Studios Community Orchestra (VSCO)
3) No Budget Orchestra (NBO)
4) Virtual Playing Orchestra (VPO)
These are not at all to bad, but if you want high quality commercial samples, you will need Wine (or switch to Windows altogether)
You can also stay with sf2 for another 30 years.

In reply to by Chuck Bermingham

You can, with a little effort use almost any Linux plugin- vst2/3, lv2 and ladspa and Windows vst2/3
But i can see why the core team does not want to put any effort into this. I have had 2 unique visitors on github since this post. Nobody is interested.

None of this will solve your problem however.
Aeolus (pipe organ synth) from
native linux vst -- works just fine. But i doubt it would be controllable enough from MS

In reply to by graffesmusic

My real problem is the sf2 files and the mixer. I'm playing around a tiny bit with broken-apart sf2, but I've done so many organ pieces, either complete or in process, on MS3 with stefans and reverb, it's just not worth it.

I spent all day going down the VST rabbit hole, and that's not worth it to me as well.

In reply to by graffesmusic

I don't have a problem if I use 3.6.2 or jojo's fork 3.7.0.

I am sorry, but this is hurtful. I have wanted to donate to Musescore recently because of my success with organ music by Buxtehude, Bach, and Sweelinck using version 3.6.2. And, sadly, I will have to continue that way, because of the incomplete soundfont supprt and make-do reverb support in 4.0. From time to time, I download development releases to see what's changed, but I guess it will take time. I don't want to bother Marc again because he seems annoyed. Still, I don't have a problem at all, but I want to be able to use the new release without these workarounds, and I'm disappointed.

I thought about this a lot overnight, and honestly, I'm wondering how serious the developers are about Linux. Maybe I'm in the minority, but I'm a very sad minority and I hope to be happy with version 4 sometime. If not, I would honestly like to know why that is.

Do you still have an unanswered question? Please log in first to post your question.