This is a how-to for getting FL Studio to run in Wine. It won't run perfectly(not yet anyway), and there are some quirks and flaws but it is usable. :)
This how-to updated as wine progresses and changes.

In my experience using cracked software for creative endeavors is a bad, bad idea. Years ago I was very poor, and could barely afford a computer. I worked day labor jobs in addition to my normal job to afford a Windows PC.

Note

1. FL Studio Crack. FL Studio 12 Crack is a complete software music production environment or Digital Audio Workstation (DAW). Representing more than 18 years of innovative developments it has everything you need in one package to compose, arrange, record, edit, mix and master professional quality music.
2. Audible artifacts in FL Studio These are usually caused by ' buffer underruns '. That is, the audio stream to the soundcard is interrupted when a temporary memory-buffer holding the audio data runs dry. This is caused by CPU and or Hard Disk overloading.

If you have FL Studio installed on your Windows partition it is recommend you keep it separate from the one you're about to install in Linux and just copy over your Project Files later.

Telling wine to access your windows install is not a good idea.

The How-To

1. make sure you have the latest Wine
2. You can get the latest Wine packages for the most common distros here: http://winehq.org/site/download
3. start your favorite terminal emulator(Konsole,GTerm)or press ALT+F2 and type in: winecfg
4. Download the latest version of FL Studio(7.0) and save it in your Home folder.
5. Open your favorite terminal program (Konsole,GTerm,etc) and type in:
   
6. wine flstudio7_RC6b.exe
7. The install will start (you'll get a few error popups, just click OK to them).
8. To make it easier to follow this how-to, chose the default install locations.
9. After you're done the installation you'll have to edit a text file to be able to play most of the sound files that come with FL Studio.
10. Copy and paste the following command into the terminal and press enter
11. sed -i 's/[drivers32]/[drivers32]nMSACM.vorbis=vorbis.acm/' ~/.wine/drive_c/windows/system.ini
12. Wasp and DrumSynth plugins(and others) need a dll called mfc42.dll to run.
13. To install this dll, at the console copy and paste the following
14. wget http://www.kegel.com/wine/winetricks && sh winetricks vcrun6

To import your FL Studio key to run FL Studio in Full Express/Fruity/Producer/whatever you paid for mode. (not needed to run in demo mode)
Download your FL Studio Registry key: FLStudioLogin
Save it in your Home folder. Now press ALT+F2(or start your terminal program) and type in: regedit
This'll start the wine registry editor. Click Registry->Import Registry File, and then select your reg file.
Put all that in a text file and save it in your Home directory. It doesn't matter what file name you give it.
REGEDIT4
[HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings]
@='
'ProxyEnable'=dword:00000000

Now import it the same way you imported the FL Studio Registry key. This will enable the news reader and FPC Drumkit and DirectWave downloads.
Ok, so that's all the tweaking that has to be done with Wine, the rest will be in FL Studio. :)
You should have an FL Studio icon on your desktop, but if you don't you'll start FL Studio from the terminal, and you can make a desktop icon yourself later.
Start FL Studio with the desktop icon or in a terminal program like this:

wine 'c:Program FilesImage-LineFL Studio 7FL.exe'
Experiment with buffer length in Options->Audio Settings.
Polling and Hardware Buffers options don't seem to have any effect on performance.
Enabling the 32-bit buffer will causes FL Studio to use up 100% cpu and not play at all.
FL Studio 7 has multithreaded support! Go to General and check 'Multithreaded generator processing'. I don't have a multi-core setup so I can't test this feature. If you do then leave a comment on how well it works when submitting test data. :)
When you start FL Studio, renice (lower the priority) of FL.exe to 19:
In KDE, Launch KSysGuard (or CTLR+ESC) and right click on FL.exe and renice it to 19.
In GNOME, launch the system process list, right click on FL.exe and set the priority to 19.
This'll lower the buffer underruns by a lot and make the whole experience much smoother (no underruns when doing other things).
That's it, just read through the Know Issues to avoid them if possible and enjoy FL Studio in Linux. :)

Known Issues

