Author: d.pattni@hdanywhere.com

  • uOS Core & Studio: what this means for MHUB, MZMA and Zone Processors

    As part of the ongoing evolution of the HDA platform, MHUB and MZMA devices are transitioning to uOS Core.

    At a Glance

    • The full uOS platform is now called uOS Studio and runs on the uControl Zone or Connect Processor.
    • From June 2026, MHUB and MZMA devices now ship with uOS Core
    • MHUBs currently running uOS 11.08 will receive one final update to uOS 11.09
    • uOS on MHUB/MZMA is now discontinued.
    • MHUBs purchased before June 2026 retain their existing uOS features.
    • From 11 March 2026, existing MHUB or MZMA systems will only receive small stability and security updates.
    • If your system is working well today, there is nothing you need to do.

    This update simplifies the role of MHUB devices, allowing them to focus entirely on what they do best: reliable switching, distribution, and secure cloud connectivity. At the same time, the full automation and integration capabilities of the platform are moving to uOS Studio, running on the uControl Zone/Connect Processor.

    This architecture reflects how most professional installations are already designed — with a dedicated controller managing the system and distribution hardware handling switching.

    The result is a more stable, scalable, and future-proof platform for both integrators and end users.

    What this means for existing systems

    If your MHUB or MZMA system is currently working well, there is nothing you need to do. Your system will continue to operate normally.

    However, the way new features and system expansion will be delivered is changing.

    Topic What’s Changing What It Means For You
    Buying new MHUB and MZMA will ship with uOS Core and will not support uControl natively. If you wish to use uControl with your MHUB or MZMA you will need to purchase a uControl Zone or Connect Processor.
    Operating System on MHUB / MZMA MHUB and MZMA devices now run uOS Core, a streamlined version of uOS focused on switching and connectivity. This improves reliability and simplifies setup, particularly when using third-party control systems.
    Full uOS Feature Set The full uOS platform is now called uOS Studio and runs on the uControl Processor. Advanced automation features such as sequences, scenes and integrations are now handled by a dedicated controller.
    Support for uOS on MHUB uOS running directly on MHUB and MZMA devices is now discontinued as of 11 August. Existing systems will continue to operate, but new platform development will focus on uOS Studio.
    Future Software Updates From 11 March 2026, uOS on MHUB/MZMA will only receive small stability and security patches. No new features will be added to MHUB-based uOS systems.
    Expanding or Upgrading Your System To continue adding new uOS features, systems must include a device that runs uOS Studio. This typically means adding a uControl Processor to your system.
    System Architecture Systems using uOS Studio operate as a stacked system. The uControl Processor becomes the system controller, while MHUB handles video distribution.

    Do I need to upgrade?

    If you are happy with your current system and it is performing well, there is nothing you need to do. Your MHUB or uControl system will continue to operate normally.

    You may want to consider upgrading if you plan to:

    • Add new integrations or automation features
    • Expand your system with additional rooms or devices
    • Take advantage of future uOS platform developments

    In these cases, adding a uControl Processor running uOS Studio will unlock the full feature set.

    When upgrading, your system will need to be reset and configured as a stacked system, where the uControl Processor manages the MHUB and any other HDA devices.

    Need help or more information?

    In these cases, adding a uControl Processor running uOS Studio will unlock the full feature set.

    When upgrading, your system will need to be reset and configured as a stacked system, where the uControl Processor manages the MHUB and any other HDA devices.

  • Troubleshooting: Mixing 3D and 2D on a matrix or splitter

    In order to route 3D content easily via a matrix switch or splitter, ALL connected displays need to be 3D compatible. Even, if just one of the displays is not 3D compatible, the 3D source player will NOT output the 3D content. The HDMI handshaking process will trigger the source player to drop it’s resolution output so that all displays can show content.

    The problem is HDMI is designed such that the source ‘polls’ the EDID data (EDID is a display’s identity card stating what it’s capabilities are, a bit like a top trumps card) from all connected Sink devices (your 3D enabled display and non-3D enabled AVR) and outputs the lowest quality video signal all devices support (2D in your case).

    To ensure 3D IS routed via the Matrix Switch or Splitter, the non-3D compatible display device must not be ‘active’. Sometimes turning the display into standby will be sufficient and sometimes full power off is required.

    Essentially, the 3D source player must not be able to ‘see’ a 2D only display connected to the Matrix Switch or Splitter.

    For best results when using 3D Blu-ray – HD Connectivity recommends… not actually connecting your 3D Blu-ray (BR) player to the Matrix. As Blu-ray 3D content is generally only viewed at a single ‘main’ TV location, in this instance it is better to have a direct connection between source and display, bypassing the Matrix completely. This will avoid any potential for ‘black screen’ situations at the other TV locations. It will also ensure that absolutely the best 3D format is selected for use on that display, not a potentially reduced quality 3D format that a lower 3D-capable display, connected to the matrix can influence the 3D BR to output. (Plus wearing those massive 3D glasses all around your house is really not cool and could result in you bumping into doorframes! – Ed)

  • Troubleshooting: Multiroom+ System IR

    Troubleshooting Approach

    When attempting to troubleshoot any issue, we need to isolate where the root cause of the fault could lie by a logical process of elimination.

    At the start of a troubleshooting process, never rule out anything as not a potential cause of the problem. Every aspect of the installation should be considered as a potential suspect. Each component of the installation should be ruled out one-by-one and only then eliminated from the troubleshooting process as the potential problem.

    (more…)