3 In order to understand how automation in Ardour works, it is necessary to
4 understand the four states of automation. They are: <kbd
5 class=menu>Manual</kbd>, <kbd class=menu>Play</kbd>, <kbd
6 class=menu>Write</kbd>, and <kbd class=menu>Touch</kbd>.
10 <img src="/images/automation-modes1.png">
11 <figcaption class=center>The automation state menu.</figcaption>
15 <kbd class=menu>Manual</kbd> state is basically analogous to a processor's
16 bypass switch. Whenever an automation lane is in this state, it is inactive
17 and any level that is manually set for controlling the lane's parameter will
18 persist during playback like normal.
22 In Ardour, every track and processor parameter is initially set to <kbd
23 class=menu>Manual</kbd> state.
27 <kbd class=menu>Play</kbd> state tells Ardour to use the automation curve in
28 the automation lane to control the level of the parameter controlled by the
29 lane <em>during playback</em>. The control that normally sets the parameter
30 will be <em>unresponsive to manual input</em> and will move automatically in
31 accord with the lane's automation curve during playback.
35 <kbd class=menu>Write</kbd> state allows continuous, dynamic setting of a
36 control during playback; all such settings are written to the lane the
37 control is in. This defines the lane's automation curve in the interval being
38 played, and overwrites any existing automation curve in the lane being
43 <kbd class=menu>Touch</kbd> state is similar to <kbd class=menu>Write</kbd>
44 mode, except it only overwrites sections of a lane's automation curve when
45 the control is changed in some way. This allows for changing only the parts
46 of an automation curve that are desired to be changed, while leaving the rest