X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fsignal-routing.html;fp=include%2Fsignal-routing.html;h=f8e61d65cbe96d5a9b61886da77e93fd8daf0754;hb=c51fb0912002ae976dad46aa297a6a16d1246a93;hp=3fd2b50d88468bdf3101cd9fe54072c204507dec;hpb=5a9ceb32aca6ec94e19f6b9c3ae70b3209512654;p=ardour-manual
diff --git a/include/signal-routing.html b/include/signal-routing.html
index 3fd2b50..f8e61d6 100644
--- a/include/signal-routing.html
+++ b/include/signal-routing.html
@@ -5,13 +5,15 @@
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 automatically 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. + sessions without any adjustment by the user. Changing these connections + 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 - way you may need or want them. + is required. Ardour offers many possibilties for connecting things to fit any + particular workflow.
-