Manuals

DiGiCo Console Integration | Setup Guide

Click here for the manual if you are using KOS below version 5.5 or DiGiCo software below version V1742.
https://www.youtube.com/watch?v=nVZiLqs5EsI

Step-by-Step Setup Guide

KOS 5.5
  • Stand-alone console integration. No additional computer required.
  • Automatic mapping following console audio routing
  • Supports console redundancy
  • Synchronous load/save of session files
All 2nd generation KLANG processors with KOS 5.5+ support the stand-alone console integration.
All KLANG processors can be used with an additional computer running KLANG:app 5.5 and support automatic mapping with socket names KLANG 1, 2, 3 etc.

Quick Start

DMI-KLANG with stand-alone Console Integration in SD12 or Q series. Stand-alone console integration without an additional computer works with all 2nd generation KLANG processors. Socket names may need to be labelled manually to KLANG 1, KLANG 2, etc.

STEP 1 | DMI-KLANG INSTALL

  1. Switch console power off.
  2. Install DMI-KLANG in console DMI slot 2.
  3. Connect DMI-KLANG console port to console network port.
  4. Switch console power on.
DMI-KLANG network activity LEDs start to flash. DMI-KLANG status LED lights up and will turn purple within 30 sec.

STEP 2 | NETWORK IP SETUP

The stand-alone KLANG integration works with DMI-KLANG, :vokal or :konductor with KOS 5.5+. If a cascade of KLANG processors is required or if :fabrik or :vier are used, a computer with KLANG:app 5.5+ is required (See instructions below)
  1. Setup > External Control > Check console IP address at the bottom “LOCAL: …”, e.g. 192.168.2.10. (DiGiCo consoles are shipped with a fixed IP in the range 192.168.2.10 – 192.168.252.252 with a subnet mask /16 = 255.255.0.0)
  2. Audio I/O > DMI-KLANG pops up (Conform all ports might be required)
  3. DMI-KLANG > Card Setup > KLANG Control > Set fixed IP to console IP +4 in the last number, e.g. 192.168.1.200. Use subnet mask /16 = 255.255.0.0 (default for DiGiCo consoles)
  4. Setup > External Control > Enable External Control: YES.
  5. KLANG Interface: KLANG enabled.
  6. Click on add device and choose KLANG. “IP Address”: Use the IP address of DMI-KLANG, e.g. 192.168.1.200
  7. Click on the red cross under “Enabled” to activate and it turns into a green checkmark when successfully activated.
External Control > KLANG connection status turns green.

STEP 3 | AUDIO ROUTING

  1. Layout > Channel List > Input Channels > Route direct outs “outputs” as required to DMI-KLANG with socket name KLANG 1, etc.
  2. Layout > Channel List > Groups > Also route direct outs “outputs as required
  3. Aux > Merge Input > Route merge inputs “alt input” from DMI-KLANG with socket names KLANG 1, etc.
  4. Setup > Ext Ctrl > KLANG Interface > Enable Mapped Channels
All routed/mapped aux nodes will become KLANG enabled.

STEP 4 | IMPORT AUX MIX to KLANG

  1. Fire a snapshot -> all KLANG nodes are now off
  2. Setup > Ext Ctrl > Enable all channels (Macro is available)
  3. Import Levels / Pans > KLANG in stereo
  4. Optional or at any later point: open the KLANG GUI on an aux node and switch from stereo to 3D and place instrument around and above or below your head.
  5. Update Snapshot.
“Start in KLANG where you left off in stereo in the DiGiCo.”
We Told You So – Lightening Fast Setup!

Optional

CONNECT KLANG:app

via CAT5

faq icon to expand accordian

    • Connect PC, Mac or tablet with ethernet cable to DMI-KLANG Control port.

    • Set fixed IP on PC, Mac or tablet ethernet port to the same range as console with the same subnet mask. E.g. console 192.168.2.10 / 255.255.0.0 use 192.168.1.50 / 255.255.0.0

via WiFi

