A very common use of Logic Flows in Pathfinder Core PRO is to perform critical actions when an audio source or destination falls silent. For example, you could have a Logic Flow send you an email if the feed to the transmitter becomes silent. In order to accomplish this, you should use the Audio Alarms section of Pathfinder Core PRO.
Almost any audio source or destination in an Axia network can be monitored for silence, clipping, and audio presence.
Click the Audio Alarms link in the Navigation Bar to create, edit, and view audio alarms in the system.
Like other Pathfinder Core PRO pages, the Audio Alarms page updates dynamically as the alarm states change. Nine columns are displayed for each audio alarm.
The name of the alarm.
The type of clearing alarm. Types can either be Silence or Clipping. If you wish to know when audio returns, use a silence alarm and then select the correct value for the Alarm state in Logic Flows. This will be discussed in greater detail below.
This displays the IP address of the device where the source or destination being monitored exists.
Displays whether the IO being monitored is a source or destination.
Displays the port number on the device of the input or output being monitored.
Displays the amount of time in milliseconds the selected source or destination must be silent (or clipping if the type is clipping) before the alarm is triggered.
Displays the amount of time in milliseconds that the selected source or destination must be not silent (or not clipping if the type is clipping) before the alarm is released.
This column shows the current countdown to Alarm Time or Release Time.
For example, when a source being monitored goes silent, this column will show CountingToAlarm. Idle means that the source or destination is currently in the state represented by the AlarmState column.
This column represents the current state of the alarm. Possible values include Silent, AudioPresent, and Clipping. This value will only change after the source or destination maintains the requested state for at least the amount of time defined in the Alarm Time or Release Time properties.
Let’s create an example.
Click the Audio Alarms link in the Navigation Bar to create, edit, and view audio alarms in the system. On the Audio Alarms page, click the plus icon to add an Audio Alarm.
Complete the fields on the Audio Alarm Editor.
Audio Alarm Name
Type a name for this Alarm. In the example above, AirChain.
Select the alarm type from the drop-down list. Options include Silence and Clipping.
Alarm Time (ms)
Alarm time is the number of milliseconds the audio must be in the specified state before the alarm becomes active. The example above defines an alarm time of 15000ms or 1.5-seconds.
Alarm Release Time
Alarm release time is the amount of time the audio needs to be in the opposing state after an alarm has tripped before the alarm clears. The example above defines an alarm release time of 5000ms, or .5-seconds.
From the drop-down list, specify the channel the system should monitor to determine the alarm state. Options include Any, All, Left, or Right.
Select whether the alarm will be on a Source or Destination.
Click the ellipsis button to choose from the list of available sources or destinations.
After clicking on the ellipsis button to open the Select IO screen (either Select Source or Select Destination, depending on how this alarm is configured), select the source or destination from the IO list and click Select.
Click Apply to save your changes to this alarm.
The Audio Alarms list view, like most lists in Pathfinder Core PRO, show alarm status changes in real time.
For example, the Timer State and Alarm State values will dynamically update in this list as alarm states change. This can be an excellent troubleshooting tool.
Once an alarm has been created, it is available for use in Logic Flows. In the Logic Flow below, we have created a Logic Flow that sends an email whenever the SilenceAlarm audio alarm has its Alarm State switch to Silent:
If we wanted to perform a different action when the alarm releases (audio returns), we would use the AudioPresent value in the translation list. For example, the following Logic Flow will light a button when audio is present and cause it to flash when there is silence.
More possible audio alarm Logic Flows examples are covered in the Email Messages section since that is a common action to be taken when things get quiet.