7 Ardour does most of its internal <dfn>signal routing</dfn> via JACK:
8 all track and bus inputs and outputs are JACK ports, as are sends and
9 inserts—which means they can be tapped into by other JACK clients.
10 Only the signal flow inside a track or bus (i.e. from <a
11 href="/working-with-plugins/processor-box/">processor to processor</a>) is
16 By default, Ardour will create the following connections:
21 <dfn>Track inputs</dfn> are optionally auto-connected to hardware inputs, in round robin order, depending on the setting you chose in the
22 <a href="/working-with-sessions/new-session-dialog"><kbd
23 class="menu">Session > New Session</kbd> dialog</a>.
26 <dfn>Bus inputs</dfn> are left disconnected.
29 The number of <dfn>track and bus outputs</dfn> are equal to the number
30 of inputs of the master bus.
33 Track and bus outputs are always auto-connected to the master bus inputs.
36 Master bus outputs are connected to hardware outputs.
41 This configuration is normally sufficient to do basic tracking and playback of sessions without any adjustments. When changing these connections, be certain that there is good reason for doing so—it is generally not necessary and can often lead to problems.
45 However, for many workflows during mixing, more complicated signal routing is required. Fortunately, Ardour is very flexible in the ways it offers to connect things to each other.