faq icon to expand accordian

  • Connect WiFi Router to DMI-KLANG control port.

  • Make sure that the WiFi Router uses either the same IP address range as the console with the same subnet mask. Console: 192.168.2.10 / 255.255.0.0 Use 192.168.x.y with subnet mask 255.255.0.0 and make sure its DHCP server does not provide the IP addresses already used by console and DMI-KLANG.

  • or a completely different (non-overlapping) IP address range e.g. 10.11.12.x with subnet mask 255.255.255.0 (DMI-KLANG can handle a fixed and a DHCP IP address simultaneously)

  1. Open KLANG:app. Download here.
  2. Go to CONFIG > CONNECT > select DMI-KLANG from the list.
  3. Go to FADER > Change a fader and check the fader on the corresponding aux node on the console.
KLANG:app can be used to control KLANG enabled aux nodes (bi-directionally)

Detailed Guide

For all other KLANG processors and using KLANG:app as the bridge.

1 | Connect Computer to Console Network

Connect your computer running KLANG:app 5.5+ to the same network as your DiGiCo SD or Quantum console.

faq icon to expand accordian

DiGiCo Consoles use a default static / fixed IP address of 192.168.x.x with a /16 = 255.255.0.0 subnet mask by default.

Make sure your computer has an IP address in the same subnet as the DiGiCo console and uses the same subnet mask. Some DiGiCo console use a second IP address for the engine, that sits just above the surface IP address

Example:
Console/Surface has IP address 192.168.2.10 and subnet mask 255.255.0.0
(Engine could occupy the IP address 192.168.2.11)
Set your computer to IP address 192.168.1.50 and subnet mask 255.255.0.0

How to Set a Fixed / Static IP Address

2 | External Device on Console

In KLANG:app > CONFIG > CONNECT a list of the computers local IP addresses is shown:

Write down the IP address that matches the IP range of your console. In this case: 192.168.1.80

On the console, go to Setup > External Control.

  1. Enable External Control: YES.
  2. KLANG Interface: KLANG enabled.
  3. Click on add device and choose KLANG.
  4. “IP Address”: Enter the IP address of the computer running KLANG:app. Do NOT enter the IP of the KLANG processor here!
  5. “Send”: leave this at default “9111” as also shown in KLANG:app.
  6. “Rcv“: enter the Console Receive Port 8200 as shown in KLANG:app.
  7. Click on the red cross under “Enabled” to activate and it turns into a green checkmark when successfully activated.

3 | Automatic Detection of Console

When no console is currently configured for console integration in KLANG:app, a popup window will appear in KLANG:app. The DiGiCo console sends out a discovery message every couple of seconds to the KLANG computer IP and port as defined above.

HELP opens this setup website.

ACTIVATE uses the current KLANG settings (icon, color, channel sorting, group assignment, mix icons)

WIPE&ACTIVATE to automatically setup Console IP and Port in KLANG:app, switch the console integration to active, request the Console Routing to KLANG socket names and perform a sync.

The right LED above KLANG:app CONFIG icon will turn green (static or blinking). On the DiGiCo console, the KLANG indicator will turn green as well, once the connection is established successfully.

In case the connection is lost afterwards, the connector on the DiGiCo will turn red:

Automatic Mapping & Socket Names

Direct Out and Merge Input routings with special Socket Names in the console are used to automatically map Console aux nodes to KLANG channels and Console Auxes to KLANG mixes

Define Socket Names

Go to Console > Setup > Audio I/O

Chose the Audio Interface that is connected to your KLANG processor. In this example we choose MADI.

Socket names are stored in snapshots on the console. Hence, use the edit range function to change the socket names for all snapshots. Do NOT forget to deactivate the edit range function afterwards.

Socket Names for KLANG Mix Returns

Skip this step for DMI-KLANG and for :konductor via OPTOCORE as they have pre-defined socket names.

The Mix returns from the KLANG processor are shown on the left.

Click on the first node and enter KLANG 1 as the socket name. “KLANG” is the important identifier that is used to determine that a KLANG mix is routed back to the console aux merge input in the next steps.

