Updated Understanding Routing

content/recording-audio/understanding-routing/index.en.md

@@ -1,179 +1,173 @@
 +++
 title = "Understanding routing"
+description = "Routing signal in Ardour"
 chapter = false
-weight = 6
+weight = 2
 #pre = "<b>1. </b>"
 featherlight = false
 +++
 
 Routing an audio signal is sending it from somewhere to somewhere else.
 
-In addition to getting audio signals to and from Ardour, routing plays
+In addition to getting audio signals to and from Ardour, routing plays an
-an important part inside Ardour itself. Examples of using routing inside
+important part inside Ardour itself. Examples of using routing inside Ardour
-Ardour include routing audio from Tracks to the Master Bus or to other
+include routing audio from tracks to the _Master_ bus or to other busses,
-Busses, creating 'sends', routing the outputs from Busses to the Master
+creating 'sends', routing the outputs from busses to the _Master_ bus, etc. (see
-Bus, etc. (see chapter on **Creating a Track** for an explanation of
+chapter on **Creating a Track** for an explanation of tracks and busses). All
-Tracks and Busses). All routing, both internal and external to Ardour,
+routing, both internal and external to Ardour, is handled by JACK.
-is handled by JACK.
 
 ### Routing in Ardour
 
-The standard routing of inputs, tracks and busses in Ardour is
+The standard routing of inputs, tracks and busses in Ardour is determined when
-determined when a new Session is created in the Advanced Options of the
+a new session is created in the _Advanced Options_ of the _New Session_ dialog
-New Session dialog box (see **Starting a Session** chapter). By default,
+box (see the [Starting Ardour](../../getting-started/starting-ardour-on-ubuntu/)
-the routing is as follows:
+page). By default, the routing is as follows:
 
-- The audio device inputs are routed to the Track inputs.
+- The audio device inputs are routed to the track inputs.
-- All outputs from Tracks and Busses are routed to the master bus
+- All outputs from tracks and busses are routed to the master bus inputs.
-  inputs.
+- The _Master_ bus outputs are routed to the audio device outputs.
-- The Master Bus outputs are routed to the audio device outputs.
 
-Note that when a new Bus is created, nothing is routed to its input.
+Note that when a new bus is created, nothing is routed to its input.
 
-This routing setup makes sense for sessions containing only Tracks, but
+This routing setup makes sense for sessions containing only tracks, but to make
-to make use of any Busses (other than the Master Bus) or to get creative
+use of any busses (other than the _Master_ bus) or to get creative with the
-with the paths of the audio signals inside Ardour, we need to be able to
+paths of the audio signals inside Ardour, we need to be able to change the
-change the routing. 
+routing. 
 
-The Audio Connection Manager window (also known as the patchbay) is the
+The _Audio Connection Manager_ window (also known as the patchbay) is the main
-main way to make connections to, from ,and within Ardour's mixer. You
+way to make connections to, from ,and within Ardour's mixer. You can open this
-can open this window with the shortcut "*Alt*" + "*N*", or through the
+window with the shortcut **Alt + P**, or through the
-menu *Window > Audio Connections*.
+`Window > Audio Connections` menu.
 
-![Audio Connection Manager](en/Ardour4_Audio_Connection_Manager_Menu.png) 
+![_Audio Connection Manager_](en/ardour7-audio-connections-in-menu.png) 
 
-The patchbay presents two groups of ports; one set of sources, and one
+The patchbay presents two groups of ports; one set of sources, and one of
-of destinations. Sources and destinations are organized by tabs. The
+destinations. Sources and destinations are organized by tabs. The available
-available sources are displayed vertically on the left side, and the
+sources are displayed vertically on the left side, and the destinations are
-destinations are displayed horizontally at the bottom.
+displayed horizontally at the bottom.
 
