This document provides a brief overview of integrating QSC Q-SYS AES67 devices with AudioScience Iyo Dante products operating in AES67 mode, utilizing Q-SYS Designer with a Q-SYS Core 110f.  Understanding of Q-SYS Designer and AES67 Networking is assumed.


Important notes

  • AES67 mode in Dante Controller for the Iyo must remain enabled.
  •  The Core AES67 Transport IP address range must remain the default (239.69.xxx.xxx). 
  • Always disconnect any Iyo subscriptions to a Core Transmitter before changing the Transmitter’s channel count. 
  • The Iyo Dante AES67 Transmitters are only compatible with 8-channel Core AES67 Receivers. 
  • A Core should only be power cycled when all Transmitter flow sessions are disabled. In the event that there are active flows at the time of the power cycle, all Iyos on the network should be rebooted either by power cycling them or by using Dante Controller to remotely restart the Iyos.
  •  Core AES67 Transmitter flows should be assigned static Multicast Addresses.  Failure to do so will affect the Iyo plugin’s ability to reconnect to flows.    


Update Iyo Dante Firmware


Use Dante Firmware Update Manager to update the Iyo to the latest firmware, downloaded from the AudioScience Iyo web page.  If the Iyo does not appear in Firmware Update Manager, ensure the selected network interface in Update Manager and the Iyo are on the same subnet (see section 3 below for help).


Configure Iyo Network interface in Dante Controller


The Q-SYS Core and Iyo must be members of the same network subnet for the QSC plugin to communicate with the Iyo.

 

Use Dante Controller to discover and configure the network interface of the Iyo.  Iyos are in DHCP mode by default.  If a static IP is required, navigate to the Network Config tab and click ‘Manually configure an IP Address’. 


 

Figure 1 Assign static IP to Iyo

 

Dante Controller will display an error (see below) if the subnet of the Iyo and the selected Dante Controller network interface do not match.  The example below is an interface with a static IP address trying to communicate with a default Iyo connected to a network without a DHCP server.  Match the selected Dante Controller network interface subnet to the Iyo’s network interface subnet in order to configure the device.

 

 

  Figure 2 Dante Controller Iyo subnet mismatch


Add Iyo Dante plugin to Q-SYS Designer


From Q-SYS Designer, open Asset Manager (Tools > Show Q-SYS Asset Manager).  Search for and install the latest AudioScience Iyo Dante plugin.

 

From the “Plugins” grouping in the bottom right corner, find and drag “Iyo Dante” onto the canvas.  

 

 


Figure 3 Adding Iyo Dante Plugin

 

Iyo Model type selection


Click on the Iyo plugin and navigate to the ‘Properties’ window in Designer.  Use the ‘Model Type’ dropdown to select the Iyo version that matches your device.

 

 

 

    Figure 4 Iyo Dante plugin Model Type selection


Iyo Dante plugin overview


 

                                                                        Figure 5 Iyo Dante Plugin


Connect to an Iyo

With the Core running, navigate to the ‘Select a Device’ grouping and click on an Iyo from the dropdown list to establish a connection to the device.  NOTE: only devices of the type selected in the Model Type Properties field (see section 2) will appear in this list.

 

 

 

Figure 6 Device Connection

 

The status bar below the device selection dropdown indicates the current connection status between the Core and the Iyo.

 

 

 

      Figure 7 Device Connecting              Figure 8 Device Connection OK          Figure 9 Device Connection Error

Connecting Q-SYS Mic/Line In to Iyo Receive/Output


In Q-SYS Designer, route a Mic/Line In component to an AES67 Transmitter component

 

      Figure 10 QSC Input and AES67 Transmitter Components

 

 

Click “Enable” in the AES67 Transmitter configuration window

 

                                                     Figure 11 QSC AES67 Transmitter Configuration

 

 

In the Iyo plugin, search for the QSC Transmitter Stream Name (e.g. AES67-TX-1) and channel in the AES67 dropdown list.  Select the desired QSC Transmit channel to route the QSC Input channel to the chosen Iyo Receive/Output channel  To unsubscribe from this channel, select “None”

 

 

                                                       Figure 12 Iyo Receive/Output AES67 Selection

 

      

When the connection is established, the Receive/Output channel’s AES67 Status label updates and the subscription details appear in the Receive/Output AES67 Details grouping

 

 

  Figure 13 Active AES67 Receive/Output connection


State

AES67 Status

AES67 Transmitter Dropdown

Example

Unsubscribed

‘Inactive’, gray background

