PREVIOUS: Local/MADI Configuration

I/O Setup: Dante

This page contains instructions on setting up SSL Live consoles for use with a Dante network, routing to and from Dante devices and controlling and gain sharing with SSL Net I/O Stageboxes.

Setting Up Dante

Setting Up Dante

IP Address Settings

Before starting to configure your console it's important to understand that your SSL Live console contains five separate network ports which must be configured to work with your external Dante network for correct operation. These devices are:

  • Primary Dante Control Network
  • Secondary Dante Control Network
  • Primary Dante Expander Audio
  • Secondary Dante Expander Audio
  • Connectivity Network Ports

If working with a BLII Bridge, these network devices will also apply:

  • Primary BLII Bridge Audio
  • Secondary BLII Bridge Audio

Primary & Secondary Dante Control - Provides control over the Dante network including making/unmaking routes and controlling input parameters such as mic gain. This pair of ports should live on the Primary and Secondary Dante networks respectively.

Primary & Secondary Dante Expander Audio - Provides transport of audio over the Dante network via the internal Dante Expander Module. The Dante Expander has no control over routing or stageboxes. This pair of ports should live on the Primary and Secondary Dante networks respectively.

Connectivity Network Ports - Used for remote control of the console via SOLSA or TaCo. This network is accessed from one of the three ports labelled NETWORK on the rear of the console. The Connectivity Network is a separate network from the Dante network and is not required for Dante operation. However, it is important to be aware of its IP address, as if set incorrectly, could conflict with your Dante network.

Primary & Secondary BLII Bridge Audio - Provides transport of audio over the Dante network via the Net I/O BLII Bridge. The BLII Bridge has no control over routing or stageboxes. This pair of ports should live on the Primary and Secondary Dante networks respectively.

The above network devices should live on 3 separate networks:

These networks should contain the following devices.

  • Dante Primary
    • Console Primary Dante Control
    • Console Primary Dante Expander Audio
    • Primary BLII Bridge Audio (if using BLII Bridge)
    • Other Dante devices' Primary connection (eg. Net I/O Stageboxes, Dante Virtual Soundcard, Third party Dante devices)
    • A computer running Dante Controller
  • Dante Secondary
    • Console Secondary Dante Control
    • Console Secondary Dante Expander Audio
    • Secondary BLII Bridge Audio (if using BLII Bridge)
    • Other Dante devices' Secondary connection (eg. Net I/O Stageboxes, Dante Virtual Soundcard, Third party Dante devices)
  • Connectivity Network:
    • Console Connectivity Network Ports
    • SOLSA in Remote mode (if used)
    • A tablet running TaCo (if used)
    • Another SSL Live console in Remote mode (if used)

Each network should have its own Netmask (also called subnet). And every device on one network must have an IP address within the same Netmask in order for those devices to communicate with each other.

Each of the network devices require a unique IP address within the correct Netmask for the network they are connected to.

SSL Live consoles ship from the factory with the following IP address settings:

Network Interface Fixed/DHCP IP Address IP Address Configured Using
Primary Dante Control Fixed 10.101.x.x MENU > Setup > Options > NETWORK tab
Secondary Dante Control Fixed 10.102.x.x MENU > Setup > Options > NETWORK tab
Primary Dante Expander Audio Fixed 10.101.x.x Dante Controller (available for free from the Audinate website)
Secondary Dante Expander Audio Fixed 10.102.x.x Dante Controller (available for free from the Audinate website)
Connectivity Network DHCP - MENU > Setup > Options > NETWORK tab

A BLII Bridge ships from the factory with the following IP address settings:

Network Interface Fixed/DHCP IP Address IP Address Configured Using
Primary BLII Bridge Audio DHCP - Dante Controller (available for free from the Audinate website)
Secondary BLII Bridge Audio DHCP - Dante Controller (available for free from the Audinate website)

