
In cases like this, it is likely that the "Current" setting has experienced a temporary overload while the "Average" CPU consumption is below the overload threshold. This means that while using "Average" setting the CPU Overload Indicator may become illuminated even though the meter does not appear to reach 100%. The CPU Overload indicator combines the "Average" and the "Current" CPU usage to provide a precise gauge of the CPU consumption in a Set. The CPU meter in Live 10 is only capable of measuring the average CPU, which results in the meter fluctuating less frequently. This is expected as the meter is now capable of measuring and displaying the total current CPU usage. Note: You may find that the CPU load meter is more active in Live 11 when using the "Current" setting compared to Live 10.


Live now includes per track CPU load metering as well as an improved overall CPU Load Meter, helping you to more accurately gauge and respond to CPU activity while using Live.
