Document version 3.0 (Nov 25, 2025)

Introduction

Audio Production mc² Release 12.2.0

This release introduces a range of performance and usability improvements across the mc² platform. At the core of the update is the powerful new Dynamic EQ module, built on FPGA and CPU-based processing. It expands tonal control with three dynamic bands, enabling precise frequency shaping in demanding production environments. Complementing this, the redesigned Main Display with EQ Touch functionality offers a more intuitive layout and faster touchscreen operation - all part of a series of meaningful updates across the entire workflow.

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.0.2 # 39
  • NodeSys: 4.3.1 #2
  • HOME Gateserver Variant: 4.4.0 #54

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 recommended HOME version is listed above; alternative versions may be used if compatible.

Version History

Release 12.2.0.2 - Nov 25, 2025 (MCX: 12.2.0.2 # 39 NodeSys: 4.3.1 #2 HOME Gateserver Variant: 4.4.0 #54)
Release 12.2.0.1 - Oct 20, 2025 (MCX: 12.2.0.1 # 28 NodeSys: 4.3.1 #2 HOME Gateserver Variant: 4.3.0 #122)
Release 12.2.0.0 - Sept 2, 2025 (MCX: 12.2.0.0 # 19 NodeSys: 4.3.0 #9 HOME Gateserver Variant: 4.1.0 #9)

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.

What's new?

Main Display Redesign

The Main Display has been redesigned to improve usability, clarity, and consistency. All mini displays are now aligned in a single row at the bottom, following the default channel strip order. 
The central area now features an expanded Zoom module, offering more space for new controls and larger, touch-friendly graphs. The new layout ensures a consistent and intuitive workflow across all blocks, making navigation faster and the interface easier to understand.

Touchscreen or mouse interaction allows now direct control of gain, frequency, and Q on he Equalizer module with multi-touch pinch support for bandwidth adjustment.

Dynamic EQ

Introduces a new 7-band equalizer module, expanding the FPGA and CPU platforms DSP capacity from the standard four bands with three additional dynamic bands. This allows more advanced and adaptive frequency shaping within the same processing structure.

Each dynamic band supports Bell, ConstQ, and Dynamic Shelving filter types, with advanced morphing options like Dyn-DynQ and ConstQ-to-Bell modes. Dynamic bands operate in Over/Under mode and support both self-keying and external key sources.

Reveal in Place - Bank Function

Reveal in Place has been extended to support bank navigation, allowing access to more than 15 contributing channels. When RIP mode is activated, the system now takes over the Bank buttons, automatically starting at Bank 1 to reveal channels 1-15. Operators can switch to subsequent banks to access contributors up to channel 90 and beyond. The source channel triggering RIP remains fixed in position, while the revealed contributors change dynamically with each bank.

Channel Display Enhancements

Two additional mini display rows have been added above each fader on the channel strip. These rows can display parameters such as dynamics status, filter activity, EQ gain reduction, or user-defined text. Display content is context-sensitive and can updates dynamically based on selected DSP module.

This feature is complemented with the new Channel Display Preset and Multirow Mini Display custom functions, allowing users to tailor the channel strip and overall workspace to specific operational needs.

MCX Endpoint Terminal Routing via HOME

The internal routing matrix of the MCX is now exposed to the HOME system via the HOME-NATS interface. All routes are presented as mono-level terminal connections, aligning with HOME’s endpoint structure. This allows integration with external control systems such as VSM. Both control and monitoring paths are accessible via the HOME API.

Updated Custom Functions


Mute Control Macro
Adds support for up to four mute groups, accessible through the central user button or assignable fader user buttons. This provides fast control over muting grouped channel strips.

Bay Fader User Buttons, Mode Toggle
Enhances the functionality of user buttons on each fader strip. These buttons can now be configured to switch local banks and layers independently per bay, improving surface ergonomics and allowing fast navigation across channel layouts.

OSC Template - Reaper Control
Enables seamless integration with Reaper using a pre-configured OSC template. Allows bi-directional control of up to 256 channels between mc² consoles and Reaper, supporting essential strip parameters and transport functions. This gives operators a streamlined hybrid workflow between the physical surface and DAW automation.

Channel Display Preset

Enables saving and recalling of full channel strip layout states, providing quick access to personalized or workflow-specific views. Users can toggle between two display setups or recall a defined preset using a central user button.


Multirow Mini Display
Adds the ability to toggle the visibility of additional mini display rows in the channel strip. This gives users control over how much contextual information is shown, depending on operational needs or available screen space.

A/B Switching Unlock Extension
Adds an optional unlock mechanism for A/B source switching, intended to reduce the risk of accidental changes in environments where source switching without confirmation may lead to signal disruption.

Change Logs - Bug Fixes

MCX

12.2.0.2

  • [RNDMCX-3472] - Load Snapshot Pop Up window is too small

  • [RNDMCX-3080] - A__UHD connection mute is triggered when sources get unavailable on control layer
  • [RNDMCX-3089] - mxGUI File Transfer is broken, it creates a file of 0Bytes
  • [RNDMCX-3107] - Waves ProLink - Disable Console Rack Navigation Link does not work
  • [RNDMCX-3108] - Waves ProLink - Navigate HotRack not working

  • [RNDMCX-3360] - Monitoring loss after DSP conf. change with signal reconnect or UHD Core failover

  • [RNDMCX-3421] - Saving isosets is not possible with UTM mxGUI and shared folders

  • [RNDMCX-3442] - Signal-routing inconsistencies caused by stale entries in the UHD Core I/O address cache.


12.2.0.1

  • [RNDMCX-2884] - UTM mxGUI takes sometimes longer to start mxStarter
  • [RNDMCX-3047] - Slider value rounding values issues
  • [RNDMCX-3315] - HOME does not show the exact software version for XCS Devices
  • [RNDMCX-3334] - Copy/Reset of EQ copies/resets other modules / Automation: Finished pass writes random parameter values
  • [RNDMCX-3375] - Nova router Mic input params (48V, Line, HiPass) not being loaded correctly from MCX production files
  • [RNDMCX-3404] - Bayservers sometimes not booting correctly after System Powercycle
  • [RNDMCX-3406] - mcx_connect to protected destination drops an "event failed" and breaks tcl script


12.2.0.0

  • [RNDMCX-741] - Channel Display: Add two more mini display rows
  • [RNDMCX-1829] - Bank and Layer Switching via Fader User Buttons
  • [RNDMCX-2365] - Blocks of 8 Channels Display on Signal List
  • [RNDMCX-2462] - Strip Assign Page Part 2
  • [RNDMCX-2493] - Expose internal routing matrix of MCX to Home
  • [RNDMCX-2870] - Add default MUTE Control Macro Custom Function
  • [RNDMCX-3032] - Redesign Highlight for "Show Fadersense"
  • [RNDMCX-988] - Gain Control may be lost after system power-up
  • [RNDMCX-1429] - Copy Complete Channel does not copy Mic/Line mode
  • [RNDMCX-2774] - Prodigy-based signals cannot be copied from user list to system list
  • [RNDMCX-2821] - Power Core RP Custom Function typo
  • [RNDMCX-2864] - 32 Fader 36mkII: aux fc button not updating channel display strips
  • [RNDMCX-3078] - Setting Timecode Display to "Timecode" crashes GUI (traps libgtkmm)
  • [RNDMCX-3162] - 32 Fader 36mkII: aux fc button not deselected when selecting other fc preset
  • [RNDMCX-3197] - GUI crashes at production load
  • [RNDMCX-3281] - MCX GUI does not reliably show new errors if complete devices are shut down
  • [RNDMCX-3299] - GUI crash on bad console configuration (odd number of strip panels)
  • [RNDMCX-3309] - Aliases cannot be copied from user list to system list
  • [RNDMCX-3327] - passwd default algorithm from DES to SHA512
  • [RNDMCX-2746] - Actively disconnect offline IO signal targets

NodeSys

4.3.1 #2

  • [RNDHOME-2026] Shared Rx does not transfer to the follower group member on one slice.

4.3.0 #9

  • [RNDNODESYS-471] - Web UI: Initial changes to the network settings via UI are not applied
  • [RNDNODESYS-1395] - Long hostnames not fully visible on UHDCore display
  • [RNDNODESYS-1441] - No UpMix initialisation on non-surround format channels
  • [RNDNODESYS-1797] - sap_connector crash: invalid UTF-8 byte
  • [RNDNODESYS-1798] - Support Snapshot download problems
  • [RNDNODESYS-1827] - Security: disable start up script
  • [RNDNODESYS-2045] - New DSP function UHD Core Part11
  • [RNDNODESYS-2161] - Upstream closing connection to client on system time change


Known Issues / Limitations


mc²/MCX Control System

  • USB file transfer not yet supported, if system uses external (redundant) 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 is not yet 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 Failures: False alarms triggered on two PSUs due to SMBus-I2C issues. Currently, functionality can be restored by performing a surface power cycle.
  • RNDMCX-3487 - Shared folders in UTM mxgui are non-functional



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.
  • RNDNODESYS-2436 PWM Frequency for Fans in UHD Core is to low for new fans


HOME mc² DSP

  • Supports a maximum of 8192 input signals.

  • Supports a maximum of 8192 output signals.

  • Supports a maximum of 2048 DSP channels in total (Inputs + Busses).

  • Supports a maximum of 256 Senders and 256 Receivers.
  • 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.