Update Using Sends

content/mixing-sessions/using-sends/index.en.md

@@ -2,132 +2,142 @@
 title = "Using sends"
 chapter = false
 weight = 5
-#pre = "<b>1. </b>"
 +++
 
-A *Send* is just an extra output for a Track or Bus with its
-own separate Fader that can be used to route the signal to other points in
-Ardour.
+A _Send_ is just an extra output for a track or bus with its own separate
+fader that can be used to route the signal to other points in Ardour.
 
-Also known as **Auxiliary Sends**, they tap the signal at a specific point in
-the signal flow (pre-fader, post-fader, before or after EQs and other
-plugins, etc.) and send a copy of that signal somewhere else, without
-affecting the normal signal flow downwards to the channel fader.
+Also known as _auxiliary sends_, they tap the signal at a specific point in
+the signal flow (pre-fader, post-fader, before or after EQs and other plugins,
+etc.) and send a copy of that signal somewhere else, without affecting the
+normal signal flow downwards to the channel fader.
 
-In Ardour, you can easily add **Sends** to Tracks and Busses through the Mixer Strip. Sends are Processors, just like Plugins.
+In Ardour, you can easily add _sends_ to tracks and busses through the mixer
+strip. Sends are processors, just like plugins.
 
 ## When is a Send useful? 
 
-In earlier chapters, we built a drum kit pattern with four separate tracks: kick, snare, hihat, and clap.
-Let's say now you'd like to add a reverb to the drums. You could of course add a separate plugin for each individual track,
-and tweak their settings separately, but this method unnecessarily increases the amount of work. Every time you want 
-to change a reverb setting across the board for all drums, you'd have to open all four reverb plugins and change them in the same way.
+In earlier chapters, we built a drum kit pattern with four separate tracks:
+kick, snare, hihat, and clap. Let's say now you'd like to add a reverb to the
+drums. You could of course add a separate plugin for each individual track,
+and tweak their settings separately, but this method unnecessarily increases
+the amount of work. Every time you want to change a reverb setting across the
+board for all drums, you'd have to open all four reverb plugins and change
+them in the same way.
 
-*This is where Sends come in handy: you can use them to add a particular effect to a set of Tracks without creating multiple
-instances of the same Plugin.*
+*This is where sends come in handy: you can use them to add a particular
+effect to a set of tracks without creating multiple instances of the same
+plugin.*
 
 Here's the overview of how we will do this:
 
-* Create a single Bus with the desired Plugin.
-* Add a Send to each drum track to which you want to apply the effect.
-* Route these Sends to the Bus.
+* Create a single bus with the desired plugin.
+* Add a send to each drum track to which you want to apply the effect.
+* Route these sends to the bus.
 
 ## Creating the Bus and adding a Plugin
 
