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

diff --git a/include/plugin-dsp-load.html b/include/plugin-dsp-load.html
index 2867615..e25b435 100644
--- a/include/plugin-dsp-load.html
+++ b/include/plugin-dsp-load.html
@@ -1,8 +1,9 @@
 <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.
+	some of the plugins need too much CPU time to process buffers,
+	resulting in audible clicks and pops in the output, but you aren't
+	quire sure which ones are causing this exactly or you do know,
+	but you need actual stats.
 </p>
 
 <figure class=center>
@@ -13,15 +14,28 @@
 <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.
+	This, along with simple color coding — green for safe amount of CPU time,
+	red for too much CPU time required — gives you a good overview of what's
+	going on in the session.
+</p>
+
+<figure class=center>
+<img src="/images/plugin-dsp-load-graph_en.svg" alt="The Plugin DSP Load window" width="75%" />
+<figcaption class=center>Plugin DSP Load chart legend</figcaption>
+</figure>
+
+
+<p>
+	The Plugin DSP Load window has basic sorting options: by worst-case load
+	or by average load. This helps easily locating the worst offenders. You
+	can also click to reset all stats.
 </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.
+	You can use the data provided by the Plugin DSP Load window 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>