CL3 Firmware V5.80 (Previous version)

Refer to these release notes when updating CL series. Please read the following instructions before updating.

Please do not use the EEE function (*) of network switches in a Dante network.

Although power management should be negotiated automatically in switches that support EEE, some switches do not perform the negotiation properly. This may cause EEE to be enabled in Dante networks when it is not appropriate, resulting in poor synchronization performance and occasional dropouts.

Therefore, we strongly recommend that:

1. If you use managed switches, ensure that they allow EEE to be disabled. Make sure that EEE is disabled on all ports used for real-time Dante traffic.
2. If you use unmanaged switches, make sure to not use network switches that support EEE.

* EEE (Energy Efficient Ethernet) is a technology that reduces switch power consumption during periods of low network traffic. It is also known as Green Ethernet and IEEE802.3az.

Cautions for Dante Firmware

• You need to update the Dante-MY16-AUD firmware to V3.3.9 or later before using the Dante-MY16-AUD with the CL series.
• The Dante Firmware Update Manager since v1.4.16.6 for Windows does not support Windows XP. Please use Windows 7, Windows 8.1, or Windows 10.
• Follow the instructions on the update guide.
• The Dante settings might not be properly initialized when the firmware is updated, which results in data inconsistency between the CL/QL console and the R series units. This might occur only when the Dante Latency was set to 0.25ms or 0.5ms. Therefore, after updating, it is recommended to briefly change the Latency to 1.0ms on the console with the Console ID #1, then restore the original setting again. This will remove the possibility data inconsistency between the console and the mounted R series units. However, Dante Controller will be needed to manually change the settings of R series units that are not mounted on the console with Console ID #1.

Cautions for Dante Domain Manager (DDM)

• Please check here when using DDM.

CL/QL/RIVAGE PM/R/Tio Series Editor/Firmware/R Remote Compatibility

Please make sure to use appropriate version of CL Editor or QL Editor which is compatible with your console firmware in reference to the following compatibility chart. Using an unsupported Editor/firmware combination may result in unexpected behavior.
The Firmware Set is a set of main (and sub) firmware of the device and the Dante firmware. The version of Firmware Set is the same as the version of the main firmware. Refer to the release note of each firmware about the details of the Firmware Set.

Compatibility List

Dante I/O Supported device information

New features in V5.80

• Now supports control of AFC Image from the console, allowing object panning and scene recall.
• Added support for the latest Shure product variants and new RF Bands in the QLX-D, ULX-D and Axient Digital product lines.

Improvements in V5.80

• Improved the performance of the connection between CL/QL Editor and the console when used on networks with high latency.

Fixed bugs in V5.80

• Fixed a rare problem in which CL/QL consoles interfered with TCP communication of other networked devices when used together with a DHCP server and those devices were rebooted.
• Fixed a bug in which the remote control status would occasionally not update from SYNCHRONIZING to CONTROLLABLE when Rio3224-D2/Rio1608-D2 were mounted.

Known issues

• On CL/QL Series consoles, if a console file (.CLF) saved on an older version is loaded into a console running V5.80, the message "Parameter out of range" may appear at the bottom of the display during file load and some parameter data will not be loaded correctly. To avoid this issue, please restart the console before loading the file again. Alternatively, the console file can be opened using CL/QL Editor V5.8.0 and re-saved. The re-saved file can then be correctly loaded into CL/QL consoles running V5.80 at any time.
• If a device running V5.80 or later has been enrolled in Dante Domain Manager and then is downgraded to V5.70 or earlier, the Dante module may occasionally not work correctly and control of the module is not possible.
  In the event of this happening, re-enroll the device in Dante Domain Manager and then restart it.
  Alternatively, initialize the device and its Dante settings* but make sure to back up the console data before initializing.
  * While holding down the [STORE] key and the [INC] key (CL series), or the master section A and B [SEL] keys (QL series), turn on the power to the device to initialize it.