For each IP address above, the netmask (also called subnet mask is 255.255.0.0

Important Things to Remember:

  • IP addresses for each device must be unique.
  • Dante Primary and Secondary networks must never be physically linked.
  • Multiple network adapters on the same device may not be given addresses in the same netmask
  • Dante Primary and Secondary addresses must be in different netmasks.
  • Dante Primary will use the 169.254.x.x netmask when set to auto-configure. This is standard IPv4 protocol and therefore the same behaviour as the Connectivity network.
  • On all Dante devices (other than SSL Live consoles, please see "Fixed IP Addresses" below) Dante Secondary will use the 172.31.x.x netmask when set to auto-configure. This is still a private address within IPv4, and is not reserved exclusively for auto-configuration, making its use for secondary auto-configuration unique to Dante.
  • In addition to being configured in different netmasks, Connectivity, Dante Primary and Dante Secondary should be treated as three physically separate networks, with their own network hardware.*
  • Default Gateway settings must be left blank as there is no current application for Dante.**

* There are exceptions - you may have a configurable network switch that could serve multiple networks, separated out using VLANs. Although this would work, reasons to keep hardware separate are primarily related to failover - if this single switch failed, both Primary and Secondary networks would fail, defeating the purpose of a secondary network, so it is not recommended for Live usage cases.

**Default Gateways are used to route IP data between netmasks. This is not supported in Dante, and entering gateway settings will link Primary and Secondary netmasks together, which is invalid.

SSL Live Recommendations

Fixed IP Addresses

SSL recommends that for Dante networks containing an SSL Live console, Fixed IP addresses are used for all Dante devices on the Primary and Secondary networks. Devices on the Connectivity network should be set to DHCP.

This is because the auto-configured netmask for the console's Dante Control Primary and Secondary as well as the Connectivity Network ports is the same, 169.254.xx.xx.

This means:

  • When there is no DHCP server present on the Dante Primary network, the Dante Control Primary port will be auto-configured to be within the 169.254.xx.xx netmask.
  • When there is no DHCP server present on the Dante Secondary network, the Dante Control Secondary port will be auto-configured to be within the 169.254.xx.xx netmask.
  • When there is no DHCP server present on the Connectivity Network, the Connectivity Network port on the console will be auto-configured to be within the 169.254.xx.xx netmask.

So if the Dante devices' Primary and Secondary connections and the Connectivity Network ports were set to DHCP, and no DHCP server was present on any of the networks, all three of the console's network devices would be auto-configured to be within the same netmask. This is an invalid configuration, linking all three networks together.

Using Fixed IP addresses for all devices on both the Dante Primary and Dante Secondary networks prevents the Dante Control Primary and Secondary network ports from being auto-configured IP addresses within the same netmask, and therefore helps to prevent the networks from becoming linked.

DHCP

Dynamic Host Configuration Protocol (DHCP) is a network protocol that allows a server to automatically assign an IP address to a device in a defined range, known as a scope. DHCP may also provide information about gateways and DNS servers. This is only of use to us if our Dante network connects through a gateway to a larger network, which may be advantageous for us to access for purposes other than audio.

If you wish to set all Dante devices to DHCP, ensure that you have a DHCP server on both the Primary and the Secondary Dante networks.

If you also wish to set the Connectivity Network Port to DHCP, ensure that you have a DHCP server on the Connectivity Network. This DHCP server should be configured to issue addresses within a different netmask to that of the Dante Primary and Secondary networks' DHCP servers or Fixed IP addresses as applicable.

If you do not have a DHCP server on the Connectivity Network, set this port to a fixed address, in a different netmask to the Primary and Secondary Dante networks. Set all other devices on the Connectivity Network to a Fixed IP address within the same netmask. For more information on setting up the Connectivity Network please go to Remote Surfaces: SOLSA, the Remote Expander & Other Consoles or Remote Surfaces: TaCo Tablet Control.

Step 1: Setting the Dante Control IP Addresses

This section describes how to set the IP addresses for the Primary & Secondary Dante Control network ports, which provide control over the Dante network including making/unmaking routes and controlling input parameters such as mic gain. This pair of ports should live on the Primary and Secondary Dante networks respectively.

On the console go to MENU > Setup > Options > NETWORK tab.

The screen will show you information for the Connectivity network on the left and the information for Primary and Secondary Dante Control Networks on the right.

Notes:
These addresses are for the network adapters used by the console to send/receive control data to/from the Dante network, not the address of the Dante audio connections. The Dante Control network adapters are not visible in, and cannot be configured by Dante Controller.

For our example we are going to set the Primary Control Network port with the following settings:

IP Address: 10.101.1.1

Netmask: 255.255.0.0

Gateway: 0.0.0.0

First set the port type to Fixed, then double-tap the IP Address and Netmask boxes and enter the values above. Once this is done, press and hold the Apply button and wait for the network adapter to restart.

Next set the Secondary Control Network port with the following settings:

IP Address: 10.102.1.1

Netmask: 255.255.0.0

Gateway: 0.0.0.0

Set the port type to Fixed, then double-tap the IP Address and Netmask boxes and enter the values above. Once this is done, press and hold the Apply button and wait for the network adapter to restart.

In our example, the Connectivity network port address settings should be left as DHCP. If this needs to be set to a Fixed IP address at a later date, ensure that a different netmask is used to that of the Dante networks.

Step 2: Setting the Dante Audio Network and Dante Control Network Names

To easily identify the console on a Dante network the console uses two unique, user defined names:

Control ID - Identifies the Dante Control Network (the name used for ownership of Net IO stageboxes)

Dante Device Name - Identifies the Dante Audio Network (the name visible in Dante Controller)

Important:
These two names must NOT be the same.

The Dante Device Name can be found in MENU > Setup > I/O > Local/MADI Configuration. Tap on the Dante Expander and the name will be displayed below. Double tap on the name to edit it.

The Control ID name can be seen in the MENU > Setup > Options > NETWORK tab. In the example below the Control ID is LIVE-L200.

The Control ID is taken from the Console Name, which can be changed in MENU > Setup > System, in the Console Name section. Double tap on the name to edit it. Then press and hold Apply.

Please note:
Changing the Console Name will power off the console and the console will lose ownership of all Net I/O stagebox parameters. This is because the console uses the Control ID (which is taken from the Console Name), to Own stagebox inputs and parameters. All previously owned inputs and parameters of the stagebox will need to be re-owned. For more information on how to Own inputs and stagebox parameters please go to Controlling Net I/O Stageboxes and Ownership

Step 3: Setting the Dante Audio Network IP Addresses and Names

To set the IP addresses of the console's Dante Audio Network devices you will need a computer running Audinate's Dante Controller application, which you can download here: www.audinate.com/products/software/dante-controller

Set your computer's network port to have a fixed IP address of 10.101.10.10, with a netmask of 255.255.0.0. Now connect your computer's network port directly to the Dante Pri port on your console and launch the Dante Controller application.

In Dante Controller find the console, in our example L200-Dante-Expander (on initial setup this name will be different).

In Device View select the Device Config tab.

Confirm that the name shown in the Rename Device field matches the Dante Device Name on the console exactly. If the name is different, enter the Dante Device Name correctly and click Apply. Alternatively the Dante Device Name can be edited from the console following the instructions in Step 2. These two names must match exactly.

In our example make sure the Dante device Sample Rate is set to 96kHz as shown above.

Next select the Network Config tab. This page shows the IP addresses for the console's Dante Audio Network devices.

For our example we will use the following IP address settings for the Primary port:

IP Address: 10.101.2.2

Netmask: 255.255.0.0

For the Secondary port use:

IP Address: 10.102.2.2

Netmask: 255.255.0.0

Press Apply for the changes to take effect. You will be asked to confirm the IP address change, click Yes. The device must now be rebooted for changes to take effect. Click Reboot. You will be asked to confirm the reboot. Click Yes.

Notes:
For our example please ensure the Virtual Tie Lines value is set to 0 in the Dante Expander Detail view (in MENU > Setup > I/O > Local/MADI Configuration). This is for the simplicity of the example. For more information on configuring Virtual Tie Lines please see Working with Virtual Tie Lines.

Step 4: Connecting SSL Net I/O Stageboxes (and other Dante Devices)

Now you have configured your console's Dante settings we can start to add network switches and other Dante devices to the network.

Notes:
The Primary and Secondary networks must remain physically separate at all times. Please do not connect the Primary and Secondary switches together, and similarly please do not connect a device's Primary connection to the Secondary switch and vica versa.

All SSL Stageboxes ship configured DHCP.

To setup a Fixed IP address on a Stagebox connect your computer (configured to use a DHCP address), directly to the stagebox and use Dante Controller to set the Fixed IP address (following the instructions in Step 3).

Every device on one network must have an IP address within the same netmask in order for those devices to communicate with each other.

So for our example any device connected to the Dante Primary network must have an IP address as follows:

IP Address: 10.101.x.x

Netmask: 255.255.0.0

Notes:
We have already used IP addresses 10.101.1.1, 10.101.2.2 and 10.101.10.10 on the Primary Network. These IP addresses cannot be used for an additional device on the network.

For the Dante Secondary network any connected device must have an IP address as follows:

IP Address: 10.102.x.x

Netmask: 255.255.0.0

Notes:
We have already used IP addresses 10.102.1.1 and 10.102.2.2 on the Secondary Network. These IP addresses cannot be used for an additional device on the network.

Using Dante Controller set all connected Stageboxes to 96kHz sample rate. This is because we have already set the Dante Expander module to 96kHz earlier in this example setup process. Dante routes are not possible between two devices with different sample rates. So to create a route between two Dante devices, those devices must be on the same sample rate.

Clocking over Dante

Dante uses its own Clock Election process to determine the most appropriate Clock Master for the Dante network and a Clock Master will be chosen automatically. For more information on the Dante Clock Election process please see the Audinate website: dev.audinate.com/GA/dante-controller/userguide/webhelp/#clock_synchronization.htm.

To choose a Clock Master manually, set this device to be the Preferred Master. To do this, open Dante Controller and click on the Clock Status tab. Check the Preferred Master checkbox for your chosen Clock Master. This device will become the Clock Master.

If multiple devices on the network are Preferred Masters, the Dante Clock Election process will automatically choose a Clock Master from the multiple Preferred Masters.

If the Clock Master's status changes, or a more suitable Clock Master comes online, the Dante network will go through the Clock Election steps again to determine the most suitable Clock Master for the network.

If you are not using Dante network redundancy, please use the primary connection (rather than the secondary) to ensure accurate synchronisation.


Setting Up the Console as Clock Master of the Network

In this configuration the console is the Clock Master of the network and all other devices on the network will clock to the console.

To set this up, on the console, go to MENU > Setup > Options > SYSTEM tab. In the SYSTEM CLOCK section select Int for the console's internal clock and press and hold Apply. Check that both the Requested and Actual fields above list Int.

In Dante Controller go to the Clock Status tab. Check the Preferred Master and Enable Sync To External checkboxes for the console's Dante Expander.

Ensure that Preferred Master and Sync to External are unchecked for all other devices on the network.

The console's internal clock is now the Clock Master of the Dante network. The console's Dante Expander module is clocking from the console's internal clock, and all other devices on the network are clocking from the Dante Expander.


Setting up the Console as a Slave of the Dante Network

In this configuration, a Dante device other than the console is the Clock Master. The console and all other devices on the network will clock to this master.

In Dante Controller, go to the Clock Status tab. Check the Preferred Master checkbox for the Clock Master device(s). For this example ensure that Preferred Master and Sync to External are unchecked for all other devices on the network (including the console's Dante Expander).

On the console, go to MENU > Setup > Options > SYSTEM tab. In the SYSTEM CLOCK section, select Dante Expander and press and hold Apply. Check that both the Requested and Actual fields above list Dante Expander.

The chosen Preferred Master is now the Clock Master of the network, including the console. The console is now clocking from its Dante Expander module. The Dante Expander module is clocking from the Preferred Master on the Dante network. All other devices on the network are clocking from the Preferred Master on the Dante network.

Notes:
If selecting Dante as a clock source on the console, the console's internal clock source will not drop back to another clock source if the Dante network clock is lost. The Dante Expander module incorporates an internal clock which will be become the Clock Master of the Dante network in this instance until another device on the network is identified as the most suitable Clock Master from the Clock Election process.
Important:
It is not recommended to clock from Dante if the Dante SRC In is engaged.
Consoles clocked from stageboxes via MADI or Wordclock are not recommended to be used as Dante network Clock Master sources.
How SSL Live Consoles Communicate with a Dante Network

Dante Expander Module

SSL Live consoles contain a Dante Expander Module which comprises a Dante Brooklyn II Module.

SSL Live consoles with a Dante Expander Module fitted are capable of 32 Dante inputs and outputs at 96kHz or 64 Dante inputs and outputs at 48kHz.

Console Sample Rate Dante Expander Sample Rate Dante Expander Sample Rate Conversion Quantity of Dante Inputs and Outputs
96kHz 96kHz SRC Out 32
96kHz 48kHz SRC In 32
48kHz 96kHz SRC In 32
48kHz 48kHz SRC Out 64

The Dante Expander Module supports Dual Domain Routes as well as Virtual Tie Lines. For more information please see What are the Differences Between Dual Domain Routes and Virtual Tie Lines?.

Net I/O BLII Bridge

A Net I/O BLII Bridge can be connected to SSL Live consoles to deliver an extra 256 Dante inputs and outputs at 96kHz or 48kHz.

SSL Live consoles can utilise the Dante I/O of a BLII Bridge and a Dante Expander module simultaneously.

BLII Bridges support Dual Domain Routes, but not Virtual Tie Lines. For more information please see What are the Differences Between Dual Domain Routes and Virtual Tie Lines? and Working with a BLII Bridge.

What are the Differences Between Dual Domain Routes and Virtual Tie Lines?

What are the Differences Between Dual Domain Routes and Virtual Tie Lines?

There are two methods available for Dante routing on SSL Live consoles: Dual Domain Routes and Virtual Tie Lines.

Dual Domain Routes

Dual Domain Routes are unique to SSL, allowing the console to interact directly with devices on the network, with no need to use Dante Controller to make routes.

When using Dual Domain Routes, Dante devices will appear in the console's routing view.

Dual Domain Routes are used for most routing situations. Dual Domain Routes from SSL Net I/O stageboxes to Channel inputs also provide gain control as well as control over other stagebox parameters (eg. +48V).

Please Note:
Dual Domain Routes should not be used for routing between multiple SSL consoles. Use Virtual Tie Lines for this purpose (see below). This is because when SSL consoles make a Dual Domain Route from the console, the console is not deterministic when choosing a Dante output to route from, or a Dante input on the other device to route to. This route will be created in any of the available routing points. If the other device is an SSL console, this non-deterministic approach means the receiving console is not aware of which input has been routed to (and vica versa).

Devices must be configured in the Dante Configuration page before Dual Domain Routes can be made. The Dante Configuration page is the console's Dante I/O Setup page.

Dual Domain Routes can be made through the Dante Expander Module or the BLII Bridge.

For more information on Dual Domain Routes and configuring Dante devices please see Working with Dual Domain Routes and the Dante Configuration Page.

Virtual Tie Lines

Using Virtual Tie Lines allows SSL Live consoles to be used as a typical Dante I/O device.

Once created, Dante Virtual Tie Lines will appear in the routing view as a local I/O type.

When routing to a Virtual Tie Line, only the internal route in the console is made - connecting a path to the Dante Expander Module.

The network route (connecting the Dante Expander Module to another Dante device on the network) must be made manually from Dante Controller.

Virtual Tie Lines are used for routing between multiple SSL consoles, for live recording and rehearse mode.

Virtual Tie Lines do not carry control data, and therefore should not be used for routes from Net I/O stagebox inputs to the console unless control is not required.

The Dante Expander Module's I/O does not contain any Virtual Tie Lines by default, they must be created.

Please note:
Virtual Tie Lines are only possible through the Dante Expander Module. The BLII Bridge does not support Virtual Tie Lines.
Please also note:
When the console is connected to a BLII Bridge, any Virtual Tie Lines must be created before Dual Domain Routes. The console is not deterministic when choosing a Dante interface to create Dual Domain Routes through. And the console cannot switch routes from the Dante Expander to the BLII Bridge once routes have been made. Failure to create Virtual Tie Lines before Dual Domain Routes, can cause the Dante Expander's Dante I/O resource to be used up by Dual Domain Routes, at which point the console will not allow more Virtual Tie Lines to be created. Routing to/from Virtual Tie Lines can be done at any time.

For more information on creating and routing with Virtual Tie Lines please see Working with Virtual Tie Lines.

Working with Dual Domain Routes and the Dante Configuration Page

Working with Dual Domain Routes and the Dante Configuration Page

Dual Domain Routes

Dual Domain Routes are unique to SSL, allowing the console to interact directly with devices on the network, with no need to use Dante Controller to make routes.

The Dante Configuration Page

Dante Devices must be configured in the console's Dante Configuration page before they can be routed to directly from the console using dual domain routes.

Go to MENU > Setup > I/O then tap Dante Configuration just below the Menu.

On the left of the page there is a list of Connected Devices. All Dante devices on the network will be listed here.

On the right of the page there is a list of Configured Devices. This is a list of all Dante devices that have been configured for use.

There are two resource bars above the Configured Devices list to indicate the total dual domain input and output routes available and how many are currently in use. The total number displayed will depend on sample rate, quantity of Virtual Tie Lines and whether a BLII Bridge is being used. The resource bars fill with light or dark blue as dual domain routes are made:

Light Blue: Routes to offline Configured Devices (Devices not connected to the network, used for prepping showfiles prior to stageboxes being physically present)

Dark Blue: Routes to online Configured Devices (Devices connected to the network)

There are a series of status LEDs for each device:

There are two NET LEDs showing the network status of the Primary and Secondary network connection.

Colour Meaning
Green Connected
Red Not Connected or Fault

Please note:
When an SB32.24 is connected with Networks A+B Linked, the Primary and Secondary network status will always report that both are connected, even if that is not the case. In this mode please consult the NET A and NET B LEDs on the front of the unit for Primary and Secondary connection status:

Colour Meaning
Green Dante Primary and Secondary connected
Red Dante Primary not connected or fault
Flashing Red Dante Secondary not connected or fault
For more information on SB 32.24 please consult the SB 32.24 Manual (http://www.solidstatelogic.com/live/remote-ecosystem/documents).

For Configured Devices, there is a single LED to the left. This shows whether the device is online or offline.

Colour Meaning
Green Online
Red Offline - Device has previously been online
(in this showfile)
Grey Offline - Device was created offline
and has never been online (in this showfile)

For SSL Net I/O Stageboxes, there are also PSU status LEDs.

Colour Meaning
Green PSU On and functioning correctly
Red PSU Off or fault

Tapping on any device in the Connected or Configured Devices list will bring up a Detail View for that device. If the device is a Connected Device, stagebox settings cannot be edited. If the device is a Configured Device, all stagebox settings and parameters (eg. gain, +48V, operating level etc.) can be changed here.

The following information is displayed:

  • Dante device name (This should be changed from Dante Controller, not from the console)
  • I/O capacity
  • PSU status for SSL devices
  • Primary and Secondary Network Status
  • IP address (which will be red if there is a netmask discrepancy) - read only
  • Dante and console sample rates (which will be red if there is an sample rate discrepancy, and the console's Dante SRC is off) - read only
Please note:
Dante routes are associated with device names. So changing Dante device names will remove all routes. Renaming devices should be changed from Dante Controller, not on the console. A warning dialogue will appear in Dante Controller before device names are changed to inform the user of a break in audio routes.

Configuring Online Dante Devices

Now we will configure an online device for Dual Domain Routing. An online device is a device that is connected to the network.

First, engage Edit. Then tap and drag a device in the Connected Devices list on the left. A + sign will appear at the bottom of the Configured Devices list once you begin to drag the device. Drop the device onto the + sign.

This device has now been added to the Configured Devices List and you can now route to/from it in the routing view or XY Routing page.


Configuring Offline Dante Devices

Offline devices can be added, configured and routed to/from even when the physical device is not present.

These settings can then be associated with online devices when the units are available (see below).

First, engage Edit. Then tap Configure New Device and select one of the devices from the list:

  • Net I/O SB 8.8
    • Main (Uncompensated)
    • Compensated Splits

  • Net I/O SB i16
    • Main (Uncompensated)
    • Compensated Splits

  • Net I/O SB 32.24
    • Main (Uncompensated)
    • Compensated Splits

  • Net I/O MADI Bridge
  • SSL Console
    • Live Dante Expansion An SSL Live console with a Dante Expander Module fitted
    • Net I/O BLII Bridge An SSL Live console connected to a BLII Bridge
    • System T Dante HC SSL Broadcast console system

  • Generic Dante Any other Dante device

Select the device you wish to add and an offline device will be added to the Configured Devices list. The new device's status LED will be Grey to show that it has never been online.

You can now route to/from this device in the routing view or XY Routing page.


Linking an Offline Device and an Online Device

When the device name and type of an offline Configured Device matches that of a Connected device, the two will be automatically linked. The previously offline device will come online.

All settings on the stagebox that were stored in the offline device will be pushed to the stagebox* and routes to/from the offline device will be assigned to the online device**. This allows for a power down or disconnection without loss of routes or device settings.

*Providing all ownership requirements have been satisfied (see "Ownership")

**Providing there are no routing conflicts with existing routes between this device and other devices on the network (see "Routing Conflicts").

To link an offline and an online device, first tap Edit, and drag the online Connected Device onto the corresponding offline Configured device.

Tap Assign to Configured Device to confirm.

Please note:
Devices must be of the same type for this to work. If they are not, the console will not allow linking.

The online and offline devices have now been linked and all settings and routes of the offline device will be assigned to the online device (providing there are no Ownership or Routing conflicts.

You can also use the above process to link an existing online Configured Device with a different online Connected Device.


Deleting Configured Devices

Deleting a device will move the online device back to the Connected Devices list. All routes between the console and this device will be unmade.

To delete a Configured Device, tap Edit, select a device in the Configured devices list using the circles to the right. Then press and hold Delete.


Unlinking

Unlinking separates the online device from the device routes and settings and saves the routes and settings within an offline device.

Unlinking a device will move the online device back to the Connected Devices list. An offline device with all the routes and settings will be retained in the Configured Devices list.

To Unlink a device, tap Edit, select a device in the Configured devices list using the circles to the right. Then press and hold Unlink.

Routing Conflicts

A routing conflict occurs when the console attempts to make a route to a Dante device on the network, but there is already a Dante route occupying this routing point.

This may occur in the following situations:

  • When the operator manually makes a route between the console and another Dante device (from the console)
  • When a showfile is loaded containing Dante routes
  • When the console is powered on and the most recent showfile contains Dante routes
  • When a offline Configured Device with routes saved is linked to an online Connected Device

Dante routing operates on a first come, first served basis. So if there is a conflict between two routes to the same destination, the first route that was created will be retained. Any routes that are subsequently made to the same destination will not be made.


When the console is powered off or goes offline

When the console is powered down correctly from the main screen, all Dante routes to/from the console are unmade. This allows Dante devices that previously contained a route to/from the console, to be freed up, and those routing points can now be used by other Dante devices on the network.

When the console loses power, or is powered off incorrectly (for example by pulling out the PSU cables or switching the PSUs off), all Dante routes to/from the console are retained. This causes any routing points on other Dante devices that were in use by the console, to be unavailable for further routing.

Notes:
For this and many other reasons, SSL recommends that the SSL Live consoles are always powered down correctly via the main screen. Please do not pull out the PSU cables or switch off the PSUs prior to a correct shut down from the main screen.

If the console loses its connection to the Dante network and goes offline, all Dante routing will be retained by the devices on the network. So when the console comes back online, routing does not need to be re-made.


When the console comes online or when a showfile is loaded

Loading showfiles containing dual domain routes can cause routing conflicts with routes already on the network. This can also occur when the console is connected to the network or powered on and the most recent showfile is loaded automatically.

For example:

An L500, an L200 and one SB 32.24 are on a Dante network. SB 32.24 input 1 is routed to the input of Channel 1 on the L500. And the output of Channel 1 is routed to SB 32.24 output 1. The L200 is connected to the network but in the current showfile there are no routes between the console and the SB 32.24.

A new showfile is loaded on the L200. In the new showfile SB 32.24 input 1 is routed to Channel 32 on the L200. And the output of this channel is routed to output 1 on the SB 32.24.

For the transmit channels of the SB 32.24, this is not a problem. Input 1 on the SB 32.24 can be sent to both the L500 and the L200 at the same time.

For the receive channels of the SB32.24, there is a routing conflict. The SB 32.24 cannot receive a route from both the L500 and the L200 at the same time.

Following Dante routing's first come, first served basis, the L500's route will be retained. This is because the L500's route was already valid at the time the L200 attempted to make its route. The L200's route will not be made.

This is to avoid active routes being stolen by devices when they come online.

Notes:
The first come, first served basis is a Dante concept and applies to SSL and non-SSL Dante devices alike.

The same first come, first served basis will apply if a Configured Device is assigned to a new Connected Device with existing routes. To check if the network route has been created please use the Routing tab of Dante Controller.


Overwriting/Unmaking Existing Dante Routes

The only time when a Live console can overwrite an existing Dante route, is from the XY Routing page.

If the operator manually makes a route in XY Routing that causes a conflict with an existing route on the network, this new route will overwrite any conflicting routes on the network. Check Dante Controller to see the current routes on the network. You can also tap on the routing point (either the source of destination point on the x and y axis respectively) to check the existing routes to that routing point. These will be displayed in the display box at the top left of the XY Routing matrix.

Routes between any two other Dante devices on the network can also be manually made or unmade from the XY Routing page.

Working with a BLII Bridge

Net I/O BLII Bridge - High Capacity Dante Interface

The Net I/O BL II Bridge is a 1U rackmount device which converts between Dante HCTM and SSL's proprietary BlackLightTM digital multichannel audio format. It provides 256 redundant bidirectional uncompressed audio channels from an SSL BLII and Dante equipped Live console to/from Dante networks at 24-bit, at either 96kHz or 48kHz resolution.

The Net I/O BLII Bridge is compatible with all BLII and Dante equipped SSL Live consoles running software version 4.5 or later.

Please Note:
10 Gigabit switches are required on networks involving a BLII Bridge.

Front Panel LEDs

There are four LED indicators on the front panel of the BLII Bridge: PSU, BL S, SRC and NET S.

LED Off Solid Red Flashing Green & Red Flashing Green Solid Green
PSU Both PSUs are off Only one PSU is functioning correctly n/a n/a Both PSUs functioning correctly
BL S BLII Bridge not set to Sync to External
BLII source and/or not connected to BLII
n/a n/a Resyncing - searching for a valid clock source Clocked to BLII and incoming
clock source present
NET S Not configured to clock from Dante network Unit it set to clock from Dante network
but there is no network connected
Primary or Secondary
network port not connected
Resyncing - searching for a valid clock source Set to clock to Dante network and
Clock Master on network detected

The BLII Bridge does not support Sample Rate Conversion. The SRC LED is not currently in use. This LED will go solid red when the device is resyncing (searching for a valid clock source).

Front Panel Connections

One pair of SFP cages is located on the front panel for Dante network connectivity:

These will be pre-populated with RJ45 but can alternatively be populated with single-mode or multi-mode fibre SFPs.

The status LED meanings are as follows:

LED Off Flashing Red Flashing Green & Red Flashing Green Solid Green
ACT Unit is off n/a Unit is on n/a n/a
SFP No SFP fitted n/a n/a n/a SFP fitted
GM Unit is not Clock Master of Dante Network Unit is Clock Master of Secondary
Dante Network only
n/a Unit is Clock Master of Primary Dante Network only Unit is Clock Master of both Primary
and Secondary Networks
STAT Hardware fault Audio muted. The BLII Bridge automatically
mutes audio during resyncing
n/a Hardware ok n/a

The Program USB port is for performing updates to the unit. Instructions on updating the BLII Bridge will accompany all relevant update packages.

Rear Panel Connections

The BLII Bridge incorporates a pair of redundant power supplies, which are powered from the pair of IEC connections on the back of the unit.

HC Link 1 Port A Main and Backup are used for connecting to BLII 1a and 1b (or 2a and 2b) ports on the console respectively.

Port B is not in use.

There is also an RX and SFP status LED for each port. The leftmost pair of RX and SFP LEDs refer to Port A Main and the second from the left refers to Port A Backup. The third and fourth from the left pairs of LEDs refer to Port B, which is not in use.

The status LED meanings are as follows:

LED Off Solid Red Flashing Green Solid Green
RX n/a Port is not connected Port is connected and is Active port
in redundant connection
Port is connected and is Inactive port
in redundant connection
SFP No SFP fitted n/a n/a SFP fitted

Connecting BLII Bridge to SSL Live Consoles

The following equipment is required to connect a BLII Bridge to an SSL Live console.

  • An SSL Live console
    • with at least one redundant pair of BLII ports fitted
    • and with a Dante Expander module fitted (if you are interested in a Dante Expander retrofit please contact support@solidstatelogic.com)
  • A BLII Bridge
  • At least one network switch (non-redundant). At least two switches (primary and secondary) are required for a fully redundant connection.

Connect the console's BLII port 1a to HC Link Port A Main on the back of the BLII Bridge via multi-mode LC fibre.*

Connect the console's BLII port 1b to HC Link Port A Backup on the back of the BLII Bridge via LC fibre.*

*or single-mode LC fibre if the console has been fitted with single-mode BLII ports and single-mode SFPs have been fitted to the BLII Bridge - not standard.

Notes:
If using an L500 Plus with two pairs of BLII ports fitted, either redundant pair can be used to connect to the BLII Bridge. The other pair can be used to connect to a BL II-MADI Concentrator or another BLII Bridge.

Connect the BLII Bridge Dante Primary and Secondary ports to the primary and secondary Dante network switches respectively.

Connect the console's Dante Expander Primary and Secondary ports to the primary and secondary Dante network switches respectively.

Setting Up the BLII Bridge with an SSL Live Console

On the console go to MENU > Setup > I/O > Local/MADI Configuration.

If there are no devices configured in the relevant BLII port when the BLII Bridge is connected, the Bridge will be automatically detected and configured.

If there are already devices configured in the relevant BLII port, the port will need to be reconfigured.

To configure the BLII port, 1. tap on the relevant BLII port column heading to view settings for the BLII port. 2. press and hold Configure Port For: in the Detail View of the BLII port and select Net I/O BLII Bridge.

Caution:
Take care when reconfiguring the BLII port as routes will be unmade. If reconfiguring the BLII port from BLII-MADI Concentrator to BLII Bridge, all existing routes between the console and devices connected via the BLII-MADI Concentrator will be unmade. If reconfiguring the BLII port from BLII Bridge to BLII-MADI Concentrator ALL Dante dual domain routes will be unmade regardless of whether they route through the BLII Bridge or the Dante Expander Module. Virtual Tie Line routes made to the Dante Expander Module will remain.

BLII port configuration is stored in showfiles.

In order for the BLII Bridge to function correctly, the name of the BLII Bridge on the console must match the name of the unit in Dante Controller.

To check this, open Dante Controller on a computer and connect it to the Dante network (or to the BLII Bridge directly using a network cable).

Check that the BLII Bridge appears in Dante Controller. (For more information on IP addresses and connecting Dante devices to the network, please see the "Setup: Dante I/O Configuration" page in the SSL Live Help system).

Check the name of the BLII Bridge in Dante Controller against the BLII Bridge name on the console.

To edit the BLII Bridge name on the console, double tap in the name field and type in a name.

To edit the BLII Bridge name in Dante Controller, double click on the BLII Bridge and go to the Device Config tab. At the top of the page under Rename Device, type in a name and press Apply. You will be asked to confirm the name change. Click Yes. Please note that changing the Dante name of a device breaks all existing routes to/from this device.

These names must match exactly, but are not case-sensitive.

PSU status, network status, and Sample Rate are also displayed here.

Sample Rate

The sample rate of the BLII Bridge must match the sample rate of the console.

The Sample Rate is changed in Dante Controller. Double click on the BLII Bridge and go to the Device Config tab. In the Sample Rate section, click on the drop down menu and select the desired sample rate. You will be asked to confirm the sample rate change. Click Yes.

The BLII Bridge must be rebooted in order for this change to take effect. Click Reboot at the bottom of the window. You will be asked to confirm the reboot. Click Yes.


Working with Multiple Sample Rates and a BLII Bridge

If working with multiple sample rates on the same network, as well as a BLII Bridge, the following instructions must be followed.

The BLII Bridge and the console must ALWAYS be running on the same sample rate.

To interface with devices on an additional sample rate on the same network, these devices must be routed to/from the console via Virtual Tie Lines.

Go to MENU > Setup > I/O > Local/MADI Configuration and tap on the Dante Expander.

Double tap on the Virtual Tie Lines quantity and type 32 (maximum quantity when either console or Dante Expander or both are running at 96kHz). Now engage SRC In.

32 Virtual Tie Lines MUST be created, even if fewer are required. This is because the console is not deterministic when choosing whether to create Dual Domain routes through the Dante Expander or the BLII Bridge. So if fewer than 32 Virtual Tie Lines are created, there will still be some Dante routes remaining, which the console could use for Dual Domain Routes. It would then be possible that the console attempts to make Dual Domain Routes to/from devices on a different sample rate. Dante network routes cannot be made between devices running different sample rates, so the network route would not be created.

In Dante Controller, set the console's Dante Expander to the same sample rate as these other devices (different from the console and BLII Bridge sample rates).

Now the console and BLII Bridge are running one sample rate. And the Dante Expander and other devices on the network are running another sample rate. The Dante Expander has been set to sample rate convert between these two sample rates.

Now make routes to/from the other devices (on the different sample rate to the console) via Virtual Tie Lines. For instructions on how to do this please see Working with Virtual Tie Lines.

Please Note:
In this configuration, SSL recommends that the console is set to clock from the BLII Bridge and the BLII Bridge is set to clock from the Dante network. See the instructions on clocking below.

IP Addresses

When BLII Bridges are shipped from SSL, they will be set to DHCP.

The BLII Bridge's IP address must be in the same netmask as the Dante Expander module and the console's Dante Control Settings. For more information about IP addresses and netmasks please see Setting Up Dante

Changing the IP address of the BLII Bridge and Dante Expander Module

The BLII Bridge and Dante Expander's IP addresses are changed in Dante Controller. Double click on the device and go to the Network Config tab. Choose either Obtain an IP Address Automatically or Manually configure an IP address. If you select Manually configure an IP address, type in an IP address and a Netmask (also known as netmask mask).

Click Apply. You will be asked to confirm the IP address configuration change. Click Yes. The BLII Bridge must be rebooted in order for these changes to take effect. Click Reboot at the bottom of the window. You will be asked to confirm the reboot. Click Yes.

Changing the IP address of the console's Dante Control Settings

On the console, go to MENU > Setup > Options > NETWORK tab. In the DANTE CONTROL SETTINGS section, the console's Dante Control IP Settings are listed. Choose either DHCP or Fixed IP addresses. If you choose Fixed, double tap on the IP Address and Netmask (also known as subnet mask) fields to edit them. Press and hold Apply.

Clocking

The console can be the Master or the Slave of the Dante Network through the BLII Bridge.

Setting up the Console as a Slave of the Dante Network

For the most reliable clocking scheme, SSL recommends that the console is set to be a slave of the Dante network when using a BLII Bridge.

In this configuration, a Dante device other than the console is the Clock Master. The BLII Bridge is set to clock from the Dante Network, and the console clocks from BLII.

In Dante Controller, go to the Clock Status tab. Check the Preferred Master checkbox for the Clock Master device.

On the console, go to MENU > Setup > Options > SYSTEM tab. In the SYSTEM CLOCK section, select BLII 1 and press and hold Apply. Check that both the Requested and Actual fields above list BLII 1.

On an L500 Plus with two pairs of BLII ports fitted, select either BLII 1 or BLII 2 depending on which BLII port has been used to connect to the BLII Bridge. To select BLII 2, tap BLII 1 twice and a drop down menu will appear. Tap 2, then tap Blacklight II. Check that both the Requested and Actual fields above list BLII 2.

If configured correctly the following LEDs will be seen on the BLII Bridge:

LED If configured correctly will light
BL S Off
NET S Solid Green
GM Off

If colours differ from the above please consult the full tables earlier in this page.

Setting up the Console as the Clock Master of the Dante Network

In this configuration, the console's Internal Clock is the Clock Master. The BLII Bridge is set to clock from BLII, and the Dante Network clocks to the BLII Bridge.

On the console, go to MENU > Setup > Options SYSTEM tab. In the SYSTEM CLOCK section select Int for the console's internal clock and press and hold Apply. Check that both the Requested and Actual fields above list Int.

In Dante Controller go to the Clock Status tab. Check the Preferred Master and Enable Sync To External checkboxes for the BLII Bridge.

If configured correctly the following LEDs will be seen on the BLII Bridge:

LED If configured correctly will light
BL S Solid Green
NET S Off
GM Solid Green

If colours differ from the above please consult the full tables earlier in this page.

When the BLII Bridge becomes the Clock Master

If the BL S and NET S LEDs are off and the GM LED is Solid Green, the BLII Bridge has become the master of the network. This could occur if the console and BLII Bridge were set to clock from a Dante device on the network, but this Clock Master loses connection to the network. The BLII Bridge could then be chosen by the Dante network as the Clock Master of the Dante network.

This is a perfectly valid clocking scheme. The BLII Bridge will now clock the console and the network from its internal clock. The console's clock source will remain as Dante.

To manually set the BLII Bridge to be the Clock Master, follow the same steps as configuring the console to clock from the Dante network, but check the Preferred Master box beside the BLII Bridge in Dante Controller.

Checking the Maximum Dante I/O Channel Count

In MENU > Setup > I/O > Dante Configuration at the top right of the page is a resource bar listing the quantity of the total number of dual domain Inputs and Outputs, as well as how many are currently in use.

The maximum quantity of Dante Inputs and Outputs varies depending on the following:

  • Whether a Dante Expander Module is fitted (32ch at 96kHz, 64ch at 48kHz)
  • Whether a BLII Bridge is connected (256ch, not Sample Rate dependant)
  • The Sample Rate of the console
  • The Sample Rate of the Dante Expander Module
  • The quantity of Virtual Tie Lines created to/from the Dante Expander Module
Please Note:
Virtual Tie Lines can only be created to and from the Dante Expander Module. The BLII Bridge does not support Virtual Tie Lines.
Please also note:
When the console is connected to a BLII Bridge, any Virtual Tie Lines must be created before dual domain routes. The console is not deterministic when choosing a Dante interface to create dual domain routes through. And the console cannot switch routes from the Dante Expander to the BLII Bridge once routes have been made. Failure to create Virtual Tie Lines before dual domain routes, can cause the Dante Expander's Dante I/O resource to be used up by dual domain routes, at which point the console will not allow more Virtual Tie Lines to be created. Routing to/from Virtual Tie Lines can be done at any time.

For example, if the console and Dante Expander are both running at 96kHz, no Virtual Tie Lines have been created from the Dante Expander Module and there is one BLII Bridge connected the maximum Dante channel count will be:

32ch (Dante Expander at 96kHz with no Virtual Tie Lines) + 256ch (BLII Bridge) = 288ch

Or for example, if the console and Dante Expander are both running at 48kHz, 10 Virtual Tie Lines have been created from the Dante Expander Module and there are two BLII Bridges connected the maximum Dante channel count will be:

64ch (Dante Expander at 48kHz) -10ch (10 Virtual Tie Lines from Dante Expander) + 512ch (two BLII Bridges) = 566

The maximum Dante I/O count is 576 channels. To achieve this the console must be an L500 Plus with two pairs of BLII ports fitted, as well as a Dante Expander Module fitted. And the console and Dante Expander Module must both be running at 48kHz:

64ch (Dante Expander at 48kHz) + 512ch (two BLII Bridges) = 576

Please Note:
All of the above is subject to network bandwidth limits.

Routing

Dual domain routes to and from Dante devices through the BLII Bridge are made in exactly the same way as they are through the Dante Expander. Please see Working with Dual Domain Routes and the Dante Configuration page for more information on making dual domain routes.

Please Note:
When making dual domain routes to and from Configured Dante devices, the console chooses whether to make that route through the Dante Expander Module or through the BLII Bridge. This means that some routes may be made through the Dante Expander and some others may be made through the BLII Bridge. This may change when the console is booted or when the showfile is reloaded. This is all perfectly normal. Please be aware of existing routes when unplugging either the BLII Bridge or the Dante Expander. You can check how many routes are going through the BLII Bridge and the Dante Expander in the Routing tab of Dante Controller.
Introduction to SSL Net I/O Stageboxes

Introduction to SSL Net I/O Stageboxes

There are three Net I/O Stageboxes:

  • SB 32.24 - 32 analogue inputs, 16 analogue outputs and 4 AES pairs
  • SB 8.8 - 8 analogue inputs and outputs
  • SB i16 - 16 analogue inputs

These three stageboxes can be remotely controlled by SSL Live or System T consoles and the Network I/O Controller application for PC.

The Network I/O Controller application can be downloaded from solidstatelogic.com/live/remote-ecosystem/downloads.

For more information on Ownership and Controlling Net I/O Stageboxes please see Controlling Net I/O Stageboxes and Ownership.

The manuals for each stagebox can be downloaded from solidstatelogic.com/live/remote-ecosystem/documents.

Controlling Net I/O Stageboxes and Ownership

Controlling Net I/O Stageboxes and Ownership

Ownership

Net I/O Stageboxes can be controlled by SSL Live or System T consoles and the Network I/O Controller application for PC.

The concept of ownership has been introduced to assign one owner to each stagebox input and GPO, so that there are no fights for control. There is also one owner of the stagebox's general setup with control over operating level and AES vs Analogue inputs on the SB32.24.

So before you can remote control a stagebox, you must become the owner of that parameter.

Please Note:
It is only possible to control the Main stagebox device. The Comp device can never be controlled or owned. For more information on the Main and Comp devices please see Gain Sharing with Net I/O Stageboxes.

First, ensure the stagebox you want to control is in the Configured Devices list (Dual Domain Routes and the Dante Configuration Page).

The following ownership options are available:

  • Stagebox ownership: Change operating level, choosing between AES and analogue inputs, turning the AES input SRCs In and turning AutoPad on or off
  • Input ownership: control input parameters only
  • GPO ownership: control all GPO parameters & settings

Stagebox Ownership

Stagebox Ownership provides control over the following parameters:

  • Operating level
  • Enabling AES Inputs (SB 32.24 only)
  • Turning on AES input SRCs (SB 32.24 only)
  • Turning AutoPad on or off (SB 8.8 or i16 only)

To become the Stagebox owner, tap on the stagebox in the Dante Configuration page and the stagebox's Detail View will appear at the bottom. Press and hold Stagebox Ownership.

The Stagebox owner is listed in cyan to the left of this button.

To release Stagebox ownership press and hold Stagebox Ownership again to disengage.

Input Ownership

The owner of an input can control all input parameters including gain, Pad, Mic/Line and +48V.

When a stagebox input is routed to the input of a Channel on the console, and that input didn't have an owner, then the console will automatically become the owner of that input.

However, if that input was already owned by another device, the console will not automatically take ownership from that device. Ownership must be taken manually.

The input settings of a Net I/O stagebox can be viewed in the Channel Detail View in the Input/Routing page (if that input has been routed to a Channel) or in the Detail View for the stagebox in the Dante Configuration page.

To view the stagebox input settings tap on the stagebox in the Dante Configuration page and then tap Inputs to the right. Tap on any input and then tap Edit Settings to the right.

That input's settings will now be displayed in a pop out.

The following instructions apply whether viewing the input settings in the Channel View or in Dante Configuration.

To own an input, navigate to that inputs settings and you will see an Ownership section with a button and a display box.

The button in the Ownership section will change its function depending on the ownership status of the input.

If the input does not currently have an owner, the button will say Own. There will be nothing displayed in the box. Press and hold Own and your console will become the owner of that input.

If the input already has an owner, the button will say Take. The current owner's device name will be displayed in the box. Press and hold Take and your console will take ownership of that input from the previous owner.

If your console is already the owner, the button will say Release. Your console's name will be displayed in the box. Press and hold Release and your console will release ownership, so that there is no owner of that input.

Notes:
Ownership does not need to be released before it is taken.

Once your console has ownership, gain and input settings can be adjusted.

If your console is not the owner of an input, you will see that the controls are greyed out, and you cannot make any changes.

Any inputs that do not currently have an owner, can be owned from the console with one button. To do this, go back to the Setup section of the stagebox Detail View and press and hold Inputs Ownership.

Please Note:
This button will only be active if all inputs are unowned.

Multiple control devices can own different inputs of a single stagebox at the same time. But there can never be more than one owner for the same input.

GPO Ownership (SB 8.8 and SB i16 only)

GPO Ownership settings must be adjusted from the Dante Configuration page. Tap on the stagebox and it's Detail View will appear. Tap GPIO to the right of the stagebox's Detail View. To become the owner of a specific GPO, press and hold Own or Take as appropriate. Press and hold Rel to release ownership.

Press and hold GPO Ownership to become the owner of all previously unowned GPOs.

Multiple control devices can own different GPOs of the stagebox at the same time. But there can never be more than one owner for the same GPO.

Loading Showfiles

Stagebox settings are retained in Live console showfiles so it can be recalled with a showfile load. When a showfile is saved, the console also whether it is the "owner" of each input (and other settings).

When a showfile is loaded, the console will attempt to become the owner of all of the inputs (and other settings) that it was the owner of when the showfile was saved. The console will only be successful if that input (or other setting) has no owner, or is owned by the console at the time of the showfile load. If that input (or other setting) is owned by another device, the console will not be able to take ownership.

Parameter Ownership Status Prior to Showfile Load Parameter Ownership Status After Showfile Load Parameter Settings Pushed from Showfile to Stagebox?
Owned by the console Owned by the console Yes
No owner Owned by the console Yes
Owned by another device Still owned by the other device No

Please Note:
If the console was not the owner of an input (or other setting) at the time of showfile save, when the showfile is reloaded, the console will not attempt to become the owner of this input (or other setting) and it will be unaffected by the showfile load.

For example:

An L500 is the owner of inputs 1, 2 and 3 on an SB 32.24 and the showfile is saved.

After the showfile is saved, an operator with an L200 takes ownership of input 1. The operator of the L500 releases ownership of input 2, and retains ownership of input 3.

The L500 operator reloads the showfile, and the following will occur:

Input 1: The L500 attempts to become the owner, but Input 1 is owned by the L200. So the L500 cannot take ownership. Any gain settings, +48V, Pad etc input settings will not be pushed from the L500 showfile to the stagebox's Input 1. Input 1 retains its previous gain and input settings.

Input 2: The L500 attempts to become the owner. Input 2 is not owned by any device, so the L500 successfully becomes the owner. Any gain settings, +48V, Pad etc input settings will be pushed from the L500 showfile to the stagebox's Input 2.

Input 3: The L500 attempts to become the owner. Input 3 is already owned by the L500. Any gain settings, +48V, Pad etc input settings will be pushed from the L500 showfile to the stagebox's Input 3.


Please be aware of the current ownership statuses of each input on your stagebox before loading a showfile with input settings stored. If other devices have ownership of some inputs, your console will not be able to take ownership of these inputs automatically on showfile load.

Before loading a showfile, go to Dante Configuration and add the stagebox to the Configured Devices List. Tap on the stagebox and its Detail View will appear. Tap on Input 1 and tap Edit Settings.

Check Input 1's ownership status. If the input is owned by another device (not your console), press and hold Take to take ownership. If the input has no owner, or the console is already the owner, proceed to the next input.

Repeat this for all inputs that you wish to have control of. Each input should either have no owner, or your console should be the owner. Then load the showfile and all appropriate inputs will be owned and settings will be pushed from the showfile to the stagebox successfully.

Control

For Net I/O stageboxes, all parameters and settings will be displayed in the Dante Configuration page Detail View when the device is tapped.

Tapping Inputs or Outputs will show the settings for each input/output.

Tapping on an input provides control over the input parameters: (providing that the Inputs are owned (see Ownership section above)).

When an input from an SSL Network I/O Stagebox has been routed to the input of a channel, the input parameters will also display in the Input/Routing section of the Detail View. The parameters can then be controlled from the Quick Controls, the Channel Control Tile and the TaCo app.

SB 32.24 Analogue vs AES Inputs

Net I/O SB 32.24 stageboxes running at 96kHz have a maximum of 32 inputs available. The inputs can either be analogue (up to 32) or AES (up to 4 pairs). This is user-definable on a pair by pair basis.

To choose between analogue and AES inputs go to the Dante Configuration page and tap on an SB 32.24 Main device to bring up the device's detail view.

Press and hold Stagebox Ownership to become the owner of the Stagebox.

Tap on AES I/O and tap on the AES pair.

At 48kHz all analogue and AES inputs of the SB 32.24 are available simultaneously.

Gain Sharing Using Net I/O Stageboxes

Gain Sharing Using Net I/O Stageboxes

What is a Gain Compensated Output?

The SSL SB 32.24 stagebox provides two Dante outputs for each of the 32 mic amp inputs; one the main output and the second a gain compensated output which delivers a constant signal level.

Gain compensated outputs are advantageous when two consoles need to receive the same mic amp input. In the example of a FOH and Monitor desk setup the FOH console would receive the main outputs and the Monitor engineer who would receive the compensated outputs. In this scenario the FOH engineer would be able to control the gain of the mic amp feeding their console without affecting the level of signal received at the Monitor console.

How do Gain Compensated Outputs work?

The output of the analogue mic amp circuit feeds an A to D converter. This digital data is then feed to two paths. The first path routes the digital audio to the Dante Main output. The second path passes the data through a digital gain control which automatically compensates for any changes made to the analogue audio level, by applying an inversely proportional gain.

So for example if the analogue mic level was increased by 3dB, the digital gain control for the compensated output would decrease by 3dB to maintain a constant signal level.

Main and Comp Devices

When an SSL Network I/O Stagebox is connected to a Dante network, it will appear in Dante Controller and on the console as two separate Dante devices:

The Main uncompensated/gain dependant device

The Comp gain compensated device

The Main device receives the uncompensated/gain dependant signal and has control over the stagebox.

The Comp device receives the gain compensated signal and never has control.

Choose which console on your network should receive the uncompensated signal and requires gain control. This console will need to route from the Main stagebox device. To use Gain Sharing, this must be an SSL console.

Choose which Dante devices will should receive the gain compensated signal. These devices will need to route from the Comp stagebox device.

When the gain is changed by the Main device the signal level on the Main device will change depending on the gain applied. The signal level on the Comp device will not change as the appropriate gain compensation will be applied.

Adjusting the Calibration Point

On the gain slider of a stagebox input there is a γ symbol. This indicates the reference point for the digital gain compensation or Calibration Point.

When the gain slider is moved above or below the calibration point, the corresponding input on the Comp device will be trimmed by the difference between the gain value and the position of the calibration point.

For example, if the Master console sets the gain to be 3dB above the γ point, -3dB of digital trim will be applied to the Comp device. So the signal level on the Comp device will not change. If the Master console sets the gain to be exactly at the γ point, no gain compensation will be applied to the Comp device.

The Main device has control over the calibration point. The Main device can reset the calibration point or adjust it manually.

Recalibrate resets the γ point. Recalibrate should only be used after rough gain levels have already been set.

When the input is in Line mode, Recalibrate moves the γ point to the exact position of the analogue gain slider.

When the input is in Mic mode, Recalibrate moves the γ point to 10dB below the position of the analogue gain slider. The reason for this is a Mic level signal is likely to be far more dynamic and also require more gain added compared to a line level signal. This is to give head room and ensure the compensated input is not overloaded.

The calibration point can be more closely aligned in 3 dB steps by using the + or - 3dB buttons. This is reset the next time the input gain is recalibrated.

Practical Use

The main practical use for gain sharing is when sharing I/O between a Front of House console and a Monitor console.

One of the consoles Owns the inputs and therefore has control of the gain and receives the gain dependant signal. This must be an SSL console.

The other console receives the signal from the gain compensated split output. This does not have to be an SSL console and can be any Dante enabled device.

The console with ownership/control of the stagebox inputs will set the gain structure of the system. This console should set rough gains before the calibration point is altered.

Once the gain structure of the system has been set the Recalibrate button should be pressed on each input. This creates a reference or calibration point for the gain compensation.

The compensated inputs will not have their gain set until the Recalibrate button is pressed.

All owned inputs can be recalibrated at the same time. Go to the Dante Configuration page and tap on the Main stagebox device. Now press and hold Recalibrate All Owned Inputs.

If the gain structure of a specific input changes drastically before the show, Recalibrate may be used again to reset the calibration point.

Caution:
DO NOT use Recalibrate on open channels during the show as this will cause gain changes on the Comp device.
Caution:
SSL recommends that all outputs are muted on any device receiving the gain compensated signal before pressing Recalibrate as this could cause a jump in gain.
Working with Virtual Tie Lines

Working with Virtual Tie Lines

Using Virtual Tie Lines allows SSL Live consoles to be used as a typical Dante I/O device.

Dante Virtual Tie Lines will appear in the routing view as a local I/O type.

When routing to a Virtual Tie Line, only the internal route in the console is made - connecting a path to the Dante Expander Module.

The network route (connecting the Dante Expander Module to another Dante device on the network) must be made manually from Dante Controller.

Virtual Tie Lines should be used for routing between multiple SSL consoles, for live recording and rehearse mode.

Virtual Tie Lines cannot carry control data, and should not be used for routes from Net I/O stagebox inputs unless control is not required.

The Dante Expander Module's I/O does not contain any Virtual Tie Lines by default, they must be created.

Please Note:
Virtual Tie Lines are only possible through the Dante Expander Module. The BLII Bridge does not support Virtual Tie Lines.
Please Also Note:
When the console is connected to a BLII Bridge, Virtual Tie Lines must be created before dual domain routes. The console is not deterministic when choosing a Dante interface to create dual domain routes through. And the console cannot switch routes from the Dante Expander to the BLII Bridge once routes have been made. Failure to create Virtual Tie Lines before dual domain routes, can cause the Dante Expander's Dante I/O resource to be used up by dual domain routes, at which point the console will not allow more Virtual Tie Lines to be created.

Creating Virtual Tie Lines

To create Virtual Tie Lines go to MENU > Setup > I/O > Local/MADI Configuration then tap on the Dante Expander Module to bring up its Detail View. Double tap on the Virtual Tie Lines label area and select the number of Virtual Tie Lines you require. This will create the same number of inputs and outputs.

Up to 32 Virtual Tie Lines can be created at 96kHz or up to 64 at 48kHz.

When dual domain routes are made, fewer Virtual Tie Lines can be created.

For example: If the console and Dante Expander Module are at 96kHz the maximum Dante routes possible is 32. If 2 dual domain routes are made, the remaining number of possible Dante routes becomes 30. So no more than 30 Virtual Tie Lines can now be created.

Creating one Virtual Tie Line creates an input and an output simultaneously.

If the quantity of Virtual Tie Lines does not update after attempting to create more, you have reached the maximum quantity of Virtual Tie Lines possible.

This could be because

  • You are trying to create more than 32 Virtual Tie Lines at 96kHz or more than 64 at 48kHz
  • Or you already have some dual domain routes made, and therefore fewer Virtual Tie Lines can now be made.
  • The more Virtual Tie Line routes that have been allocated, the fewer Direct Distributed Routes will be available for other Dante devices. Virtual Tie Lines are always allocated to the first n number of Dante inputs and outputs. Direct Distributed Routes can be created from the remaining Dante inputs/outputs.

For example (at 96kHz), if I make 10 Virtual Tie Lines, Dante inputs and outputs 1-10 will be assigned to Virtual Tie Lines. All existing dual domain routes using these I/O points will be moved to different routing points. Only Dante inputs and outputs 11-32 are now available for dual domain routes.

The total quantity of dual domain routes and Virtual Tie Lines cannot exceed 32 channels at 96kHz or 64 channels at 48kHz. The number of Dual Domain Routing inputs/outputs currently in use is displayed in a resource bar above the Configured Devices list in the Dante Configuration page.

Important:
Changing the quantity of Virtual Tie Lines may cause a brief loss of audio.

Routing to/from Virtual Tie Lines

The Dante Virtual Tie Lines created will now appear in the routing view.

First, make a route on the console to/from Dante Virtual Tie Lines.

Then in Dante Controller, make the route between the console's Dante Expander Module and the other Dante device.

For example, let's say we want to route two channels from a computer running Dante Virtual Soundcard to the input of Channels 1 and 2 on the console using Virtual Tie Lines.

Ensure both the console's Dante Expander Module and the computer running Dante Virtual Soundcard are visible in Dante Controller and within the same netmask (names in black text).

Now create two Virtual Tie Lines on the console. Go to MENU > Setup > I/O > Local/MADI Configuration and tap on the Dante Expander. Double tap on the Virtual Tie Lines quantity and enter 2.

Now locate Channels 1 and 2 in the Channel View. Double tap on Channel 1's eyeconix image and tap on Input/Routing. Now tap on Route Input A. Tap on the console (first routing point, usually starts with "LIVE"). Now tap on Dante Virtual Tie Lines. Tap on 1 and tap Make. The route will go green.

Now repeat this for Channel 2 and Dante Virtual Tie Line 2.

Back in Dante Controller, open the crosspoint matrix for the computer's transmit channels and the console's Dante Expander receive channels.

Create a route from the computers Dante Virtual Soundcard channels 1-2 to the console's Dante Expander channels 1-2 by clicking in those crosspoints.

Green checkmarks will appear in those crosspoints.

Using the Dante Expander Module as a Live Recorder

You can also use the Dante Expander Module as a Live Recorder.

To do this go to MENU > Setup > I/O > Local/MADI Configuration and tap on the Dante Expander Module.

Select the appropriate recorder ID, and the quantity of Virtual Tie Lines will be created automatically (32 at 96kHz or 64 at 48kHz).

The Dante Expander can now be used as a Live Recorder or with Rehearse mode, just as MADI devices. For more information on Live Recorders please see Live Recorder Setup and Rehearse Mode.

Further Reading

Further Reading

If you would like to learn more about Dante, the following resources are available:

SSL Live Application Notes

LAN-009 Configuring a Live Console for Use with Dante

LAN-010 Configuring a Dante Device and Virtual Tie Lines in the Console

LAN-012 Live Console IP Address Configuration Guidance


Audinate Website

audinate.com/resources

The Audinate website is a fantastic resource for further documentation, video tutorials and whitepapers. Audinate also offers an online Dante Certification programme.

Useful Links:

Setup: Installation Guide
Index and Glossary
NEXT: Console Configuration