Add basic Plugin DSP Load documentation

[ardour-manual] / include / plugin-dsp-load.html

diff --git a/include/plugin-dsp-load.html b/include/plugin-dsp-load.html
new file mode 100644 (file)
index 0000000..2867615
--- /dev/null
+++ b/include/plugin-dsp-load.html
@@ -0,0 +1,30 @@
+<p>
+       The <dfn>Plugin DSP Load</dfn> window is helpful in cases where
+       some of the plugins in use overload the CPU, resulting in audible
+       clicks and pops in the output, but you aren't quire sure which ones
+       are causing this exactly.
+</p>
+
+<figure class=center>
+<img src="/images/plugin-dsp-load.png" alt="The Plugin DSP Load window" width="50%" />
+<figcaption class=center>The Plugin DSP Load window</figcaption>
+</figure>
+
+<p>
+       For each plugin in use, there is a chart and numeric data that represents
+       minumum, maximum, and average CPU time used, as well as standard deviation.
+       This, along with simple color coding — green for safe amount of CPU use,
+       red for CPU overload — gives you a good overview of what's going on
+       in the session.
+</p>
+
+<p>
+       You can use this data to decide whether you want to replace a plugin with
+       a less resource-hungry one, freeze a track, or report a potential bug
+       to the plugin's developer and wait for an update.
+</p>
+
+<p>
+       It's worth noting that certain type of plugins, like convolution reverbs
+       and guitar amp simulators, tend to consume more resources.
+</p>
\ No newline at end of file