Skip to content

Fix #766: Behavior of automations and nominal ranges #808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 12, 2016
Merged

Fix #766: Behavior of automations and nominal ranges #808

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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">
Expand Down