1 <?xml version="1.0" standalone="no"?>
3 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
7 <section id="sn-automation">
8 <title>Automation</title>
10 This chapter will explain how to use Ardour's automation facilities to make
11 editing and mixing your sessions more productive.
14 <section id="what-is-automation">
15 <title> What is automation? </title>
17 Automation refers to Ardour's ability to remember changes you made to
18 various parameters in the session, and at what point along the timeline
19 playback had reached when you made them. Later, Ardour can make these
20 changes happen automatically at the same point on the timeline, thus
21 leaving your hands free to do something else. A typical practice when using
22 automation is to work on one or two tracks while leaving others alone,
23 recording the edits/changes. Once satisfied with the track(s), you can move
24 on to adjust other tracks. As the overall mix changes, you can return to
25 earlier tracks and adjust their existing automation.
29 <section id="what-can-be-automated">
30 <title> What can be automated? </title>
32 You can automate all changes to track/bus gain control, panning (currently
33 only for stereo output) and all plugin parameters. Future versions of
34 Ardour will allow automation of mute/solo controls, non-stereo panning, and
39 <section id="automation-modes">
40 <title> Automation Modes </title>
42 Each parameter that can be automated has a button available to control its
43 state of automation. Each button can be used to put the parameter into one
44 of 4 possible automation states:
53 No changes to the parameter are recorded, and any existing automation
54 for the parameter is ignored. This is the default.
63 Existing automation data controls the value of the parameter, and
64 graphical/hardware editing of the value is disabled.
73 All changes to the parameter are recorded as new automation data,
74 overwriting any existing data for that point in time.
83 Existing automation data controls the value of the parameter, but new
84 changes to the parameter are recorded, overwriting any existing data for
92 <section id="basic-automation-recording">
93 <title> Basic Automation Recording </title>
94 <section id="automation-recording-gain-and-pan">
95 <title> Gain and Pan </title>
97 Each track/bus has two automation control buttons for gain and pan in its
98 mixer strip. For each track/bus that you wish to automate, click on the
99 relevant automation button. From the popup menu that appears (showing all
100 automation states) choose <guibutton>Record</guibutton> . As long as the
101 automation state remains in "Record", then any changes you make to gain or
102 pan for that track/bus will be recorded.
106 <section id="automation-recording-plugin-parameters">
107 <title> Plugin Parameters </title>
109 Many plugins have many parameters that you might wish to play while
110 recording gain automation, so Ardour offers independent control of
111 recording changes to these parameters. You can access the controls in
118 open the plugin's editor window, and click on the appropriate automation
119 control button. From the menu that pops up, choose
120 <guibutton>Record</guibutton>
125 make the automation track for this parameter visible (see
126 plugin_automation_tracks on how to do this), and click on the automation
127 control button in the track controls. From the menu that pops up, choose
128 <guibutton>Record</guibutton> .
134 To record edits to the parameter, click on the appropriate
135 <guibutton>arec</guibutton> button. As long as the button stays pressed,
136 all edits to that parameter will be recorded.
141 <section id="basic-automation-playback">
142 <title> Basic Automation Playback </title>
143 <section id="automation-playback-gain-and-pan">
144 <title> Gain and Pan </title>
146 Each track/bus has two automation control buttons for gain and pan in its
147 mixer strip. For each track/bus where you want existing automation data to
148 control gain and/or panning, click on the relevant automation button. From
149 the popup menu that appears (showing all automation states) choose
150 <guimenuitem>Play</guimenuitem>. As long as the automation state remains in
151 <guimenuitem>Play</guimenuitem>, you can no longer control the gain and/or panning from the
152 graphical user interface or an external hardware control surface.
156 <section id="automation-playback-plugin-parameters">
157 <title> Plugin Parameters </title>
159 For each plugin parameter you want controlled by automation data, you need
160 to activate automation playback which can be done in one of two ways:
166 open the plugin's editor window, and click on the appropriate automation
167 control button, and choose <guimenuitem>Play</guimenuitem> from the menu
173 make the automation track for this parameter visible (see
174 plugin_automation_tracks on how to do this), and click on the automation
175 control button in the track controls. Choose <guimenuitem>Play</guimenuitem>
176 from the menu that pops up.
182 You also need to enable automation playback for the plugin itself. This
183 needs to be done in the plugin's editor window by clicking on the
184 automation button in the upper right corner. Without this step, the
185 individual parameter buttons will not enable automation playback.
189 The plugin automation button also allows you to globally disable
190 automation control of all parameters by unsetting it (clicking it so that
191 it is no longer "pressed"). This leaves the individual automation control
192 buttons in whatever state they were already in, but it stops the use of
193 automation data for all parameters. This can be useful if you have a
194 hardware control surface, and have automation-playback-enabled several
195 parameters. You can override the automation playback settings and manually
196 control parameter values from the control surface without having to click
197 on each parameter's automation control button individually.
202 <section id="editing-automation-data">
203 <title> Editing Automation Data </title>
205 The editor window can display all automation data for a track. Each type of
206 automation data is shown in its own "track" to make it easy to see the
207 data, and to edit it.
211 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
212 href="Some_Subsection.xml" />