CL3 Firmware V3.11-2 (Previous version)

Dante firmware has been changed to "3.8.32.1-3.5.33.8-1.2.7". This change corresponds to the hardware change of the Dante module due to the completion of part production. The function is the same as the previous version "3.8.0.24-3.5.1.8-1.2.2", and there is no change in the product firmware. Therefore, customers already using V3.11 do not need updating. In addition, Dante firmware "3.8.0.24-3.5.1.8-1.2.2" and "3.8.32.1-3.5.33.8-1.2.7" products can be used together. Please refer to the version compatibility table of each device.

• 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 (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 v1.4.13.2 for Mac does not support Mac OS X 10.6.8. Please use Mac OS X 10.7.5, 10.8.5, 10.9.5 or 10.10.
• The Dante Firmware Update Manager v1.4.13.2 for Windows does not support Windows XP. Please use Windows 7 or Windows 8/8.1.
• We found a problem in which the Dante settings might not be properly initialized when the firmware is updated to V3.0/V3.1, 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 to V3.0/V3.1 it is recommend 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 possible 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

• You can remotely control one RSio64-D unit from a maximum of two CL/QL/R Remote units.
• You can remotely control one RMio64-D unit from a maximum of six CL/QL/R Remote units.
• You can remotely control one Rio/Ri/Ro unit from a maximum of two computers operating R Remote. You can also remotely control from four separate CL/QL units.

New Features in V3.10

• Now supports the RSio64-D control.
• You can now remotely control supported third-party head amps (HA) from the console.
• Functions related to cascade connections have been added.
• You can now select CENTER NOMINAL or LR NOMINAL for the pan setting of monaural input channels.
• You can now appropriately switch PAN mode and PAN knob settings due to changes in the stereo input signal processing of L-MONO, R-MONO and LR-MONO. 
  For details, refer to the CL5/CL3/CL1 V3.10 Supplementary Manual

Improvements in V3.10

• You can now update the Dante firmware for CL and QL by using the USB memory.
• The files for updating CL and QL have been changed from the same name "C-MD1.BIN" to separate names. This will prevent updating with the wrong file.
• You can now manually remount when the USB memory is not recognized.

Fixed bugs in V3.10

• Solved a problem in which the levels were not the same when odd-numbered/even-numbered MIX and MATRIX buses with different levels were linked to use as a stereo bus.
• Solved a problem in which if GPI OUT was set for the current scene, GPI operated when the scene was recalled by using PREVIEW mode.
• Solved a problem in which if GPI OUT was set for that scene after storing a scene, GPI OUT was output also when a library was recalled.
• Solved a problem in which it appeared that RMio64-D, as a member of the NUAGE Workgroup Manager, could operate from CL. (In actuality, you cannot operate from CL while it is a member of the NUAGE Workgroup Manager.)

Fixed bugs in V3.11

• Solved a problem in which GEQ Rack 8 outputs a pulse noise when mounting or dismounting the 8ch Automixer on GEQ Racks 1-4.
• Solved a problem in which faders resist any manual adjustment when scenes are recalled with the faders made safe by Focus.
• Solved a problem in which the WORD CLOCK screen incorrectly shows DANTE SLAVE in some cases.

Known issue

• 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.
• When performing Ch Move for a channel which is a member of a Ch Link, the channel parameters may (in some cases) be altered according to Ch Link A settings, rather than maintaining the correct settings of the channel.

NOTICE

• 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.
• The following device labels are used for detecting a SUPPORTED DEVICE.
  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.