For a cascade of KLANG processors, the socket names must include the cascade device ID, e.g. processor 1 is named BAND(1) and processor 2 is named BAND(2) in CONFIG > INFO > SET > set device name, then the socket names on the DiGiCo must be KLANG(1) 1,2,3… and KLANG(2) 1,2,3… etc.

Then increase the number of sockets to exactly double the KLANG mixes. In our case, we have 16 KLANG mixes on the processor, so we enter 2*16=32 sockets.

Then click on auto-name.

Socket Names for KLANG Direct Outs

Skip this step for DMI-KLANG and :konductor via Optocore (engine A, ch 1–64) as the have pre-defined socket names that will work for auto mapping. For :konductor engine B (ch 65–128) use socket names KLANG 65 … KLANG 128.
When using a cascade of KLANG processors, the direct out routings to both processors need to be exactly the same. KKA-998

Repeat the same steps for the outgoing signals (from Console to KLANG processor). Enter the number of channels in this case 64 channels.

When e.g. working with a :konductor, label the first socket name of a second MADI port to KLANG 65, auto-map 64 channels.

MADI 1 will send ch 1-64 to :konductor, MADI 2 will send ch 65-128. The mixes will be returned via MADI 1.

Channel List

Layout > Channel List.

Route Direct Outs

  • Unfold Input Channels or Group Output
  • Enable Edit
  • Click on a field in the outputs column

Click on direct outs > port > choose MADI > Select a signal group > Choose one of the free KLANG channels.

Route Merge Inputs

Unfold Aux Output

Click on a field in the alt input column

Merge input > Choose MADI > select a signal group > select a KLANG mix e.g. “KLANG 1” for the left channel of the mix return.

Auxes for KLANG integration need to be stereo auxes!
The merge input has to be switched “on”.

KLANG Interface Settings on the Console

KLANG enabled

  • Must be ON for the KLANG DiGiCo console integration to work. It will then communicate via network with the KLANG system. Aux nodes can be “KLANG enabled”
  • Turn OFF, if KLANG integration should not be used. Aux nodes, that were previously KLANG enabled will be send to the consoles internal aux processing instead.

KLANG bypassed

  • Must be OFF for the KLANG DiGiCo console integration to work.
  • Turn OFF to temporarily bypass the KLANG processing for KLANG enabled aux nodes, and use the console’s internal aux processing instead.
The Mix Volume of Mapped Mixes will be forced to 0dB (KLANG bypassed: OFF) and -INF dB (KLANG bypassed: ON)

Copy KLANG to Aux Send

When ON, KLANG levels of KLANG enabled aux nodes will constantly be copied to the internal aux send levels. But changes of the internal aux send levels will NOT be copied to KLANG levels.

Enable Mapped Channels

See section below on “Enable Mapped Channels” in KLANG:app > CONFIG > EXT CTRL.

Import send levels

For all KLANG enabled nodes, the aux send levels will be imported into KLANG channel levels.

DiGiCo’s Global Set to Defaults cannot directly alter KLANG parameters.
Workaround #1: Use the Global Set to Defaults > send levels and then click on External Control > Import send levels
Workaround #2: Use KLANG:app > CONFIG > PRESET > Set Values

Import levels + pans

For all KLANG enabled nodes, the aux send levels and the DiGiCo pannings will be imported into KLANG channel levels and stereo panning will be copied as well. As a result the imported KLANG mix will sound identical to the DiGiCo mix (In KOS 5.5 the stereo panning law D1 will be used automatically).

Stand-alone Console Integration

The KLANG DiGiCo console integration can now also be run on the KLANG processor directly, without the need for a computer or tablet running KLANG:app.

The stand alone integration does not work for a cascade of KLANG processors.
  1. Find out the IP Address of your KLANG processor. For DMI-KLANG in a DiGiCo Console, the IP address can be set via the KLANG Control panel.
  2. In External Control > Enter the IP Address of your KLANG processor with Send port 9111 and Rcv port 8200.
  3. In order to configure advanced settings connect with KLANG:app in Admin mode to your KLANG processor. Instead of K or D an “X” is shown above the CONFIG icon.
