CL1 Firmware V5.50 (Previous version)

Use this release notes to update CL/QL to V5.50. 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.

CL/QL/RIVAGE/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.50

• Now supports System Monitoring of ProVisionaire Control.

Improvements in V5.50

• Changed the specification so that the temporary unmute would be cleared when you changed the setting for the mute group function.

Fixed bugs in V5.50

• Solved a problem in which the brightness of the panel LEDs became maximum after exiting the FADER CALIBRATION MODE screen.
• Solved a problem in which all the DANTE INPUT PATCH settings for the console's 64 channels that had already been made might be removed if you opened the startup menu screen by turning on the console while holding down the [STORE] key.
• Solved a problem in which CUE functions such as Specific CUE, Clear CUE and so on did not work correctly with MIDI Control Change messages in firmware V4.00 or later.
• Solved a problem in which operations that were not allowed to Guests were temporarily possible while the password input dialog was displayed after the console logged in with administrator privileges was restarted.
• Solved a problem in which the audio signal might not be sent to both L and R buses or the MIX buses could not be switched on or off if MIX buses that had different settings each other were set in stereo.
• Improved a symptom in which a faulty USB memory drive inserted into the console’s USB port might cause the console to generate an error. Please see the following supplementary information.
  Supplement
  A console with version 5.10 or earlier firmware may become inoperable after a "kernel sysdwn" message that is caused by an inserted USB memory drive which cannot be recognized due to corrupt data or insufficient contact with the USB port.
  To recover from this state, the console must be restarted. However, restarting the console will initialize all the data including Dante settings*, returning the console to its default settings.
  This version reduces the frequency of occurrence but cannot completely eliminate it since the error is caused by the USB memory drives. Therefore, this issue may still occur if a faulty USB memory drive is used.
  Ensure that any USB memory drive that will be used works properly beforehand and avoid removing or inserting the USB memory drive during shows.
  Please perform back-ups on a regular basis to avoid any loss of data.
  * 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.
• Solved a problem in which all 24 devices might not be mounted if many mixer controllers such as CL/QL Editor and StageMix were connected to the console.
• Solved a problem in which the patching to the AES67 Flow was not displayed in the DANTE INPUT PATCH screen.
• Solved a problem in which only the Dante firmware failed to update when updating the CL/QL series firmware and the Dante firmware from USB memory.
• Solved a problem in which the operation was not reflected in the online CL/QL Editor when you operated the GEQ FLAT function on the CL/QL StageMix.
• Solved a problem in which parameter values of CL/QL series and MTX/MRX series might not match after synchronization with the MTX-MRX Editor.
• Solved a problem in which the DEVICE IDENTIFY button was activated if the blank column was selected in the DEVICE LIST field when you mounted a device manufactured by Shure.
• Solved a problem in which EQ types might not match each other if you select RESET BOTH to link 8Band PEQ in stereo.
• Solved some minor errors.

Known issue

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

NOTICE

• You can use the following amount of CL/QL/RIVAGE PM10/PM7/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 PM10/PM7 units plus six separate computers operating R Remote.
• You can connect maximum of ten iOS devices operating 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.0.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.