Are you running a 32 bit version of FL Studio? Doesn't matter if you have 1,000 gigs of RAM and a processor with the power of Zues. The 32bit Daw is going to only be able to acquire 4gigs of your RAM resources.

 

If the particular plug-in locks the CPU performance it will do that whenever is active. Smart disable won't change that.

 

CPU load has nothing to do with the amount of RAM.

 

This was about to be my question.

 

Also use ram patchers for activating all of your RAM in a 32bit OS (I am using one).

 

not trying it won't change anything so it's worth a shot

 

Thanks for this bro, but i already know about it, and uses it all the time... no more producing for me until Image line get's this fixed up lol

 

Read this article http://www.themusicproducerblog.com/2015/10/optimising-your-pc-for-audio-use.html

 

is your computer overheating? i had that problem and cleaned my computer and it worked like a charm afterwards

 

I get the impression you are overloading a core.

Try rebuilding the project (doesn't have to be musically identical) and watch the resources as you increase VSTs etc *and* when you do the routing through the mixer.

Just work out where the issue is and work around it. Bounce down? Sort your routing out? IF the problem doesn't happen with one instance, then that isn't the problem. Add another instance. Check the routing. At some point the problem will appear. Go back, bounce down...change your routing.....

I suspect you are just asking too much from your machine. But regardless, work to the point it works, and bounce down. Why do you not do that?

 

Actually your CPU sends data to RAM to free up it's resource. When you have less RAM resource you're requiring your system to use more virtual memory from your HDD. This causes your cpu to do more work (overload) from having to move data between your RAM and HDD and modifying page tables. So yeah, less RAM when working with large chunks of paged data will definitely strain your CPU.

 

FL in my opinion is the worst DAW when it comes in CPU performance, specially in version 12 and with third party plugins! Unfortunately there is no solution if you want to match the CPU performance from other DAWs with FLs. Try to use as many internal plugins you can and third party that are not so CPU hangry like Sylenth1 from instruments.

 

I'm pretty sure you can find the solution of your problem in some BIOS settings of your motherboard.

 

I was going to use the old classic, doubling your RAM will make your computer run 30% faster, but unfortunately, you cannot educate someone who is unwilling to learn. You also explained it far better.

 

using a bunch of effects and midi and receiving audio in, roland vsts, serum and Steinberg vsts, 99 out of a 100 times i dont have a single problem

 

You're right. What I meant is that nowdays on an average machine that scenario almost certainly won't be the cause of cpu overload in your DAW so you don't have to waste your time on that matter. Even on Win7 32bit and 4GB RAM and large libraries that scenario won't happen. Been there done it.