The stand-alone integration always runs in the mode “Full DiGiCo Integration” with “Automatic Mapping” and cannot be switched off via KLANG:app.

What’s new | Feature List

This requires KLANG:app 5.5+ and DiGiCo SD / Q software version 1742+

A console Session report (*.rtf) can no longer be imported in KLANG:app.

Console Group Mapping

DiGiCo group channels (mono and stereo groups, not surround groups) can now be mapped to KLANG channels just in the same way as regular input channels.

Console IP Ping / Reachable

KLANG:app 5.5+ is able to ping IP addresses on the network. Once a console IP is pingable the color switches green.

If the IP address is outside of the computers IP address range, the color will switch to orange. Grey means, that no response has been obtained.

Redundant Console IPs

No Redundancy (default): Use only one Console IP

When Console A active or Console B active is selected a second Console IP address field appears.

Configure the IP address of the Console A and Console B. Use the Redundancy Mode dropdown to select which console IP address should be used. When switching from Console A to B and vice versa a sync between DiGiCo and KLANG will automatically be triggered.

If a console is NOT audio master and it is communicating with a KLANG:app or KLANG processor, its KLANG status LED will always be green, although it is not actively controller any values.

Automatic Show File Load/Save

When a DiGiCo session is saved, a KLANG show file with the exact same name (including .ses) will be stored on the KLANG processors.

All mix parameters (panning, level, mute, solo, stereo link) as well as mix/aux and channel names will be stored in the DiGiCo session file. However, the KLANG file saves the last state of the mixing parameters, but additionally it saves channel icon, color, sorting and group association as well as mix icons.

When a DiGiCo session is loaded the matching KLANG show file will be loaded (if available on the processor) and a sync will be triggered (Pull mix settings)

Lite Translator | Only Names and Snapshot Fire

A “lite” KLANG DiGiCo console integration is now available. While the “full” integration requires Aux and Channel mapping and syncs all KLANG mixing parameters between console and KLANG, the “lite” version only requires channel mapping and only syncs channel names.

  • Requires channel mapping, auto-mapping via direct out socket names KLANG 1, 2, 3…
  • Saves and Loads KLANG show file with the same name when a DiGiCo session is saved/loaded
  • Console Snapshot fire (with ID “num” in Snapshots panel) will recall KLANG snapshot with this index in the KLANG snapshot list

Enable Mapped Channels

The button on the DiGiCo is identical to the button in KLANG:app > CONFIG > EXT CTRL. KLANG enable all aux nodes with a direct out socket name KLANG 1,2,3 etc and aux merge input with socket names KLANG 1,2,3. Also deactivates all NOT mapped nodes on the console and in KLANG.

DiGiCo Integration 1.0 | Quick Start Guide

https://www.youtube.com/watch?v=ULPdyzsp2bk

Network Overview

In order for the KLANG DiGiCo remote to work, a computer with KLANG:app is required as the bridge between the DiGiCo console and KLANG hardware. Hence, the computer needs to have a network connection to the DiGiCo console and also to the KLANG hardware.

Standard network setup

faq icon to expand accordian

The standard network uses one network adaptor and simply connects the console, the computer running KLANG:app and the KLANG processor as well as additional KLANG:apps or :kontroller for personal mixing to the same network.

Advanced | Separate KLANG and DiGiCo Networks

faq icon to expand accordian

In some scenarios it is advantageous to keep the DiGiCo console network and the KLANG network separate. This can easily be achieved by using a computer with two network adaptors, e.g. by using an additional USB Gigabit adaptor.rnrnReasons to keep the two networks separate might be one or more of the following:

    • KLANG control network is also used for Dante

Waves is used on the DiGiCo network and should be kept separate from the Dante network

Downloads

faq icon to expand accordian
Network Setup Guide PDF

External Control Setup

