manual/_manual/14_signal-routing/07_Patchbay.html

52 lines
5.6 KiB
HTML
Raw Normal View History

2013-01-29 19:26:36 -05:00
---
layout: default
title: Patchbay
2013-01-29 19:26:36 -05:00
---
<p>The patchbay is the main way to make connections to, from and within Ardour's mixer. </p>
<blockquote><p>
Notable exceptions are aux sends and connections to the monitor bus (if you are using one): these cannot be controlled from a patchbay, and are basically not under manual control at all.
</p></blockquote>
<p><img align="center" src="/ardour/manual/html/screenshots/connection-manager.png" alt="an example patchbay"></p>
<p>The patchbay presents two groups of ports; one set of sources (which produce data), and one of destinations (which consume data). Depending on the relative number of each, the sources will be placed on the left or the top of the dialogue, and the destinations on the right or the bottom. Thus, in general, signal flow is from top or left to right or bottom.</p>
<p>Both sources and destinations are divided up into groups, with each group being given a tab. Click on the appropriate tab to show the ports in each group (Ardour Busses, Ardour Tracks and so on).</p>
<p>The groups that are used are as follows:</p>
<dl class="narrower-table">
<dt>Hardware</dt>
<dd>ports which are connected to a physical piece of hardware (a sound card or MIDI interface).</dd>
<dt>Ardour Busses</dt>
<dd>ports belonging to busses.</dd>
<dt>Ardour Tracks</dt>
<dd>ports belonging to tracks.</dd>
<dt>Ardour Misc</dt>
<dd> other ports that do not fit into the previous two categories; for example, the ports on which the metronome click is output, and MIDI ports for things like control surfaces and timecode.</dd>
<dt>Other</dt>
<dd>If you have other JACK clients running, their ports will be found here. If there are no such ports, the tab will not exist (on one or both axes of the grid).</dd>
</dl>
<p>The main body of the patchbay is a grid. Within this grid, green dots represent connections, and you can click in any of the squares to make or break connections. You can also click and drag to draw a line of connections, which is sometimes useful for making many connections at once.</p>
<p>In the example patchbay shown above we can note various things. We are using the Ardour Tracks sources tab, so we see the output ports of the three tracks in our session: Fred, Jim and Foo. Our destinations are from the Ardour Busses tab, so we have the inputs of a session bus, Sheila, and the inputs of the master bus. Fred and Jim have stereo outputs, so have L and R connections. Foo is a MIDI track, so it only has one connection, and its squares in the grid are coloured light grey to indicate that no connection can be made between Foo (a MIDI output) and our busses (which are all audio-input).</p>
<p>The green dots in the example show that both Foo and Bar are connected to the master bus, left to left and right to right.</p>
<h2>Variants on the Patchbay</h2>
<p>Slightly different versions of the patchbay are available from different places in Ardour. For a global view of all JACK audio connections, use the Audio Patchbay which can be opened from the Window menu, or by using Alt+P. A corresponding MIDI Connection Manager can be opened using Shift+Alt+P.</p>
<p>There is also a patchbay available when connecting individual tracks; clicking on the input or output buttons of a mixer strip will open a connection manager which has the corresponding track input or output as the only destination or source, with all other ports available for connection to it.</p>
<h2>Other patchbay features</h2>
<p>Context-clicking on a port name in the connection manager opens a menu which provides a few handy options:</p>
<dl class="wide-table">
<dt>Add audio port and Add MIDI port</dt>
<dd>these options add audio or MIDI ports to the thing that you opened the menu over, if this is possible. In this way, for example, tracks and busses can be extended to have more inputs or outputs.</dd>
<dt>Remove</dt>
<dd>removes the given port, if possible.</dd>
<dt>Disconnect all from…</dt>
<dd>disconnects everything from the given port.</dd>
<dt>Rescan</dt>
<dd>Ardour will try to keep abreast of any changes to the JACK ports on your system, and reflect them in any connection managers which are open. If for some reason this fails, choosing Rescan will re-scan the list of ports and update the manager.</dd>
<dt>Show individual ports</dt>
<dd>if you have a session which has lots of multi-channel tracks or busses, it may be an unnecessary detail that you have to connect left to left and right to right every time you make a connection. This obviously gets worse with higher channel counts (such as for 5.1 or ambisonics). To make life easier with such sessions, you can untick Show individual ports. After that, the channels of tracks and busses will be hidden, and any green dots you add in the connection manager will automatically connect each channel of the source to the corresponding channel of the destination (left to left, right to right and so on). In this mode, a half-circle in the connection grid indicates that some (but not all) of the source's ports are connected to the destination.</dd>
<dt>Flip</dt>
<dd>this will flip the visible ports on the vertical axis with those on the horizontal. If, for example, the top of the connection manager is showing Ardour Busses and the right is showing Hardware, flip will swap the view to the opposite so that the top of the manager displays Hardware and the right Ardour Busses. You can also flip by pressing <kbd>f</kbd>. Note that if there are no matching tabs on both axes, flipping will be impossible.</dd>
</dl>
<p>  </p>
<!-- remove if more text is added below --><!-- remove if more text is added below -->