Dante Configuration is where you define I/O names and settings for Dante connections. These settings are saved with the showfile.
To open this menu go to Menu > Setup > I/O then tap Dante Configuration.
SSL Live consoles fitted with a Dante Expander Module are capable of 32 Dante inputs and outputs at 96kHz, or 64 Dante inputs and outputs at 48kHz.
The Dante Expander Module provides a Dante interface for SSL Live consoles. The Dante Expander has its own Sample Rate and its own Clock.
Therefore, the Dante Expander Module can be set to a different sample rate from the console itself. The Dante Expander's sample rate can be changed from within Dante Controller. The console's sample rate can be changed in Menu > Setup > System.
The Dante Expander features sample rate conversion, allowing the console to run at a different sample rate to the Dante network. The Dante Expander and the console must be running at the same Sample Rate unless SRC In is engaged. For more information on configuring the Dante Expander Module please see the setup instructions.
Use either Direct Distributed Routing or Virtual Tie Lines to route to/from Dante devices.
Direct Distributed Routes provide Dante and internal console routing directly from SSL Live consoles.
A Direct Distributed Route consists of:
Both routes can be made in one action from the console.
With Direct Distributed Routing, Dante devices will appear in the console's routing view, just as MADI devices do.
Devices must be configured in the Dante Configuration page before Direct Distributed Routes can be made.
When multiple Dante devices need to subscribe to a Dante channel or for routing between SSL consoles, Virtual Tie Lines should be used. Virtual Tie Lines are an alternative to Direct Distributed Routes.
Virtual Tie Line routing uses the Dante Expander module as a static I/O type.
Virtual Tie Lines are visible in the routing view under the console's local I/O as Dante Virtual Tie Lines. These can then be routed to/from just like any other local I/O type.
With Virtual Tie Lines only the console's internal route is made. The Dante route must be made manually in Dante Controller.
In order for the console to communicate correctly with the Dante network, the correct naming structure must be implemented.
First, ensure the Dante Expander Name is the same on the console as it is in Dante Controller.
Before any Direct Distributed Routes can be made, the Dante Expander's Dante name must match the one displayed in Dante Controller.
To check this, open the Detail View for the Dante Expander module in Menu > Setup > I/O then tap Local/MADI Configuration.
If the two names do not match either adjust the name on the console, to match the one listed in Dante Controller, or vica versa.
Back in the Dante Configuration page: 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 with a status bar to indicate the quantity of Dante inputs and outputs currently in use.
For each device in the Connected Devices or Configured Devices list, the device's Dante name and device type will be displayed.
There are two LEDs for the Primary and Secondary network port on each device, which indicate the primary and secondary network status. There are also PSU status LEDs for SSL Network I/O devices.
Configured Devices also have a status indicator to the left:
Tapping on a device in the Connected Devices list will bring up a read only Detail View for that device with the following information:
Before you can control or route to/from a Dante device, you must first move it to the Configured Devices list.
To do this tap Edit, then drag a device from the Connected Devices list (left), to the Configure New Device row at the bottom of the Configured Devices list (right).
Offline devices can be added, configured and routed to/from when setting up a Showfile without the particular devices physically available.
To do this first tap Edit, then tap Configure New Device and select one of the devices from the list:
Devices created offline will only be automatically assigned to a Connected Device when the names and device types match. Allowing for a power down/disconnection without losing any routing.
When the Dante names do not match, offline and Connected Devices will not be automatically assigned.
To assign a device on the network with an offline device manually, first press Edit, and simply drag and drop the device from the Connected Devices list onto the corresponding offline device from the Configured Devices list.
In the Detail View, you will be asked to confirm with the following dialogue:
Tap Assign to Configured Device to confirm.
Devices must be of the same type for this to work. Now the Configured Device and routing has been matched up with the online device.
This drag & drop method can be used to change which Connected Device is assigned to a Configured Device. Simply drag another Connected Device onto the Configured Device and the same warning will appear. Tap Assign to Configured Device to confirm.
It is also possible to unlink or separate Configured and Connected device pairings. The online device will move back to the Connected Devices List. An offline device will remain in the Configred Devices list. This offline device will have retained the routes and settings from the original linked device. This allows the user to transfer routes and settings from one device to another. To unlink a device, tap Edit and then press and hold Unlink.
Deleting a device will move the online device back to the Connected Devices list. All routes and settings will be deleted. To delete a Configured Device, tap Edit then press and hold Delete.
Configured Devices, routes and settings are stored in showfiles. When loading a pre-configured showfile, a Connected Device with the same Dante name and device type as a Configured Device will be automatically matched.
To configure a Dante device, tap on the device in the Configured Devices list. The Detail View will show the options for each device, which are now editable.
Any Configured Dante Device (online or offline) will now show up in the routing views on the console, and routes can be made as normal. The colours of each device and route will match the normal SSL Live routing colour key, which can be found here:
Routes made to/from a Configured Dante device will be Direct Distributed Routes. The Dante side of a Direct Distributed Route is visible in Dante Controller.Notes:
Creating Virtual Tie Lines allows you to interface with the Dante Expander Module as a static I/O type of the console. This is an alternative to Direct Distributed Routing.
Meaning that in the Local I/O menu of the routing view, Dante Virtual Tie Lines will be visible as an I/O type. Dante Virtual Tie Lines would have up to 32 or 64 inputs and outputs depending on the sample rate of the console and the Dante Expander Module.
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.
The Dante Virtual Tie Lines created will now appear in the routing view. You can also use the Dante Expander Module as a Live Recorder by selecting the appropriate recorder ID, and the quantity of Virtual Tie Lines will be created automatically.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.
The total quantity of Direct Distributed Routes and Virtual Tie Lines cannot exceed 32 channels at 96kHz or 64 channels at 48kHz. The number of Dante inputs/outputs currently in use is displayed in a status bar above the Configured Devices list in the Dante Configuration page.Important:
For SSL devices, all available parameters and settings of a Configured Dante Device will display in the Dante Configuration Page Detail View when the device is tapped.
Tapping Inputs or Outputs will show the settings and routes for each input/output.
When an input from an SSL Network I/O Stagebox has been routed to the input of a channel, the input parameters will display in the Input/Routing section of the Detail View, just as they would with MADI Stageboxes.
Just like Local/MADI preamps, the parameters can also be controlled from the Quick Controls and Channel Control Tile.
SSL Network I/O SB32.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.
In the Dante Configuration page, ensure that SB32.24 is in the Configured Devices list. Tap on an SB32.24 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 to activate. Then tap AES Input Enabled to engage. This AES pair is now active.
Disengage AES Input Enabled to deactivate that AES pair.
When AES inputs are activated the corresponding analogue inputs are deactivated:
At 48kHz all analogue and AES inputs are active and the above steps are not required.
When multiple SSL consoles are connected to the Dante Network, each console has the ability to adjust all parameters and settings for SSL Network I/O Stageboxes.
SSL Network I/O Stageboxes can be controlled by all SSL Live consoles, SSL System T consoles as well as PC computers running the Network I/O Controller application (which can be downloaded from the SSL website).
The concept of ownership has been introduced to assign one owner to each stagebox parameter, so that there are no fights for control.
To "own" a Network I/O Stagebox, first it must be listed in the Configured Devices list. Once this has been done, tap on the stagebox and its Detail View will appear.
There are five levels of ownership:
To become the Stagebox owner, press and hold Stagebox Ownership in the stagebox's Detail View. The Stagebox owner is listed in cyan to the left of this button.
To become the Input owner, press and hold Input Ownership.
To become the owner of one or more specific inputs, first tap Inputs x-x to the right of the stagebox's Detail View. Tap on the desired input and press Edit Settings. Then press and hold Own.
To become the GPO Owner tap GPIO to the right of the stagebox's Detail View. Then press and hold GPO Ownership.
To become the owner of one or more specific GPOs, press and hold Own beside the desired output.
Multiple control devices can "own" different settings of the device at the same time. But there can never be more than one owner for the same settings.
To Release ownership, locate the owned parameter in the device's Detail View and press and hold Rel.
To release Stagebox Ownership, press and hold the Stagebox Ownership button to toggle it off.
Ownership can be "taken" from other owners. To do this locate the desired parameter and press and hold Take.
Ownership does not need to be released before it is taken.
To find out which device is currently the owner of a parameter, locate the parameter in the device's Detail View. Next to the buttons for Own, Take or Rel there is a label area showing Dante name of the owner device.
When an SSL Network I/O Stagebox is connected to the Dante network it will appear in the Connected Devices list as two separate devices.
One device is for the Main (uncompensated) signal, and the other device is a compensated Dante split.
Only the Main device can own and have control of the Stagebox gain settings and other controls. The Compensated device can never own or have control.
The Compensated device's gain is compensated in the Stagebox itself, so any Dante device can receive the compensated signal. It does not have to be an SSL device.
Gain Compensation works by applying a digital trim offset, which is the negative equivalent of the analogue gain change value.
The Gamma point is the point at which the analogue gain value equals a digital trim value of 0dB, and there is no digital trim applied. Digital trim will be applied when the analogue gain level is above or below the Gamma point. The Gamma point is indicated on the analogue gain readout as γ.
The owner of an input has access to the Gain Compensation Recalibrate button. Pressing and holding the Recalibrate button will reset the Gamma point.
When the preamp is in Line mode, pressing and holding Recalibrate will move the Gamma point to the current position of the analogue gain knob. This means that the analogue gain value now equals a digital trim value of 0dB and no digital trim is applied.
When the preamp is in Mic mode, pressing and holding Recalibrate will move the Gamma point to 10dB below the current position of the analogue gain knob. This feature has been designed to protect the compensated signal against digital clipping, in the event that the analogue gain control is drastically reduced. This means that the initial digital trim value is -10dB, as the analogue gain value is 10dB above the Gamma point.
Pressing the + or - 3dB buttons raises or lowers the Gamma point by 3dB.
With an SB32.24, the Main device and the Compensated device can also live on two separate networks if desired.