diff --git a/content/recording-audio/understanding-routing/en/Ardour4_Ardour_Connection_Manager_4.png b/content/recording-audio/understanding-routing/en/Ardour4_Ardour_Connection_Manager_4.png deleted file mode 100644 index 87866d9..0000000 Binary files a/content/recording-audio/understanding-routing/en/Ardour4_Ardour_Connection_Manager_4.png and /dev/null differ diff --git a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_1.png b/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_1.png deleted file mode 100644 index f0ce511..0000000 Binary files a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_1.png and /dev/null differ diff --git a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_2.png b/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_2.png deleted file mode 100644 index 51c9af2..0000000 Binary files a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_2.png and /dev/null differ diff --git a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_3.png b/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_3.png deleted file mode 100644 index ff26ea4..0000000 Binary files a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_3.png and /dev/null differ diff --git a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_5.png b/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_5.png deleted file mode 100644 index 0562da7..0000000 Binary files a/content/recording-audio/understanding-routing/en/Ardour4_Audio_Connection_Manager_5.png and /dev/null differ diff --git a/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-1.png b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-1.png new file mode 100644 index 0000000..1a954f3 Binary files /dev/null and b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-1.png differ diff --git a/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-2.png b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-2.png new file mode 100644 index 0000000..fe0a589 Binary files /dev/null and b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-2.png differ diff --git a/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-3.png b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-3.png new file mode 100644 index 0000000..0c6b1ad Binary files /dev/null and b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-3.png differ diff --git a/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-4.png b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-4.png new file mode 100644 index 0000000..f00693b Binary files /dev/null and b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-4.png differ diff --git a/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-5.png b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-5.png new file mode 100644 index 0000000..32d9614 Binary files /dev/null and b/content/recording-audio/understanding-routing/en/ardour7-audio-connection-manager-5.png differ diff --git a/content/recording-audio/understanding-routing/en/ardour7-drawing-connection-lines.gif b/content/recording-audio/understanding-routing/en/ardour7-drawing-connection-lines.gif new file mode 100644 index 0000000..cd3c85d Binary files /dev/null and b/content/recording-audio/understanding-routing/en/ardour7-drawing-connection-lines.gif differ diff --git a/content/recording-audio/understanding-routing/index.en.md b/content/recording-audio/understanding-routing/index.en.md index 4a383e9..d0e1652 100644 --- a/content/recording-audio/understanding-routing/index.en.md +++ b/content/recording-audio/understanding-routing/index.en.md @@ -52,17 +52,16 @@ in the bottom. This means that the matrix you see displays connections from available hardware sound sources (for example, a microphone), into existing Ardour tracks.  -![ACM 1](en/Ardour4_Audio_Connection_Manager_1.png)  +![ACM 1](en/ardour7-audio-connection-manager-1.png)  The green dots represent a connection. The screenshot above tells us that -incoming sounds from "*system: capture\_1*" (the first input source of your -soundcard, or the built-in microphone of your laptop) are going into Ardour -track named "*Audio 1*", and also that incoming sounds from "*system: -capture\_1*" and "*system: capture\_2*" are respectively going into the Left and -Right inputs of Ardour track named "*Audio 2.*" +incoming sounds from _capture\_1_ (the first input source of your soundcard, or +the built-in microphone of your laptop) are going into Ardour track named _Audio +1_, and also that incoming sounds from _capture\_2_ are going into input of +Ardour track named _Audio 2_. -Notice we can see that "*Audio 1*" is a Mono track because it only has one -connection slot, while track "*Audio 2*" is Stereo since it has two slots (Left +Notice we can see that _Audio 1_ is a Mono track because it only has one +connection slot, while track _Audio 2_ is Stereo since it has two slots (Left and Right). The next screenshot shows the signal path from _Ardour Tracks_ (selected @@ -70,10 +69,10 @@ vertical tab) into Ardour busses (selected horizontal tab). As mentioned earlier, the default setting for all _Ardour Tracks_ is that their sound goes to the _Master_ bus. -![ACM 2](en/Ardour4_Audio_Connection_Manager_2.png) +![ACM 2](en/ardour7-audio-connection-manager-2.png) -Note: remember that "*Audio 1*" is a Mono track? We saw it in the earlier -screenshot that "*Audio 1*" only has one input slot. But now on the screenshot +Note: remember that _Audio 1_ is a Mono track? We saw it in the earlier +screenshot that _Audio 1_ only has one input slot. But now on the screenshot above you see that "Audio 1" has two outputs (Left and Right). This is normal: we define whether a track is Mono or Stereo by its *number of inputs*, not outputs. Mono tracks will hold a single channel of audio, but you can still @@ -84,9 +83,9 @@ Finally, let's explore a couple more tabs in the _Audio Connection Manager_ to see the sound going from the _Master_ bus to the actual hardware outputs (your loudspeakers or headphones): -![ACM 3](en/Ardour4_Audio_Connection_Manager_3.png) +{{< figure src="en/ardour7-audio-connection-manager-3.png" alt="ACM3" >}} -As you can see, the selected source tab is now "*Ardour Busses*", and the +As you can see, the selected source tab is now _Ardour Busses_, and the destination tab is _Hardware_. This session happens to have only one bus, the default "master out". The green dots show that all sounds coming out of the _Master_ bus are going to system playback 1 and 2, which are the outputs of your @@ -100,12 +99,18 @@ dot will appear to indicate the connection is made. To undo a connection, simply click on an existing green dot and it will disappear. +There is a neat trick you can use when you need to map many mono/stereo outputs +to many mono/stereo inputs: rather than making many single clicks, draw a +connection line. Here is how you do it: + +{{< figure src="en/ardour7-drawing-connection-lines.gif" alt="Drawing connection lines" >}} + ### Practical example of routing to a bus In the following example session, there are two guitar tracks and one unused bus called _Guitar_ bus, all Stereo. -![ACM 4](en/Ardour4_Ardour_Connection_Manager_4.png)  +![ACM 4](en/ardour7-audio-connection-manager-4.png)  Suppose you want to send the output from the two guitar tracks to the _Guitar_ bus instead of the _Master_ bus. This can be useful to control the volume of @@ -119,29 +124,29 @@ destinations (horizontal bottom tabs). Undo existing connections from both tracks to _Master_. Then create connections from both tracks to _Guitar_ bus. The final result would look like this: -![ACM 5](en/Ardour4_Audio_Connection_Manager_5.png)  +![ACM 5](en/ardour7-audio-connection-manager-5.png)  Now both guitar tracks are routed to the _Guitar_ bus, and no longer directly -connected to the _Master_ bus. We then make sure that the _Guitar_ bus is, by its -turn, routed to the _Master_ bus (the output routing of a bus is edited in the -same way as for a track), so that we can still hear the sound from both guitar -tracks. Now we can control the volume of both guitar tracks together by changing -the fader of the _Guitar_ bus. What's more, we can now add plugins to the Guitar -Bus to process the sound of both guitar Tracks together. +connected to the _Master_ bus. We then make sure that the _Guitar_ bus is, by +its turn, routed to the _Master_ bus (the output routing of a bus is edited in +the same way as for a track), so that we can still hear the sound from both +guitar tracks. Now we can control the volume of both guitar tracks together by +changing the fader of the _Guitar_ bus. What's more, we can now add plugins to +the Guitar Bus to process the sound of 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 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 +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. The **Inputs** button is at the top, and the **Outputs** button is on the bottom of the strip. Clicking on either one will show you a menu of connection options. In the screenshot below, for example, you would click on the **1/2** -button right under 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/ardour7-editor-mixer-in-out.png) @@ -170,4 +175,4 @@ the chapter _Routing Between Applications_. If you would prefer to work only with Ardour, then skip ahead to the section on _Arranging Tracks_. NEXT: [ROUTING BETWEEN APPLICATIONS](../routing-between-applications) or -[ARRANGING TRACKS](../arranging-tracks) +[ARRANGING TRACKS](../../editing-sessions/arranging-tracks/)