Managing CPU load when using Echo

  • Live Versions: 10
  • Operating System: All

While Live 10's new effect device Echo is designed to be as CPU-efficient as possible, there are certain features which can tax the CPU more heavily than others. If you encounter high CPU load or dropouts while using Echo, try minimising the usage of the following features:


  • CPU resources are freed up whenever a device is silent. If a device is not passing any signal, then Live will "silence" it so that no CPU resources are wasted. It can take quite long until Echo turns into its energy saving state because one has to measure for a while that Echo and its reverb are really silent (see also Reverb)
  • Because of the nature of the device, it is easy to end up in a state where the Echo device is never really silent, thus impacting the CPU severely depending on the circumstances (how many instances, which kind of Live set).
  • Using the "Gate" feature (under Character tab) is an effective way of preventing Echo from passing signals under a certain threshold, therefore improving overall CPU performance. (see also Gate)


A high feedback amount can cause the device to infinitely repeat the signal, so that it takes a toll on the CPU even if the device itself is not being heard (e.g., channel is muted / faded out).


Delay Time

Different delay times, be it free or synced, should not impact the CPU in a significant way. It is however true that longer delay time, depending on the amount of signal, will keep the device as "active" for a longer amount of time:



Echo uses a classic plate reverb per channel. Hence the reverb effect is quite CPU heavy. To lower the the CPU usage, set the Reverb amount to 0%:



Echo uses the Cytomic PRD filter which is CPU demanding. Disabling the filter reduces Echo's CPU load significantly:



This parameter is actually improving performance, depending on its setting, in that it silences the device input whenever that is below a certain threshold (see also Delay Time)



Using Noise from Echo's character section has the potential of increasing CPU usage, due to the fact that the device will never be completely silent and never turn into its energy saving state. Therefore, it's almost always a good idea to combine the noise with the gate:



On Windows, make sure that “High Performance” is active in the Windows Power Plan. See this third party guide to setting a high performance power plan on Windows.

Further Reading

Reducing the CPU load in Live
Managing CPU load when using Wavetable