Polycom SoundStructure C16 Design Manual page 160

Note: Muting SoundStructure Microphones
In pre-1.3 SoundStructure firmware, if the SoundStructure system's microphones
are muted independently of the Polycom
Video Codec
In 1.3 SoundStructure firmware and later, SoundStructure Events may be used to
link the SoundStructure mute to the
Note: Muting Audio Not Supported in CLink2 Interface
No audio paths are muted internal to the Polycom
mute command is sent to an
SoundStructure device over the CLink2 interface. The muting must occur within the
SoundStructure device.
Any mute command sent to the Video Codec triggers the mute command shown above which causes all
the signals on the SoundStructure device that are members of the "Mics" virtual channel group to be muted
or unmuted, respectively. By default the "Mics" virtual channel group is created by SoundStructure Studio
and includes all the local microphone virtual channels. A SoundStructure command status message is sent
out to the SoundStructure control ports indicating the mute status has changed.
Muting the SoundStructure microphones does not affect the routing of an attached PSTN telephone caller
on the SoundStructure to the remote Video Codec participants. In other words, by default the local
SoundStructure participants is muted to all remote participants while the remote telephony participants and
remote video participants are able to talk to each other.
Using Advanced Muting Applications
By default, a SoundStructure design automatically defines the "Mics" virtual channel group and places all
the microphones in the design in that group. The membership of this group may be changed and other
signals placed into the "Mics" group if it is desired to change the behavior of how the mute command from
the Video Codec maps to the audio signals within a SoundStructure system. It is possible to put line level
input sources (such as program audio) or even the output signal that is sent to the Video Codec into the
"Mics" group and have those signals be affected when the Polycom Video Codec mute status is changed.
Although the name of the group is "Mics", any virtual channel can be part of the group.
As another example, it is possible to rename the current "Mics" virtual channel group to another name and
create a submix called "Mics" and have that virtual channel be muted instead of the default "Mics" group.
This could be used to allow in-room reinforcement, for example, while the "Mics" submix would be muted to
prevent that audio from being transmitted to the remote participants.
There is tremendous design flexibility by mapping the Video Codec Mute command to affect the "Mics"
virtual channel or virtual channel group. If there is no "Mics" virtual channel or virtual channel group defined,
then no audio paths are muted when the end user mutes the Polycom Video Codec system directly.
Polycom, Inc.
mute status may not reflect the actual SoundStructure mute status.
Video Codec
Video Codec
Video Codec
system, the Polycom
mute and vice versa.
Video Codec
system when a
system that is connected to a
160