mc² Release Notes - 10.2.0

Document Version 16.2 – 2022-01-26

Introduction

Version 10.2.0 is a major release version for mc² consoles based on the A__UHD Core Phase 2 technology. Version 10.2.0 adds in various new functionalities to the system.

This software release applies to the following products:

mc²96
mc²56 MKIII
mc²36 MKII
A__UHD Core
A__stage series
A__digital64
A__madi4/6 (running NodeSys 2.2.0)
A__mic8 (running NodeSys 2.2.0)
mc² Compact I/O (running NodeSys 2.2.0)
Power Core Gateway

New Features

New Main Display Design
New De-Esser Module
Extended Panning Granularity
Signallist 'Classic' Legview
New Custom Function Page
MCX Control System Redundancy
MCX Headless Consoles
MCX Mirrored Consoles
NodeSys Warmstart
Automatic A__UHD Core Redundancy Failover
Global HOME Snapshots

Known Issues

When unplugging a Home server this may cause an unexpected A__UHD Core failover, loss of control and audio (only applies to cluster configurations).
Unplugging management cables from a Home server also caused unexpected A__UHD Core failover (only applies to cluster configurations).
Streams have to be repatched after upgrade from v10.0.2.
NodeSys devices may come up without stream configuration after upgrade from v10.0.2.
NodeSys devices may come up with different Device ID after upgrade from v10.0.2
De-Esser not working.
Receive Midi Sysex data not working via callbacks.
Existing User vGPIOs are lost after snapshot load.
MTC not working via rtpMidi.
Source Settings greyed out on channel display when switching sources (A/B/C).
Single EQ control LEDs on the console surface may not be lit, but EQ band is operational.
MCX Signallist: Auto-increment in Label pop-up does not increment a number, if it is part of the string but not at the end.
MCX Signallist: Auto-increment in Label pop-up adds a number, if there is no number at the end of the string.
MCX Signallist: RTW Metering Outputs not listed in Misc > Matrix/Monitoring Outputs.
MCX Signallist: AES3 Signal L and R legs cannot be labeled independently.
USB file transfer not yet supported, if system uses external (redundant) control system (XCS).
Monitoring: User-assignable buttons not yet assignable.
mxGUI: 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.
A__UHD Core: Dynamics Metering not working for Surround Masters.
A__UHD Core: 2-Channel Mode currently not supported.
A__UHD Core: Channel Config page indicates four Aux-Pickup points, but the system only utilizes PEQ, PF and AF.
A__UHD Core: System uses Bus Aux-Pickup point rather than AF.
HOME: Tie-Line Streams between A__UHD Cores don't bring up corresponding Signals in the mc² Signallist.
HOME: External Tie-Lines may not have the same label for RX and TX.

Known Limitations

mc²/MCX Control System:

User Lists in the Signallist not yet supported.
De-Esser ist not yet operable in ISO BAY mode.
Dynamic TC Automation not yet supported.
Power Core^RP and LCU Integration not yet supported.
LiveView^TM Thumbnails not yet supported.
Label Transfer for Waves Plug-In Integration not yet supported.
HOME UI cannot yet be displayed natively inside the console UI.

A__UHD Core:

A__UHD Core redundancy does only work for HOME native devices.
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.
256 processing channel systems only support surround formats up to 5.1.
Reference Level / Headroom settings cannot yet be adjusted, being fixed to 24 / 0 dB.
44.1, 88.2 / 96 kHz is not supported with A__UHD Core systems.
RX statistics not yet supported in the WebUI.
Front display control / interaction not yet supported.
Factory defaults sets the device to DHCP.
Reference Sync when acting as PTP GM has to be configured using Ember+.
Sync Input does not yet support Video Sync.

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

44.1, 88.2 / 96 kHz not yet supported.
Input / Output metering not yet supported.
RX statistics not yet supported in the WebUI.
Enabling/disabling/editing senders and receivers not yet supported.
A__mic8: Front display control / interaction not yet supported.
A__mic8: Factory defaults / upgrade from RAVENNA Suite Butler sets the device to DHCP.
A__madi: Second and third bridges do not report health data.
A__stage / A__digital64: FAN LED does not yet display the correct status.

HOME:

User labels for Signals are not yet supported.
DHCP/DNS is not supported, when HOME Services are located on the Gateserver.
Radius Authentication is currently not working with Cisco Catalyst 9300A switches.

mc²36 MKII:

Point-to-point mode for mc²36 MKII with directly connected NodeSys I/O systems is not yet supported officially.
HOME does not handle mc²36 MKII as a single item, instead of 4 single components (MCX, A__UHD Core, VMS, Local I/O).

For a more detailed list of possible limitations, please refer to the Comparison Reference List - Nova73 vs. A__UHD Core.

Breaking Changes History

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/homerm -r /data/config/nats/cluster.conftouch /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