-In the screenshot below, notice that the "*Hardware*" tab is selected on
+In the screenshot below, notice that the _Hardware_ tab is selected on the top
-the top left (that's a source), and the "*Ardour Tracks*" is selected as
+left (that's a source), and the *_Ardour Tracks_* is selected as a destination
-a destination in the bottom. This means that the matrix you see displays
+in the bottom. This means that the matrix you see displays connections from
-connections from available hardware sound sources (for example, a
+available hardware sound sources (for example, a microphone), into existing
-microphone), into existing Ardour tracks.  
+Ardour tracks.  
 
 ![ACM 1](en/Ardour4_Audio_Connection_Manager_1.png) 
 
-The green dots represent a connection. The screenshot above tells us
+The green dots represent a connection. The screenshot above tells us that
-that incoming sounds from "*system: capture\_1*" (the first input source
+incoming sounds from "*system: capture\_1*" (the first input source of your
-of your soundcard, or the built-in microphone of your laptop) are going
+soundcard, or the built-in microphone of your laptop) are going into Ardour
-into Ardour track named "*Audio 1*", and also that incoming sounds from
+track named "*Audio 1*", and also that incoming sounds from "*system:
-"*system: capture\_1*" and "*system: capture\_2*" are respectively going
+capture\_1*" and "*system: capture\_2*" are respectively going into the Left and
-into the Left and Right inputs of Ardour track named "*Audio 2.*" 
+Right inputs of Ardour track named "*Audio 2.*" 
 
-Notice we can see that "*Audio 1*" is a Mono track because it only has
+Notice we can see that "*Audio 1*" is a Mono track because it only has one
-one connection slot, while track "*Audio 2*" is Stereo since it has two
+connection slot, while track "*Audio 2*" is Stereo since it has two slots (Left
-slots (Left and Right).
+and Right).
 
-The next screenshot shows the signal path from Ardour Tracks (selected
+The next screenshot shows the signal path from _Ardour Tracks_ (selected
-vertical tab) into Ardour Busses (selected horizontal tab). As mentioned
+vertical tab) into Ardour busses (selected horizontal tab). As mentioned
-earlier, the default setting for all Ardour Tracks is that their sound
+earlier, the default setting for all _Ardour Tracks_ is that their sound goes to
-goes to the Master Bus.
+the _Master_ bus.
 
 ![ACM 2](en/Ardour4_Audio_Connection_Manager_2.png) 
 
-Note: remember that "*Audio 1*" is a Mono track? We saw it in the
+Note: remember that "*Audio 1*" is a Mono track? We saw it in the earlier
-earlier screenshot that "*Audio 1*" only has one input slot. But now on
+screenshot that "*Audio 1*" only has one input slot. But now on the screenshot
-the screenshot above you see that "Audio 1" has two outputs (Left and
+above you see that "Audio 1" has two outputs (Left and Right). This is normal:
-Right). This is normal: we define whether a track is Mono or Stereo by
+we define whether a track is Mono or Stereo by its *number of inputs*, not
-its *number of inputs*, not outputs. Mono tracks will hold a single
+outputs. Mono tracks will hold a single channel of audio, but you can still
-channel of audio, but you can still choose to place the sound on the
+choose to place the sound on the left or the right speaker (or anywhere in
-left or the right speaker (or anywhere in between). More on this in the
+between). More on this in the chapter **Panning**.
-chapter **Panning**.
 
-Finally, let's explore a couple more tabs in the Audio Connection
+Finally, let's explore a couple more tabs in the _Audio Connection Manager_ to
-Manager to see the sound going from the Master Bus to the actual
+see the sound going from the _Master_ bus to the actual hardware outputs (your
-hardware outputs (your loudspeakers or headphones):
+loudspeakers or headphones):
 
 ![ACM 3](en/Ardour4_Audio_Connection_Manager_3.png) 
 
-As you can see, the selected source tab is now "*Ardour Busses*", and
+As you can see, the selected source tab is now "*Ardour Busses*", and the
-the destination tab is "*Hardware*". This session happens to have only
+destination tab is _Hardware_. This session happens to have only one bus, the
-one bus, the default "master out". The green dots show that all sounds
+default "master out". The green dots show that all sounds coming out of the
-coming out of the Master Bus are going to system playback 1 and 2, which
+_Master_ bus are going to system playback 1 and 2, which are the outputs of your
-are the outputs of your soundcard. 
+soundcard. 
 
 ### How to connect and disconnect?
 
-To make a connection, click on the desired empty square in the matrix; a
+To make a connection, click on the desired empty square in the matrix; a green
-green dot will appear to indicate the connection is made.
+dot will appear to indicate the connection is made.
 
 To undo a connection, simply click on an existing green dot and it will
 disappear.
 
 ### Practical example of routing to a bus 
 
-In the following example session, there are two guitar Tracks and one
+In the following example session, there are two guitar tracks and one
-unused Bus called Guitar Bus, all Stereo.
+unused bus called _Guitar_ bus, all Stereo.
 
 ![ACM 4](en/Ardour4_Ardour_Connection_Manager_4.png) 
 
-Suppose you want to send the output from the two guitar Tracks to the
+Suppose you want to send the output from the two guitar tracks to the _Guitar_
-Guitar Bus instead of the Master Bus. This can be useful to control the
+bus instead of the _Master_ bus. This can be useful to control the volume of
-volume of both guitars with just one Fader (in this case the Guitar Bus
+both guitars with just one fader (in this case the _Guitar_ bus fader). Then the
-fader). Then the output of the Guitar Bus, which is the sum of the two
+output of the _Guitar_ bus, which is the sum of the two guitars, goes directly
-guitars, goes directly to the Master Bus.
+to the _Master_ bus.
 
-Here is how to edit the patchbay to get the desired routing. Select
+Here is how to edit the patchbay to get the desired routing. Select _Ardour
-"Ardour Tracks" tab from Sources (vertical tabs), and "Ardour Busses"
+Tracks_ tab from _Sources_ (vertical tabs), and _Ardour Busses_ from
-from destinations (horizontal bottom tabs). Undo existing connections
+destinations (horizontal bottom tabs). Undo existing connections from both
-from both Tracks to Master. Then create connections from both Tracks to
+tracks to _Master_. Then create connections from both tracks to _Guitar_ bus.
-Guitar Bus. The final result would look like this: 
+The final result would look like this: 
 
 ![ACM 5](en/Ardour4_Audio_Connection_Manager_5.png) 
 
-Now both guitar tracks are routed to the Guitar Bus, and no longer
+Now both guitar tracks are routed to the _Guitar_ bus, and no longer directly
-directly connected to the Master Bus. We then make sure that the Guitar
+connected to the _Master_ bus. We then make sure that the _Guitar_ bus is, by its
-Bus is, by its turn, routed to the Master Bus (the output routing of a
+turn, routed to the _Master_ bus (the output routing of a bus is edited in the
-Bus is edited in the same way as for a Track), so that we can still hear
+same way as for a track), so that we can still hear the sound from both guitar
-the sound from both guitar Tracks. Now we can control the volume of both
+tracks. Now we can control the volume of both guitar tracks together by changing
-guitar Tracks together by changing the Fader of the Guitar Bus. What's
+the fader of the _Guitar_ bus. What's more, we can now add plugins to the Guitar
-more, we can now add Plugins to the Guitar Bus to process the sound of
+Bus to process the sound of both guitar Tracks together.
-both guitar Tracks together.
 
 ### Track- or Bus-specific views of the Patchbay
 
-The Audio Connection Manager (Patchbay) that you open with **Alt + P** shows you 
+The _Audio Connection Manager_ (Patchbay) that you open with **Alt + P** shows you 
 the complete matrix of every single source and every single destination
 available in Ardour. Sometimes this is too much: you just want to quickly change 
 the routing of a single track input or output, for example. Ardour allows you to 
 access a relevant subset of Patchbay connections when you click directly on the 
-Inputs or Outputs button of a Track or Bus in the Mixer Strip.
+**Inputs** or **Outputs** button of a track or bus in the mixer strip.
 
-The Inputs button is at the top, and the Outputs button is on the bottom of the 
+The **Inputs** button is at the top, and the **Outputs** button is on the bottom
-strip. Clicking on either one will show you a menu of connection options. In the 
+of the  strip. Clicking on either one will show you a menu of connection
-screenshot below, for example, you would click on the "1/2" button right under
+options. In the  screenshot below, for example, you would click on the **1/2**
-the track name "Guitar-1" in order to access this menu:
+button right under the track name "Guitar 1" in order to access this menu:
 
-![Editor Mixer In Out](en/Ardour4_Editor_Mixer_In_Out.png)
+![Editor Mixer In Out](en/ardour7-editor-mixer-in-out.png)
 
-You may select a connection right there from the menu, or choose "Routing Grid" 
+You may select a connection right there from the menu, or choose _Routing Grid_ 
-to see a simpler version of the Audio Connection Manager with only the Inputs 
+to see a simpler version of the _Audio Connection Manager_ with only the
-or Outputs of the selected Track or Bus. 
+**Inputs** or **Outputs** of the selected track or bus. 
 
 ### All Ardour connections are JACK connections
 
-It is important to realize that any routings that you make or disconnect
+It is important to realize that any routings that you make or disconnect from
-from within Ardour are in fact JACK routings, which you can see from
+within Ardour are in fact JACK routings, which you can see from other
-other applications like Qjackctl, Catia, or JackPilot, depending on your
+applications like _Qjackctl_ or _Catia_, depending on your operating system.
-Operating System. Below is an example of a Catia window (Linux only)
+Below is an example of a _Catia_ window (Linux only) displaying the same JACK
-displaying the same JACK connections discussed above:
+connections discussed above:
 
 ![Catia](en/Ardour4_Catia_Example.png) 
 
 Continuing
 ----------
 
-In this chapter, we covered how to manage Routing inside Ardour, or
+In this chapter, we covered how to manage routing inside Ardour, or between
-between Ardour and the sound card. However, one of the strengths of
+Ardour and the sound card. However, one of the strengths of using the JACK
-using the JACK system is that it can also manage connections between
+system is that it can also manage connections between applications on the same
-applications on the same computer. To gain a better understanding of how
+computer. To gain a better understanding of how this works, please continue to
-this works, please continue to the chapter **Routing Between
+the chapter _Routing Between Applications_. If you would prefer to work only
-Applications**. If you would prefer to work only with Ardour, then skip
+with Ardour, then skip ahead to the section on _Arranging Tracks_.
-ahead to the section on **Arranging Tracks**.
 
-Next: [ROUTING BETWEEN APPLICATIONS](../routing-between-applications) or [ARRANGING TRACKS](../arranging-tracks)
+NEXT: [ROUTING BETWEEN APPLICATIONS](../routing-between-applications) or 
-
+[ARRANGING TRACKS](../arranging-tracks)
-
-