Step 1 | Settings in KLANG:app

  1. Open KLANG:app and connect to KLANG Processor. Go to CONFIG
  2. Click on EXT. CTRL. If this is not shown in the menu, switch to ADMIN mode (Click and hold CONFIG for 3 seconds > ADMIN).
  3. Under MIXING CONSOLE LINK, switch Mode to Setup. Set Console Type to “DiGiCO_SD”. Select Init Master as required for your workflow. See further below for details.
  4. Enter Console IP and the Console Receive Port. See the following diagram for details.

Step 2 | Settings on Console

On the console, go to Setup > External Control.

  1. Enable External Control: YES
  2. Suppress OSC retransmit needs to be enabled.
  3. KLANG Interface:”KLANG enabled
  4. Click on add device and choose KLANG.
  5. “IP Address”: enter the IP address of the computer running KLANG:app, shown after “App IP:” in KLANG:app. Do NOT enter the IP of the KLANG processor here!
  6. “Send”: leave this at default “9111” as also shown in KLANG:app.
  7. “Rcv“: enter the Console Receive Port 8200 as shown in KLANG:app.
  8. Click on the red cross under “Enabled” to activate and it turns into a green checkmark when successfully activated.
Screenshot of DiGiCo > Setup > External Control
DiGiCo > Setup > External Control: The KLANG Interface should have a green checkmark, then it is enabled.

Signal Flow and KLANG Control

On the console, switch to the master screen. To enable aux nodes for KLANG processing, first click on the grey button with the KLANG logo. It turns purple and then you can KLANG enable aux nodes which is idendified by a purple G button. Internal aux processing for KLANG enabled channels is off. Route audio via direct out to KLANG and return the KLANG immersive in-ear mixes back to the console via the aux merge input.

KLANG enabling for aux nodes is turned off
KLANG enabling for aux nodes is activated. Tapping on the aux node will toggle this aux node between internal aux processing and KLANG immersive processing.

KLANG control is available for each aux node:

  • channel modes mono/stereo/3D/i3D, azimuth (angle on the orbit around the head in KLANG:app STAGE view),
  • elevation (height in KLANG:app STAGE view),
  • width for stereo input channels,
  • level (aux send level and channel level in KLANG:app)
  • and the on button that shows the opposite of mute in KLANG:app.

KLANG mix settings are stored in the console’s snapshots and sent to KLANG when a snapshot is recalled.

Click on the small KLANG head to open or close the expanded view.
  • Console aux names are sent to KLANG mix names.
  • All KLANG controllers are sent both ways.
  • In case of a reconnect, a re-sync or a restart of KLANG:app all KLANG controls will be synced. Depending on the Sync Master: Console -> all controllers stored in SD will be sent to KLANG. KLANG -> all values stored in KLANG will be sent to the console. See further below for details.
  • When an aux node is not KLANG enabled, it will be deactivated and hence hidden in KLANG:app’s fader and stage view. When a channel is switched on or off it will be automatically KLANG enabled or disabled in the console.
  • KLANG bypass can be used to quickly switch to console’s internal aux buss mixing. Create your own custom KLANG bypass macro that also switches off all merge inputs from KLANG.

Connection Status in KLANG:app

Back in KLANG:app, you will see a

  • “D” indicator (DiGiCo console is Init Master) or
  • “K” (KLANG is Init Master) or
  • “T” Throttling (temporarily slowing down the connection speed to prevent network congestion)

indicator above CONFIG icon and basic information on the console.

  • <No indicator>: Mixing Console Link Mode is set to OFF
  • Blinking Green: Mixing Console Link Mode is set to Setup
  • Static: Mixing Console Link Mode is set to Active
  • Blinking Red: Link Mode is set to Active but NO Mix or NO Channel Mappings are set.
  • RED: Console Link connection not working / lost connection
  • YELLOW: Console Link connection issues, loosing connection
  • GREEN: Console Link connection OK and working.

Mixing Workflows

In the following we show two different workflows. The first Workflow (3.1) shows SD/Quantum users how to upgrade to KLANG and the second (3.2) shows KLANG users how to upgrade to the SD/Quantum mixing console link.

We recommend to NOT use fade times between snapshots in the SD/Quantum as the network communication from the console will slow down the workflow.
Currently, KOS/KLANG:app only support to map console input channels but no groups. This feature might be added in the future.
Snapshots do not need to be transferred from the console to KLANG, because all settings will be sent to KLANG once a snapshot is fired.

