Bug 21545: remove old text about computedValue
authorcrogers
Tue, 16 Jul 2013 12:13:55 -0700
changeset 326 4f8714b58ef1
parent 325 28a38310adae
child 327 0511c6585cb6
Bug 21545: remove old text about computedValue
webaudio/specification.html
--- a/webaudio/specification.html	Mon Jul 08 17:32:25 2013 -0400
+++ b/webaudio/specification.html	Tue Jul 16 12:13:55 2013 -0700
@@ -1862,7 +1862,8 @@
 <h3>4.5.3. Computation of Value</h3>
 
 <p>
-<dfn>computedValue</dfn> is the final value controlling the audio DSP.  It must be internally computed as follows:
+<dfn>computedValue</dfn> is the final value controlling the audio DSP and is computed by the audio rendering thread during each rendering time quantum.
+  It must be internally computed as follows:
 </p>
 
 <ol>
@@ -1887,16 +1888,6 @@
 
 </ol>
 
-
-<p>
-The <em>computedValue</em> is constantly being updated by the audio rendering thread at each rendering time quantum.
-Thus when the main JavaScript thread reads this value, then it will reflect the latest computed value.
-This will mean that reading computedValue twice in a row will potentially return different results
-if the audio thread's computations have changed the computed value of an AudioParam.  This is similar to how
-calling <code>performance.now()</code> will return an different up-to-date high-resolution time if called two times in a row.
-</p>
-
-
 </div>