Using Events, Logic, And Ir; Understanding Events; Sources - Polycom SoundStructure C16 Design Manual

Using Events, Logic, and IR

This chapter introduces the new concept of Events and how events may be created and used to control the
behavior of SoundStructure systems including using the logic input and output capabilities.

Understanding Events

SoundStructure Studio and firmware version 1.3 introduces the concept of Events. Events are built from
sources, triggers, and actions as described in the following sections. Events are used to connect both
external stimuli, such as logic input pins or IR key presses, and internal stimuli such as mute and gating
status, to control settings within SoundStructure such as executing presets, or muting microphones. Events
are also used to integrate the Polycom IR remote controller with a SoundStructure device, allowing the
different key presses to execute functions within SoundStructure such as taking the PSTN interface offhook,
dialing digits, or muting microphones.

Sources

With an event the source defines the set of parameters that can be used to make something happen within
SoundStructure. Sources may be button pushes, IR key presses, or particular SoundStructure parameters.
The event sources that are allowed within SoundStructure are shown in the following table.
SoundStructure Event Sources
Event Sources (parameter name)
Safety mute (safety_mute)
Codec volume status (clink_volume)
Mute state (mute)
Gating status (am_gate)
Signal activity status (signal_active)
Phone ring (phone_ring)
Digital logic inputs held
(digital_gpio_held)
IR keypress (ir_key_press)
IR key held (ir_key_held)
Polycom, Inc.
Codec mute status (clink_mute)
Temperature status (dev_temp_status)
Call Status (clink_call_active)
Fader value (fader)
Camera gating status
(am_camera_gate)
Phone hook status (phone_connect)
Digital logic inputs (digital_gpio_state)
Analog logic input values
(digital_gpio_value)
233