Lawo mc² UHD 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² UHD console connects to hi as one Node through the MCX Ember+ provider. The Node has two capabilities on the same address and Port: Crosspoint Management for the audio signal 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² UHD Routing and Parameters	The audio matrix at `facades > vsm > routing > signalMatrix` as Sources, Destinations, and Crosspoints, and the parameters that you pin on the Node.	hi must route mc² UHD signals, or monitor and change mc² UHD parameters.

Caution

Confirm that the installed MCX release publishes the signalMatrix branch. From MCX release 10.4 (build 9 of 10.4.0), the console also disconnects external Ember+ connections when a production is loaded.

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 installed MCX release, and use the Lawo tooling for the signal labels.
Confirm the network access in Network Requirements.

Configure mc² UHD Routing and Parameters

Device Configuration

Confirm that the console publishes the signalMatrix branch, and that the Ember+ provider is enabled. The MCX Ember+ provider uses TCP Port 9000, the hi default.
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² UHD 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 signal matrix 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	Port of both capabilities default `9000`
Signal matrix	`facades > vsm > routing > signalMatrix`	Read automatically no hi setting
Port names	User label of each signal	Port names controlled by Overwrite Names

Common Checks

Symptom	Check
The Node connects, but no Sources or Destinations appear.	Confirm that the installed MCX release publishes the `signalMatrix` branch.
The Node disconnects and reconnects.	Check whether a production was loaded, or whether the signal matrix changed on the console. hi reads the console again in both cases.
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 signal matrix 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.