Document Version 3.0 – 2023-08-16



Introduction

Version 10.6.0 is a major release version for mc² consoles based on the A__UHD Core Phase 2 technology. Version 10.6.0 adds in various new functionalities to the system, such as Immersive Mixing, Pooling for up to 8 Virtual Mixers, and NMOS IS-04/IS-05 support in HOME. 

This software release 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
  • Power Core Gateway


Upgrading HOME Cluster to Release 10.6.0

With 10.6.0 a temporary internet connection is not required anymore, when upgrading a HOME cluster. Online as well as offline installers are available now.

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.

Updating A__UHD Cores and A__Line Devices

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

Breaking Changes 10.6.0

A new vdsp protocol version has been introduced. Therefore 10.6.0 is only compatible with NodeSys version 2.8.0.

New Features

Immersive Mixing Package

Support for 5.1.2, 5.1.4, 7.1.2, 7.1.4, 9.1.4, 9.1.6 and 4.0.4 multichannel formats including multichannel Downmix, Metering, Panning, DSP Processing and Loudness. Additionally, a new 3D Panning Visualisation as well as a new CRM Sidepanel layout accompanying the new formats have been introduced. 

Pooling 8

A new Pooling 8 license allows to split an A__UHD Core into up to 8 Virtual Mixers. Therefore, Virtual Mixers can now share streaming interfaces which has to be defined in the vdsp config accordingly. 

Signal Ownership Enhancements

It is now possible to temporarily take ownership of source signals like microphone preamps which are currently owned by another mc² console. The timeout length can be defined via TCL.
Access to Ownership Groups on the mc² console can be completely disabled.

Adjustable Reference Level / Headroom / Mic Level

The full featured Analog Reference Level settings, including Overload Threshold have been reintroduced. The displayed gain in dB is now respecting the Analog Reference Level.

LabelView

A new view for the miniTFTs on the surface is available which replaces the fader level indication with a second label. For example the User or Inherit Label. Upon fader sense, the fader level is temporarily displayed as usual. This option can be enabled in the System Settings and is saved and loaded from productions. 

De-Esser Threshold

A threshold parameter for the De-Esser DSP Module is now available in the UI.

Improved Metering

The Metering characteristics as well as scales have been improved conforming to IEC-60268-10 Type I, IIa and IIb. The metering scales also do better adapt to resizing and limited space on the Channel Display. 

AFL/PFL prioritised in resource allocation

The AFL/PFL channel resources are prioritised over normal buses in the DSP configuration, making sure listen buses are always available. 

Console miniTFT EQ and DYN graph overhaul

The EQ and DYN graphs in the miniTFTs on the surface now use the LUX theme.

DirectOut and Insert Level Metering Ember+ Parameters 

The DirectOut and Insert Level Metering parameters are available in the MCX Ember+ tree. 

Default stream format changed to dual redundant

Sender & Receiver are now created with Streaming Indices 0 & 1 = dual redundant. This change was made to better accommodate installations with external controllers like VSM utilising SDP patching. Stream Routing in HOME will resize the format of an Receiver according to the Sender format as usual.

NTP and DNS settings on NodeSys WebUI

NTP and DNS configurations can now be made on the WebUI. In already configured systems, initially all Interfaces are queried for NTP as well as DNS entries and the first found ones are displayed in the WebUI. There are no changes made to an existing configuration! Once a manual entry is made via the WebUI the value will be written to ALL interfaces. In case individual NTP servers need to be set per Interface, this can be still done via Ember+.

Static Routes on NodeSys WebUI

Static routes can be set via the NodeSys WebUI on a per interface basis. 

HOME NMOS IS-04/IS-05 support

There are three separate NMOS capabilities that are now included in Home:

  1. An Easy NMOS Registry (disabled by default) - Released for Cluster deployments, currently not planned for Gate Server installation.
  2. NMOS Importer (enabled by default) - Released for Cluster deployments, planned for Gate Server installation in an upcoming HOME release.
  3. NMOS Exporter (enabled by default but requires configuration) - Released for Cluster deployments, currently not planned for Gate Server installation.

For more information, please refer to the HOME documentation: Home with NMOS v1.8

