Bug 17399: AudioParam sampling is undefined
authorcrogers
Fri, 05 Oct 2012 18:13:44 -0700
changeset 179 b70ebeca5d18
parent 178 51b6809790c9
child 180 b7050f141b60
Bug 17399: AudioParam sampling is undefined
webaudio/specification.html
--- a/webaudio/specification.html	Fri Oct 05 17:41:52 2012 -0700
+++ b/webaudio/specification.html	Fri Oct 05 18:13:44 2012 -0700
@@ -1291,14 +1291,19 @@
  be taken into account on a per-audio-sample basis.
 For other <code>AudioParams</code>, sample-accuracy is not important and the value changes can be sampled more coarsely.
 Each individual <code>AudioParam</code> will specify that it is either an <em>a-rate</em> parameter
-which means that its values must be taken into account on a per-audio-sample basis, or it is a <em>k-rate</em> parameter whose value
-changes must be taken into account at least at a 3ms resolution, but can be more precise than this.  
+which means that its values must be taken into account on a per-audio-sample basis, or it is a <em>k-rate</em> parameter.  
 </p>
 
 <p>
-Because practical implementations will use <em>block</em> processing, and will process a fixed number of sample-frames at a time
-(<em>block-size</em> sample-frames).  For each block, the value of a <em>k-rate</em>
-parameter will be sampled at the time of the very first sample-frame, and that value will be used for the entire block.
+Implementations must use block processing, with each <code>AudioNode</code>
+processing 128 sample-frames in each block.
+</p>
+
+<p>
+For each 128 sample-frame block, the value of a <em>k-rate</em> parameter must
+be sampled at the time of the very first sample-frame, and that value must be
+used for the entire block.  <em>a-rate</em> parameters must be sampled for each
+sample-frame of the block.
 </p>
 
 <div class="block">