X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fsignal-routing.html;h=3fd2b50d88468bdf3101cd9fe54072c204507dec;hb=f56f685d73572cad74ad34f4b9dc8acf5ed68fdf;hp=d8b23e8c6e800359f27e3cf2cac22bf332e6c41d;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual diff --git a/include/signal-routing.html b/include/signal-routing.html index d8b23e8..3fd2b50 100644 --- a/include/signal-routing.html +++ b/include/signal-routing.html @@ -1,18 +1,18 @@

- Ardour does most of its internal signal routing via JACK: + 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. Only the signal flow inside a track or bus (i.e. from processor to processor) is + href="@@processor-box">processor to processor) is handled internally.
By default, Ardour will create the following connections for you:

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

- However, for many workflows during mixing, more complicated signal routing - is required. Ardour offers many possibilties for connecting things in the + 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.