<scripttype=text/javascript>varbaseurl="https://prokoudine.github.io/ardour-tutorial/en"</script><scripttype=text/javascriptsrc=/ardour-tutorial/js/search.js?1650973131></script></div><sectionid=homelinks><ul><li><aclass=paddinghref=/ardour-tutorial/en/><iclass="fas fa-home"></i> Home</a></li></ul></section><divclass=highlightable><ulclass=topics><lidata-nav-id=/ardour-tutorial/en/introduction/title=Introductionclass=dd-item><ahref=/ardour-tutorial/en/introduction/><b>1. </b>Introduction</a><ul><lidata-nav-id=/ardour-tutorial/en/introduction/conventions/title=Conventionsclass=dd-item><ahref=/ardour-tutorial/en/introduction/conventions/>Conventions</a></li><lidata-nav-id=/ardour-tutorial/en/introduction/what-is-digital-audio/title="What is digital audio?"class=dd-item><ahref=/ardour-tutorial/en/introduction/what-is-digital-audio/>What is digital audio?</a></li></ul></li><lidata-nav-id=/ardour-tutorial/en/getting-started/title="Getting started"class=dd-item><ahref=/ardour-tutorial/en/getting-started/><b>2. </b>Getting started</a><ul><lidata-nav-id=/ardour-tutorial/en/getting-started/starting-ardour-on-ubuntu/title="Starting Ardour"class=dd-item><ahref=/ardour-tutorial/en/getting-started/starting-ardour-on-ubuntu/>Starting Ardour</a></li><lidata-nav-id=/ardour-tutorial/en/getting-started/overview-of-the-interface/title="Overview of the Interface"class=dd-item><ahref=/ardour-tutorial/en/getting-started/overview-of-the-interface/>Overview of the Interface</a><ul><lidata-nav-id=/ardour-tutorial/en/getting-started/overview-of-the-interface/editor-window/title="Editor window"class=dd-item><ahref=/ardour-tutorial/en/getting-started/overview-of-the-interface/editor-window/>Editor window</a></li><lidata-nav-id=/ardour-tutorial/en/getting-started/overview-of-the-interface/mixer-window/title="Mixer window"class=dd-item><ahref=/ardour-tutorial/en/getting-started/overview-of-the-interface/mixer-window/>Mixer window</a></li><lidata-nav-id=/ardour-tutorial/en/getting-started/overview-of-the-interface/recorder-window/title="Recorder window"class=dd-item><ahref=/ardour-tutorial/en/getting-started/overview-of-the-interface/recorder-window/>Recorder window</a></li><lidata-nav-id=/ardour-tutorial/en/getting-started/overview-of-the-interface/cue-window/title="Cue window"class=dd-item><ahref=/ardour-tutorial/en/getting-started/overview-of-the-interface/cue-window/>Cue window</a></li></ul></li><lidata-nav-id=/ardour-tutorial/en/getting-started/creating-tracks-and-busses/title="Creating tracks and busses"class=dd-item><ahref=/ardour-tutorial/en/getting-started/creating-tracks-and-busses/>Creating tracks and busses</a></li><lidata-nav-id=/ardour-tutorial/en/getting-started/importing-audio/title="Importing audio"class=dd-item><ahref=/ardour-tutorial/en/getting-started/importing-audio/>Importing audio</a></li><lidata-nav-id=/ardour-tutorial/en/getting-started/setting-up-the-timeline/title="Setting up the timeline"class=dd-item><ahref=/ardour-tutorial/en/getting-started/setting-up-the-timeline/>Setting up the timeline</a></li></ul></li><lidata-nav-id=/ardour-tutorial/en/recording-audio/title=Recordingclass=dd-item><ahref=/ardour-tutorial/en/recording-audio/><b>3. </b>Recording</a><ul><lidata-nav-id=/ardour-tutorial/en/recording-audio/recording-audio/title="Recording audio"class=dd-item><ahref=/ardour-tutorial/en/recording-audio/recording-audio/>Recording audio</a></li><lidata-nav-id=/ardour-tutorial/en/recording-audio/understanding-routing/title="Understanding routing"class=dd-item><ahref=/ardour-tutorial/en/recording-audio/understanding-routing/>Understanding routing</a></li><lidata-nav-id=/ardour-tutorial/en/recording-audio/routing-between-applications/title="Routing between applications"class=dd-item><ahref=/ardour-tutorial/en/recording-audio/routing-between-applications/>Routing between applications</a></li></ul></li><lidata-nav-id=/ardour-tutorial/en/editing-sessions/title="Editing sessions"class=dd-item><ahref=/ardour-tutorial/en/editing-sessions/><b>4. </b>Editi
<spanclass=links><ahref=/ardour-tutorial/en/>Home</a> > <ahref=/ardour-tutorial/en/mixing-sessions/>Mixing sessions</a> > Using automation</span></div><divclass=progress><divclass=wrapper><navid=TableOfContents><ul><li><ahref=#creating-a-fader-automation-line>Creating a Fader Automation Line</a><ul><li><ahref=#automation-states>Automation States</a></li></ul></li><li><ahref=#creating-a-plugin-for-automation>Creating a Plugin for Automation</a></li><li><ahref=#adding-better-visual-resolution-to-automation>Adding Better Visual Resolution to Automation</a></li><li><ahref=#working-with-automation-points>Working with Automation Points</a></li><li><ahref=#moving-automation>Moving Automation</a></li><li><ahref=#region-specific-gain-automation>Region-specific Gain Automation</a><ul><li><ahref=#deactivating-and-removing-gain-automation>Deactivating and Removing Gain Automation</a></li><li><ahref=#when-should-i-use-region-gain-automation-or-track-fader-automation>When should I use region Gain Automation or Track Fader Automation?</a></li></ul></li><li><ahref=#continuing>Continuing</a></li></ul></nav></div></div></div></div><divid=head-tags></div><divid=body-inner><h1>Using automation</h1><p><em>Automation</em> is a way of dynamically changing audio processing parameters over
time.</p><p>Up to now, we have used fixed values for various parameters of our tracks, for
example, a track fader set to -3.0dB; or a mono panner set to 100% left. These
fixed values would apply for the entire track throughout the whole session.</p><p>But what if you would like these values to change over time in a
pre-determined way? For example, you may want to have the gain of a track to
gradually decrease over twenty seconds. Or you may want to make a sound move
from left to right over two seconds.</p><p>This is accomplished with automation. The fader, panning, and any of the
parameters of the plugins used in that track can be automated. An automated
parameter is displayed underneath the parent track in its own <em>automation
track</em>. Automation data is visually represented as an <em>automation line</em>, made
up of a number of <em>automation points</em>. Here’s how a track with automation
looks like:</p><figure><imgsrc=en/Ardour4_Automation_Fader_1.pngalt="Typical automation lane"></figure><p>In the image above, the automation lane called <em>Fader</em> is associated to the
parent track called <em>Audio 1</em>. The automation line controls fader (volume)
changes over time.</p><h2id=creating-a-fader-automation-line>Creating a Fader Automation Line</h2><p>Let’s create a simple fader automation. Click the <strong>A</strong> button of a chosen
track. A menu will appear, where you can select the parameter you would like to
automate. Choose <em>Fader</em>.</p><figure><imgsrc=en/Ardour4_Automation_Button.pngalt="Choose Fader"></figure><p>An automation lane will then appear. Select the <em>Draw</em> mode (<strong>D</strong> shortcut):</p><figure><imgsrc=en/Ardour4_EditModes_D.pngalt="Draw mode"></figure><p>Now you can create automation points by clicking anywhere in the automation
automation point.</p><figure><imgsrc=en/Ardour4_Automation_Fader_2.pngalt="Automation point value indication"></figure><h3id=automation-states>Automation States</h3><p>The automation curve will not play, however, until you set the automation state
to <em>Play</em>.</p><figure><imgsrc=en/Ardour4_Automation_Fader_3.pngalt="automation state"></figure><dl><dt><strong>Manual</strong></dt><dd>When set to <em>Manual</em>, the track will ignore any automation data. It will just
play with whatever volume is the fader is set to. In this mode, you are able to
move the track fader by hand to set a new fixed level. That’s the default
behavior of a track when it’s first created.</dd><dt><strong>Play</strong></dt><dd>When set to <em>Play</em>, the track will automatically change the gain levels
following the automation curve drawn in the automation lane. You will no longer
be able to move the track fader by hand. During playback, you will see the track
fader moving up and down according to the curve.</dd><dt><strong>Write</strong></dt><dd>This mode will continuously record user changes to the automated parameter as
the transport plays, creating an automation line. For instance, you may start
playback and then make real-time changes in gain using the fader of your track.
All the changes you make will be written (recorded) as an automation line, which
then you can play back later by switching the automation mode back to <em>Play</em>.</dd><dt><strong>Touch</strong></dt><dd>This mode is similar to the <em>Write</em> mode but it won’t record over existing
automation data unless the parameter is being changed.</dd></dl><p>If these concepts are new to you, focus now on just the first two modes
(<em>Manual</em> and <em>Play</em>) and practice creating automation by drawing automation
curves by hand.</p><h2id=creating-a-plugin-for-automation>Creating a Plugin for Automation</h2><p>You may add automation to any plugin which has already been added to a track. In
the example below, we have the <em>AM pitchshifter</em> plugin added to a track.</p><figure><imgsrc=en/Ardour4_Automation_Plugin1.pngalt=pluginautomation1></figure><p>In order to select a plugin parameter for automation, click the button on the
find a listing of the plugins you have added for that track.</p><figure><imgsrc=en/Ardour4_Automation_Plugin2.pngalt=pluginautomation2></figure><p>Within each listed plugin, you may choose which parameter you want to automate
state to <em>Play</em>.</p><figure><imgsrc=en/Ardour4_Automation_Plugin3.pngalt=pluginautomation3></figure><p>In the image above, the pitch shift of the sound is now changing over time,
controlled by the curve.</p><divclass="notices tip"><p>You can hide an automation lane by clicking on the “X” at the upper left corner
of the automation lane. Note that a hidden automation lane continues to function
even when it is not visible.</p></div><h2id=adding-better-visual-resolution-to-automation>Adding Better Visual Resolution to Automation</h2><p>You can achieve a greater amount of vertical precision by increasing the height
of the automation lane. Move your cursor near the lower edge of the automation
track. The pointer turns into a vertical double arrow. Drag it down to increase
the height of the automation lane. Notice that the parent track and the
automation lane heights are independent, so while working in your automation
curves you might set them up like this:</p><figure><imgsrc=en/Ardour4_Automation_Plugin4.pngalt=pluginautomation5></figure><divclass="notices tip"><p>Remember that you can also zoom in and out to increase resolution in the
horizontal axis.</p></div><h2id=working-with-automation-points>Working with Automation Points</h2><p>There are several ways to adjust automation points, depending on the editing
mode you are in:</p><ul><li>An automation point can be dragged in any direction with the mouse (works in
<em>Grab</em>, <em>Draw</em>, and <em>Edit</em> modes).</li><li>To remove an automation point, hold down the <strong>Shift</strong> key while
right-clicking on it (works in <em>Grab</em>, <em>Draw</em>, and <em>Edit</em> modes).</li><li><em>Edit</em> mode only: any segment of the automation line between automation points
may be dragged vertically, affecting both end points at once, without affecting
their horizontal position. Simply click somewhere on the line between two
points, and drag up and down.</li><li>How to delete multiple automation points at once (<em>Grab</em> mode and <em>Edit</em> mode
only): select multiple automation points by dragging a box starting on the track
background around the points. Then the selected points may be deleted by hitting
<strong>Delete</strong> (<em>not</em><strong>Backspace</strong>). If you are on a Mac and do not have a true
<strong>Delete</strong> key, try <strong>Function + Backspace</strong>.</li></ul><p>After an automation curve ends, its value will stay at that level for all
subsequent regions, whether or not you have drawn a continuation of the curve.</p><figure><imgsrc=en/Ardour4_Automation_Fader_End.pngalt="end point"></figure><p>In the example above, the last point of the curve is at -23dB. That same level
that might be aligned with it, as we can see in the following screen shots.</p><p>Before moving:</p><figure><imgsrc=en/Ardour4_Automation_Moving_1.pngalt=mv1></figure><p>After moving:</p><figure><imgsrc=en/Ardour4_Automation_Moving_2.pngalt=mv2></figure><p>You can change this behavior if you like. In other words, if you want automation
curves to stay where they are even when you move regions around, go to <code>Edit > Preferences > Editor</code> and uncheck <em>Move relevant automation when audio regions
are moved</em>.</p><h2id=region-specific-gain-automation>Region-specific Gain Automation</h2><p>There is a way to create a gain automation directly bound to a region. When you
select the <em>Draw</em> mode, you should see a flat line on the top half of each
region rectangle:</p><figure><imgsrc=en/Ardour4_Automation_Region_Specific_1.pngalt=gain-automation></figure><p>Click directly on that line to create automation points. These will be drawn
in addition to, fader automation.</p><figure><imgsrc=en/Ardour4_Automation_Region_Specific_2.pngalt=gain-automation2></figure><p>As with the automation lanes, a <em>gain automation point</em> can be dragged in any
direction with the mouse. To remove a gain automation point, hold down the
<strong>Shift</strong> key while right-clicking on it.</p><h3id=deactivating-and-removing-gain-automation>Deactivating and Removing Gain Automation</h3><p>Gain automation can be reset or deactivated from the region context menu, which
is reached by right-clicking on the region.</p><figure><imgsrc=en/Ardour4_Automation_Gain_Tool_Reset.pngalt=gain-automation3></figure><p>Here, the gain automation is referred to as the <em>envelope</em>:</p><ul><li><em>Reset Envelope</em> removes the gain automation points you have drawn in the
region.</li><li><em>Envelope Active</em> toggles the gain automation envelope on and off.</li></ul><h3id=when-should-i-use-region-gain-automation-or-track-fader-automation>When should I use region Gain Automation or Track Fader Automation?</h3><p>As seen above, both are very similar. With practice you will notice situations
in which one is more convenient than the other. Here are two examples:</p><ul><li>If all you need to do is a little touch up (cut or boost gain) in a specific
portion of a region, and you are otherwise happy with the level for the rest of
the passage or entire track, use the region-specific automation.</li></ul><figure><imgsrc=en/Ardour4_Automation_Region_Specific_2.pngalt=gain-example1></figure><ul><li>If you have a more complex track with crossfades over regions, and/or need to
automation.</li></ul><figure><imgsrc=en/Ardour4_Automation_Gain_Comparison.pngalt=gain-automation2></figure><p>The screenshot above shows a simple gradual fade starting from the first region