Workflow 1: SD/Quantum User Upgrades to KLANG

On SD/Quantum:

Load an existing session or start from scratch.
Activate KLANG enable for Channels and Aux as required.

In KLANG:app:

Load default showfile. Go to CONFIG > PRESET > SHOWS, select “default” and click the button LOAD.

Mix Mapping

CONFIG > CONNECT. Start with the first KLANG mix and proceed with all other mixes accordingly. Under remote, choose the console’s aux that should be mapped. Now you can switch between Auxes on the console and KLANG:app will follow and switch to the associated KLANG mix.

Channel Mapping

Go to Mix 1
Go to CONFIG > Channels

Start with the first channel you want to map. Then proceed exactly the same step for each channel till the end:

  1. *Map the cons’s channel to this KLANG channel. Click on the REMOTE CH dropdown menu and choose a console channel.
  2. Check if stereo LINK status in the console and KLANG is matching. If stereo LINK is red in KLANG, adjust the stereo LINK in KLANG:app accordingly
  3. Click RIPPLE DOWN in the REMOTE CH dropdown menu of the last channel you mapped.
  4. Jump back to 1. and proceed with the next channel…

When finished go to KLANG:app > CONFIG > CHANNELS > Paste META to ALL users
If working with a Cascade of KLANG units. Proceed with the first mix auf den next unit.

When finished go KLANG:app > CONFIG > EXT CTRL and set MIXING CONSOLE LINK > MODE from Setup to Active.

Now, select your Init Master from the drop down menu and click CONSOLE.

In order to sync the settings between console and KLANG, finally click Pull Mix Settings from Console.

Workflow 2: KLANG user upgrades to SD/Quantum console link

On SD/Quantum:

Files > Load default.ses session on console or create a new one.

In KLANG:app

Load your show you want to start with.

REMOTE MIX Mapping

CONFIG > CONNECT. Start with the first KLANG mix and proceed with all other mixes accordingly. Under remote, choose the console’s aux that should be mapped. Now you can switch between Auxes on the console and the KLANG:app will follow and switch to the associated KLANG mix.

The REMOTE MIX dropdown menu has the following entries:

  • NONE
  • <1,2,3,4,…>: concole Aux buss numbers followed with their labels.

 

REMOTE CH Mapping

Go to Mix 1. Go to CONFIG > CHANNELS.

The REMOTE CH dropdown menu has the following entries:

  • NONE
  • RIPPLE DOWN: Map all following channels with increasing numbers
  • CLEAR DOWN: Clear this current and all following mappings.
  • REFRESH: Pull the latest Channel Labels from console and refresh this list
  • <1,2,3,4,…>: Console Input Channel numbers followed with their respective labels.

Start with the first channel you want to map. Then proceed exactly the same step for each channel till the end:

  1. *Map the console’s channel to this KLANG channel. Click on the REMOTE CH dropdown menu and choose a console channel.
  2. Check if stereo LINK status in the console and KLANG is matching. If stereo LINK is red in KLANG, adjust in the console accordingly.
  3. Click RIPPLE DOWN in the REMOTE CH dropdown menu of the last channel you mapped.
  4. Jump back to 1. and proceed with the next channel…

When finished go KLANG:app > CONFIG > EXT CTRL and set MIXING CONSOLE LINK > MODE from Setup to Active.

Now, select your Init Master from the drop down menu and click KLANG.

In order to sync the settings between console and KLANG click on Push Mix Settings to Console.

Related Manuals

:app menu – CONFIG > CONNECT

Connect to KLANG devices on your network and manage the user settings. User Name & Assign Icon You can then edit the...

Musician and Engineer CUE modes

What is the CUE Feature? If you are in need and want to listen into an artists mix, this is what we call CUE. In th...

:app menu – CONFIG > ROUTING

The audio source is shown on the left. The audio sink is shown in the top line. The white square with an arrow in it ind...

Still Have Questions?

Contact us here