Contained Versions

  • MCX: 10.6.0.0-b33
  • HOME: 1.8.2.2-84
  • NodeSys: 2.8.0.0-b18

Changes

10.6.0.0

MCX

  • Fixed: RNDBUGSMC2CTRL-4 - RIP moves faders in unexpected ways.
  • Fixed: RNDBUGSMC2CTRL-31 - Hold SEL and activate stereo reveals RIP layer.
  • Fixed: RNDBUGSMC2CTRL-34 - Module dropdown menu on Main Display Page empty.
  • Fixed: RNDBUGSMC2CTRL-41 - Access strip is clobbered if a channel is assigned to the surface more than once after the fader of the selected strip is sensed.
  • Fixed: RNDBUGSMC2CTRL-56 - external signals loose their ownership icon.
  • Fixed: RNDBUGZ-22088 - De-Esser FC no Colour Coding or On/Off functionality.
  • Fixed: RNDBUGZ-22430 - Sensed faders do not reveal when sensing is stopped after a reveal.
  • Fixed: RNDBUGZ-22494 - Reveal (activate followed by deactivat) overwrites strip isolate SEL FADER and MAIN FADER.
  • Fixed: RNDBUGZ-22670 - missing a-matrix connects after production load.
  • Fixed: RNDBUGZ-22710 - No pre-amp control with stereo channel with only one leg connected.
  • Fixed: Bug 22334 - Wrong HW gain of MIC/Line resource after switching off/on IO device.
  • Fixed: Bug 22636 - File Transfer Page does not show productions and presets.

NodeSys

  • Fixed: RNDBUGZ-22800 - UHD Core stops receiving RTP packets on multiple Interfaces at the same time.

  • Fixed: RNDBUGSNODESYS-8: Sender name is changed from "sender" to "s_<streamName" cause problems with external controllers.

  • Fixed:  INC-31937 - A-Matrix level.
  • Fixed: RNDBUGSNODESYS-10 - no Audio after Stream Connect via VSM, message is MQTT topic "receivers/strm0:40204624/mapping" is already subscribed!

HOME

  • Fixed: TP36569 - Completed add support for PowerCore AIOX, and support all four front panel MADI port.
  • Fixed: RNDHOME-53 - Completed Get Grid Table ready to deploy.
  • Fixed: RNDHOME-65 - Completed Convert GCF Ctl value to use the new values.Value type.
  • Fixed: RNDHOME-70 - Completed As a customer I want to reduce the sound created by the Home cluster for small environments.
  • Fixed: RNDHOME-97 - Completed As a developer I want to provide a template QSC Proxy.
  • Fixed: RNDHOME-118 - Completed  As a developer I want to to improve clarity of protobuffs, allow for auto-subscribing receivers and allow for new GPIO mechanism in the data model.
  • Fixed: RNDHOME-119 - Completed As a developer I want to update all back-end HOME services, bifrost, HOME UI, and HomeAgent to build with latest data model.
  • Fixed: RNDHOME-129 - In QA As a customer I want to control the devices which are exported into Home from an external registry.
  • Fixed: RNDHOME-142 - BugFix Enabling experimental features breaks the NMOS UI Page.
  • Fixed: RNDHOME-143 - Completed QSC Polling/subscription mechanism.
  • Fixed: RNDHOME-144 - Completed QSC Components being used on device at MSG.
  • Fixed: RNDHOME-151 - BugFix Gateserver Home UI fails to load due to incorrect bifrost flags preventing bifrost from starting.
  • Fixed: RNDHOME-155 - Completed Build a framework to use QSC Request/Replies and autopoll for the QSC Proxy.
  • Fixed: RNDHOME-175 - Completed Add QSC as a Device Type to be selected from in UI for Proxy Page.
  • Fixed: RNDHOME-182 - EDIT button need to remove from NMOS page.

10.6.0.1

MCX

  • Fixed RNDBUGSMC2CTRL-49 - Missing icons on File Transfer Page.
  • Fixed RNDBUGSMC2CTRL-58 - File Transfer Page: Preset folder displays subfolders unintentionally.
  • Fixed RNDBUGSMC2CTRL-61 - Handling of productions broken.
  • Fixed RNDBUGSMC2CTRL-62 - Difference in brightness between GUI-0 and BAY-X.

