175 lines
5.2 KiB
HTML
175 lines
5.2 KiB
HTML
|
|
<h2 id="ace-amplifier">ACE Amplifier</h2>
|
|
|
|
<p>
|
|
This plugin can adjust gain by +/- 20dB anywhere in the processor box.
|
|
It's typically useful in scenarios where a plugin's output needs to be
|
|
adjusted, but the plugin does not provide its output level control.
|
|
</p>
|
|
|
|
<p>
|
|
<em>Gain</em> is the only available setting. It can be set in the generic
|
|
plugin editor dialog or adjusted on the respective automation lane.
|
|
</p>
|
|
|
|
<h2 id="ace-a-b-switch">ACE A/B Switch</h2>
|
|
|
|
<p>
|
|
This plugin allows switching between two plugins earlier in the processing
|
|
chain using an automation lane and custom pin connections.
|
|
</p>
|
|
<p>
|
|
In the example below, the processor box for a 1-channel track has two
|
|
<em>ACE Delay</em> plugins processing the input differently. Each plugin
|
|
has one manually added output so that the original signal would flow into
|
|
one instance of a plugin while bypassing the other one. All two resulting
|
|
outputs then flow into the ACE A/B Switch plugin. Input 1 is considered the
|
|
A version, input 2 is the B version.
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:50%;" src="/images/a-b-switch-pin-connections.png"
|
|
alt="Pin Connections for ACE A/B Switch">
|
|
<figcaption>
|
|
Pin Connections for ACE A/B Switch
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
ACE A/B Switch will default to the A version. Using an automation lane, it's
|
|
possible to momentarily switch to the B version and back.
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:75%;" src="/images/a-b-switch-lane.png"
|
|
alt="Pin Connections for ACE A/B Switch">
|
|
<figcaption>
|
|
Pin Connections for ACE A/B Switch
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
The plugin supports 1-, 2-, and 4-channel configurations:
|
|
</p>
|
|
|
|
<ul>
|
|
<li>Mono out: In 1/2 -> Out 1</li>
|
|
<li>Stereo out: In 1/3 -> Out 1, In 2/4 -> Out 2</li>
|
|
<li>Quad out: In 1/5 -> Out 1, In 2/6 -> Out 2, In 3/7 -> Out 3, In 4/8 -> Out 4</p></li>
|
|
</ul>
|
|
|
|
<h2 id="ace-cross-fade">ACE Cross Fade</h2>
|
|
|
|
<p>
|
|
This plugin allows gradual transitions between two plugins earlier in the
|
|
processing chain using an automation lane and custom pin connections.
|
|
</p>
|
|
<p>
|
|
In the example below, the processor box for a 1-channel track has two
|
|
<em>ACE Delay</em> plugins processing the input differently. Each plugin
|
|
has one manually added output so that the original signal would flow into
|
|
one instance of a plugin while bypassing the other one. All two resulting
|
|
outputs then flow into the ACE Cross Fade plugin. Input 1 is considered the
|
|
A version, input 2 is the B version.
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:50%;" src="/images/a-b-switch-pin-connections.png"
|
|
alt="Pin Connections for ACE A/B Switch">
|
|
<figcaption>
|
|
Pin Connections for ACE A/B Switch
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
ACE Cross Fade will default to the A version. Using an automation lane, it's
|
|
possible to gradually transition to the B version and then back, mixing A and
|
|
B signal in different ratios.
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:75%;" src="/images/a-b-crossfade-lane.png"
|
|
alt="Pin Connections for ACE Cross Fade ">
|
|
<figcaption>
|
|
Pin Connections for ACE Cross Fade
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
The plugin supports 1-, 2-, and 4-channel configurations:
|
|
</p>
|
|
|
|
<ul>
|
|
<li>Mono out: In 1/2 -> Out 1</li>
|
|
<li>Stereo out: In 1/3 -> Out 1, In 2/4 -> Out 2</li>
|
|
<li>
|
|
Quad out: In 1/5 -> Out 1, In 2/6 -> Out 2, In 3/7 -> Out 3,
|
|
In 4/8 -> Out 4
|
|
</li>
|
|
</ul>
|
|
|
|
<h2 id="ace-mute">ACE Mute</h2>
|
|
|
|
<p>
|
|
This plugin can mute the signal anywhere in the processing chain as opposed
|
|
to automating the mute state of the track that works on all processed audio
|
|
only. Using <em>ACE Mute</em> in the very beginning of the signal chain means
|
|
that in the muted state no signal is processed by plugins further in the
|
|
processing chain.
|
|
</p>
|
|
|
|
<p>
|
|
<em>ACE Mute</em> has no settings. All user interaction happens
|
|
in the dedicated automation lane:
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:75%;" src="/images/a-mute-example.png" alt="Using ACE Mute">
|
|
<figcaption>
|
|
Using ACE Mute
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
Ardour also ships with a variation of <em>ACE Mute</em> called
|
|
<em>ACE Slow Mute</em> that applies a 1 second long fade out/in before/after
|
|
the muting.
|
|
</p>
|
|
|
|
<h2 id="voice-level-activate">Voice/Level Activate</h2>
|
|
|
|
<p>
|
|
This plugin rolls the transport when the signal level on the plugin's input
|
|
exceeds a user-defined level. A common scenario where this is helpful is
|
|
recording in a home studio where an instrument or a vocal mic is at a distance
|
|
from the computer. Arming a track for recording, toggling recording mode, then
|
|
clapping in front of a mic or plucking a string will roll the transport and
|
|
start recording to a track of choice.
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:50%;" src="/images/voice-level-activate.png" alt="Voice/Level Activate">
|
|
<figcaption>
|
|
Voice/Level Activate
|
|
</figcaption>
|
|
</figure>
|
|
|
|
<p>
|
|
The only configurable setting is the input level threshold.
|
|
</p>
|
|
|
|
<h2 id="midi-note-mapper">MIDI Note Mapper</h2>
|
|
|
|
<p>
|
|
Maps arbitrary MIDI notes to others. This affects both note-on and note-off
|
|
events, as well as polyphonic key pressure. A single note can be mapped
|
|
twice, but only the last mapping is used.
|
|
</p>
|
|
|
|
<figure>
|
|
<img style="width:50%;" src="/images/midi-note-mapper.png" alt="MIDI Note Mapper">
|
|
<figcaption>
|
|
MIDI Note Mapper
|
|
</figcaption>
|
|
</figure>
|