Manuals
Console Integration | For Redundant Consoles
Please make sure DiGiCo V1742+ and KOS 5.5 are installed on your devices.
There are two scenarios:
A fully redundant setup with a dedicated KLANG:processor on each engine, or a single KLANG:processor connected to both engines.
While the fully redundant setup is preferable for Monitor Consoles where the engineer controls all musician’s mixes, the single KLANG variant is allowing the simultaneous use of KLANG:kontrollers and/or :apps.
FULLY REDUNDANT SETUP — DMI-KLANG
STEP 1 | DMI-KLANG INSTALL
- Install DMI-KLANG in each engine
- Connect DMI-KLANG’s console port with one of the used engine’s network ports.
- As in any redundant application, we also connect both engined with a network cable.
STEP 2 | NETWORK IP SETUP
- The IP Address of DMI-Klang A is added as a KLANG Device in Engine A’s External Control Configuration.
- The IP Address of DMI-Klang B is added as a KLANG Device in Engine B’s External Control Configuration.
- Now each engine talks directly and independently to the installed DMI-Klang, while the console’s redundancy keeps both devices synchronised.
FULLY REDUNDANT SETUP — :KONDUCTOR ON MADI
The setup for a :konductor or :vokal on MADI is very similar:
STEP 1 | CONNECT :KONDUCTOR
- Processor A is connected to Engine A via MADI and between one Control Port and one Console Network Port via network cable.
- The same is done on Processor B.
- Engine B and both engines are connected with a network cable.
REDUNDANT CONSOLE — SINGLE KLANG
STEP 1 | CONNECT :KONDUCTOR
- A single :konductor needs to be connected via Optocore to both engines.
- Connect one of :konductor’s control ports to one console network port on engine B.
Make sure to avoid connecting another :konductor network port to engine A, as this would create a network loop!
STEP 2 | NETWORK IP SETUP
- The IP Address of :konductor is added as a KLANG Device in Engine A’s External Control Configuration.
- The IP Address of :konductor is also added as a KLANG Device in Engine B’s External Control Configuration.
:konductor will now follow the Console’s Network Audio Master setting:
If Engine A is Audio Master, :konductor will communicate with the IP of Console Engine A,
if Engine B is Audio Master, :konductor will communicate with the IP of Console Engine B.
If Engine A is Audio Master, :konductor will communicate with the IP of Console Engine A,
if Engine B is Audio Master, :konductor will communicate with the IP of Console Engine B.
Adding a network switch with connections to a DMI-Dante and Link-port in :konductor allows the deployment of :kontrollers – regardless which console engine is active.
