To expand upon the point of running Windows VSTs in Linux in FL via WINE, teh initial setup is very, very tedious, as you have ot install all the essential windows dependencies/bloat in order to make all of them run. off the top of my head i can think of .net framework and visual c++ (yes, you will need to install most.all of them, takes quite a while you cna imagine). and enve after that, once you have all your VSTs working (or most of them), one odd WINE update can either cause the GUI of a plugin to not render, leaving you to either go in blind or control the plugin by browsing its parameters (which pray the dev has made them automatable), or less likely but more devastating it just won’t work anymore, either by instafreezing your daw, or straight up crashing it. had that happen with Spectral Compressor, it will forever be missed. Lucily subsequent WINE updates can fix the UI break issue, but it’ll feel like forever until that update lmao

TLDR if you can deal with maybe a few of your plugins breaking, hopefully getting ifxed after a WINE update, and a chance that one or two plugins just don’t run (classic WINE jank), it’s pretty much smooth sailing cause FL actually runs pretty damn good in WINE, i’d say shockingly close to native. Only things that don’t work for me are the WebView rendered stuff (like diagnostics and gophr but i don’t use gophr. A friend of mine got diagnostics to work by installing dotnet and webview2, i already had them installed and it didn’t work). WINE can vary from system to system.