Updating pages : passive form, new menu locations, etc.
This commit is contained in:
parent
5a9ceb32ac
commit
c51fb09120
@ -17,8 +17,8 @@
|
||||
wedge mixes), or returned to the main mix (in the case of an effect).
|
||||
</p>
|
||||
<p>
|
||||
Aux sends are not JACK ports, use <a href="@@external-sends">
|
||||
External Sends</a> to send audio to Jack ports. External Sends can
|
||||
Aux sends are not JACK ports, <a href="@@external-sends">
|
||||
External Sends</a> should be used to send audio to Jack ports. External Sends can
|
||||
send the tapped signal somewhere else directly, which is not usually
|
||||
possible on hardware mixers.
|
||||
</p>
|
||||
@ -31,35 +31,49 @@
|
||||
|
||||
<h2>Adding a new aux bus</h2>
|
||||
<p>
|
||||
Choose <kbd class="menu">Session > Add New Track or Bus</kbd>. In the
|
||||
<kbd class="menu">New Track & Bus</kbd> dialog, select "Busses" in the Track/Bus
|
||||
selector at the upper right.
|
||||
New busses can be created using the <kbd class="menu">Session > Add Track, Bus or VCA…</kbd>
|
||||
menu, and selecting <kbd class="menu">Audio Busses</kbd> in the Template/Type
|
||||
selector on the left of the <kbd class="menu">Add Track/Bus/VCA</kbd> dialog.
|
||||
</p>
|
||||
|
||||
<h2>Adding a send to an aux bus</h2>
|
||||
<p>
|
||||
Context-click on the processor box for the track you want to send to the bus, and
|
||||
choose <kbd class="menu">New Aux Send</kbd>. From the submenu, choose the bus you
|
||||
want to send to. A send will be added (and will be visible in the processor box).
|
||||
Note that the submenu may be empty if you have not created a bus yet.
|
||||
Context-clicking on the processor box for the track to send to the bus, and
|
||||
choosing <kbd class="menu">New Aux Send …</kbd> shows a submenu, listing the busses.
|
||||
Choosing one bus will add a send (which will be visible in the processor box).
|
||||
Note that if the only existing bus is the Master Bus, the menu will be grayed out.
|
||||
</p>
|
||||
|
||||
<h3>Pre-fader and Post-fader Aux Sends</h3>
|
||||
<p>
|
||||
Depending on whether you context-click above or below the fader in the processor box,
|
||||
the new aux send can be placed before or after the fader in the channel strip.
|
||||
<dfn>Post-fader</dfn> aux sends are typically used when using an aux for shared signal
|
||||
processing (FX), so that the amount of effect is always proportional to
|
||||
the main mix fader. <dfn>Pre-fader</dfn> sends ensure that the level sent to the bus
|
||||
is controlled <em>only</em> by the send, not the main fader—this is typical
|
||||
when constructing headphone and monitor wedge mixes.
|
||||
Depending on whether the context-click happened above or below the fader in the
|
||||
processor box, the new aux send can be placed before or after the fader in the
|
||||
channel strip.
|
||||
</p>
|
||||
<ul>
|
||||
<li><dfn>Post-fader</dfn> aux sends are typically used when using an aux for
|
||||
shared signal processing (FX), so that the amount of effect is always
|
||||
proportional to the main mix fader.</li>
|
||||
<li><dfn>Pre-fader</dfn> sends ensure
|
||||
that the level sent to the bus is controlled <em>only</em> by the send, not the
|
||||
main fader—this is typical when constructing headphone and monitor wedge
|
||||
mixes.</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
The color of the processor will reflect this pre/post position (red for
|
||||
<span style="color:darkred;">Pre</span>, green for <span
|
||||
style="color:darkgreen;">Post</span>). Dragging and dropping the send inside
|
||||
the processor box before or after the Fader processor changes the type of
|
||||
fader accordingly.
|
||||
</p>
|
||||
|
||||
|
||||
<h2>Adding a new aux bus and sending a Track Group to it</h2>
|
||||
<p>
|
||||
You can add aux sends to all members of a group and connect them to a new aux bus
|
||||
with a single click. After creating the <a href="@@track-and-bus-groups">track group</a>
|
||||
(and adding tracks to it), context-click on the group tab and choose either
|
||||
All members of a group can be sent to a new aux bus at once with a single click.
|
||||
After creating the <a href="@@track-and-bus-groups">track group</a>
|
||||
(and adding tracks to it), context-clicking on the group tab allows to choose either
|
||||
<kbd class="menu">Add New Aux Bus (pre-fader)</kbd> or
|
||||
<kbd class="menu">Add New Aux Bus (post-fader)</kbd>. A new aux bus will be created,
|
||||
and a new aux send added to every member of the track group that connects to
|
||||
@ -68,44 +82,38 @@
|
||||
|
||||
<h2>Altering Send Levels</h2>
|
||||
<p>
|
||||
You can alter the amount of the signal received by a send that it delivers to the bus
|
||||
it connects to. There are three approaches to this:
|
||||
The amount of the signal received by a send that it delivers to the bus it connects to
|
||||
can be altered in two ways:
|
||||
</p>
|
||||
<h3>Use the Send Fader</h3>
|
||||
<h3>Using the Send Fader</h3>
|
||||
<p>
|
||||
Every send processor has a small horizontal fader that can be adjusted in the usual way. It is
|
||||
not very big and so this can be a little unsatisfactory if you want very fine control
|
||||
over the send level.
|
||||
</p>
|
||||
<h3>Mapping the Main Fader</h3>
|
||||
<p>
|
||||
Double-clicking on the send in the processor box will allow you to use the
|
||||
big fader of the mixer strip to control the send. The visual appearance of
|
||||
the mixer strip will change to reflect this. Double-click the send again to
|
||||
revert back to normal function for the strip.
|
||||
Every send processor has a small horizontal fader that can be adjusted in the
|
||||
usual way. It is not very big and so this can be a little unsatisfactory if you
|
||||
a very fine control over the send level is required.
|
||||
</p>
|
||||
<h3>Map Aux Sends To Main Faders</h3>
|
||||
<p>
|
||||
Pressing the button marked <kbd class="menu">Aux Sends</kbd> on a aux bus will
|
||||
In Mixer mode, pressing the button marked <kbd class="menu">Aux</kbd> on a aux bus will
|
||||
alter the channel strip for every track or bus that feeds the aux bus. Many
|
||||
aspects of the strip will become insensitive and/or change their visual
|
||||
appearance. More importantly, the main fader of the affected channel strips
|
||||
will now control the send level and <strong>not</strong> the track gain.
|
||||
This gives a larger, more configurable control to alter the level. Click the
|
||||
<kbd class="menu">Aux Sends</kbd> button of the aux bus again to revert the
|
||||
This gives a larger, more configurable control to alter the level. Clicking the
|
||||
<kbd class="menu">Aux</kbd> button of the aux bus again reverts the
|
||||
channel strips to their normal use.
|
||||
</p>
|
||||
|
||||
<h2>Disabling Sends</h2>
|
||||
<p>
|
||||
Clicking on the small "LED" in the send display in the processor box of the
|
||||
Clicking on the small LED in the send display in the processor box of the
|
||||
channel strip will enable/disable the send. When disabled, only silence will
|
||||
be delivered to the aux bus by this track. When enabled, the signal arriving
|
||||
at the send will be delivered to the aux bus.
|
||||
</p>
|
||||
|
||||
<h2>Send Panning</h2>
|
||||
<p>
|
||||
Send panners can be configured to either be independent of the main
|
||||
panner, or to follow it. The latter could be useful for Reverb effects, or
|
||||
for in-ear monitor mixes delivered in stereo.
|
||||
</p>
|
||||
|
||||
|
@ -1,57 +1,52 @@
|
||||
|
||||
<p>
|
||||
Like a normal aux send, an <dfn>external send</dfn> taps the signal at a
|
||||
specific within a channel strip, but delivers it to an external application
|
||||
specific point within a channel strip, but delivers it to an external application
|
||||
or piece of hardware rather than an Ardour bus. By itself, an external
|
||||
send has no effect whatsoever on the audio signals within Ardour—it
|
||||
is a one-way signal routing that leaves all existing signal processing
|
||||
just as it was.
|
||||
</p>
|
||||
<p>
|
||||
Most people will not have much use for this, but it can be useful if you
|
||||
want to experiment with external applications or hardware signal processing
|
||||
applications.
|
||||
Most people will not have much use for this, but it can be useful to experiment
|
||||
with external applications or hardware signal processing applications.
|
||||
</p>
|
||||
|
||||
<h2>Adding an External Send</h2>
|
||||
<p>
|
||||
Context-click on the
|
||||
Context-clicking on the
|
||||
<a href="@@processor-box">processor box</a> in a
|
||||
channel strip (at the desired location, pre or post fader) and choose
|
||||
<kbd class="menu">Add new External Send</kbd>. A dialog will appear
|
||||
containing the standard Ardour
|
||||
<a href="@@patchbay"><dfn>patchbay</dfn></a> to allow
|
||||
you to connect the send to the desired destination.
|
||||
channel strip (at the desired location, pre or post fader) and choosing
|
||||
<kbd class="menu">Add new External Send</kbd> will show a dialog containing the
|
||||
standard Ardour <a href="@@patchbay"><dfn>patchbay</dfn></a> to allow
|
||||
to connect the send to the desired destination.
|
||||
</p>
|
||||
|
||||
<h2>Removing an External Send</h2>
|
||||
<p>You can remove an external send in several ways:</p>
|
||||
<p>An external send can be removed in several ways:</p>
|
||||
<ul>
|
||||
<li><kbd class="mouse mod3">Right</kbd>-click the send in the processor box.</li>
|
||||
<li>Position the pointer over the send and press the <kbd>Del</kbd> key.</li>
|
||||
<li>Position the pointer over the send and press <kbd class="mod1">x</kbd>.</li>
|
||||
<li>Context-click the send and choose either <kbd class="menu">Cut</kbd> or
|
||||
<kbd class="menu">Delete</kbd>.</li>
|
||||
<li><kbd class="mouse mod3">Right</kbd>-clicking the send in the processor box and
|
||||
choosing either <kbd class="menu">Cut</kbd> or <kbd class="menu">Delete</kbd>.</li>
|
||||
<li>Selecting the send (with a single <kbd class="mouse">left</kbd> click) and
|
||||
pressing the <kbd>Del</kbd> key.</li>
|
||||
</ul>
|
||||
|
||||
<h2>Altering Send Levels</h2>
|
||||
<p>
|
||||
Just below the send in the processor box is a small fader that can be used
|
||||
like all other faders in Ardour to control the gain applied to the signal
|
||||
delivered by the send. Drag it to alter the level, Shift-click to restore
|
||||
delivered by the send. Dragging it alters the level, Shift-click restores
|
||||
to unity (0dB) gain.
|
||||
</p>
|
||||
|
||||
<h2>Disabling Sends</h2>
|
||||
<p>
|
||||
Click the small "LED" in the send display within the processor box to turn
|
||||
Clicking the small LED in the send display within the processor box turns
|
||||
it on and off. When turned off, silence will be delivered to the send. When
|
||||
turned on, the signal within the channel strip will be delivered.
|
||||
</p>
|
||||
<h2>Editing Send Routing</h2>
|
||||
<p>
|
||||
Double-clicking or Edit-clicking on the send in the processor box will
|
||||
redisplay the patchbay dialog that allows you full control over the routing
|
||||
of the send.
|
||||
Double-clicking on the send in the processor box will redisplay the patchbay
|
||||
dialog that gives full control over the routing of the send.
|
||||
</p>
|
||||
|
||||
|
@ -5,13 +5,15 @@
|
||||
inserts, which means they can be tapped into by other JACK clients.
|
||||
Only the signal flow inside a track or bus (i.e. from <a
|
||||
href="@@processor-box">processor to processor</a>) is
|
||||
handled internally.<br>
|
||||
By default, Ardour will create the following connections for you:
|
||||
handled internally.
|
||||
</p>
|
||||
<p>
|
||||
By default, Ardour will automatically create the following connections:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
<dfn>Track inputs</dfn> are optionally auto-connected to hardware inputs, in round robin
|
||||
order, depending on the setting you chose in the
|
||||
order, depending on the setting chosen in the
|
||||
<a href="@@newopen-session-dialog"><kbd
|
||||
class="menu">Session > New Session</kbd> dialog</a>.
|
||||
</li>
|
||||
@ -31,13 +33,11 @@
|
||||
</ul>
|
||||
<p>
|
||||
This configuration is sufficient to do basic tracking and playback of many
|
||||
sessions without any adjustment by the user. If you are using Ardour and
|
||||
start to change these connections, be certain that you have a good reason
|
||||
to do so—it is generally not necessary and often leads to problems.
|
||||
sessions without any adjustment by the user. Changing these connections
|
||||
is generally not necessary and often leads to problems.
|
||||
</p>
|
||||
<p>
|
||||
However, for many workflows during mixing, more complicated signal routing
|
||||
is required. Ardour offers many possibilties for connecting things in the
|
||||
way you may need or want them.
|
||||
is required. Ardour offers many possibilties for connecting things to fit any
|
||||
particular workflow.
|
||||
</p>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user