Multiple KLANG immersive processors can be linked in KLANG:app to act as a single unit. This cascade of units will be defined by the unit name followed by an alphabetically sorted index in braces ().

For a cascade of KLANG processors, it is important that all devices are in the same network and connected correctly.

DMI-KLANG

ONLY connect one network cable between DMI-KLANG devices and the network switch.

ONLY connect one network cable between DMI-KLANG and the DiGiCo console. DO NOT connect the console a second time to the same network.

DO NOT additionally connect the WiFi access point to the Dante network switch. The two networks are connected through DMI-KLANG KLANG(1) already.

:konductor

No VLANs configured for :konductor.

ONLY connect one network cable between :konductor devices and the network switch.

DO NOT additionally connect the WiFi access point to the switch.

:vokal

No VLANs configured for :vokal, i.e. Dante/CONTROL and CONTROL ONLY are switched.

ONLY connect one network cable between :vokal devices and the network switch.

:vokal | EXPERTS – Separate Dante and Control

This connection scenario is more complex and requires thorough configuration of all KLANG processors first, i.e. CONFIG > INFO > SET > Expert Network Settings > Dante VLAN ID: 0 for each :vokal. With this setting, the Dante/CONTROL port of each :vokal will no longer carry CONTROL data.

A managed switch with proper VLAN settings and TRUNKS needs to be configured for :kontrollers to connect to both the CONTROL and the Dante network through dedicated VLANs.

www.klang.com/vlan

With this connection it is possible to keep Dante and CONTROL on separate VLANs.

:fabrik / :vier

ONLY connect one network cable between :fabrik/:vier devices and the network switch.

DO NOT additionally connect the WiFi access point to the switch.

 

1. Switch to Admin mode in KLANG:app
2. Log into the first KLANG processor/device of your new cascade
3. Go to CONFIG > INFO > Set > Set Device Name
4. Enter a Device Name and choose the Cascade index. Start with index 1.
5. Proceed with the next KLANG processor in the cascade. Set the same Device name and increase the cascade index e.g. 2.
6. Repeat for more devices if required
7. Refresh the Device list in CONFIG > CONNECT

KLANG:app automatically detects a cascade once more than one unit with the same Device Name and a different Device Index is found.

In the Fast User Switching Bar the cascade device index will be used as a prefix before the OUTPUT number.

• Go to CONFIG > INFO > Set > Set Device Name and click Revert

With KOS 5.5, the KLANG DiGiCo console integration offers an auto mapping feature using socket names on the console with the prefix “KLANG” followed by the channel number. For this to work with a cascade of KLANG processors, the socket names of the merge inputs need to reflect the cascade index as well.

Example: Two KLANG processors: BAND(1) and BAND(2). The socket names of the port receiving the mixes from BAND(1) need to be labelled KLANG(1) 1, …, KLANG(1) 32. The socket names for the connection from BAND(2) need to be labelled KLANG(2) 1, …, KLANG(2) 32, respectively.

• All mixes of all units of a cascade will be shown in the Fast User Switching Bar in KLANG:app
• Clicking on a Mix in the Fast User Switching Bar will log into the corresponding KLANG hardware
• Show File save and load commands will be triggered on all units of a cascade
• Snapshot commands (save, recall, rename, delete, first, next/previous, move up/down) will be sent to all units of a cascade
• Cascading of units is only visible in Show and Admin mode
• In Channels Menu “Paste THIS to ALL users” and “Paste META to ALL users” will copy settings to ALL mixes of a cascade
• Engineer CUE allows to listen to ALL mixes of a cascade. Musician CUE is not available in Admin mode when working on a cascade. Musician CUE is available in Show mode, but is limited to the mixes of this KLANG processor.
• Keyboard shortcuts for mixes e.g. CMD + 3 etc will trigger mixes in the fast user switching bar across all units of a cascade.