2017-02-21 15:55:11 -05:00
|
|
|
|
|
|
|
|
<figure class=right>
|
2019-01-24 06:00:52 -05:00
|
|
|
<img src="/images/automation-fader1.png" alt="An example of a fader automation lane (below) with its associated track (above).">
|
|
|
|
|
<figcaption class=center>An example of a fader automation lane (below) with its associated track (above).
|
|
|
|
|
</figcaption>
|
2017-02-21 15:55:11 -05:00
|
|
|
</figure>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
Track automation occurs in one or more <dfn>lanes</dfn>. Each lane has a
|
|
|
|
|
control that allows setting the amount or position of a certain
|
|
|
|
|
<dfn>parameter</dfn> associated with the lane. Parameters are things that can
|
|
|
|
|
be controlled on a track's automation lane, such as volume, panning, muting,
|
2019-07-30 13:44:58 -04:00
|
|
|
trim, etc. <dfn>Automation curves</dfn> typically consist of lines connected by
|
2017-02-21 15:55:11 -05:00
|
|
|
<dfn>control points</dfn>, that live within the confines of a lane; these
|
|
|
|
|
tell Ardour how to change a given parameter over time. <dfn>Automation
|
2019-07-30 13:44:58 -04:00
|
|
|
modes</dfn> define how Ardour creates the values in between the control
|
|
|
|
|
points of a given automation curve, either by connecting them with continuous
|
|
|
|
|
lines or not. <dfn>Automation states</dfn> govern how a given automation lane
|
|
|
|
|
will behave during playback.
|
2017-02-21 15:55:11 -05:00
|
|
|
</p>
|
