User guide

iControl

Release Notes

• [Ref. #37262] If the Loudness Logger is active while you switch inputs to the Kaleido-Solo

(KS910), the Logger may not recover (restart logging) automatically. In such a case, on the

Loudness Logger configuration page, the corresponding KS910 would display

NODATA.

Workaround:

To recover logging capability:

1. Open the Densité Manager.

2. Select the problematic Kaleido Solo.

3. Put the Kaleido Solo in Standby mode.

4. Put the Kaleido Solo in Online mode.

•

[Ref. #36220] Loudness Analyzer does not display TIMECODE metadata.

Miranda Interface Updater

• [Ref. #21974/25234] A Densité card upgrade may fail when another application—in addition

to the MIU—is already connected to the CPU-ETH 2 controller of this card’s frame.

As of iControl version 3.40, the MIU displays a message listing all applications or services

already connected to the same Densité frame. Such connections can come from the

iControl Densité Manager, but also from other Application Servers, from computers

running iControl Solo, or from iControl Router Manager (if the Densité frame contains

cards with router capabilities, such as the HRS-1801, HCO-18x1, DCO-17x1, MSB-1121).

Miranda Media Player

• [Ref. #28668] On an iC Web page that has several players, when you switch from NTSC to PAL

format, one or more players may no longer function properly.

Workaround:

Make sure you select the appropriate video format check box (525 or 625)

in the device’s control panel.

•

[Ref. #26916] When launching iC Navigator on a system with a 64-bit Java Virtual Machine

installed, several streaming-related exception errors are listed in the logs.

Workaround:

Use a 32-bit JVM on the client machine instead of a 64-bit JVM.

Note: The message lists the IP addresses associated with connections made to the

Densité controller. From the IP addresses, your system administrator will be able to

identify the associated application or service.