Document version 1.0 (Jun 3, 2026)

Introduction

Audio Production mc² Release 12.2.2

12.2.2 is a minor release focused on usability, stability, and workflow improvements across the MCX platform. 

A key addition is the integration of Input Stage Parameter Control directly into MCX, enabling accurate, real-value control when working with DirectOut Prodigy devices. Additionally, the Signal List has been improved for better visibility and clearer connection handling. The Aux Mixer App has also been updated to improve stability and address scrolling and caching issues, contributing to a smoother overall user experience.

This release is accompanied by Nodesys 4.3.4, which includes a security patch addressing CVE-2026-31431 ("Copy Fail") for A__UHD Core.


This software release package applies to the following products:

  • mc²96
  • mc²56 MKIII
  • mc²36 MKII
  • mc²36 MKII xp
  • A__UHD Core

  • A__stage series

  • A__digital64

  • A__madi4/6
  • A__mic8
  • mc² Compact I/O
  • HOME mc² DSP

Contained Versions

  • MCX: 12.2.2.0-11
  • NodeSys: 4.3.3.1
  • A__UHD Core 4.3.4.2 (CVE-2026-31431 security patch)
  • HOME Gateserver Variant: 4.6.0-70

Minimum Requirements

  • HOME Server variant: 4.1.0
  • HOME Apps: 1.10.1


As of this release, the AP package no longer includes HOME software or HOME Apps. These components must now be downloaded separately from their respective sources.
The tested and recommended HOME version is the one included in the gateserver variant

Version History

Release 12.2.2.0 - Jun 3, 2026 (MCX: 12.2.2.0-11 NodeSys: 4.3.4 -1 HOME Gateserver Variant: 4.6.0-70)

Power Core Compatibility

  • Power Core Gateway - OnAirDesigner. 8.0.0.14 or higher required
  • Power Core RP v2 - OnAirDesigner 8.2.0.96 required

crystal Panel Controller

crystal Control Panel Firmware 8.2.185 or higher required


BREAKING CHANGE: 12.2.0.0 introduces a breaking change on the VDSP Protocol. MCX 12.2.0.0 is only compatible with A__UHD Core version 4.3.0 and HOME mc² DSP App 1.10.1!

Before you begin.
Please make sure that you have all necessary applications and tools available before you start the update.
We strongly recommend that the software versions used are from the same release packages.

If you are upgrading from prior versions, ensure that you review the release notes of all intermediate versions to identify any breaking changes or updates that may impact the upgrade process.

Update redundant A__UHD Cores safely

When upgrading A__UHD Cores that are part of a redundancy group, please follow the procedure below:

  • The primary A__UHD Core should be active.
  • Update the passive/backup A__UHD Core first.
  • After successful update - turn off the backup/passive A__UHD Core.

  • Update the primary A__UHD Core

  • When primary comes back online, power up the backup/passive A__UHD Core again.

Using NodeSys Upgrader will handle this automatically - beware to enable automatic failovers in NodeSys Upgrader, once the upgrade is finished.

Starting with NodeSys release 4.0.0, the SFP drivers enforce the autonegotiation flag more strictly and are less forgiving of mismatches. Previously working setups with unbalanced configurations-such as Auto-Neg ON on the device and OFF on the switch-may now fail to establish a link. This can lead to unexpected issues after an update if such mismatches exist.

Recommendation: Ensure both ends of the link are configured identically. If Auto-Neg is not supported on one side, explicitly configure both sides to 1G Full Duplex. Check configurations carefully before updating.

Updating A__UHD Cores and A__line Devices

After updating NodeSys based devices, always perform a full power cycle of the devices afterwards.

KICK

Release 12.0 requires KICK software version 2.2.0.1 or higher

LCU

There were improvements made on the LCU proxy (HOME version 2.1.3) - For a seamless integration please use comimx_lcu-10-4-0-52 firmware included on the AP 10.8.2.1 release package

Power Core Gateway

  • Due to the implementation of Power Core Rev3, a backup of the crosspoints needs to be created. After the update the Power Core loses existing cross points and uses default connections, similar to what happens during a coldstart
  • It is necessary to upload a converted config to the device, otherwise signals may be wrong or not available. 
  • Please note that source related Loudness gain parameters and settings available in On-Air designer and Web UI should not be used in production. They are experimental features only and will be licensable add-on.
  • The maximum samples per frame for an outgoing stream is reduced to 64. If a higher value was previously configured, it will be reduced to 64 automatically.
  • Due to the new logic engine of VisTool, projects needs to be recompiled and may report errors of non-connected logical states. These need to be set again.

