Ardour does most of its internal signal routing via JACK:
all track and bus inputs and outputs are JACK ports, as are sends and
- inserts, which means they can be tapped into by other JACK clients.
+ inserts—which means they can be tapped into by other JACK clients.
Only the signal flow inside a track or bus (i.e. from processor to processor) is
- handled internally.
- By default, Ardour will create the following connections for you:
+ handled internally.
+ By default, Ardour will create the following connections: +
+- This configuration is sufficient to do basic tracking and playback of many - sessions without any adjustment by the user. If you are using Ardour and - start to change these connections, be certain that you have a good reason - to do so — it is generally not necessary and often leads to problems. + 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.
+- However, for many workflows during mixing, more complicated signal routing - is required. Ardour offers many possibilties for connecting things in the - way you may need or want them. + 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.
{% children %} +