Lawo mc² UHD Series Audio Console

Lawo mc² UHD Series Audio Console

Minimum hi Version: v2.5.0

Overview

The Lawo^® mc²^™ UHD series integration uses Ember+ for Crosspoint routing and the parameters published by the console.

Network Requirements

• Connection Model: Outbound from hi

• Multicast / Unicast: Unicast only

• Firewall: Allow outbound TCP from hi to the console on Port 9000 by default.

• Callback: No inbound callback to hi is used.

• Security: Keep the plaintext control connection on a trusted management network.

Standards Conformance

Operator Workflow

• UI Surface in hi: Inventory, Parameter Control, and Control Panels

• Layers Controlled: Audio, Control

• Routing Semantics: hi exposes the Ember+ matrix and parameters published by the console.

• Notes for Operators Familiar with the Vendor's Own Tooling: The exact controls available in hi are defined by the console's published Ember+ tree. Use Lawo tooling for DSP design and show-file configuration.

Connection Details

Required Configuration

Device-Side Setup

Follow Lawo mc² UHD Series Audio Console Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Device Coverage

Tested With identifies devices that have been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

This integration supports the Lawo mc² UHD range.

Tested With

• Lawo mc²56 MkIII

Supported Product Range

Lawo lists the following consoles for the MCX software that this integration reads. Confirm that the installed MCX release publishes the signalMatrix branch.

• Lawo mc²96

• Lawo mc²56 MkIII

• Lawo mc²36 MKII

• Lawo mc²36 MKII xp

Known Limitations

• Redundancy is not supported by this hi integration.

• Validate the available Ember+ tree and matrix behavior during commissioning.

• hi reads the audio matrix from the signalMatrix branch of the MCX Ember+ tree. Confirm during commissioning that the installed MCX release publishes this branch.

• Lawo documents breaking changes to the MCX Ember+ provider in the mc² release notes: the signal label node renamed from userLabel to user in release 10.0.2 (build 1), and physical GPIOs removed from the provider in release 10.2.4. Physical GPIOs must be connected to virtual GPIOs in Lawo HOME.

• Lawo documents that, from MCX release 10.4.0 build 9, the console disconnects every external Ember+ connection when a production is loaded. Expect the Node to disconnect and reconnect when a production is loaded.

• Lawo documents further value changes in the MCX Ember+ provider: from release 10.0.2 (build 5), the output DSP gain range is scaled by a factor of 32, and from release 10.2, the panning range of all DSP channels and GPCs is ±100; from release 10.4, the provider removes trailing spaces from labels. Re-check pinned parameters and label-based workflows after an MCX upgrade.

• Lawo documents a correction to the MCX Ember+ provider in release 10.6: before it, a mixture of implicit and explicit subscriptions could cause missing updates on consumers that had no explicit subscription. Validate value updates in hi on earlier MCX releases.

• Lawo documents that startup labels in the MCX Ember+ tree are reduced from release 10.10.2, and that third-party control systems that rely on default labels can be affected.

• When the console reports a changed signal matrix, hi reinitializes the Node and reads the matrix and labels again.

• hi names each Port from its Lawo user label. A signal without a user label appears as Input or Output followed by its number.

• hi sends an Ember+ keep-alive request every 5 seconds, and it disconnects when the provider does not answer within 10 seconds. hi requires the provider to answer keep-alive requests.

What's Not Supported

• Firmware updates and DSP design - use the vendor's native software, such as its show-file editor or channel-configuration tool.

• Offline scene and show-file programming remain in the vendor tooling.

• Audio metering visualization beyond basic level readback where exposed by the protocol.

• Ember+ Functions, including Qualified Functions, and function invocation. The Ember+ specification defines them from Glow 2.20, and hi never sends an Invoke command.

• Ember+ Templates, including Qualified Templates, and template references. The specification defines them from Glow 2.40. hi requests all fields of each element, and it does not resolve template references.

Trademarks