Linux VST3

• Jul 1, 2023 - 05:31

While reading the handbook chapter on the Mixer, one might get the impression that all of this works on every supported OS.
But it does not (and probably never will)
I have a 4.1 beta for Linux compiled with VST re-enabled.
=> deleted. see below
Most Linux VST's do not show a gui, but some do work: e.g. 3Vstudio Orchestools and Decentsampler (amongst others)
Also work: (almost all) Windows VST3 with yabridge (provided they can be made working with wine in the first place), e.g. Spitfire BBC discover/core, Spitfire Labs, Miroslav Philharmonic 2, Sampletank, Kontakt, ...
The Linux version of Kushview elements rack-plugin vst3 also works. This one can load Linux VST2, VST3 and LV2 plugins. It's working reasonably well (for the most part).


In reply to by Are Jayem

As said, most Linux VST's installed on my system do not work, which is normal since Linux VST support isn't implemented. (on my system, for instruments only Orchestools and Decentsampler - and also the Kushview elements, which can load most linux VST2/3 and LV2 - but there also are problems with this)
See for Linux audio plugins or/and you can try if you want.
Windows VST3 under wine with yabridge seem to be working fine (but i normally don't use those, exception made for some orchestral libraries)
This is completely experimental of course.

For the desperate Linux users, a Linux VST3 enabled appimage 4.1.0 can be downloaded here:
deleted- see below
(not official, provided "as is", only minimal tested: use at your own risk)

After starting it once - vst's will be scanned - have a look at

All plugins should have
"hasNativeEditorSupport": true,
or they will not work.
On my system, every plugin had initially this parameter set to "false", since v4.1. (it was more or less ok before a couple of weeks.)
I would suggest to test the vst's, and if they don't show a gui, just edit same file and set the vst to
"enabled": false,
so it does not show up anymore in the list.

As said, lots of native Linux VST3 do work - e.g. 3Vstudio Orchestools, Apisonic Speedrum, Aeolus, Decentsampler, DiscoDSP Highlife sampler - and a lot of fx. Some do not however.
Most Windows VST3 (wine + yabridge) work flawlessly.
And there is always Kushview elements - works reasonably well, and can load Linux VST2, VST3, lv2 and even ladspa.

In reply to by graffesmusic

New build here:
see below
known_audio_plugins.json now has always "hasNativeEditorSupport": true,

List of Native Linux VST3's (probably all build with Juce) tested and working - WITH GUI:
Orchestools from
Speedrum (Lite, Beat(from Beat magazine)) and Transperc from
Aeolus (pipe organ synth) from
Decentsampler from
HY-plugins (the free Linux versions) from
Kushview Element from
Tracktion MOC Waverazor
Bitklavier . Linux vst3 version here:…
Everything from Socalabs (except piano: crashes MS)
Odin-2 synth from
Tracktion Retromod LoFreq Classic from
DiscoDSP Highlife from
Panagement 2 from
Filterjam from
Free ASAP plugins from ircam
Firecomp2 (free for Linux) from
Librewave Sordina from
Tonelib Noice Reducer from
Venomode Maximal 3 CM (I have the Computer Music Magazine version) from
Everything from While Elephant Audio
Fire by Wings Music
Chowmultitool from
Everything by SuperflyDsp

Windows VST3's that can be made working with Wine + yabridge, all work fine. (e.g. Ik Multimedia plugins - Miroslav, Spitfire Audio plugins - BBCSO, Labs, Kontakt, and so on...)

When loading Kushview Elements, all Linux VST2, VST3, LV2 and ladspa audio plugins, and Windows VST2/3 can be used.

And then there is also Audiogridder
AudioGridder is a plugin host that allows for offloading the DSP processing of audio plugins to remote computers running macOS or Windows. The DSP code of the loaded plugins will be executed on the server machine and the plugin UIs will be streamed over the wire.
Tested with remote Windows computer and Linux VST3 in MS. It works!
Can probably be very useful with big scores on small computers.
Also with Windows VST's that can't work with wine (e.g. because of ilok)

In reply to by graffesmusic

Should anyone be interested, new AppImage 4.1.1 with vst enabled here:

Other native Linux vst3 tested and found OK:

CqtAnalyzer from
All recent free from (Tal-filter2, Tal-Chorus, Tal-Reverb-4, Tal-Noisemaker)
TurboPaco and MixMaxtrix from Artv
All from
BlindfoldEq from
Room reverb from
SmartAmp from
Eqoder from Jade Hochschule
PeakEater from T-audio
Plastiq Funeral and VU from unplugred
Declicker from (you must compile it yourself for Linux, but it goes without any problems)
Dexed (DX7 modeled synth) from Digital Suburban - (the binary release for Linux does not show a Gui on my system, but a local build from latest github source works fine)

And then there is also
YSFX from Jean Pierre Cimalando
Allows you to use any jsfx plugin (Reaper), or script one yourself .
Tested with local build.
Binaries are available at Joep Vanlier’s fork (not tested)

In reply to by graffesmusic

Thanks for being on this! Frankly, the only VST's I personally would care about would be the Muse Effects plugins, and I suspect there would be others who feel the same way. These have GUI's, but extremely simple ones. To me, if this can be made to work with just those, it's absolutely worth a PR. If there are many other VST's (especially instruments) that don't work, it might make sense to only do this for Muse Effects say that's all that is supported, and it would still be a huge win.

Of course, the Muse Hub team would have to make the Muse Effects available for testing on Linux in order to know if this is feasible or not.

In reply to by Marc Sabatella

Hi Marc
AFAICS, only native Linux vst's made with Juce do work.
If the Muse plugins are made with Juce and developers are willing to compile Linux versions, then it should hopefully be easy to do.
For other frameworks the vst host must handle this (so MuseScore)

Meanwhile, e.g. vst3 plugins do work, and offer some simple basic 'classical' audio plugins; compressor, delay, ...

In reply to by revdjohngoodman

The Linux versions of Pianoteq are lv2 and vst2. No vst3. So not usable directly in MS. (does kind of work with Kushview elements - but you loose the first note)
I asked for a vst3 version via the forum, but no response.
The good news: the windows vst3 works just fine (wine+yabridge)
(you can download a trial version)

I'm a very beginner to vst. So i downloaded a linux version of ms that supports vst and downloaded the vst itself (Aeolus). Where do i have to put it that MuseScore recognizes it?
Thx in advance, Pentatonus

In reply to by Pentatonus

which link?
I assume
-the Appimage starts
-you downloaded the Linux version of Aeolus from
( , and extracted the vst3 ~/.vst3 so you end up with
~/.vst3/Aeolus.vst3/Contents/x86_64-linux/ (note the hidden directory .vst3 )
Can you check
These should be en entry in it for the Aeolus vst3 plugin.

In reply to by graffesmusic

> which link?
Your steinbergmedia link. I can see the content table but if i click an entry there is only a error message

>I assume
>-the Appimage starts

>-you downloaded the Linux version of Aeolus from
>( ,

and extracted the vst3 ~/.vst3 so you end up with
>~/.vst3/Aeolus.vst3/Contents/x86_64-linux/ (note the hidden directory .vst3 )
No hidden .vst3 directory in my home folder
I have the .so file here:
>Can you check
>These should be en entry in it for the Aeolus vst3 plugin.

In reply to by Pentatonus

So is /home/linuxmint/Musik/MuseScore4.2/VST/ defined in the MS via n MS via Edit>Preferences>Folders ?
Why not using an official vst3 location?
As said, i always use I always use $HOME/.vst3/ , which works perfectly and does not need root privileges.
The entry in your known_audio_plugins.json does not seem complete. Some lines are missing. I have:
"enabled": true,
"meta": {
"attributes": {
"categories": "Instrument|Synth"
"hasNativeEditorSupport": true,
"id": "Aeolus",
"type": "VstPlugin",
"vendor": "Arthur Benilov"
"path": "\/home\/xxx\/.vst3\/Aeolus.vst3""

I deleted everything, and started again. Same entry. I don't know why yours is incomplete. I think you will not see the plugin if
"attributes": {
"categories": "Instrument|Synth"
is not there

By the way, sfizz does not work. You should be able to see it and select it, but it will not show a gui. (at least not on my system) This is the reason vst3 support is disable din the official Linux image. See above.

In reply to by graffesmusic

Thanks again for your great help. So i created a .vst3 folder and put the extracted Aeolus.vst3 in. I also changed the known_audio_plugins.json to that you have just posted.
Now i see a entry for Aeolus in the mixer menu (there are two entrys). But when i click one, only an empty window appears (like for sfizz)?


In reply to by Pentatonus

There should only be one entry in the json file. You can disable one of the two by changing "enabled" to false.
If you have multiple copies on the plugin in multiple directories, then every instance will have a new entry in the file and will show multiple times in MS. One should only have one location with the same plugin IMHO.
The path /home/xxx/.vst3 should reflect your home directory, obviously. So probably not xxx .
It happens to me sometimes that a Gui works only after a restart. After that, it always work, at least for the plugins listed above.
I have tested this only on Ubuntu 22.04TLS, with Xorg.
Perhaps you could try with some other plugin (from above) if this one does not show a Gui.

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