X-Git-Url: https://git.sesse.net/?p=nageru-docs;a=blobdiff_plain;f=audio.rst;h=58e3ed07a71df0f3d11c2dc144e8f5ac1abfe4c6;hp=94b31b63e689e388e96938ce51d9afd36626207f;hb=b3f0e3e5c219318325bc0be1653e31042d234399;hpb=0f110ea32b84bee95b9f9662d1824e82cb5dcac7

diff --git a/audio.rst b/audio.rst
index 94b31b6..58e3ed0 100644
--- a/audio.rst
+++ b/audio.rst
@@ -26,7 +26,7 @@ Simple mode
 **Simple** audio mode is the default, and was the only mode available
 up until Nageru 1.4.0. Despite its name, it contains a powerful
 audio processing chain; however, in many cases, you won't need to
-understand or twiddle any of the knobs availale.
+understand or twiddle any of the knobs available.
 
 Simple mode allows input from only a single source, and that source
 has to be one of the capture cards. (You choose which one by right-clicking
@@ -126,7 +126,7 @@ The audio strip
 
 The audio strip contains controls for the processing chain for the audio from
 start to end, left to right. Note that by default, everything is enabled;
-if you have a premade audio mix that you are confident that you
+if you have a pre-made audio mix that you are confident that you
 want 1:1 into the stream, you can start Nageru with the “--flat-audio”
 flag, that instead starts with everything disabled.
 
@@ -169,7 +169,7 @@ the distinction won't matter, but for multichannel, the previous
 effects are separate per-bus and the remaining are applied
 after the mix. (More on this below.) The mastering section begins
 with a **limiter**, basically a compressor with very high ratio.
-It's there as an emergency brake for really loud compressors
+It's there as an emergency brake for really loud sounds
 that got through the other compressors—a classic example is a
 speaker suddenly coughing, or a very loud bass drum. This prevents
 both clipping and blowing out the speakers' ears.
@@ -220,7 +220,8 @@ The input mapping dialog should be pretty much self-explanatory;
 you can use the + button to add a new bus, and the - button to remove
 the currently selected one (you select by clicking on it). The up and
 down buttons rearrange the order by moving the currently selected bus
-up or down, if possible.
+up or down, if possible. Note that you can create a mono bus by
+assigning the same input channel to the left and right inputs.
 
 Because mappings can be tedious to setup, you wouldn't want to set up
 a complicated one every time you started Nageru. Therefore, mappings
@@ -284,7 +285,7 @@ effect as pulling the fader all the way down, ie., it will make the bus
 go all silent.
 
 Then there's the **peak meter** to the left of that. For each bus, unlike
-for the meters used for mastering (see :ref:`audio meters`),
+for the meters used for mastering (see :ref:`audio-meters`),
 you don't want to know loudness; you want to know recording levels,
 so this is a peak meter, *not* a loudness meter. (There's some holdoff
 so you can see the actual peaks over a short period.) In particular,
@@ -391,7 +392,7 @@ Creating and updating mappings
 
 Unless you have a reference sheet for your MIDI controller, specifying which
 controller and number numbers the different physical knobs and faders
-emit, inputting these numbers by hand can be a frustating procedure.
+emit, inputting these numbers by hand can be a frustrating procedure.
 (Actually, even with a reference sheet, it probably is.) Thus, the preferred
 way is by autosensing; simply select the given mapping with the mouse
 and use the control you want to bind it to, and Nageru automatically
@@ -446,4 +447,12 @@ Some more expensive controllers support *motorized faders*, where
 the host can simply tell the control to move to the right place
 and thus solve the problem, but Nageru does not currently support them.
 
-(TODO: write about highlighting)
+.. image:: images/highlight.png
+
+To help you know which bank is active (or even that you have a MIDI
+controller connected at all), the currently mapped controller have
+a green **activity highlight**. When you switch banks, the highlight
+also updates—a controller is only highlighted if its mapping is
+active in the currently selected bank. This way, it is easy to see
+which controllers are currently controllable by MIDI, and which ones
+that are not.