CPU meter only shows load from processing audio?

[clay]

Ive used ableton for 15 years or so. Im putting together a performance set and am trying to optimise the use of CPU.

live's manual says - Note that the CPU meter takes into account only the load from processing audio, not other tasks the computer performs (e.g., managing Live’s user interface).

also says - When there is no incoming audio, the effects are deactivated until they are needed again.

However Im noticing that some VSTS/AU plugins seem to be getting around this and are using considerable CPU when no audio is being fed to the plugin and the set is not playing. For example, GW Voicecentric uses around 9% of live's CPU on my computer just by dragging it into a new set that is not playing. Many other examples too.

So for plugins, it appears that actually live's CPU meter is not only taking into account the load from processing audio. As soon as some plugins are instantiated, they start using CPU whether they are being actively used or not.

Has anyone looked into this more and is it a live 10 thing? or is it just that vsts/au plugins don't adhere to ableton's rules around CPU usage?

[fishmonkey]

Ive used ableton for 15 years or so. Im putting together a performance set and am trying to optimise the use of CPU.

live's manual says - Note that the CPU meter takes into account only the load from processing audio, not other tasks the computer performs (e.g., managing Live’s user interface).

also says - When there is no incoming audio, the effects are deactivated until they are needed again.

However Im noticing that some VSTS/AU plugins seem to be getting around this and are using considerable CPU when no audio is being fed to the plugin and the set is not playing. For example, GW Voicecentric uses around 9% of live's CPU on my computer just by dragging it into a new set that is not playing. Many other examples too.

So for plugins, it appears that actually live's CPU meter is not only taking into account the load from processing audio. As soon as some plugins are instantiated, they start using CPU whether they are being actively used or not.

Has anyone looked into this more and is it a live 10 thing? or is it just that vsts/au plugins don't adhere to ableton's rules around CPU usage?

nup, the deactivation doesn't apply to VST/AU plugins.

my understanding, based upon comments made by Ableton staff in that past, is that the Live load meter gives you a rough idea of how much leeway your system has to keep processing audio without glitching. for example, if your sample rate is 44.1 kHz and your buffer size is 1024 samples, then the buffer needs to be filled in less than about 23 milliseconds—and this buffer processing needs to happen continuously to avoid an audio glitch. the Live load meter gives you a rough measure of how much of those 23 milliseconds is being used up...