NodeSys

  • Fixed RNDBUGSNODESYS-16 - NEVION iPath slow to create new routes on UHD cores on 2.8.0.12.
  • Fixed RNDBUGSNODESYS-19 - disturbed Audio on AES Channels after reboot with SRC ON on Lattice Boards.

HOME

  • Fixed RNDHOME-245 - Preserve UHD mixer slice device IDs when upgrading to AP 10.6 release with Pooling 8 option.

10.6.0.3

MCX

  • RNDBUGSMC2CTRL-13 - Downmix: no audio on last internal downmix bus channels.
  • RNDBUGSMC2CTRL-42 - Signal routing not effective with unavailable source.
  • RNDBUGSMC2CTRL-48 - Confirmation buttons move out of screen when User Lists have more than 53 items.
  • RNDBUGSMC2CTRL-53 - Main Display Page: Ambit plugin buttons are not greyed-out on not supported surr format masters channels.
  • RNDBUGSMC2CTRL-69 - Tone generator not working anymore after production load and connect to external signal.
  • RNDBUGSMC2CTRL-71 - Link for /var/log on mxGUI points to non-existent destination.
  • RNDBUGSMC2CTRL-74 - No connect lines drawn in signal mode on signal list.
  • RNDBUGSMC2CTRL-77 - Switch between leg and signal mode leads to connection counter loss.
  • RNDBUGSMC2CTRL-79 - in VCA coupled Channels you cannot decrease the IMAGE width smaller than its VCA Master.

NodeSys

  • RNDBUGSNODESYS-4 - PSU Voltage Status not refreshed via EMBER properly after powerloss.
  • RNDBUGSNODESYS-19 - disturbed Audio on AES Channels after reboot with SRC ON on Lattice Boards.
  • RNDBUGSNODESYS-31 - No Source IP in SDP in Ember tree.

HOME

  • RNDHOME-190 - Prelude fails to run if the mgmt network is lost in a layer2 setup.
  • RNDHOME-197 - NMOS Export Debug CLI is not accessible via URL in nginx config.
  • RNDHOME-259 - LCU Proxy: Control ID mismatch with InternalTerminal IDs.
  • RNDHOME-272 - HomeInstallerError - Javascript Error "Uncaught ReferenceError: experimentalFeatureFlags is not defined".
  • RNDHOME-274 - GraphQL error when creating new device proxy.
  • RNDHOME-279 - Proxies are shown offline on devices page.
  • RNDHOME-280 - The Home easy-NMOS Registry does not automatically turn on after a server reboot.
  • RNDHOME-281 - The online installer for ansible is not executable by default.
  • RNDHOME-283 - Installation fails if the home_user does not exist.
  • RNDHOME-305 - In PowerCore proxy, ensure that MADI Port is only reported when both configured and the right card type fitted.
  • RNDHOME-6 - Signal Ownership group list can become out of sync between HOME backend <> HOME UI.
  • RNDBUGSHOME-9 - Samplerate of Nova73 not shown correctly in HOME.


10.6.0.4

MCX

  • RNDBUGSMC2CTRL-36 - GUI crashes during runtime due to Out Of Memory (OOM) error.
  • RNDBUGSMC2CTRL-78 - AMBIT metering sticks full on all legs of a surround when disengaging AMBIT.
  • RNDBUGSMC2CTRL-101 - lighttpd stops working after time change.
  • RNDBUGSMC2CTRL-104 - Production snapshot file-sync issue.
  • RNDBUGSMC2CTRL-114 - AES signal parameters changes not working.

