glados.no/_files/sound/bss/london/manual/MAIN/Gated_Automixer.htm

343 lines
20 KiB
HTML
Raw Normal View History

2020-08-16 15:32:44 +02:00
<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="generator" content="Adobe RoboHelp 9">
<title>Gated Automixer</title>
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
<style title="hcp" type="text/css">
<!--
p.hcp1 { font-style:italic; }
span.hcp2 { font-weight:bold; }
p.hcp3 { font-style:normal; }
img.hcp4 { border:none; }
h4.hcp5 { font-size:12pt; }
p.hcp6 { font-weight:bold; }
span.hcp7 { font-weight:normal; }
p.hcp8 { font-weight:bold;
font-size:12pt; }
-->
</style>
</head>
<body>
<h1 class="firstHeading">Automixer Gated</h1>
<p>&#160;<img src="gated&#32;automixer.jpg" alt="" border="0"></p>
<h2>Overview</h2>
<p>The gated automixer is designed to replace a standard mixer and to provide
a degree of automatic mixing with little or no manual input. All channels
are gated to remove low level noise. As a signal is detected on a particular
channel the gate requests to open. However, the gated automixer may or
may not allow the gate to open based on a number of rules. These rules
allow the installer to specify a maximum number of open microphones (NOM)
as well as allocating priority levels to individual channels. The gated
automixer will manage the channels such that the number of open microphones
does not exceed the NOM value as well and ensuring the highest priority
channels take preference over lower priority channels.</p>
<h4>Priority Scheme</h4>
<p>Each channel of the gated automixer is allocated a priority between
1 and 32 (1 is the highest priority). As the channel gates try to open,
their priorities are compared and only the highest priority channels are
allowed to open. This means that higher priority channels will take preference
over lower priority channels. In some cases this may mean that an existing
channel will be muted because a higher priority channel has opened.</p>
<h4>NOM</h4>
<p>This parameter limits the maximum Number of Open Microphones (NOM) allowed
in the system. &#160;Numerous open microphones present in the system will
cause the ambient noise of the system to increase as well as causing potential
audio coupling (feedback or howling) between the open microphones and
the system speakers. &#160;The gated automixer keeps the ambient noise
to a minimum and prevents acoustic feedback by automatically reducing
the gain of the system. &#160;The amount of attenuation applied is determined
by the number of open mics.</p>
<h4>NOM Attenuation</h4>
<p>For every doubling of open channels (mics), the gated automixer will
reduce the gain by the amount of the NOM Attenuation parameter.</p>
<h4>Duck Gain</h4>
<p>Some applications require that higher priority channels not only take
preference when deciding which channels should be open, but also that
they should be louder than lower priority channels. The duck gain allows
you to specify how much a lower priority channel should be ducked by if
a higher priority channel is open.</p>
<h4>Default Mic and Last Mic</h4>
<p>In some circumstances the installer would want to allocate one microphone
as the <20>default<6C>. If all channels are below threshold then the default
microphone channel will open automatically.</p>
<p>If no default is set then the Last Mic setting can be used to leave
the last microphone on even though it has dropped below the threshold.</p>
<h4>Adaptive Threshold</h4>
<p>The level at which a gate opens is the channel threshold, however, in
some circumstances having a fixed threshold can be problematic. For example,
if an audience applauds loudly this may raise the level above the threshold
on many channels causing the gated automixer to open those channels in
error. To implement an adaptive threshold the <20>Threshold In<49> input is
typically connected to an ambient microphone. As the ambient level rises
then the gate thresholds also rise so that they are less likely to open.</p>
<h4>Cascaded Automixers</h4>
<p>The gated automixer is capable of being cascaded to create much larger
gated automixers. The gated automixers must be connected via BLU Link
because of the digital nature of the information being passed between
them. They cannot be connected via analog cards, digital cards or <a href="Cobranet&#32;Information.html">CobraNet</a>.
A number of cascaded gated automixers act as a single very large gated
automixer up to thousands of channels.</p>
<h2>Internals</h2>
<p>The internal audio processing for a single channel of the gated automixer
is shown below :-</p>
<p style="text-align: center;"><img src="mixer_internals.jpg" alt="" border="0"></p>
;
<ul type="disc">
<li class="p"><p>The input audio first passes through the channel gain
before being fed into both the Gate Threshold Detect and the Gate
Attenuation.</p></li>
<li class="p"><p>The Gate Threshold Detect monitors the audio level
to decide if the gate needs to open taking into account the current
level of the ambient input.</p></li>
<li class="p"><p>The output of the Gate Threshold Detect passes through
the Priority Logic which decides if the channel may actually open
and also the level of NOM attenuation and duck gain that should be
applied. All channels feed into the same Priority Logic so it can
decide which channels should come on based on their priorities and
the NOM etc.</p></li>
<li class="p"><p>The Priority logic then sends control signals to the
Gate Attenuation (to open or close the gate) and also to the NOM Attenuation
(to apply the NOM attenuation and duck gain).</p></li>
<li class="p"><p>The resulting signal is then mixed with all the other
channel outputs to create the output signal. If direct outputs are
enabled they are taken before the mixer.</p></li>
<li class="p"><p>In the case of a cascaded automixer the Priority Logic
communicates with the logic in the other automixers via the chain
signals to ensure that they all act as a single large automixer.</p></li>
</ul>
<p class="hcp1"><span class="hcp2">Note</span>:
- The NOM attenuation and duck attenuation are applied even when the gate
is closed and therefore the signal will be attenuated by the off gain
plus the nom attenuation and the duck gain. The reason for doing this
is to ensure that when the gate opens the channel is already at the correct
level. Also, if the NOM and duck gain were not applied to the <20>off<66> signal
then it would be possible for the <20>on<6F> signal to actually be quieter than
the <20>off<66> signal.</p>
<h2>Inputs and Outputs</h2>
<ul type="disc">
<li class="p"><p class="hcp3">The number of inputs can
be set from 2 to 96.</p></li>
<li class="p"><p class="hcp3">The output can be either
mono or stereo.</p></li>
<li class="p"><p class="hcp3">The direct out property
produces an output per channel.</p></li>
<li class="p"><p class="hcp3">The master option adds
a further Mix Input, Chain Input and Chain Output.</p></li>
<li class="p"><p class="hcp3">The slave option adds
a further Mix Input, Chain Input, and Chain Output.</p></li>
</ul>
<h2>Properties</h2>
<h4>Number of Channels:</h4>
<p class="hcp3">The number of input channels can be selected
between 2 and 96.</p>
<h4>Stereo:</h4>
<p class="hcp3">Set to &quot;Yes&quot; the gated automixer
will have a stereo pair of outputs, L and R. In Master or Slave mode there
will also be a Left and Right Mix Input</p>
<h4>Pan Law:</h4>
<p class="hcp3">The law of the pan controls may be set to
either -3.0dB, -4.5dB or -6.0dB. These figures relate to the attenuation
applied to each channel at the central pan position.</p>
<h4>Master/Slave Status:</h4>
<p class="hcp3">For expanding the mixer, either for making
a larger mixer within a device, or for splitting a mixer across more than
one device. The control signals are shared using two special versions
of the gated automixer <20> Master and Slave.</p>
<h4>Voice Band filters:</h4>
<p class="hcp3">Filtering may be included so that the automixing
action favours frequencies in the human vocal range. This helps the mixer
to distinguish between speech and noise, giving a voice signal a better
chance of 'winning' against a noise signal on another channel.</p>
<h4>Direct Outs:</h4>
<p class="hcp3">In addition to a single mixed output, the
individual channels may be output for further processing or mixing elsewhere.
These individual outputs are taken from before the mix but after any processing
such as priority logic, gain and so on are applied. &#160;Set to Yes if
Direct outputs are required.</p>
<p style="font-style: normal; font-weight: bold;">Channel Number Start:</p>
<p class="hcp1"><span style="font-style: normal;">Only available
for the slave option. &#160;Since the slave automixer is cascaded from
a master it is likely that you would want the channel numbering to continue
from the last channel number of the previous automixer.</span> &#160;</p>
<h2>Control Panel</h2>
<p><img src="GA_panel.jpg" alt="" width="699" height="661" border="0" class="hcp4"></p>
<h4 class="hcp5">Channel Controls</h4>
<p><span class="hcp2">Polarity</span> button for each input
for signal inversion.</p>
<p><span class="hcp2"><a name="Local_Gate_button_for_each_input._If_set_the_attack,_hold_and_release_settings_for_the_gate_are_specified_in_the_channel_strip_rather_than_in_the_Global_Gate_section."></a>Local
Gate</span> button for each input. If set the attack, hold and release
settings for the gate are specified in the channel strip rather than in
the <a href="Gated_Automixer.htm#Global_Gate_Controls">Global Gate</a> section.</p>
<p><span class="hcp2"><span class="hcp2">A</span>ttack</span>
control sets the gate attack time for the channel. Only available if the
Local Gate button is on.</p>
<p><span class="hcp2">Hold</span> control sets the gate hold
time for the channel. Only available if the Local Gate button is on.</p>
<p><span class="hcp2"><span><span><span class="hcp2">R</span></span></span>elease</span>
control sets the gate release time for the channel. Only available if
the Local Gate button is on.</p>
<p class="hcp6">Threshold <span class="hcp7">control
sets the gate threshold for the channel. This is the level at which the
gate opens. The gate threshold may be raised due to the &#160;<a href="Gated_Automixer.htm#Ambient_Controls">Adaptive
Threshold</a>.</span></p>
<p><span class="hcp2">Off Gain</span> control for each input:
Determines what maximum attenuation will be applied to the channel when
off.</p>
<p><span class="hcp2">Gate Override</span> button for each
input: Force the gate to open for that channel. The channel is still subjected
to priority logic so may still be muted.</p>
<p><span class="hcp2">Gate indicator</span> for each input
shows when a channel is above threshold (the gate wants to open).</p>
<p class="hcp6">Open indicator <span class="hcp7">for
each input shows when a channel is active.</span></p>
<p><span class="hcp2"><span class="hcp2">P</span>an</span>
control (stereo objects only)</p>
<p><span class="hcp2">Gain fader</span> for each input. This
controls the level of the channel's input before the automix logic is
applied.</p>
<p><span class="hcp2">Mute</span> button for each input.</p>
<p><span class="hcp2">Solo</span> control for each input
channel for quick identification of signals and level setting: Allows
only 'soloed' channels to be heard. &#160;Note the NOM count is invalid
when any channel is solo'ed.</p>
<p class="hcp6">! <span class="hcp7">This
is a 'solo-in-place' which impacts the main output.</span></p>
<p class="hcp6">Default Mic<span class="hcp7">.
One microphone can be set to be on as the default when all channels are
below the threshold.</span></p>
<p><span class="hcp2">Priority</span> control for each channel.
1 is the highest priority and 32 is the lowest.</p>
<p><span class="hcp2">Auto</span> <span class="hcp2">button</span>
assigns each channel to operate as either a conventional mixer channel
or an automated channel. By switching Auto to off the channel is completely
removed from the automix logic and NOM attenuation.</p>
<p><span class="hcp2">Signal Name</span> shows the name of
the input signal</p>
<h4 class="hcp5"><a name="Global_Gate_Controls" id="Global_Gate_Controls"></a>Global
Gate Controls</h4>
<p><span class="hcp2">Attack</span> control sets the gate
attack time for all channel gates with the exception of any channels which
have the <a href="Gated_Automixer.htm#Local_Gate_button_for_each_input._If_set_the_attack,_hold_and_release_settings_for_the_gate_are_specified_in_the_channel_strip_rather_than_in_the_Global_Gate_section.">Local
Gate</a> button set.</p>
<p><span class="hcp2">Hold</span> control sets the gate hold
time for all channel gates with the exception of any channels which have
the <a href="Gated_Automixer.htm#Local_Gate_button_for_each_input._If_set_the_attack,_hold_and_release_settings_for_the_gate_are_specified_in_the_channel_strip_rather_than_in_the_Global_Gate_section.">Local
Gate</a> button set.</p>
<p><span class="hcp2">Release</span> control sets the gate
release time for all channel gates with the exception of any channels
which have the <a href="Gated_Automixer.htm#Local_Gate_button_for_each_input._If_set_the_attack,_hold_and_release_settings_for_the_gate_are_specified_in_the_channel_strip_rather_than_in_the_Global_Gate_section.">Local
Gate</a> button set.</p>
<p><span class="hcp2">Hysteresis</span> control sets the
level below threshold that the gate uses when turning off.</p>
<p class="hcp8"><a name="Ambient_Controls"
id="Ambient_Controls"></a>Ambient
Controls</p>
<p><span class="hcp2">Threshold</span> control set the ambient
level at which the adaptive threshold starts. Above this level the gate
thresholds will be raised accordingly.</p>
<p><span class="hcp2">Attack</span> control sets the speed
at which the adaptive threshold logic responds to changes in the ambient
level.</p>
<p><span class="hcp2">Release</span> control sets the speed
at which the adaptive threshold logic responds to changes in the ambient
level.</p>
<p><span class="hcp2">Ambient meter</span> shows the current
ambient level.</p>
<p class="hcp8">NOM Controls</p>
<p><span class="hcp2">NOM</span> control sets the maximum
number of open microphones while NOM count displays the number of microphones
which are actually open.</p>
<p><span class="hcp2">Attenuation</span> control sets the
amount that the output gain is attenuated by per doubling of open channels.
For example, if the attenuation is -3dB and the number of open mics is
2 then -3dB of gain will be applied to the output. If the number of open
channels is 4 then -6dB of gain will be applied.</p>
<p><span class="hcp2">Speed</span> control sets the speed
at which the NOM attenuation is applied.</p>
<p><span class="hcp2">Last Mic</span> control tells the automixer
to leave the last open mic on even if the level drops below the gate threshold.</p>
<p><span class="hcp2">Duck Gain</span> control sets the amount
that lower priority channels are attenuated by if a higher priority channel
is also open.</p>
<p><span class="hcp2">Nom Attenuation meter</span> shows
the current NOM attenuation that is being applied.</p>
<p class="hcp8">Master Mix Controls</p>
<p><span class="hcp2">Master Gain</span> control for the
Main output(s)</p>
<p><span class="hcp2">Master Mute</span> button for the Main
output(s)</p>
<h2>Automixer Expansion</h2>
<p>It is possible to combine several gated automixers together so that
they act as one very large gated automixer. This makes use of the Master/Slave
Status setting in the Properties Pane and also makes use of the Chain
control signals. If the automixers are on different devices then the Chain
control signals can only be sent over <a href="BLU_link.html">BLU Link</a>.
The gated automixers are always connected in a ring with a single master
and one or more slaves.</p>
<h4>Connecting two Gated Automixers</h4>
<p>Connect the Chain Out of the master to the Chain In of the slave, and
the Chain Out of the slave to the Chain In of the master. If you require
the outputs of the two mixers to be combined, connect the Mix Out of the
slave to the Mix In of the master, then use the Mix Out of the master.</p>
<p>&#160;<img src="2GA_1.jpg" alt="" width="319" height="271" border="0" class="hcp4"><img src="2GA_2.jpg" alt="" width="404" height="269" border="0" class="hcp4"></p>
<h4>Connecting more than two Automixers</h4>
<p>Create one master and several slaves and connect the Chain Out of the
master to the Chain In of the first slave. Then <20>daisy chain<69> the Chain
Out of the slave to the Chain In of the next slave, and so on (in any
order) to the Chain In of the master. If you require the outputs of all
the mixers to be combined, 'daisy chain' the Mix Out of one slave to the
Mix In of the next slave and so on (in any order) to the Mix In of the
master, then use the Mix Out of the master.</p>
<p><img src="many_GA_1.jpg" alt="" width="314" height="541" border="0" class="hcp4"> &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;<img src="many_GA_2.jpg" alt="" width="407" height="541" border="0" class="hcp4"></p>
<h2>Notes on connecting several Gated Automixers</h2>
<ul type="disc">
<li class="p"><p>The Speed controls should be set the same on all linked
gated automixers for consistent operation.</p></li>
<li class="p"><p>The Chain signals can only be sent via <a href="BLU_link.html">BLU
Link</a> if the automixers are on different devices. Those signals
are digital information and rely on the bandwidth and low latency
of BLU Link for correct operation. They cannot be sent by any other
means. They are displayed using a different line color in London Architect
to help differentiate them from audio signals.</p></li>
<li class="p"><p>If you are using adaptive threshold then the ambient
signal must be connected to the Threshold In of all gated automixers
manually.</p></li>
<li class="p"><p>When connecting several automixers together the data
takes longer to circulate around the loop. The time it takes for the
data to circulate around the loop has an effect on the attack time
of the gates. The BLU Link network is low latency so under normal
circumstances the round trip time is very short and does not adversely
affect the gate attack time. However, in some very large BLU Link
rings with many slave gated automixers the round trip may become significant.
Switching the design to 96KHz will halve any communication delays
since the devices and the BLU Link network all run at double the speed.</p></li>
<li class="p"><p>When gated automixers are cascaded across 2 or more
devices you may require an indication that they are connected. &#160;For
this purpose an LED is available for use on custom control panels.
&#160;You can access this from the <a href="MAINDesign_tree.htm">design
tree</a> in the NOM folder for the gated automixer in each device.
&#160;Just drag and drop onto the custom panel. &#160;If for any reason
the link between automixers is broken (e.g. Blu link is pulled out)
the LED on your custom panel will go off. &#160;In the event of a
broken link, the slaves mute and the master reverts to fully functional
standalone. When the link is re-established, cascaded functionality
resumes (including any changes made to the masterslave(s) during broken
link). Whenever the link is established or broken an event is logged
in the <a href="MAINEvent_Log.htm">eventlog</a> and the LED set accordingly.</p></li>
</ul>
<h2>Generating the ambient from mics</h2>
<p><img src="image11.jpg" alt="" width="703" height="177" border="0" class="hcp4"></p>
<p>Sometimes it is not convenient to install a dedicated ambient microphone
and in those situations the signals from all the microphones can be summed
using a mixer to produce the ambient signal.</p>
<p class="hcp1"><span class="hcp2">Note: !</span>
This object is capable of raising signal levels beyond the clipping point,
so care should be exercised when using positive gain values.</p>
</body>
</html>