HOME mc² DSP Known Issues 

  • Mix Latency should not be set to 333us for critical applications.
  • Senders should not be configured to other packet times than 6 samples (0.125ms) or 48 samples (1ms).

Please also see the Known Limitations section below.

Downdating A__UHD Cores

If an A__UHD Core needs to be downdated to a version < 4.3.0 it is required to manually delete the settings file /data/config/settings.json, otherwise a Virtual Mixer within this A__UHD Core will not be able to be connected to an MCX < 12.2.0.

Change Logs - Bug Fixes

MCX

12.2.2.0

  • [RNDMCX-3256] - Input Stage Parameter Control Integration with MCX
  • [RNDMCX-3437] - Signal List - connection line redraw
  • [RNDMCX-3709] - Implement automated core dump collection and cleanup for GUI/BAY processes
  • [RNDMCX-3312] - Column Connected Destinations not updated in mxGUI when switching between mcx instances
  • [RNDMCX-3508] - Fader misses the return notch on PFL Backstop release
  • [RNDMCX-3659] - Production files page file-size label cut off
  • [RNDMCX-3685] - Encoding issue in Tcl configuration script for VLoopback Label assignment
  • [RNDMCX-3686] - Label export and import to CSV by Tcl custom configuration helper does not work with special characters
  • [RNDMCX-3687] - Signal Labels (Long) can be fed with non UTF-8 compliant strings
  • [RNDMCX-3688] - Signal Labels (Short) can be fed with UTF-8 strings
  • [RNDMCX-3689] - GtkGUI: Encoding error in display of short label after using special characters and "Increment Next" function
  • [RNDMCX-3706] - Waves: snapshot load during session sync can delete data

Aux Mixer App

  • [RNDWORKSPACES-161] - Parameter adjustment is jumpy when working over VPN
  • [RNDWORKSPACES-214] - Top Bar Design Issues
  • [RNDWORKSPACES-215] - High Contrast Mode Issues
  • [RNDWORKSPACES-216] - Fader Strip Issues
  • [RNDWORKSPACES-258] - Caching issue with Safari and iOS 26, which leads to version mismatch
  • [RNDWORKSPACES-340] - Fader and box slider are moving after being released
  • [RNDMCX-3617] - Unable to scroll AUX Mixer webpage

   

4.3.4

  • [RNDNODESYS-2679] - A__UHD CORE Security patch for CVE-2026-31431 ("Copy Fail") vulnerability


Known Issues / Limitations


mc²/MCX Control System

  • USB file transfer not yet supported, if system uses external control system (XCS).
  • User-assignable monitoring buttons not yet assignable, but must be routed manually.
  • MCX Signallist: RTW Metering Outputs not listed in Misc > Matrix/Monitoring Outputs.
  • De-Esser and MB compressor is not operable in ISO BAY mode.
  • Couple does not work for double-tap reset of parameters.
  • mxGUI: VirtualBox host-only adapter IP address is not displayed properly in mxGUI.
  • mxGUI: When using mxGUI on macOS based systems with retina display, it is necessary to adjust the resolution macOS is using to run VirtualBox. Go to Applications, right-click VirtualBox and select Show Package Contents. Continue to Contents > Resources > VirtualBoxVM and press command + I. Now check the option Open in Low Resolution.
  • OASIS Label transfer only works from Pyramix to MCX, but not the other way around.
  • OASIS Metering is not supported.
  • HOME UI cannot be displayed natively inside the console UI.
  • Desk PSU Communication: False alarms triggered on two PSUs due to SMBus-I2C issues. Currently, functionality can be restored by performing a surface power cycle.


A__UHD Core

  • A__UHD Core redundancy does only work for HOME native devices and NMOS registered endpoints. (requires NMOS HOME license)
  • A__UHD Core redundancy is not supported with NATS Relay (NATS messages forward by the A__UHD Core on Gateserver systems) L3 network routing required!
  • RX statistics not yet supported in the WebUI.
  • Enabling/disabling senders and receivers not supported (use HOME instead).
  • Front display control / interaction not supported.
  • Factory defaults sets the device to DHCP.
  • Sync Input does not support Video Sync.
  • Ext Keys are limited to 8 even though A__UHD Core is able to provide up to 32.