• Moving a window in FL Studio is extremely slow and will spike the cpu usage to 100%. This is because Wine is very inefficient with this part of the windows API at the moment.
• FL Studio playback will stutter and freeze for a second if you do anything anything else that uses the cpu. This is because Wine is unable to prioritize cpu usage to a section of the wine sound driver, and this causes stutters and buffer underruns(bug #1631).
• (This might not be as noticable on multi-core setups since the cpu load will be distributed on the extra cores.)
• Renice FL.exe to 19. This will prioritize core parts of Wine (like sound) over the really slow FL Studio GUI and this will greatly decrease buffer underruns.
• If you get a notice saying something like 'Cannot open DSound device' when starting FL Studio then log out and in and the problem should be gone.
• Audio latiencies should not be a problem since realtime kernels can be used and JACK substitutes ASIO, but until Wine can prioritize cpu usage to avoid buffer underruns this problem can't be solved.
• EDIT: The sound thread is now reasonably prioritized with the renicing. I'll have a go at the realtime kernel and JACK.
• The ReWired plugin does not work.
• Using .rex files does not work.
• Any hardware synths or keyboards probably won't work with FL Studio, however MIDI hardware might work. A user mentioned their midi keyboard works. Thanks for the comment. :)
• Anything beyond stereo(5.1,7.1) will not work. This is a limitation of the current Wine sound driver.
• 'Help' starts, but isn't very usable. Use a native CHM viewer(KchmViewer,GnoCHM) to view the help files.
• They're located in: FL Studio 7/Help
• 'About' does not scroll through the credits.

FL Studio is one of the best music software solutions that can be used as a Digital Audio Workstation (DAW).

It provides you with the ability to create your own music as well as edit other music files. But sometimes people can be heard complaining about FL Studio’s performance issues. Most of the complaints are centered around the ‘extra sounds’ issue which is very much audible at times. These are mostly glitches or crackles and the sound is often choppy and strange.

We recommend putting the System Cache and Software Junk features of ST Cleaner to good use. These features ensure everything is fine, as far as the basics relating to keeping your computer in an unkempt state are concerned.

ST Cleaner is distributed with verifiable digital signatures

There can be two different reasons related to this choppy sound. It could be because of some random plug-in which is behaving like this, or it could be the buffer underrun problem.

Crackling In Fl Studio

To fix the plug-in problem, you need to open the plug-in wrapper processing tab where you can find the Allow threaded processing option. Now deselect this option and check if the problem is solved or not. If the problem persists then you need to select the Use fixed sized buffer option. Once you’ve made these two adjustments, you will stop getting the ‘extra sounds’, in most of the cases.

Fl Studio Crackling No Underruns

But if the problem is due to buffer underruns then there are some steps which you need to perform to solve this issue.

• Navigate to Audio settings and select FL Studio ASIO in the Device drop-down menu
• Now you need to change the buffer length settings as well
• Try to get the buffer length to somewhere near 10 ms (which basically means at 441 samples)
• Make sure that there is little addition in Underruns Count during this process
• If you find that underruns count stop increasing you can decrease the Buffer Length settings
• Make sure that the Buffer Length settings value never comes under 10ms else the load on your CPU will increase sharply
• Remember that Buffer Length and Underruns Count values are inversely proportional to each other
• For ASIO driver, there can be three different Buffer Length settings
  • 1–4 ms (44–176 samples) which is very good but you don’t need this as it will increase the load on your CPU
  • 5–10 ms (220–440 samples) this is excellent and ideal setting. We recommend setting it at 10ms
  • 11–20 ms (485–882 samples) which is acceptable and can provide you with a reasonably good sound

With all these steps the choppy sound problem will be solved and you will be able to hear clear music. But if the problem persists, you can check its memory and CPU optimization section but at your own risk. You can also check different other programs which might cause FL Studio to make these unpleasant sounds. As an example, a program called f.lux that changes the color temperature of the screen can cause this issue. If you have installed it, please get rid of it at the earliest.

If the Buffer Length setting is more than 100 ms (4410 samples) and the CPU usage is at 80%, this is basically an indication to upgrade your PC because your system isn’t capable enough to support FL Studio in this case.