Lawo mc² Series Audio Console Integration Configuration

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Configuration Overview

An mc² console connects to hi as one Node through its Ember+ provider. The Node has two capabilities on the same address and Port: Crosspoint Management for the audio matrix and the global GPIO matrix, and Parameter Control for the Ember+ tree. hi names each Port from the Lawo user label of its signal.

Configuration	What hi Sees	Use When
mc² Routing and Parameters	The audio matrix and the global GPIO matrix as Sources, Destinations, and Crosspoints, and the parameters that you pin on the Node.	hi must route mc² signals or GPIOs, or monitor and change mc² parameters.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Confirm the network access in Network Requirements.

Configure mc² Routing and Parameters

Device Configuration

Enable the Ember+ provider of the console. Lawo documents Ember+ access to the mc² parameter tree from Release 5.0 onward, on TCP Port 9000. Optionally browse the provider with an Ember+ viewer to confirm which Channels, Signals, Matrices, and other branches the console publishes before you configure hi.
Give a user label to each signal that hi must show by name.
Record the console address and the provider Port. Ensure that the hi server can reach the provider.

hi Configuration

Add the mc² Series Audio Console integration (manufacturer Lawo) in Inventory.
Enter the console address and the provider Port for the Crosspoint Management capability and for the Parameter Control capability. hi defaults both to 9000.
Create the Node and wait for hi to read the matrices and labels.
After the Node is created, set Overwrite Names in the Startup group. With Yes, the default, hi replaces the Port names with the console labels when it reconnects. With No, hi keeps the Port names that it has.
After the Node is created, use Refresh Labels in the Operations group to read the console labels again. hi restarts the connection to read them.
Browse the parameter tree of the Node and pin the parameters that your workflow needs. See Parameter Control Nodes.

Settings Summary

Setting	Device Side	hi Side
Control Port	Ember+ provider Port documented as `9000`	Port of both capabilities default `9000`
Port names	User label of each signal	Port names controlled by Overwrite Names

Common Checks

Symptom	Check
A Port shows Input or Output followed by a number.	Give the signal a user label on the console, then use Refresh Labels.
A label edited in hi changes back after a reconnect.	Set Overwrite Names to `No`.

Verify the Configuration

Confirm that the matrices and the pinned parameters appear in hi. Compare the Port names in hi with the console labels. Route a noncritical Destination from hi and confirm the change in the Lawo tooling. Change a pinned, noncritical parameter from hi and confirm the change in the Lawo tooling. Change the same parameter in the Lawo tooling and confirm that the new value appears in hi.