HOME mc² DSP

  • AMBIT 5.1 Upmix is not yet supported.

  • 2 Fs / 96 kHz sampling rate is not yet supported.

  • No support yet for NDI, SRT, and Dante I/O.
  • No support yet for mDNS/SAP announcements for transmitters.


A__mic8, A__stage series, A__digital64, A__madi4/6, mc² Compact I/O

  • A__mic8: Front display control / interaction not yet supported.
  • A__mic8: Factory defaults / upgrade from RAVENNA Suite Butler sets the device to DHCP.


HOME

  • User labels for Signals are not yet supported.
  • There is no possibility to restrict HOME Snapshots. A HOME Snapshot is a global recall functionality, that can be compared to a Snapshot of a Virtual Machine.
  • It is not possible to update an existing HOME Snapshot - delete the old Snapshot and store a new one as a workaround.
  • Health issue notification always pops up on any mc² console / mxGUI, even if it does not affect assigned resources.
  • Health monitoring does not respect Dell servers and mc² console surfaces yet.
  • Existing Signal Ownership Groups cannot be renamed - delete the old group and store a new one as a workaround.
  • Available Ownership Groups always pop up on any mc² console / mxGUI, even if it does not affect assigned resources.
  • DHCP/DNS is not supported, when HOME Services are located on the Gateserver.
  • Radius Authentication is currently not working with Cisco Catalyst 9300A switches.
  • Tie-Line Streams between A__UHD Cores don't bring up corresponding Signals in the mc² Signallist - use External Tie-lines as a workaround.
  • Power Core Streams cannot be renamed.


mc²36 MKII

  • Point-to-point mode for mc²36 MKII with directly connected NodeSys I/O needs manual configuration, but does not setup connections automatically.
  • HOME does not handle mc²36 MKII as a single device, but as 4 single components (MCX, A__UHD Core, VMixer, Local I/O).


Breaking Changes History

BREAKING CHANGES: This release introduces a breaking change in the VDSP protocol. MCX 12.2.0.0 is only compatible with Nodesys 4.3.0 and HOME mc² DSP 1.10.1! 

BREAKING CHANGES: Version 12.0.0.2 patch introduced a breaking changes between HOME & MCX. Therefore 12.0.0.2 is only compatible with HOME 2.8

BREAKING CHANGES: Version 10.12.0.4 patch introduced a breaking changes between HOME & MCX. Therefore 10.12.0.4 is only compatible with HOME 2.8

BREAKING CHANGES: Version 10.12.0.x introduced breaking changes in Waves API integration -Waves will now use a different API, which is based on the OSC protocol. The previous API will no longer work with systems utilizing MultiRack Soundgrid.

BREAKING CHANGES  Ember-Tree Parameter Naming: Startup Labels have been reduced in version 10.10.2.0

This may affect 3rd party control systems that rely on default labels such as Mosart. Issues may be encountered and need to be updated to the new startup labels.

BREAKING CHANGES: Version 10.6.0.x introduced breaking changes in bus routing

MCX: Stereo channels cannot be individually deselected in bus routing, hindering assignment to a Stereo Bus on individual Legs, L/R

BREAKING CHANGES: Version 10.4.0.x introduced breaking changes compared to previous versions

MCX Ember Provider: Remove trailing whitespaces from scribs/labels upon getValue.

MCX Ember Provider (applies from Release 10.4.0.9). Any external Ember+ connection will be disconnected upon production load. External controller will have to reconnect again. Will prevent flooding external controllers with Ember+ data. 

BREAKING CHANGES: Version 10.2.4.x introduced breaking changes compared to previous versions

Ember Provider Channel metering is now using the Ember streaming format instead of int64.

Compressor and Expander Hold parameter has been removed from the Ember Provider, since it actually is not available in the system.

Physical GPIOs are no longer available in Command Trigger and Ember+ Provider of MCX, but may only be used using TCL. Physical GPIOs need to be connected to vGPIOs in Home, in order to use them in MCX.