‘None’

 

Subscribed, receiving audio, session name resolved

‘Active’, blue background

Transmitter Session Name substring and flow channel, e.g. AES...1

Subscribed, receiving audio - session name unresolved.    This state should transition to the above state

‘Active’, blue background

‘...’

Subscribed to a flow found on the network but NOT receiving audio

‘Inactive’, red background

‘Error’

Subscribed to a flow that is NOT found on the network, NOT receiving audio

‘Inactive’, red background

‘Missing’

In the process of subscribing or unsubscribing to a flow.

‘Pending’, gray background

‘...’

 Figure 14 Iyo AES67 Receiver States


Connecting Iyo Input/Transmit to Q-SYS Output

In the Iyo plugin, add Iyo input channels to flows by clicking the AES67 toggle button. Iyo Input channels are configured to stream via 8-channel flows, e.g. “Mic/Line 1 to 8”, “Mic/Line 9 to 16”, etc.  Note: Only 8-channel Core AES67 Receiver blocks are compatible. 

 

  

Figure 15 Iyo Input/Transmit AES67 Setup

 

The Input/Transmit AES67 details grouping displays the transport IP addresses of active flows

 

 

 

Figure 16 Iyo Input/Transmit AES67 Setup



State

AES67 Status

AES67 Button

Example

Transmitter channel is not in an active flow

‘Idle’, gray background

‘Off’, gray background

Transmitter channel is in an active flow

‘Active’, blue background

‘On’, blue background

Transmitter channel is in the process of changing state to ON or OFF

‘Pending’, gray background

‘...’, gray background

Figure 17 Iyo AES67 Transmitter States

 

In Q-Sys Designer, route an AES67 Receiver component to an Output component


Figure 18 QSC AES67 Receiver and Output Components

 

In the AES67 Receiver configuration window, choose the Iyo Transmit Stream Name (e.g. Iyo1616M-146294 : Mic/Line 1-8)  from the Stream Name dropdown list

 

Figure 19 QSC AES67 Receiver Configuration


Contol pin overview


Device

Pin Name 

Type

Range

Pins Available

Firmware:AudioScience

Text

-

Output

Firmware:XMOS

Text

-

Output

Info:Hardware Rev.

Text

-

Output

Info:Model Name

Text

-

Output

Info:Model No.

Text

-

Output

Info:Primary MAC

Text

-

Output

Info:Serial No.

Text

-

Output

Settings:LED Brightness

Text

‘25%’, ‘50%’, ‘75%’, ‘100%’

Input/Output

Status:Identify

Button

trigger

Input/Output

Status:Sync

Indicator

-

Output

Status:Sys

Indicator

-

Output

MuteAllInputs

Button

trigger

Input

UnmuteAllInputs

Button

trigger

Input

MuteAllOutputs

Button

trigger

Input

UnmuteAllOutputs

Button

trigger

Input

 

Input/Transmit (per channel) 

Pin Name 

Type

Range

Pins Available

AES67 Status

Text

‘Idle’ or ‘Active’

Output

Gain (dB)

Knob

0 to 84 dB

Input/Output

Level (dBu)

Text

-60 to +24 dBu

Output

Peak Meter (dBFS)

Text

-60dBFS to 0 (Clipping)

Output

Phantom Power

Button

1 (‘true’) - On, 0 (‘false’) - Off

Input/Output

Mute

Button

1 (‘true’) - On, 0 (‘false’) - Off

Input/Output

 

Receive/Output (per channel) 

Pin Name 

Type

Range

Pins Available

Level (dBu)

Knob

-10 to +24 dBu

Input/Output

Peak Meter (dBFS)

Text

-60dBFS to 0 (Clipping)

Output

AES67 Status

Text

‘Active’ or ‘Inactive’

Output

Mute

Button

1 (‘true’) - On, 0 (‘false’) - Off

Input/Output

 

Plugin Release Notes

v2.1.0 (March 2019)

  • Add per-channel output mute
  • Add MuteAllInputs, UnmuteAllInputs, MuteAllOutputs, UnmuteAllOutputs pins

 

v2.0.2 (March 2019)

  • Improved, documented AES67 error reporting
  • Implement device reconnect

 

v2.0.1 (February 2019)

  • Modify Iyo Firmware compatibility check

 

v2.0.0 (January 2019)

 

v1.1.0 (December 2018)

  • Add per-channel input mute
  • Add incompatible Iyo firmware alert

v1.0.0 (December 2018)

  • Initial release