3 <img src="/images/automation-lane1.png">
4 <figcaption class=center>A typical automation lane.</figcaption>
8 An <dfn>automation lane</dfn> is similar to a track in that it holds data
9 that can be played back; however, unlike a track, it is not an independent
10 entity—it is always attached to the track that it controls. Automation
11 lanes also contain zero to one <dfn>automation curves</dfn>. Each lane
12 controls one and only one parameter of the track it is attached to.
16 Every track will have at least five automation lanes associated with it:
17 trim, fader, mute, and pan (which consists of two lanes: L/R and Width); it
18 can possibly have many more if there are any processors associated with it.
19 All these lanes are automatically attached to the track but hidden, and
20 initially they are all empty (have no automation curves in them).
24 <img src="/images/automation-multi-lane1.png">
25 <figcaption class=center>An example of a track with three lanes of automation (fader & pan).</figcaption>
29 Automation lanes typically have the following controls:
33 <li>A hide button (square button with an "X" inside)</li>
34 <li>A horizontal fader</li>
35 <li>An <dfn>automation mode</dfn> selector</li>
39 The hide button, as the name implies, hides the automation lane. The
40 horizontal fader controls the level of the parameter that the lane controls;
41 manipulating this while in <kbd class=menu>Write</kbd> or <kbd
42 class=menu>Touch</kbd> mode during playback will make changes to the lane's
43 automation curve. The automation mode selector selects which mode the lane is
44 in (<kbd class=menu>Manual</kbd>, <kbd class=menu>Play</kbd>, <kbd
45 class=menu>Write</kbd>, or <kbd class=menu>Touch</kbd>).
49 The hide button will only hide the lane; it does not remove it from the
50 track. The automation lane never really goes away—the closest one can
51 get to that is to clear the automation curve and hide the lane.