X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fpatchbay.html;h=7e881c41574bdd1b47da0ec4cae459047ffe6178;hb=081e7af0b6f6dec0ca685d3a538eacf20394c2cc;hp=50f96940cc6273cd4ef661c1b5146cb689b1e765;hpb=2098e011e638b5c86c56e68df7757975fc4d728f;p=ardour-manual diff --git a/include/patchbay.html b/include/patchbay.html index 50f9694..7e881c4 100644 --- a/include/patchbay.html +++ b/include/patchbay.html @@ -1,134 +1,134 @@ - +

- The patchbay is the main way to make connections to, from and - within Ardour's mixer. + The patchbay is the main way to make connections to, from and + within Ardour's mixer.

- Notable exceptions are internal aux sends and connections to the monitor bus (if - you are using one): these cannot be controlled from a patchbay, and are + Notable exceptions are internal 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.

an example patchbay

- The patchbay presents two groups of ports; one set of sources - (which produce data), and one of destinations (which consume - data). Depending + 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 + 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.

- Both sources and destinations are divided up into groups, with each + Both sources and destinations are divided up into groups, with each group being given a tab:

-
-
Hardware
-
- These are ports which are connected to a physical piece of hardware - (a sound card or MIDI interface).
-
Ardour Busses
-
All ports belonging to busses.
-
Ardour Tracks
-
All ports belonging to tracks.
-
Ardour Misc
-
- These are 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 + + + + + + + + + + + +
Hardware + These are ports which are connected to a physical piece of hardware + (a sound card or MIDI interface).
Ardour BussesAll ports belonging to busses.
Ardour TracksAll ports belonging to tracks.
Ardour Misc + These are 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. - -
Other
-
- 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).
- +
Other + 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).

- The main part of the patchbay is a matrix grid. Within this + The main part of the patchbay is a matrix 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 + 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.

- 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 + 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).

- The green dots in the example show that both Foo and Bar are connected + 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.

Variants on the Patchbay

- Slightly different versions of the patchbay are available from different - places in Ardour. For a global view of all JACK audio connections, use - Window > Audio Patchbay, or press - P. A corresponding MIDI Connection Manager can + Slightly different versions of the patchbay are available from different + places in Ardour. For a global view of all JACK audio connections, use + Window > Audio Patchbay, or press + P. A corresponding MIDI Connection Manager can be opened using 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 + 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.

Other patchbay features

- Context-clicking on a port name in the connection manager opens a menu + Context-clicking on a port name in the connection manager opens a menu which provides a few handy options:

-
-
Add audio port and Add MIDI port
-
- 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 + + + + + + + + + + + + + +
Add audio port and Add MIDI port + 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. - -
Remove
-
- Removes the given port, if possible. Right-clicking +
Remove + Removes the given port, if possible. Right-clicking a port will do the same. - -
Disconnect all from…
-
Disconnects everything from the given port.
-
Rescan
-
- 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, use this to re-scan the list of ports and +
Disconnect all from…Disconnects everything from the given port.
Rescan + 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, use this to re-scan the list of ports and update the manager. - -
Show individual ports
-
- 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 +
Show individual ports + 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. - -
Flip
-
- 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 +
Flip + 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. You can also flip by pressing f. Note that if there are + opposite. You can also flip by pressing f. Note that if there are no matching tabs on both axes, flipping will be impossible. - - +