NodeSys

  • RNDBUGSNODESYS-35 - DRAM bus bandwidth limits RX stream combination, crackling & distortion (improvement, no fix.

HOME

  • RNDHOME-228 - Update QSC Proxy on receiver side for SDP patching.
  • RNDHOME-230 - User Name and Password entry fields when adding Proxy in UI.
  • RNDHOME-303 - Standardise usage of VidParams::ExactFrameRate field.
  • RNDHOME-312 - Promote QSC to an Official Home Feature.
  • RNDHOME-317 - HOME routing respects the protection level for sender and receiver when making routes on the QSC.
  • RNDHOME-326 - Support devices that operate in IGMPv2 only.
  • RNDHOME-246 - Audio Sender - can't edit when primary or secondary only.
  • RNDHOME-247 - Ensure HomeAgent sets correct Protection when setting destination Sords.
  • RNDHOME-329 - GPIO Stream Routing is incorrect.
  • RNDHOME-351 - Nova Router Effective Gain needs to take account of System Reference Level.
  • RNDHOME-352 - Nova Router fails to read sample rate depending on model type.
  • RNDHOME-427 - Powercore MADI SRC card signals not shown in HOME.
  • RNDHOME-351 - Nova Router Effective Gain needs to take account of System Reference Level.
  • RNDHOME-464 - QSC Proxy Floods Network.

10.6.0.5

MCX

  • RNDBUGSMC2CTRL-148 - Ember+ Provider: Using a mixture of implicit and explicit subscriptions for parameters leads to missing updates on consumers that have no explicit subscription
  • RNDBUGSMC2CTRL-149 - Loading a snapshot with cross connects when having multiple stream destinations on the same UHD Core TX leads to MUTE state
  • RNDBUGSMC2CTRL-21 gtkgui restart with error BadIDChoice.

10.6.0.6

MCX

  • RNDBUGSMC2CTRL-146 - Pyramix MRC not working with 10.6
  • RNDBUGSMC2CTRL-153 - Adding a XCS in VSM leads to a timeout/failover of the XCS while doing a snapload.
  • RNDBUGSMC2CTRL-155 - Suppression-Band Listen not working

Known Issues

Browser may require a refresh, in order to clear alarms on the HOME Health page.

Manually enabled mDNS and SAP announcements are getting lost, when loading a HOME Snapshot.

Device Options and Wordclock Profile are currently not stored and loaded from HOME Snapshots.

MCX redundancy failover may render Automation data corrupt.

MCX redundancy failover may require reloading Automation, when writing an automation pass.

A__UHD Core: Bug 21627 - Dynamics Metering not working for Surround Masters.

A__UHD Core: Bug 22205 - De-Esser Suppression Band Listen not working.

A__UHD Core failover may not work properly, when media interface IPs are assigned using DHCP.

RNDHOME-7 PowerCore looses audio after UHDCore failover. (Config adaption necessary and stated in the ticket).

RNDMC2CTRL-19 - Failover of UHDCore and MCX leads to non-working surround signals in Automix. (Workaround is stated in the ticket).

RNDBUGZ-20809 PSU monitoring communication error on Gateserver systems.

RNDBUGSNODESYS-26 - Internal bottleneck in Decoders with L24+L16 in high load.

RNDBUGSNODESYS-35 - DRAM bus bandwidth limits RX stream combination, crackling & distortion.

Power Core Gateway: 710/60 MADI SRC I/O Cards are not correctly registered in HOME.

Nova Proxy: Sample Rates other than 48khz are not respected in HOME with Device Types other than Nova73 HD Core. 

Known Limitations

mc²/MCX Control System

When switching a Signal from Mono to Stereo or vice versa, the label is being reset.

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 ist not yet operable in ISO BAY mode.

Couple does not work for double-tap reset of parameters.

Power CoreRP not yet supported.

Label Transfer for Waves Plug-In Integration not yet supported.

Rack-follows-Console-Channel-Select not yet supported with MultiRack/SuperRack.

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 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.

RX statistics not yet supported in the WebUI.

Enabling/disabling senders and receivers not yet supported.

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.

Ext Keys are limited to 8 even though A__UHD Core could provide up to 32.


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

Input / Output metering not yet supported.

RX statistics not yet supported in the WebUI.

Enabling/disabling senders and receivers not yet supported in the WebUI.

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.


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.

Power Core GPIOs are not yet supported.

Power Core MADI Port 3/4 are not yet supported.


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).


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.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. 


© Lawo AG, 2023, Am Oberwald 8, D-76437 Rastatt, Germany, +49 7222 1002-0