Katz, scale aligned to -20 dBFS, rise/fall times and color schema
according to spec.</li>
<li><dfn>K14</dfn>: Same as K20 with scale aligned to -14 dBFS.</li>
+ <li><dfn>K12</dfn>: Same as K20 with scale aligned to -12 dBFS (since 3.5.143).</li>
<li><dfn>Peak + RMS</dfn>: standard RMS, customizable via
<kbd class="menu">Edit > Preferences > GUI > Metering</kbd></li>
</ul>
<p>
<kbd class="mouse">Left</kbd> on the peak-indicator button resets the
<dfn>peak-hold indicator</dfn> of a single channel.<br />
- <kbd class="mod1 mouse">Left</kbd> resets a whole <dfn>group</dfn>, and<br
- />
+ <kbd class="mod1 mouse">Left</kbd> resets a whole <dfn>group</dfn>, and<br/>
<kbd class="mod13 mouse">Left</kbd> resets all meters.
</p>
<p>
Due to layout concerns and consistent look&feel all meters available in
- Ardour3 itself are bar-graph type meters. Corresponding needle-style meters
+ Ardour itself are bar-graph type meters. Corresponding needle-style meters
— which take up more visual screen space — are available as
- LV2 plugins (on the right).
+ LV2 plugins (see image on the right):
+ <a href="https://github.com/x42/meters.lv2/">meters.lv2</a>.
</p>
-
--- /dev/null
+---
+layout: default
+title: Plugin Sidebar
+---
+
+<p>
+ Since Version 4.5, Ardour has a plugin-sidebar on the top-left side of the
+ Mixer Window.
+ Like other elements in that sidebar it has variable height and can be hidden
+ by dragging it to zero-height. If it is not visible, grab the top-handle
+ and drag it down.
+</p>
+
+<img src="/files/a4/a4_plugin_sidebar.png" alt="Plugin Sidebar"/>
+
+<h2>Features</h2>
+<p>
+ The Plugin sidebar provides easy access to common operations.
+ All interaction is done with the mouse and Drag/Drop.
+</p>
+<ul>
+ <li>The sidebar lists "favorite" plugins only.</li>
+ <li>Plugins can be dragged from the sidebar to any track or bus, which will add the plugin to that track/bus at the given position.</li>
+ <li>The list includes user-presets for the plugins. Dragging a preset to a given track/bus will load that preset after adding the plugin.</li>
+ <li>Double-click on a plugin or preset adds the given plugin to all selected tracks/busses pre-fader. Other insert positions are available from the context menu (right click).</li>
+</ul>
+<p>
+ The sidebar also allows to manage presets and favorites.
+</p>
+<ul>
+ <li>Dragging a plugin from a track into the sidebar will add it to the "favorites" and optionally create a new preset from the current settings.</li>
+ <li>The context-menu allows to delete presets or remove the plugin from the "favorite" list.</li>
+ <li>Plugins in the list can be re-ordered using drag/drop. The custom order is saved.</li>
+</ul>
+
+<p>
+ Note, when favorites are added with the <a href="/working-with-plugins/plugin-manager">plugin-manager</a>, they are appended at the bottom of the list.
+</p>
<h2>Adding an External Send</h2>
<p>
Context-click on the
- <a href="/working-with-plugins/the-processor-box">processor box</a> in a
+ <a href="/working-with-plugins/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
<h2>Enabling Mackie Control in Ardour</h2>
<p>
- Navigate to <kbd class="menu">Edit > Preferences > Control Surfaces</kbd>. Double-click on <kbd class="menu">Mackie Control</kbd>
- to see the setup dialog:
+ Navigate to <kbd class="menu">Edit > Preferences > Control Surfaces</kbd>.
+ Double-click on <kbd class="menu">Mackie Control</kbd> to see the setup dialog:
</p>
<img src="" alt="Mackie Control Setup Dialog" />
<p>
Most interfaces will require some configuration to send and respond to
MCP.
</p>
+
+<p class="note">
+ When setting up the control surface, do <em>not</em> use "Pro Tools"
+ mode. Pro Tools is the only DAW that still requires HUI. The rest of
+ world uses Mackie Control Protocol. Ardour does not support HUI.
+</p>
{% children %}
<code>pgm</code> (to create a binding for a Program Change message).
</p>
<p>
- <code>enc-r</code>, <code>enc-l</code>, <code>enc-2</code> and
+ As of Ardour 4.2, <code>enc-r</code>, <code>enc-l</code>, <code>enc-2</code> and
<code>enc-b</code> may be used for surfaces that have encoders that send
offsets rather than values. These accept Continuous Controller messages
but treat them as offsets. These are good for banked controls as they are
</p>
<p class="note">
- It is not possible at this time to use multi-event MIDI strings such as
+ As of Ardour 4.6 it is possible to use multi-event MIDI strings such as
two event CC messages, RPN or NRPN.
</p>
<p>
Encoders are showing up more frequently on controllers. However, they use
the same MIDI events as Continuous Controllers and they have no standard
- way of sending that information as MIDI events. Ardour has implemented 4 of
- the more common ways of sending encoder information.
+ way of sending that information as MIDI events. Ardour 4.2 has implemented
+ 4 of the more common ways of sending encoder information.
</p>
<p>
Encoders that send the same continuous values as a pot would are not
If you want the bindings you set up to be used automatically in every
session, the simplest thing to do is to use <kbd class="menu">Session > Save
Template</kbd>. Then, when creating new sessions, select that template and
-all the bindings will be automatically set up for you. You can also
-save a specific track/bus configuration as a template, and use that
-when adding new tracks or busses. Click on the track name at the top
-of a mixer strip and select <kbd class="menu">Save as Template</kbd>.
+all the bindings will be automatically set up for you.
</p>
projects / ardour-manual-diverged / commitdiff
