X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=include%2Fplugin-dsp-load.html;fp=include%2Fplugin-dsp-load.html;h=2867615e3f8610a94fccecf2bffa8afefabce401;hb=56cc1b98148c58196d66cc510e0c3d5b948de21e;hp=0000000000000000000000000000000000000000;hpb=44106a3552904ca832ba1e7e09ef276dd39fead7;p=ardour-manual

diff --git a/include/plugin-dsp-load.html b/include/plugin-dsp-load.html
new file mode 100644
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