Added chapter on track automation.
This commit is contained in:
Shamus Hammons
parent
68df18aa44
commit
389c23a3b5
3
build.py
3
build.py
@ -259,7 +259,8 @@ def BuildList(lst, fs, pagePos, cList):
|
|||||||
nextPos = lst[i + 1] if i + 1 < len(lst) else len(fs)
|
nextPos = lst[i + 1] if i + 1 < len(lst) else len(fs)
|
||||||
|
|
||||||
active = ' class=active' if curPos == pagePos else ''
|
active = ' class=active' if curPos == pagePos else ''
|
||||||
content = content + '<dt' + active + '><a href="/' + fs[curPos]['filename'] + '/">' + fs[curPos]['title'] + '</a></dt><dd' + active + '>'
|
menuTitle = fs[curPos]['menu_title'] if 'menu_title' in fs[curPos] else fs[curPos]['title']
|
||||||
|
content = content + '<dt' + active + '><a href="/' + fs[curPos]['filename'] + '/">' + menuTitle + '</a></dt><dd' + active + '>'
|
||||||
|
|
||||||
# If the current page is our page, and it has children, enumerate them
|
# If the current page is our page, and it has children, enumerate them
|
||||||
if curPos == pagePos:
|
if curPos == pagePos:
|
||||||
|
|||||||
@ -111,9 +111,6 @@ for line in master:
|
|||||||
if 'menu_title' in header:
|
if 'menu_title' in header:
|
||||||
explode.write('menu_title: ' + header['menu_title'] + '\n')
|
explode.write('menu_title: ' + header['menu_title'] + '\n')
|
||||||
|
|
||||||
if 'link' in header:
|
|
||||||
explode.write('link: ' + header['link'] + '\n')
|
|
||||||
|
|
||||||
if 'style' in header:
|
if 'style' in header:
|
||||||
explode.write('style: ' + header['style'] + '\n')
|
explode.write('style: ' + header['style'] + '\n')
|
||||||
|
|
||||||
@ -126,6 +123,9 @@ for line in master:
|
|||||||
explode.write('include: ' + inclFile + '\n')
|
explode.write('include: ' + inclFile + '\n')
|
||||||
filenames.append(inclFile)
|
filenames.append(inclFile)
|
||||||
|
|
||||||
|
if 'link' in header:
|
||||||
|
explode.write('link: ' + header['link'] + '\n')
|
||||||
|
|
||||||
if 'uri' in header:
|
if 'uri' in header:
|
||||||
explode.write('uri: ' + header['uri'] + '\n')
|
explode.write('uri: ' + header['uri'] + '\n')
|
||||||
|
|
||||||
|
|||||||
@ -91,9 +91,6 @@ for line in master:
|
|||||||
if 'menu_title' in header:
|
if 'menu_title' in header:
|
||||||
implode.write('menu_title: ' + header['menu_title'] + '\n')
|
implode.write('menu_title: ' + header['menu_title'] + '\n')
|
||||||
|
|
||||||
if 'link' in header:
|
|
||||||
implode.write('link: ' + header['link'] + '\n')
|
|
||||||
|
|
||||||
if 'style' in header:
|
if 'style' in header:
|
||||||
implode.write('style: ' + header['style'] + '\n')
|
implode.write('style: ' + header['style'] + '\n')
|
||||||
|
|
||||||
@ -104,6 +101,9 @@ for line in master:
|
|||||||
implode.write('include: ' + header['include'] + '\n')
|
implode.write('include: ' + header['include'] + '\n')
|
||||||
implode.write('exclude: yes\n')
|
implode.write('exclude: yes\n')
|
||||||
|
|
||||||
|
if 'link' in header:
|
||||||
|
implode.write('link: ' + header['link'] + '\n')
|
||||||
|
|
||||||
if 'uri' in header:
|
if 'uri' in header:
|
||||||
implode.write('uri: ' + header['uri'] + '\n')
|
implode.write('uri: ' + header['uri'] + '\n')
|
||||||
|
|
||||||
|
|||||||
@ -132,3 +132,4 @@
|
|||||||
Hairy issues that might cause things to go wrong, lose data, impair sound
|
Hairy issues that might cause things to go wrong, lose data, impair sound
|
||||||
quality, or eat your proverbial goldfish, are displayed in this way.
|
quality, or eat your proverbial goldfish, are displayed in this way.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
|||||||
18
include/automation-curves.html
Normal file
18
include/automation-curves.html
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
|
||||||
|
<figure class=right>
|
||||||
|
<img src="/images/automation-curve1.png">
|
||||||
|
<figcaption class=center>A typical automation curve.</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
An <dfn>automation curve</dfn> is a series of lines connected by <dfn>control
|
||||||
|
points</dfn> that defines a continuous line. As the curve is traversed from
|
||||||
|
left to right, the line defines the level of the parameter controlled by the
|
||||||
|
automation lane.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
The curve by itself does nothing; it will <em>only</em> control playback if
|
||||||
|
the lane it is in is in <kbd class=menu>Play</kbd> mode.
|
||||||
|
</p>
|
||||||
|
|
||||||
53
include/automation-lanes.html
Normal file
53
include/automation-lanes.html
Normal file
@ -0,0 +1,53 @@
|
|||||||
|
|
||||||
|
<figure class=right>
|
||||||
|
<img src="/images/automation-lane1.png">
|
||||||
|
<figcaption class=center>A typical automation lane.</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
An <dfn>automation lane</dfn> is similar to a track in that it holds data
|
||||||
|
that can be played back; however, unlike a track, it is not an independent
|
||||||
|
entity—it is always attached to the track that it controls. Automation
|
||||||
|
lanes also contain zero to one <dfn>automation curves</dfn>. Each lane
|
||||||
|
controls one and only one parameter of the track it is attached to.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
Every track will have at least five automation lanes associated with it:
|
||||||
|
trim, fader, mute, and pan (which consists of two lanes: L/R and Width); it
|
||||||
|
can possibly have many more if there are any processors associated with it.
|
||||||
|
All these lanes are automatically attached to the track but hidden, and
|
||||||
|
initially they are all empty (have no automation curves in them).
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<figure class=center>
|
||||||
|
<img src="/images/automation-multi-lane1.png">
|
||||||
|
<figcaption class=center>An example of a track with three lanes of automation (fader & pan).</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
Automation lanes typically have the following controls:
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>A hide button (square button with an "X" inside)</li>
|
||||||
|
<li>A horizontal fader</li>
|
||||||
|
<li>An <dfn>automation mode</dfn> selector</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
The hide button, as the name implies, hides the automation lane. The
|
||||||
|
horizontal fader controls the level of the parameter that the lane controls;
|
||||||
|
manipulating this while in <kbd class=menu>Write</kbd> or <kbd
|
||||||
|
class=menu>Touch</kbd> mode during playback will make changes to the lane's
|
||||||
|
automation curve. The automation mode selector selects which mode the lane is
|
||||||
|
in (<kbd class=menu>Manual</kbd>, <kbd class=menu>Play</kbd>, <kbd
|
||||||
|
class=menu>Write</kbd>, or <kbd class=menu>Touch</kbd>).
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p class=note>
|
||||||
|
The hide button will only hide the lane; it does not remove it from the
|
||||||
|
track. The automation lane never really goes away—the closest one can
|
||||||
|
get to that is to clear the automation curve and hide the lane.
|
||||||
|
</p>
|
||||||
|
|
||||||
49
include/automation-modes.html
Normal file
49
include/automation-modes.html
Normal file
@ -0,0 +1,49 @@
|
|||||||
|
|
||||||
|
<p>
|
||||||
|
In order to understand how automation in Ardour works, it is necessary to
|
||||||
|
understand the four modes of automation. They are: <kbd
|
||||||
|
class=menu>Manual</kbd>, <kbd class=menu>Play</kbd>, <kbd
|
||||||
|
class=menu>Write</kbd>, and <kbd class=menu>Touch</kbd>.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<figure class=right>
|
||||||
|
<img src="/images/automation-modes1.png">
|
||||||
|
<figcaption class=center>The automation mode menu.</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<kbd class=menu>Manual</kbd> mode is basically analogous to a processor's
|
||||||
|
bypass switch. Whenever an automation lane is in this mode, it is inactive
|
||||||
|
and any level that is manually set for controlling the lane's parameter will
|
||||||
|
persist during playback like normal.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p class=note>
|
||||||
|
In Ardour, every track and processor parameter is initially set to <kbd
|
||||||
|
class=menu>Manual</kbd> mode.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<kbd class=menu>Play</kbd> mode tells Ardour to use the automation curve in
|
||||||
|
the automation lane to control the level of the parameter controlled by the
|
||||||
|
lane <em>during playback</em>. The control that normally sets the parameter
|
||||||
|
will be <em>unresponsive to manual input</em> and will move automatically in
|
||||||
|
accord with the lane's automation curve during playback.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<kbd class=menu>Write</kbd> mode allows continuous, dynamic setting of a
|
||||||
|
control during playback; all such settings are written to the lane the
|
||||||
|
control is in. This defines the lane's automation curve in the interval being
|
||||||
|
played, and overwrites any existing automation curve in the lane being
|
||||||
|
manipulated.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<kbd class=menu>Touch</kbd> mode is similar to <kbd class=menu>Write</kbd>
|
||||||
|
mode, except it only overwrites sections of a lane's automation curve when
|
||||||
|
the control is changed in some way. This allows for changing only the parts
|
||||||
|
of an automation curve that are desired to be changed, while leaving the rest
|
||||||
|
unchanged.
|
||||||
|
</p>
|
||||||
|
|
||||||
17
include/automation-nomenclature.html
Normal file
17
include/automation-nomenclature.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
|
||||||
|
<figure class=right>
|
||||||
|
<img src="/images/automation-fader1.png">
|
||||||
|
<figcaption class=center>An example of a fader automation lane (below) with its associated track (above).</figcaption>
|
||||||
|
</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,
|
||||||
|
trim, etc. <dfn>Automation curves</dfn> consist of lines connected by
|
||||||
|
<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
|
||||||
|
modes</dfn> govern how a given automation lane will behave during playback.
|
||||||
|
</p>
|
||||||
|
|
||||||
@ -1,220 +1,22 @@
|
|||||||
|
|
||||||
<p class="fixme">This section requires some significant rework to fit as manaul content.</p>
|
|
||||||
|
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<strong>Automation</strong> is a way of dynamically changing audio processing parameters over time.
|
<dfn>Automation</dfn> is the ability to dynamically control various aspects
|
||||||
</p>
|
of a track's innate attributes and the attributes of any processors attached
|
||||||
|
to it. In Ardour, automation can be used to make dynamic changes to a
|
||||||
<p>
|
track's:
|
||||||
Up to now, we have used fixed values for various parameters of our Tracks (for example, a Track Fader set to -3.0 dB; or a Mono Panner set to 100% Left; etc.) 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 <strong>Automation</strong>. 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 <strong>Automation Track</strong>. Automation data is visually represented as an <strong>Automation Line</strong>, made up of a number of <strong>Automation Points</strong>. Here’s how a track with Automation looks like:
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Fader_1.png" alt="automation1"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
In the image above, the Automation Track 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>
|
|
||||||
|
|
||||||
<h2>Creating a Fader Automation Line</h2>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Let’s create a simple Fader Automation. Click the “<em>A</em>” 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>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Button.png" alt="automation2"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
An Automation Track will then appear. Select the Draw Mode (shortcut “<em>D</em>”):
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_EditModes_D.png" alt="automation3"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Now you can create Automation Points by clicking anywhere in the Automation Track. An Automation Line joins the Automation Points you add. The yellow number (-15.3 decibels in the image below) indicates the Gain level for the selected Automation Point.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Fader_2.png" alt="automation3"></p>
|
|
||||||
|
|
||||||
<h3>Automation States</h3>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
The Automation Curve will not play, however, until you set the Automation State to “<em>Play</em>”.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Fader_3.png" alt="automation state"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
<strong>Manual</strong>: 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.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
<strong>Play</strong>: When set to “<em>Play</em>”, the Track will automatically change the Gain levels following the Automation Curve drawn in the Automation Track. 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.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
<strong>Write</strong> 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 Play
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
<strong>Touch</strong> mode is similar to Write mode. Unlike Write mode though, Touch mode won’t record over existing Automation data unless the parameter is being changed.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<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>
|
|
||||||
|
|
||||||
<h2>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 a “<strong>AM pitchshifter</strong>” Plugin added to a track.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Plugin1.png" alt="pluginautomation1"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
In order to select a Plugin parameter for Automation, click the button on the Track marked “<em>a</em>”. The menu will appear. Under “<em>Processor Automation</em>” you will find a listing of the Plugins you have added for that Track.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Plugin2.png" alt="pluginautomation2"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Within each listed Plugin, you may choose which parameter you want to Automate from a list. In the example, we chose the parameter “<em>Pitch shift</em>” of the Plugin “<em>AM pitchshifter</em>”. An Automation Track for that parameter appears. Note that as you open several Automation Tracks, they will appear one after the other below the main parent Track.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Draw an automation curve for that parameter. Don’t forget to set the Automation State to “<em>Play</em>”.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Plugin3.png" alt="pluginautomation3"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
In the image above, the pitch shift of the sound is now changing over time, controlled by the curve.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<blockquote>
|
|
||||||
<p>TIP: You can hide an Automation Track by clicking on the “X” at the upper
|
|
||||||
left corner of the Automation Track. Note that a hidden Automation Track
|
|
||||||
continues to function even when it is not visible.</p>
|
|
||||||
</blockquote>
|
|
||||||
|
|
||||||
<h2>Adding Better Visual Resolution to Automation</h2>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
You can achieve a greater amount of vertical precision by increasing the height of the Automation Track. 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 Track. Notice that the parent Track and the Automation Track heights are independent, so while working in your Automation Curves you might set them up like this:
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Plugin4.png" alt="pluginautomation5"></p>
|
|
||||||
|
|
||||||
<blockquote>
|
|
||||||
<p>TIP: Remember you can also Zoom In and Out to increase resolution in the horizontal axis.</p>
|
|
||||||
</blockquote>
|
|
||||||
|
|
||||||
<h2>Working with Automation Points</h2>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
There are several ways ways of adjusting Automation Points, depending on the editing mode you are in:
|
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>An Automation Point can be dragged in any direction with the mouse (works in Grab, Draw, and Edit modes).</li>
|
<li>Volume</li>
|
||||||
<li>To remove an Automation Point, hold down the “<em>Shift</em>” key while Right-Clicking on it (works in Grab, Draw, and Edit modes).</li>
|
<li>Panning</li>
|
||||||
<li>“<em>Control</em>” + <em>click</em> + <em>drag</em> moves the current point in any direction, and also all subsequent points horizontally only (works in Grab, Draw, and Edit modes).</li>
|
<li>Trim</li>
|
||||||
<li>Edit 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>Muting</li>
|
||||||
<li>How to delete multiple Automation Points at once (Grab Mode and Edit 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 “<em>Delete</em>” (<em>not</em> “<em>Backspace</em>”). If you are on a Mac and do not have a true “<em>Delete</em>” key, try “<em>Function</em>” + “<em>Backspace</em>”).</li>
|
<li>Any attached processor's parameters</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<p>
|
<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.
|
Any combination of these can be enabled on a single track; as such, it offers
|
||||||
</p>
|
a lot of power and flexibility over how a track will ultimately sound when
|
||||||
|
played back.
|
||||||
<p><img src="/images/Ardour4_Automation_Fader_End.png" alt="end point"></p>
|
|
||||||
|
|
||||||
<p>In the example above, the last point of the curve is at -23 decibels.
|
|
||||||
That same level will be kept for the remainder of the Track, even
|
|
||||||
though the line is not drawn until the end.</p>
|
|
||||||
|
|
||||||
<h2>Moving Automation</h2>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Moving a Region to a new location will automatically move the Automation data that might be aligned with it, as we can see in the following screen shots.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>Before moving:
|
|
||||||
<img src="/images/Ardour4_Automation_Moving_1.png" alt="mv1"></p>
|
|
||||||
|
|
||||||
<p>After moving:
|
|
||||||
<img src="/images/Ardour4_Automation_Moving_2.png" alt="mv2"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
You can change this behaviour if you like. In other words, if you want automation curves to <em>stay where they are</em> even when you move Regions around, go to Edit > Preferences > Editor and uncheck “Move relevant automation when audio regions are moved.”
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<h2>Region-specific Gain Automation</h2>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
There is a way to create a gain automation directly bound to a Region. When you select Draw Mode, you should see a flat line on the top half of each Region rectangle:
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Region_Specific_1.png" alt="gain-automation"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Click directly on that line to create Automation points. These will be drawn directly on the Region itself, unlike Fader Automation which is drawn or recorded in the Automation track. Region Gain Automation is separate from, and in addition to, Fader Automation.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Region_Specific_2.png" alt="gain-automation2"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
As with the Automation Tracks, a <strong>Gain Automation Point</strong> can be dragged in any direction with the mouse. To remove a Gain Automation Point, hold down the “<em>Shift</em>” key while Right-Clicking on it.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<h3>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>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Gain_Tool_Reset.png" alt="gain-automation3"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
Here, the Gain Automation is referred to as the <strong>Envelope</strong>.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
“<em>Reset Envelope</em>” removes the Gain Automation Points you have drawn in the Region.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
“<em>Envelope Active</em>” toggles the Gain Automation Envelope on and off.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<h3>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>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Region_Specific_2.png" alt="gain-example1"></p>
|
|
||||||
|
|
||||||
<ul>
|
|
||||||
<li>If you have a more complex Track with crossfades over Regions, and/or need to shape a longer dynamic curve across several Regions on the same Track, use Fader Automation.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p><img src="/images/Ardour4_Automation_Gain_Comparison.png" alt="gain-automation2"></p>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
The screenshot above shows a simple gradual fade starting from the first Region in the track, and ending at the last Region. It’s very straightforward to do this with Fader Automation, but but it would be much harder to do it using region-specific automation.
|
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
|||||||
@ -5,17 +5,30 @@
|
|||||||
</figure>
|
</figure>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
In Ardour, every <dfn>region</dfn> has a <dfn>gain envelope</dfn>, which is normally hidden. Clicking on the Draw tool will cause all the gain envelopes on all regions to show themselves; these will appear as green lines with square dots (<dfn>control points</dfn>) at the beginning and end of each region. The vertical axis represents gain, with the top of the region representing +6dB and the bottom representing approximately -170dB. By default, the line starts and ends at 0dB; the control points can be moved up and down to change the amount of gain at that point.
|
In Ardour, every <dfn>region</dfn> has a <dfn>gain envelope</dfn>, which is
|
||||||
|
normally hidden. Clicking on the Draw tool will cause all the gain envelopes
|
||||||
|
on all regions to show themselves; these will appear as green lines with
|
||||||
|
square dots (<dfn>control points</dfn>) at the beginning and end of each
|
||||||
|
region. The vertical axis represents gain, with the top of the region
|
||||||
|
representing +6dB and the bottom representing approximately -170dB. By
|
||||||
|
default, the line starts and ends at 0dB; the control points can be moved up
|
||||||
|
and down to change the amount of gain at that point.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
Gain follows the line between control points continuously during playback, and adjusts the gain for that region accordingly. It is completely automatic, unlike channel <a href="@@automation">automation</a>.
|
Gain follows the line between control points continuously during playback,
|
||||||
|
and adjusts the gain for that region accordingly. It is completely automatic,
|
||||||
|
unlike channel <a href="@@automation">automation</a>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h2 style="clear: both">Manipulating Gain Envelopes</h2>
|
<h2 style="clear: both">Manipulating Gain Envelopes</h2>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
The default gain curve, by itself, is not very useful; in order to have more control over the shape of the gain envelope it is necessary to add extra control points. To add a control point to the envelope, click anywhere in the region where there are no existing control points; it will appear <em>on the line</em> at the X-axis of the mouse's current position in the region.
|
The default gain curve, by itself, is not very useful; in order to have more
|
||||||
|
control over the shape of the gain envelope it is necessary to add extra
|
||||||
|
control points. To add a control point to the envelope, click anywhere in the
|
||||||
|
region where there are no existing control points; it will appear <em>on the
|
||||||
|
line</em> at the X-axis of the mouse's current position in the region.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<figure class=center>
|
<figure class=center>
|
||||||
@ -24,5 +37,10 @@
|
|||||||
</figure>
|
</figure>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
Once added, a control point can be <kbd class=mouse>Left</kbd> clicked and dragged to the desired location. Hovering over a control point will show its current level in dB. To remove a control point, <kbd class=mouse>Left</kbd> click it and press <kbd>Delete</kbd>.
|
Once added, a control point can be <kbd class=mouse>Left</kbd> clicked and
|
||||||
|
dragged to the desired location. Hovering over a control point will show its
|
||||||
|
current level in dB. To remove a control point, <kbd class=mouse>Left</kbd>
|
||||||
|
click it and press <kbd>Delete</kbd>, or <kbd class=mod3n></kbd><kbd
|
||||||
|
class=mouse>Right</kbd>-click on it.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
|||||||
@ -1,6 +1,7 @@
|
|||||||
|
|
||||||
<figure class=right>
|
<figure class=right>
|
||||||
<img src="/images/processor-box.png" alt="the Processor Box" />
|
<img src="/images/processor-box.png" alt="the Processor Box" />
|
||||||
|
<figcaption class=center>Processor Box.</figcaption>
|
||||||
</figure>
|
</figure>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|||||||
83
include/track-automation.html
Normal file
83
include/track-automation.html
Normal file
@ -0,0 +1,83 @@
|
|||||||
|
|
||||||
|
<figure class=right>
|
||||||
|
<img src="/images/automation-menu1.png">
|
||||||
|
<figcaption class=center>The automation menu.</figcaption>
|
||||||
|
</figure>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
To automate a parameter on a given track, click on the track's <kbd
|
||||||
|
class=menu>A</kbd> button and select a parameter to control from the menu
|
||||||
|
that appears. Once a parameter has been selected, an automation lane for that
|
||||||
|
parameter will appear beneath the track. The lane thus shown will be empty;
|
||||||
|
from here an automation curve must be defined.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p class=note>
|
||||||
|
If the height of the automation lane is too small to see all of its controls,
|
||||||
|
the height can be increased by <kbd class=mouse>Left</kbd> clicking on the
|
||||||
|
bottom border of the lane and dragging it.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
There are three ways to define an automation curve:
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<ul>
|
||||||
|
<li>Record it using <kbd class=menu>Write</kbd> mode</li>
|
||||||
|
<li>Record it using <kbd class=menu>Touch</kbd> mode</li>
|
||||||
|
<li>Draw it using the mouse</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<h2>Recording an Automation Curve Using Write Mode</h2>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
To create an automation curve using <kbd class=menu>Write</kbd> mode, first
|
||||||
|
set the lane's mode selector to <kbd class=menu>Write</kbd>, then set the
|
||||||
|
playhead to the position where the automation curve should start, then set
|
||||||
|
the transport to play. While the playhead is moving, Ardour will continuously
|
||||||
|
record any changes made with the lane's fader. Even if no changes are made to
|
||||||
|
the fader, they will overwrite anything that existed in the lane where the
|
||||||
|
playhead is moving. When the desired automation curve has been recorded, stop
|
||||||
|
the transport.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p class=note>
|
||||||
|
After the transport is stopped, the lane's mode selector will automatically
|
||||||
|
switch to <kbd class=menu>Touch</kbd> mode—it is generally a bad idea
|
||||||
|
to leave an automation lane in <kbd class=menu>Write</kbd> mode, as it is a
|
||||||
|
destructive operation that makes it easy to inadvertently overwrite existing
|
||||||
|
automation curves.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<h2>Recording an Automation Curve Using Touch Mode</h2>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
Creating an automation curve using <kbd class=menu>Touch</kbd> mode is
|
||||||
|
similar to the method employed in creating one using <kbd
|
||||||
|
class=menu>Write</kbd> mode; the only difference is that changes are written
|
||||||
|
to the automation curve <em>only</em> when the lane's fader is moved—at
|
||||||
|
all other times, whatever was in the automation curve will remain as it was.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p class=note>
|
||||||
|
<kbd class=menu>Touch</kbd> mode is useful when only small parts of the
|
||||||
|
automation curve need touching up versus <kbd class=menu>Write</kbd> mode,
|
||||||
|
which is usually used to create the automation curve in the first place.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<h2>Drawing an Automation Curve Using the Mouse</h2>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
In <dfn>Draw</dfn> mode, <dfn>control points</dfn> can be entered in the
|
||||||
|
automation lane by <kbd class=mouse>Left</kbd>-clicking in the lane at a
|
||||||
|
point where there is no existing control point.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
Once added, a control point can be <kbd class=mouse>Left</kbd>-clicked and
|
||||||
|
dragged to a desired location. Hovering over a control point will show its
|
||||||
|
current level in dB. To remove a control point, <kbd
|
||||||
|
class=mouse>Left</kbd>-click it and press <kbd>Delete</kbd>, or <kbd
|
||||||
|
class=mod3n></kbd><kbd class=mouse>Right</kbd>-click on it.
|
||||||
|
</p>
|
||||||
|
|
||||||
613
master-doc.txt
613
master-doc.txt
File diff suppressed because it is too large
Load Diff
BIN
source/images/automation-curve1.png
Normal file
BIN
source/images/automation-curve1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.5 KiB |
BIN
source/images/automation-fader1.png
Normal file
BIN
source/images/automation-fader1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
source/images/automation-lane1.png
Normal file
BIN
source/images/automation-lane1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.7 KiB |
BIN
source/images/automation-menu1.png
Normal file
BIN
source/images/automation-menu1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
source/images/automation-modes1.png
Normal file
BIN
source/images/automation-modes1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
source/images/automation-multi-lane1.png
Normal file
BIN
source/images/automation-multi-lane1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.3 KiB After Width: | Height: | Size: 3.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 12 KiB |
Loading…
Reference in New Issue
Block a user