At 4 hours ago, midimachine wrote:
Yeah smart disable only affects stuff that isn't doing anything, so if every plugin in your project is doing something at the same time then smart disable won't make a difference.
It does make a massive difference for me, mostly when I'm not listening to the track but adding stuff to it or listening to individual patterns. Without smart disable my CPU goes up to like 70% usage in some tracks when I'm idle and just to listen to one instrument playing or add another instrument, for example, I've got to go through a crapload of lag.
FL will even affect outside programs too, so if smart disable isn't on, I've got a project file with more East/West VST's than there are letters in the alphabet (which is nearly always the case), while, say, browsing NG, I'll get lag over there too.
With smart disable on, the CPU goes down to 5%-ish and it's a lot easier to work with. @WizMystery, to check if it really is making a difference or not, take note of your CPU usage while you're not doing anything, then enable it and see if it went down dramatically.
Alternatively you can check manually if the macro worked by opening the plugin window of the plugins you're using and clicking on the small arrow at the top left corner. In the menu that comes up it'll show you whether the VST has smart disable on or not. If it did switch smart disable on and you're still getting lag, then I'm stumped I'm afraid.