-Create a Bus (menu *Track > Add Track, Bus, or VCA...*), name it appropriately, and add a
-Plugin in the Pre-Fader Region (right-click just above the Fader blue
-rectangle in the Processor Box), as discussed in the chapter **Using
-Plugins**.
+Create a bus (menu *Track > Add Track, Bus, or VCA...*), name it
+appropriately, and add a plugin in the pre-fader region (right-click just
+above the fader's blue rectangle in the processor box), as discussed in the
+previous chapter, _Using Plugins_.
 
-In this example, we have created a Mono Bus called "*DRUMS*", and added
-the "*Freeverb*" Reverb LADSPA Plugin to the bus.
+In this example, we have created a mono bus called _Drums_, and added the
+_ACE Reverb_ plugin to the bus.
 
-![sends1](en/Ardour4_Sends_1.png) 
+![sends1](en/ardour7-ace-reverb-in-mixer-strip.png) 
 
 ### Bus inputs
 
-The "-" display in the Bus Input button indicates that nothing
-is routed to this bus yet. We will take care of this later.
+The "-" display in the bus input button indicates that nothing is routed to
+this bus yet. We will take care of this later.
 
 ### Bus output
 
-Before routing a send to this Bus, first make
-sure that the Bus outputs are Routed to the Master Bus, as shown below
-(button at bottom reads "*master*").
+Before routing a send to this bus, first make sure that the bus outputs are
+routed to the _Master_ bus, as shown below (button at bottom reads "*master*").
 
 ![sends2](en/Ardour4_Sends_2.png) 
 
-Also, open the Plugin Window (double click on the Freeverb rectangle) and set the Plugin's signal mix to 1.0 Wet
-Level and 0.0 Dry Level. 
+Also, open the plugin window (double click on the _ACE Reverb_ rectangle) and
+set the plugin's signal mix to 1.0 _Blend_ value.
 
-![sends3](en/Ardour4_Sends_3.png) 
+![sends3](en/ardour7-ace-reverb-settings.png) 
 
-This ensures that the Bus carries all of the processed signal (the 'Wet'
-signal) from the Plugin, and none of the unprocessed signal (the 'Dry'
-signal) to the Master Bus. Remember, the unprocessed, 'clean' signals
-are still available from their original tracks, so there is no need to
-duplicate them in this Bus.
+This ensures that the bus carries all of the processed signal from the plugin,
+and none of the unprocessed signal to the _Master_ bus. Remember, the
+unprocessed, 'clean' signals are still available from their original tracks,
+so there is no need to duplicate them in this bus.
 
 ## Creating and Routing Sends
 
-Now we can create Sends in the other Tracks and route them to the Bus
-inputs.
+Now we can create sends in the other tracks and route them to the bus inputs.
 
-Like Plugins, Sends are also created in the Processor Box. Go to each of
-your drum tracks, right-click in empty space of the Processor Box, and create a *New Aux
-Send...* directed to the appropriate Bus (in our case, named DRUMS).
+Like plugins, sends are also created in the processor box. Go to each of your
+drum tracks, right-click in empty space of the processor box, and create a
+_New Aux Send..._ directed to the appropriate bus (in our case, named _Drums_).
 
-![sends4](en/Ardour4_Sends_4.png) 
+![sends4](en/ardour7-adding-aux-send.png) 
 
 {{% notice tip %}}
-If you do *not* see the "*New Aux Sends...*" option in the menu, it's probably because you did not create any bus yet. Go back to the previous step to create the bus.
+If you do *not* see the _New Aux Sends..._ option in the menu, it's probably
+because you did not create any bus yet. Go back to the previous step to create
+the bus.
 {{% /notice %}}
 
-You should now see the Send displayed in the Processor Box:
+You should now see the send displayed in the processor box:
 
-![postfader](en/Ardour4_Post-Fader_Send.png) 
+![postfader](en/ardour7-post-fader-send.png) 
 
-The little "*Send*" slider you see just below the green rectangle is the Send Fader, which 
-controls how much sound will be sent from this Track to the Bus.
+The little _Send_ slider you see just below the green rectangle is the send
+fader, which  controls how much sound will be sent from this track to the bus.
 
 ### Post-Fader vs Pre-Fader Sends
 
-Notice that the image above shows a Post-Fader Send (it sits "*after*" the Fader rectangle).
-In Post-Fader Sends, the Send Level is controlled *first* by both the Track/Bus Fader and *second* by the
-Send Fader.
+Notice that the image above shows a post-fader send (it sits _after_ the fader
+rectangle). In post-fader sends, the send level is controlled _first_ by both
+the track/Bus Fader and _second_ by the send fader.
 
-In a *Pre*-Fader Send, on the other hand, the Send Level is controlled only
-by the Send Fader, independently of the Track/Bus Fader. A Pre-Fader Send would look like this:
+In a _pre_-fader send, on the other hand, the send level is controlled only by
+the send fader, independently of the track/bus fader. A pre-fader send would
+look like this:
 
-![prefader](en/Ardour4_Pre-Fader_Send.png) 
+![prefader](en/ardour7-pre-fader-send.png) 
 
-You can drag the Send rectangle up and down the Processor box to make it Pre- or Post-Fader as needed.
+You can drag the send rectangle up and down the processor box to make it pre-
+or post-fader as needed.
 
 {{% notice tip %}}
-The choice of Pre- or Post-Fader depending on the type of effect Plugin
+The choice of pre- or post-fader depending on the type of effect plugin
 used and the desired result. For this exercise, either one will work.
 {{% /notice %}}
 
-A Send behaves just like any other Plugin in the Processor Box.
-You can deactivate it temporarily by clicking on the small "LED", and you can right click on the rectangle to access other options, including "*Delete*".
+A send behaves just like any other plugin in the processor box. You can
+deactivate it temporarily by clicking on the small LED, and you can right
+click on the rectangle to access other options, including _Delete_.
 
 ### Send Fader
 
-To control level of each Send, simply click and drag the Send Fader to increase or decrease its volume.
+To control the level of each send, simply click and drag the send fader to
+increase or decrease its volume.
 
 ![sendfader](en/Ardour4_Send_Fader.png) 
 
-The DRUMS Bus is now receiving the sum of all tracks, and applying the effect to it. A single Plugin applied to the Bus controls the effect for the mix of all drum sounds routed there. This way, you have independent control over the "dry" sound of the original tracks, and the "wet" sound of coming out of the Bus. 
+The _Drums_ bus is now receiving the sum of all tracks, and applying the effect
+to it. A single plugin applied to the bus controls the effect for the mix of
+all drum sounds routed there. This way, you have independent control over the
+"dry" sound of the original tracks, and the "wet" sound of coming out of the
+Bus. 
 
-Because Sends are very useful for this kind of work with effect Plugins, they are also commonly
-called "Effect Sends".
+Because sends are very useful for this kind of work with effect plugins, they
+are also commonly called "Effect Sends".
 
 ## Continuing
 
-Now that you know how to **Add Plugins** to a Track, as well as how to
-**Add Sends** to Tracks to create Plugin Busses usable by any number of
-Tracks, it might be helpful to learn about a few other Plugins useful in
-the Mixing Process. Please continue on to the following chapters
-covering **Dynamics** and **Equalizing**.
+Now that you know how to add plugins to a track, as well as how to add sends
+to tracks to create plugin busses usable by any number of tracks, it might be
+helpful to learn about a few other plugins useful in the mixing process.
+Please continue on to the following chapters covering _dynamics_ and
+_equalizing_.
 
 Next: [DYNAMICS](../dynamics)