Document unsynchronized HDMI/SDI output.

[nageru-docs] / audio.rst

diff --git a/audio.rst b/audio.rst
index e17a2acd2bb5807a3602e9d63e77414f86b9bbfa..bb6876ecb85f5da3cf9c99a0428ab4ff4025dbf8 100644 (file)
--- a/audio.rst
+++ b/audio.rst
@@ -23,8 +23,7 @@ use, reusing such a mix isn't the worst choice you can make.
 Simple mode
 -----------
 
 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
+**Simple** audio mode is the default. 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 available.
 
 audio processing chain; however, in many cases, you won't need to
 understand or twiddle any of the knobs available.
 


@@ -136,7 +135,7 @@ of taste (and also depends on the speaker), but the main point
 is that it gets rid of low-frequency hum and a lot of the background
 noise that is not related to the speaker's voice. (If you were
 producing music, you'd probably want it there to make room for
 is that it gets rid of low-frequency hum and a lot of the background
 noise that is not related to the speaker's voice. (If you were
 producing music, you'd probably want it there to make room for

-music *under* it, but the you'd want it higher than the default 120 Hz.)
+music *under* it, but then you'd want it higher than the default 120 Hz.)

 
 Next comes a chain of no less than four compressors. They are
 based on the same basic structure, but have very different settings,
 
 Next comes a chain of no less than four compressors. They are
 based on the same basic structure, but have very different settings,


@@ -322,14 +321,14 @@ headroom, while some are much more variable and need tighter settings.
 Nearly at the top (and nearly first in the chain), there's the EQ section. The **lo-cut** is again
 well-known from the simple audio mode (the filter is separate for each
 bus, the cutoff **frequency** is the same across all buses),
 Nearly at the top (and nearly first in the chain), there's the EQ section. The **lo-cut** is again
 well-known from the simple audio mode (the filter is separate for each
 bus, the cutoff **frequency** is the same across all buses),

-but there's now also a simple **three-band EQ** per bus. Simply ask the speaker
+but there's now also a simple **three-band EQ** per bus. Ask the speaker

 to talk normally for a bit, and tweak the controls until it sounds good.
 People have different voices and different ways of holding the microphone,
 and if you have a reasonable ear, you can use the EQ to your advantage to
 make them sound a little more even on the stream. Either that, or just
 put it in neutral, and the entire EQ code will be bypassed.
 
 to talk normally for a bit, and tweak the controls until it sounds good.
 People have different voices and different ways of holding the microphone,
 and if you have a reasonable ear, you can use the EQ to your advantage to
 make them sound a little more even on the stream. Either that, or just
 put it in neutral, and the entire EQ code will be bypassed.
 

-Finally (or, well, first), since 1.7.3, there's the **stereo width** knob.
+Finally (or, well, first), there's the **stereo width** knob.

 At the default, 100%, it makes no change to the signal, but if you turn it
 to 0% (at the middle), the signal becomes perfect mono. Between these two,
 there's a range where the channels leak partially over into each other.
 At the default, 100%, it makes no change to the signal, but if you turn it
 to 0% (at the middle), the signal becomes perfect mono. Between these two,
 there's a range where the channels leak partially over into each other.


@@ -415,7 +414,7 @@ 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 frustrating procedure.
 (Actually, even with a reference sheet, it probably is.) Thus, the preferred
 controller and number numbers the different physical knobs and faders
 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
+way is by autosensing; select the given mapping with the mouse

 and use the control you want to bind it to, and Nageru automatically
 fills it in.
 
 and use the control you want to bind it to, and Nageru automatically
 fills it in.
 


@@ -465,7 +464,7 @@ same position for the two controllers. (There is a similar problem
 when starting up Nageru for the first time, where the controllers
 are not necessarily in the place matching Nageru's startup settings.)
 Some more expensive controllers support *motorized faders*, where
 when starting up Nageru for the first time, where the controllers
 are not necessarily in the place matching Nageru's startup settings.)
 Some more expensive controllers support *motorized faders*, where

-the host can simply tell the control to move to the right place
+the host can tell the control to move to the right place

 and thus solve the problem, but Nageru does not currently support them.
 
 .. image:: images/highlight.png
 and thus solve the problem, but Nageru does not currently support them.
 
 .. image:: images/highlight.png