• The following problems are found in version 8.1.1 of CL StageMix.
  • If the CL StageMix screen is switched from the Master Bank that shows the Stereo/Mono levels properly to another bank and then returned to the Master Bank via the Navigation/Meter Bridge, the level meters in the Master Bank become inactive. This can be solved by rebooting the application or changing the metering points for Output Channels from the SETUP options.
  • CL StageMix is often forced to terminate if a scene is recalled via a console just after the DANTE NAMES TO CHANNELS function in the Input Port Patch OPTIONS menu is executed. This can be solved by rebooting the application.
• The console may become inoperable after a "kernel sysdwn" message due to an unexpected error.
  If this happens, the console needs to be restarted. However, since all the settings including Dante settings* will be initialized to the default, please back up data regularly.
  * It will be set to DAISY CHAIN after the initialization. If the console is used via a redundant connection, unplug the Dante network cable first before reconfiguring the Dante settings.
• A device enrolled via DDM (Dante Domain Manager) rarely appears with a “VIRTUAL” indicator on the DEVICE MOUNT page. If this indicator is shown, press the REFRESH button.
• If Dante Virtual Soundcard (DVS) is patched to the CL series device using Dante Controller, the patching may not be recalled correctly when the CL series device is restarted. In such cases, patch the DVS again. In addition, when using a version of DVS for Windows that is older than v3.2.0, patches after CH41 cannot be performed from CL series consoles.
• Loading of a file created by version V1.15 or older will not include the mount information of Dante devices other than any connected R-series. It is the same when recalling a DANTE INPUT PATCH LIBRARY. Please reset MOUNT, PATCH, and DANTE INPUT PATCH Library data using V1.51 or later if necessary.

NOTICES

• You can use the following amount of CL/QL/RIVAGE PM/R Remote units to remotely control each device unit (listed at left).
  • RMio64-D/RSio64-D/Tio1608-D (V1.04 or later): Maximum of four CL/QL units, or six R Remote units.
  • Rio/Ri/Ro/Rio3224-D2/Rio1608-D2: Maximum of four CL/QL/RIVAGE PM units plus six separate computers operating R Remote.
• You can connect up to ten units of external controllers such as MonitorMix.
• When setting up the latency in Dante Controller, and there is a discrepancy in latency with the transmit device or the receive device, the largest (slowest) latency setting becomes effective.
• You need to assign Y###- (# is a three-digit hexadecimal number containing the digits 0 - 9 and uppercase A - F (000 - FFF)) to the head of the device label for CL/QL consoles to recognize the device as a SUPPORTED DEVICE.
  • An appropriate device label will be automatically assigned to a Dante-supported device manufactured by Yamaha by referring its device ID and so on. (You will still need to assign a device label manually to some of the products such as AIC128-D.)
  • Device labels need to be assigned manually to third-party products including Dante-MY16-AUD2.
  • Regarding wireless receivers manufactured by Shure, refer to their setup guide to set up properly.
  • Restriction of a device label
    • Y###-**********
    • # is a three-digit hexadecimal number containing the digits 0 - 9 and uppercase A - F (000 - FFF)
    • * indicates any desired character (alphabetical uppercase or lowercase, numerals, or - (hyphen) may be used) Up to 31 characters including the 'Y' are supported.
    • For the R-series, make sure that the ID indicated by Y###- is not duplicated by any other R-series unit, even if it is a different size.
• In V2.0 and later, custom fader bank settings are not only included in user settings, but in scene data as well. The custom fader bank settings that are called up vary depending on the logged-in user, the type of the loaded data, and the version. Please note the following points:
  • If you load console data of the ALL type as Administrator, the custom fader bank settings for the saved Administrator are recalled. If you load ALL data as Guest or another user, the custom fader bank settings for the saved current scene are called up.
  • If you load ALL data that was saved in CL V1.70 or earlier, since scenes do not include custom fader bank settings, the custom fader bank settings for the current scene when the load was performed are applied to all scenes. Therefore, before loading ALL data, we recommend that you either change users to set the custom fader bank to the desired setting, or that you enable Recall Safe for the custom fader bank.
• File Converter V5.2.0, compatible with CL firmware V2.xx, V3.xx, V4.xx and V5.xx and QL firmware V3.xx, V4.xx and V5.xx has been made available for use.