4 ms·

What about VSTs? They won't all work on Linux.

richrichardsson 4y ago
Quite a list here of Linux compatible VST/VSTi, some paid, some FOSS : http://linux-sound.org/linux-vst-plugins.html http://linux-sound.org/linux-vst-plugins.html
justaj 4y ago
Next to some awesome open source VSTs (SurgeXT, Helm, Vital etc.) there's plenty of closed source VSTs that run native on Linux (u-he plugins come to mind) But you could also use something like yabridge [0] in order to run Windows-only VSTs. 0: https://github.com/robbert-vdh/yabridge https://github.com/robbert-vdh/yabridge
squarefoot 4y ago
Many work 100% a few may have cosmetic quirks on their UI but remain usable, a few don't work at all, but those are a small number. Take a look at Yabridge, as suggested by another user, it's great. A nice aspect of running plugins under Yabridge/WINE is that you can run obsolete plugins that wouldn't load anymore on modern Windows versions, so there's no planned obsolescence that would stop you from using that beloved synth or effect that was never upgraded for example beyond Windows XP. The only problem I encountered with some among really old plugins, and I mean from well over 20 years ago, is that the installer stops as it detects a negative amount of storage available, which is very likely the result of trying to fit a bigger variable carrying the number of bytes free of modern filesystems structures into the smaller one that old code can read. I believe the error could be prevented through a quick & dirty kludge by implementing a WINE executable option that fakes the free storage the installer sees just temporarily until the end of the install procedure.
cageface 4y ago
One of the reasons I like Bitwig is that the included instruments are really good and you can use the grid to build just about anything. So I find myself reaching for third party instruments much less. Hopefully this new CLAP plugin format takes off though.

Quite a list here of Linux compatible VST/VSTi, some paid, some FOSS : http://linux-sound.org/linux-vst-plugins.html http://linux-sound.org/linux-vst-plugins.html

justaj 4y ago

Next to some awesome open source VSTs (SurgeXT, Helm, Vital etc.) there's plenty of closed source VSTs that run native on Linux (u-he plugins come to mind) But you could also use something like yabridge [0] in order to run Windows-only VSTs. 0: https://github.com/robbert-vdh/yabridge https://github.com/robbert-vdh/yabridge

squarefoot 4y ago

Many work 100% a few may have cosmetic quirks on their UI but remain usable, a few don't work at all, but those are a small number. Take a look at Yabridge, as suggested by another user, it's great. A nice aspect of running plugins under Yabridge/WINE is that you can run obsolete plugins that wouldn't load anymore on modern Windows versions, so there's no planned obsolescence that would stop you from using that beloved synth or effect that was never upgraded for example beyond Windows XP. The only problem I encountered with some among really old plugins, and I mean from well over 20 years ago, is that the installer stops as it detects a negative amount of storage available, which is very likely the result of trying to fit a bigger variable carrying the number of bytes free of modern filesystems structures into the smaller one that old code can read. I believe the error could be prevented through a quick & dirty kludge by implementing a WINE executable option that fakes the free storage the installer sees just temporarily until the end of the install procedure.

cageface 4y ago

One of the reasons I like Bitwig is that the included instruments are really good and you can use the grid to build just about anything. So I find myself reaching for third party instruments much less. Hopefully this new CLAP plugin format takes off though.