I forgot to mention that FL Studio 11 and 12 ought to also partially work if you follow the specific instructions for Linux. Mainly, first you have to install the Windows Core Fonts into the fake c:\Windows\Fonts directory nested within your /home/username/.wine/ area. It won't be there until you start at least one Windows or Wine program, such as /opt/wine-staging/bin/winecfg
But after the wine area is created, you can copy the .ttf (true type font) files from your old Windows archives into that folder (c:\Windows\Fonts) and restart the computer.
Without the essential fonts, FL Studio is unusable. And other programs need those fonts as well. There are supposed to be some debian install files for acquiring the Microsoft Core Fonts, but the installer is buggy and fails lately. So the best way to get the fonts these days is directly from a Windows archive or install (legally, I think you can do this if you are the owner). Put them on a flash drive and copy the fonts over. TTF fonts are cross-platform; it doesn't matter whether MacOS or Windows or Linux.
The more basic fonts you copy over, the more natural some web pages will appear also.
As mentioned elsewhere, some programs will require Mono and Gecko. If I remember correctly, Mono is the Linux substitute for .NET Framework and Gecko allows wine programs to use the internet.
In the past, the FL Studio installer would crash without one or both of those. I'm not sure if that's still the case though.
After you get the fonts installed, from a Linux console terminal, type "regedit" and wait for the Linux equivalent of the Windows Registry Editor to load up. Then, go to the file menu and import your FL Studio license (the "regKey.reg" type of file). If you don't have one, you can download it from your ImageLine account.
After it tells you the file imported, then you can quit RegEdit and the FL Studio installer ought to run quite alright. If it doesn't you might not have the right type of wine installed or it's too old. You might be able to remedy this by installing missing .DLL files, but it's typically kinda of tedious to do this and it doesn't always work. I'm not really sure, but it also might make Wine a little bit instable. Personally, I find the best approach is to always use wine-staging, as that's the most up to date wine.
Also, after you get wine installed, you should turn off the automatic updates from within the Software & Updates shortcut in the Linux application menu. The wine automatic upgrades seem to break wine lately. It's safer to manually upgrade wine, and only when you feel like it. Wine is constantly being improved and it's not worth risking breakage for every single little incremental upgrade. So only upgrade wine if you feel like something might actually get fixed. You can always read the release notes on the winehq.org website.
ASIO4ALL, doesn't seem to work fully on Linux, although it does partially load, so maybe on some systems it might work, but I doubt it. FL Studio ASIO does work, and it works pretty nicely, even in other programs beyond FL Studio, such as Reaper or EnergyXT.
The FL Studio Downloader might work, I haven't tried it. I've had issues with it being buggy for certain VST instruments, such as Toxic Biohazard, so I try to avoid it.
One thing that might make things easier, is whenever you need to put stuff into a directory, try not to use directory names that have spaces or underscores or other wierd characters in them. Sometimes Wine or Linux can't get past those gaps and links and shortcuts will fail. So if you can, create a folder called "Programs" or "PortableApps" or whatever, and use that whenever you can.
I was successfully able to put all of my non-installer based Windows programs into "c:\Programs" and then created my "\VSTplugins" folder inside of that. It works just fine. My installer programs still go into "c:\Program Files\" or "c:\Program Files (x86)\" but I try to steer away from that.
Windows .LNK shortcuts don't work the same way in Linux, also, so although some programs need them to be created and even some Linux desktop shortcuts use them somehow, they aren't user-friendly.
But you can still manually create Linux shortcuts such as
The quotation marks are usually necessary. .MSI files use the same syntax.