The Aux Bus pickup point has been removed, previous Aux Bus pickups are automatically converted to Aux AF (after fader).

PRODUCTION / SNAPSHOT INCOMPATIBLITY: Release Version 10.2.0

Release 10.2.0 introduced incompatible hash-codes, resulting in newly created external device signals in the console, being incompatible with the ones being restored from productions and snapshots. Release version 10.2.2 is required, in order to properly load and restore production files coming from 10.0.2 and 10.0.0. This only affects native Home devices like A__line devices. External Tie-lines and Third-Party proxies are not affected by this. Productions created with 10.2.0 are not compatible with versions > 10.2.0 and need manual porting! If this is required please reach out to AP PL!

BREAKING CHANGES: Version 10.2.0.x introduced breaking changes compared to previous versions

Over Snap Incompatibility: 

Over Snaps that have been created with 10.0.0 or 10.0.2 release versions are not compatible with 10.2.0 and will be discarded!

Over Snaps that have been created with 6.4.0 release versions are compatible and will be loaded.

Behaviour of receivers of A__UHD Core and A__line (NodeSys): 

If one routes a source stream with fewer channels (S) than the receiver (R), then only the first S audio channels of the receiver will have signal.

If one routes a source stream with more channels (S) than the receiver (R), then only the R audio channels as specified by the receiver will be present.

Ember+ Provider: 

The panning granularity of all DSP channels and GPCs has been changed to +-100. Depending on the implementation of an Ember+ consumer, this may break compatibility!

Output DSP gain parameter range has been changed from -128 ... 15 to -4096 ... 480 with factor 32 in order to be consistent with other gain parameters in the Ember+ tree.

BREAKING CHANGE: Version 10.0.2.6 introduced one breaking change about NATS Relay configuration!

If the system relies on NATS Relay on the A__UHD Core (the A__UHD Core forwards NATS messages from media networks to a Gateserver in the management network, this is e.g. mandatory for mc²36 MKII) you have to adapt your system by invoking the following command on the Gateserver:

rm -r /data/config/home
rm -r /data/config/nats/cluster.conf
touch /data/config/nats/leafnode.conf

BREAKING CHANGE: Version 10.0.2.5 introduced one breaking change in the Ember+ provider!

Output DSP gain parameter range has been changed from -128...15 to -4096...480 with factor 32 in order to be consistent with other gain parameters in the Ember+ tree.

BREAKING CHANGES: Version 10.0.2.1 introduced breaking changes with respect to TCL configuration and Ember+ provider!

TCL Configuration File Locations: 

Please be aware that from now on MCX expects its TCL configuration files in a different location. The location has been changed from /data/config to /data/config/mcx.

This change affects both physical systems, as well as mxGUIs with an externally mounted mxgui_config_share and in the case of the latter it affects the configuration for each product type individually.

For physical systems and mxGUIs the new versions include a helper script migrateEarlyPhase2Config (that can simply be invoked from CLI) to convert a set of configuration files to the new structure. In case of a physical system the script has to be executed once and then has to be followed by a reboot of the system.

For mxGUIs multiple conversions can be performed subsequently by passing an explitcit base path as the one and only argument to the conversion script.

Please note, that further custom configuration files (such as Mackie HUI or special custom configs) might need to be adapted manually!

Ember+ Provider: 

In the signal's 'labels' node, the identifier changes from 'userLabel' to 'user'. /signals/{sources,targets}/<signalId>/labels/userLabel becomes .../user. Furthermore, there have been added more parameters in this node (namely 'userShort', 'startupShort', 'inheritShort'), making use of a new schema 'com.lawo.emberplus.labels.v1.0' instead of 'com.lawo.emberplus.signal.labels.v1.0'.

The AfV event identifiers have been changed from 'event1' to 'event-1' etc. /mixer/global/afv/eventX becomes .../event-X

Information about open source packages and versions used in this release

This information is provided within the WebUIs of each device.

MCX

Open the MCX Landing Page and navigate to the bottom section of the page.

NodeSys Devices

Open the WebUI and navigate to General Settings under the About section.

HOME

Open the About window on the WebUI by clicking the LAWO Logo in the left upper corner and navigate to Open Source Attributions.

Power Core

Open the WebUI and navigate to the Licenses tab.