you can buy a better CPU but the problem could be still there...

 

hi change you device or driver is set to M-Audio at the moment
change it to ASIO4ALL v2 or Fl studio ASIO,
next resampling qualty is set to 2-point
should be 24 point if it don't change to 24 when you set your driver to ASIO
change it yourself to 24 ,
you should also shut down all backround programs your not useing
can find some vids on youtube about how to do this,
some more info is xp vid lol but works the same way on all o/s

at 3.40 set yours to backround services

just under backround services is vertual memory
click change and make sure its set to c / system managed size
press set then ok restart pc,

setting backround services as best preformance
is what your plugins use and will help you get the most from your pc
when making music,but you will only get the most out of it after shuting
down unneeded backround programs,

 

Last edited: Jan 30, 2016

Maybe the problem it's because the OP messed up with OVERCLOOK settings...

 

I had the same problem and i fixed it.

you can have 64Go of RAM the problem still here cuz it's a bug, i dont know for you but in my case only one SFX plugin f***ed up 80% of the CPU, it was "2C Aether", so try to remove all SFXs plugins one by one and and see exactly which one causes the CPU bug.
Salam

 

This has absolutely nothing to do with RAM and it's no bug either... Some plugins just are more CPU-intensive than others. This might be due to bad optimization or just because it has "many things to calculate".

 

i use fl studio since version 9.... and this the WORST version of all time, I KNOW HOW TO CONFIGURATE..its a problem wiht this version dps/ new gui suport for touch something here made frutty loops A REAALLY SHI*T....
fl studio fall in decande.....
if you open the extly same project, whit the exactly SAME configuration (means..) fl 11 to fl 12. yuo see fl 11 WORKS PERFECT, fl 12 have a blac screen every time you load a pluggin... and have this shi*t off RAM AND /cpu....
now NOT for compare whit exp: studio one... but on studio one SAME project WORKS perfect like on fl 11.

for me frutty loops 12 . fell into decline, you can not use, have problems since q was Beta 12.

ps: the BEST of this version .... absolutely ''FL studio ASIO ´´ on every daws, the rest SUCKS.....

 

it's a direct quote from support site https://www.image-line.com/support/FLHelp/html/panel_cpu.htm

 

I ran into quite the same problem when i upgraded fl to 12.2.3. So i'm back to version 12.2.2, and no stability or cpu issues... I mean, most likely it's the silliest and simpliest answer, but maybe worth a try if you haven't already done it.

 

Oh really ? 2C Aether used 99% of my CPU in an empty project with no instruments ... how can you explain that ? i know what im talkin' about, i use FL Studio since 2002... it was a bug

 

Last edited: Jan 31, 2016

Possible, but 2C reverb plugins are pretty CPU-intensive. I noticed myself that I just can't use certain presets. It doesn't matter if the project is empty besides that plugin too, and as the plugin also treats silence, the existence of audio didn't matter for me as well. But of course, if you've got the strongest CPU on the market and it still didn't work as it's supposed to, a bug would be a possible reason.

 

I'have figure it out, I've followed some of the replys here...

I have downloaded Fl Studio 11.1.1, I've used a lot of Spire instances with multiple Pads presets (i have this bad experience with pads using hell a lot of CPU power) so i used that to test my CPU, i have used Serum, too, guess what, fl Now is using up to 80-85% of my CPU, it does use almost all my CPU, so Fuck this shit of a new version of FL Studio...

i have noticed this too, when you routing, from channel to another it consumes a lot more CPU...

so i'm going back to FL Studio 11.1.1... don't really do care about interface anymore, i have suspected this because i'have been mixing a track in pro tools lately, and i've been using a lot of demanding Plugins, didn't really go above, 40% CPU...

so Yeah @Image-Line get your shit together and fix your god damn Program...

 

purely out of interest, could u guys tell me your pc specs having this 'worse' cpu experience?

I'm guessing it correlates with certain things:

1. Old/under powered video card or intel igpu.
2. not enough video memory
3. enabled Aero? disable it and other windows optimization settings.
4. power settings or motherboard settings: over-clocking, under-clocking, speedstepping, turbo-core, spread-spectrum

or you installed win 10, but then you are on your own

 

Windows 10 x64Bit Build10586

i7 870 up to 3.6Ghz non overclocked

16Gigs of DDR3 Ram @1333

Nvidia Asus GTX 670 2GB of GDDR5

XFX Core Edition Pro 850W


Power Setting or put to High Performance.

 

it is not an optimization fault, i know my OS, i know my Daw, i'm not new to this and if you saw the photo i put on in my thread, you will see it is a weird problem coming from Fl Studio my OS has nothing to do with it, thanks for trying to help tho.

 

Just tested Aether "Mystical" presets in FL 12.2 with Fl Asio drivers. CPU load max.8% on i7 3770k stock freq. The plug-in and FL are 64bit.

 

am sure in fl asshole spire killing cpu -_-

 

I had similar vexations with Logic Pro X, so I quit using it and now work with lightweight DAWs. Currently lovin' Bitwig, but Reaper and Ardour have got my number, too. Studio One is good, too, but it's also puttin' on the pounds.

 

http://www.reveal-sound.com/knowledge.php?27-30

1.1 feels like an open beta, better switch to 1.0xxx

 

i managed to get my cpu usage from 45% to 6% with this 'trick' that was on their support pages

Smart Disable - Enable Smart disable on the Audio Settings and then run the Tools Menu > Macros Switch smart disable for all plugins. This will disable effects & instruments when they are not making any sound and can decrease CPU usage significantly. If this global option causes issues with any plugins it can be disabled for those individual plugins using the wrapper menu setting 'Smart disable'. NOTE: Smart Disable is active only during live playback, it is temporarily disabled when rendering.

 

Last edited: Apr 23, 2016