From ae22039995eba8e33c1aa1f206a019cb0a8ed237 Mon Sep 17 00:00:00 2001
From: Raymond Toy <rtoy@chromium.org>
Date: Wed, 11 May 2016 14:26:30 -0700
Subject: [PATCH] Fix #766: Behavior of automations and nominal ranges

Specify the behavior of automations with nominal ranges.  Automations
are internally computed as there were no nominal ranges.  Only when
they are applied is the clamping done.  A simple example is given.
---
 index.html | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/index.html b/index.html
index c21e77941..90181bc51 100644
--- a/index.html
+++ b/index.html
@@ -3185,6 +3185,26 @@ <h3>
             range</a> after having been computed from the different
             <a>AudioParam</a> value they are composed of.
           </p>
+          <p>
+            When automation methods are used, clamping is still applied.
+            However, the automation is run as if there were no clamping at all.
+            Only when the automation values are to be applied to the output is
+            the clamping done as specified above.
+          </p>
+          <p>
+            For example, consider a node \(N\) has an AudioParam \(p\) with a
+            nominal range of \([0, 1]\), and following automation sequence
+          </p>
+          <pre class="highlight example">
+            N.p.setValueAtTime(0, 0);
+            N.p.linearRampToValueAtTime(100, 1);
+            N.p.linearRampToValueAtTime(0, 2)
+          </pre>
+          <p>
+            The initial slope of the curve is 100, until it reaches the maximum
+            value of 1, at which time, the output is held constant. Finally,
+            near time 2, the slope of the curve is -100.
+          </p>
         </section>
         <section>
           <h3 id="example1-AudioParam">