2 The <dfn>Plugin DSP Load</dfn> window is helpful in cases where
3 some of the plugins in use overload the CPU, resulting in audible
4 clicks and pops in the output, but you aren't quire sure which ones
5 are causing this exactly.
9 <img src="/images/plugin-dsp-load.png" alt="The Plugin DSP Load window" width="50%" />
10 <figcaption class=center>The Plugin DSP Load window</figcaption>
14 For each plugin in use, there is a chart and numeric data that represents
15 minumum, maximum, and average CPU time used, as well as standard deviation.
16 This, along with simple color coding — green for safe amount of CPU use,
17 red for CPU overload — gives you a good overview of what's going on
22 The Plugin DSP Load window has basic sorting options: by worst-case load
23 or by average load. This helps easily locating the worst offenders. You
24 can also click to reset all stats.
28 You can use the data provided by the Plugin DSP Load window to decide
29 whether you want to replace a plugin with a less resource-hungry one,
30 freeze a track, or report a potential bug to the plugin's developer and
35 It's worth noting that certain type of plugins, like convolution reverbs
36 and guitar amp simulators, tend to consume more resources.