Public Beta 5 of the Metric Halo 3d software is now available for download.

A detailed change log is available at the bottom of this message.

The direct download link for the software is:

MIO3dIcon
3d Public Beta - pb5

3d Public Beta Quick Start Guide

There is an abbreviated quick start guide linked below to help you get started; it has been updated for pb5:

3d Beta Quickstart Guide

The component versions in this release are:

Package Version:beta_3d-pb5Updated
MIO Console Version:6.0.0 [3321]Updated
Firmware Version :6.0.70Updated
Driver Version :2.0.43Unchanged

NOTE: You only need to install updated components.

The highlights of this release are:

New Features Overview: Digital Port Status and Control UI

You can access the Digital Port Status and Control UI from the system status pane. Each box has a "Digital Port Status and Control UI" button (which looks like "01010..." in the upper right corner of the pane, circled in red below) in its status pane:

UnitTileDigitalIndicator

Click the "01010..." to pop up the Digital Port Status and Control UI for that box:

AES-MADIStatus

The UI has 3 columns:

The UI will list all the installed ports for the device (so it will also show any digital ports that are installed via EdgeCard).

For most digital port types (AES/SPDIF/MADI) the input can either be locked or not, and there is no configurable mode for the output.

For the ADAT Optical ports each input port can be locked to either ADAT or TOSLINK (Optical SPDIF) or unlocked (if there is no valid input signal of either type on the port). The output ports can either send ADAT (8 channels) or TOSLINK (e.g. Optical SPDIF - 2 Channels). You can select what signal type you want to send on a per port basis with the associated popup menu.

AES-MADIStatus

New Features Overview: Optical Routing

The 3d Card has a SPDIF transmitter and an ADAT transmitter for each Optical Output Port. When you select between the output port mode, you are selecting which transmitter is physically connected to the port. Each transmitter has its own output routing in the system. As a result, when an output port is set to TOSLINK mode, you must route to the associated TOSLINK channels in order to get output. When it is set to ADAT mode, you must route to the associated ADAT channels to get output.

When an input port is receiving TOSLINK the hardware automatically determines the incoming format. The first two channels of each receiver block will carry either the first two ADAT inputs for the port or the SPDIF inputs for the port, depending on the received signal. So you can route from the TOSLINK input channels or from the first two channels of the associated ADAT block. When it is receiving ADAT, you should use the associated ADAT inputs to have access to all of the ADAT channels.

New Features Overview: Delete Offline Unit/Domain

When you use multiple boxes and systems it is possible to get an offline Unit or Domain in your console setup that is now redundant and unneeded. pb5 provides support to allow you to remove these offline items from your setup.

To remove an offline Unit from your setup:

To remove an offline Domain from your setup:

[Detailed Changelog]

Changes Since beta_3d/pb4: (90 commits)

Firmware Changes since 6.0.62 (77 commits)