CL1 Firmware V5.81
Refer to these release notes when updating CL series. Please read the following instructions before updating.
Cautions when updating
- Use the "cl*_firm581.zip "(* is the model number) when updating.
- If updating from CL V5.80, copy files "CL_SUBP_V581.BIN" and "MCLP5_81.PGM" to the root directory of the USB flash drive. Follow the instructions on the update guide. You don’t need to update the Dante firmware.
- If updating from CL V5.70 or older, copy files "CL_SUBP_V581.BIN" and "MCLP5_81.PGM" to the root directory of the USB flash drive. Follow the instructions on the update guide. You also need to update the Dante firmware. You can now update the Dante firmware for CL also by using the USB flash drive. This method allows you to update both the firmware and the " CL_SUBP_V581.BIN " and "MCLP5_81.PGM" files together at the same time.
- If updating from CL V1.61 or older, or if the message "NAME SUB CPU is old" appears after updating to V5.80, copy "CL-MD101.BIN" file in CL*_firm580/NAME SUB (* is the model number) to the root directory of the USB flash drive. Follow the instructions on the update guide. This method allows you to update both the Dante firmware and the " CL_SUBP_V581.BIN " and "MCLP5_81.PGM" files together at the same time.
Before copying files, delete all files with extension .PGM and .BIN if any exists in the root directory of the USB memory. Prior to V3.0, the CL and QL Series used different files when updating, but both files used the same name * "C-MD1.BIN." For this reason, an error may occur during update when the incorrect "C-MD1.BIN" file is used or left in the root directory.
Updating Dante firmware by using a USB flash drive takes approximately 30 minutes.
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:
- 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.
- 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 v22.214.171.124 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.
Main Revisions and Enhancements
Changes in V5.81
- Now supports updated networking parts. Hardware revised due to the parts change have "A" marked next to the model number on the serial number label, and these products cannot be downgraded to versions earlier than V5.81.
Fixed bugs in V5.81
- Fixed a bug that cannot change the Dante Latency settings from the console of R series fitted with a Brooklyn 3 Dante module. (The Dante module used in this product can be identified in Dante Controller).
- Fixed a bug in which, if a console file (.CLF) saved on an older version was loaded into a console running V5.80, the message "Parameter out of range" might appear at the bottom of the display during file load and some parameter data was not loaded correctly.
- Fixed a bug in which Shure AXT400 did not appear in the ONLINE DEVICE LIST.
- Fixed a rare problem in which the Dante module did not operate when starting up due to specific network conditions.
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.
- 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.
- 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
- # 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.
Lizenzvereinbarung und Download-Datei
PLEASE READ THIS SOFTWARE LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFORE USING THIS SOFTWARE. YOU ARE ONLY PERMITTED TO USE THIS SOFTWARE PURSUANT TO THE TERMS AND CONDITIONS OF THIS AGREEMENT. THIS AGREEMENT IS BETWEEN YOU (AS AN INDIVIDUAL OR LEGAL ENTITY) AND YAMAHA CORPORATION ("YAMAHA").
BY DOWNLOADING, INSTALLING, COPYING, OR OTHERWISE USING THIS SOFTWARE YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE WITH THE TERMS, DO NOT DOWNLOAD, INSTALL, COPY, OR OTHERWISE USE THIS SOFTWARE. IF YOU HAVE DOWNLOADED OR INSTALLED THE SOFTWARE AND DO NOT AGREE TO THE TERMS, PROMPTLY ABORT USING THE SOFTWARE.
1. GRANT OF LICENSE AND COPYRIGHT
Subject to the terms and conditions of this Agreement, Yamaha hereby grants you a license to use copy(ies) of the software program(s) and data ("SOFTWARE") accompanying this Agreement, only on a computer, musical instrument or equipment item that you yourself own or manage. The term SOFTWARE shall encompass any updates to the accompanying software and data. While ownership of the storage media in which the SOFTWARE is stored rests with you, the SOFTWARE itself is owned by Yamaha and/or Yamaha's licensor(s), and is protected by relevant copyright laws and all applicable treaty provisions. While you are entitled to claim ownership of the data created with the use of SOFTWARE, the SOFTWARE will continue to be protected under relevant copyrights.
- You may not engage in reverse engineering, disassembly, decompilation or otherwise deriving a source code form of the SOFTWARE by any method whatsoever.
- You may not reproduce, modify, change, rent, lease, or distribute the SOFTWARE in whole or in part, or create derivative works of the SOFTWARE.
- You may not electronically transmit the SOFTWARE from one computer to another or share the SOFTWARE in a network with other computers.
- You may not use the SOFTWARE to distribute illegal data or data that violates public policy.
- You may not initiate services based on the use of the SOFTWARE without permission by Yamaha Corporation.
- You may not use the SOFTWARE in any manner that might infringe third party copyrighted material or material that is subject to other third party proprietary rights, unless you have permission from the rightful owner of the material or you are otherwise legally entitled to use.
Copyrighted data, including but not limited to MIDI data for songs, obtained by means of the SOFTWARE, are subject to the following restrictions which you must observe.
- Data received by means of the SOFTWARE may not be used for any commercial purposes without permission of the copyright owner.
- Data received by means of the SOFTWARE may not be duplicated, transferred, or distributed, or played back or performed for listeners in public without permission of the copyright owner.
- The encryption of data received by means of the SOFTWARE may not be removed nor may the electronic watermark be modified without permission of the copyright owner.
This Agreement becomes effective on the day that you receive the SOFTWARE and remains effective until terminated. If any copyright law or provision of this Agreement is violated, this Agreement shall terminate automatically and immediately without notice from Yamaha. Upon such termination, you must immediately abort using the SOFTWARE and destroy any accompanying written documents and all copies thereof.
4. DISCLAIMER OF WARRANTY ON SOFTWARE
If you believe that the downloading process was faulty, you may contact Yamaha, and Yamaha shall permit you to re-download the SOFTWARE, provided that you first destroy any copies or partial copies of the SOFTWARE that you obtained through your previous download attempt. This permission to re-download shall not limit in any manner the disclaimer of warranty set forth in Section 5 below.
You expressly acknowledge and agree that use of the SOFTWARE is at your sole risk. The SOFTWARE and related documentation are provided "AS IS" and without warranty of any kind. NOTWITHSTANDING ANY OTHER PROVISION OF THIS AGREEMENT, YAMAHA EXPRESSLY DISCLAIMS ALL WARRANTIES AS TO THE SOFTWARE, EXPRESS, AND IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF THIRD PARTY RIGHTS. SPECIALLY, BUT WITHOUT LIMITING THE FOREGOING, YAMAHA DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED.
5. LIMITATION OF LIABILITY
YAMAHA'S ENTIRE OBLIGATION HEREUNDER SHALL BE TO PERMIT USE OF THE SOFTWARE UNDER THE TERMS HEREOF. IN NO EVENT SHALL YAMAHA BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY DAMAGES, INCLUDING, WITHOUT LIMITATION, ANY DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EXPENSES, LOST PROFITS, LOST DATA OR OTHER DAMAGES ARISING OUT OF THE USE, MISUSE OR INABILITY TO USE THE SOFTWARE, EVEN IF YAMAHA OR AN AUTHORIZED DEALER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event shall Yamaha's total liability to you for all damages, losses and causes of action (whether in contract, tort or otherwise) exceed the amount paid for the SOFTWARE.
6. OPEN SOURCE SOFTWARE
This SOFTWARE may include the software or its modifications which include any open source licenses, including but not limited to GNU General Public License or Lesser General Public License ("OPEN SOURCE SOFTWARE"). Your use of OPEN SOURCE SOFTWARE is subject to the license terms specified by each rights holder. If there is a conflict between the terms and conditions of this Agreement and each open source license, the open source license terms will prevail only where there is a conflict.
7. THIRD PARTY SOFTWARE AND SERVICE
Third party software, service and data ("THIRD PARTY SOFTWARE") may be attached to the SOFTWARE. IF, in the written materials or the electronic data accompanying the software, Yamaha identifies any software and data as THIRD PARTY SOFTWARE, you acknowledge and agree that you must abide by the terms of any agreement provided with the THIRD PARTY SOFTWARE and that the party providing the THIRD PARTY SOFTWARE is responsible for any warranty or liability related to or arising from the THIRD PARTY SOFTWARE. Yamaha is not responsible in any way for the THIRD PARTY SOFTWARE or your use thereof.
- Yamaha provides no express warranties as to the THIRD PARTY SOFTWARE. IN ADDITION, YAMAHA EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, as to the THIRD PARTY SOFTWARE.
- Yamaha shall not provide you with any service or maintenance as to the THIRD PARTY SOFTWARE.
Yamaha is not liable to you or any other person for any damages, including, without limitation, any direct, indirect, incidental or consequential damages, expenses, lost profits, lost data or other damages arising out of the use, misuse or inability to use the THIRD PARTY SOFTWARE.
U.S. GOVERNMENT RESTRICTED RIGHTS NOTICE:
The Software is a “commercial item,” as that term is defined at 48 C.F.R. 2.101 (Oct 1995), consisting of “commercial computer software” and “commercial computer software documentation,” as such terms are used in 48 C.F.R. 12.212 (Sept 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.72024 (June 1995), all U.S. Government End Users shall acquire the Software with only those rights set forth herein.
This Agreement shall be interpreted according to and governed by Japanese law without reference to principles of conflict of laws. Any dispute or procedure shall be heard before the Tokyo District Court in Japan. If for any reason a court of competent jurisdiction finds any portion of this Agreement to be unenforceable, the remainder of this Agreement shall continue in full force and effect. All legal notices, notice of disputes and demands for arbitration, and any other notice which purports to change these provisions or to assert legal entitlements must be sent in writing to:
10-1, Nakazawa-cho, Naka-ku, Hamamatsu, Shizuoka, 430-8650, Japan
9. ENTIRE AGREEMENT
This Agreement constitutes the entire agreement between the parties with respect to use of the SOFTWARE and any accompanying written materials and supersedes all prior or contemporaneous understandings or agreements, written or oral, regarding the subject matter of this Agreement.
Yamaha may amend, revise or update this Agreement at its discretion. Any change or update that Yamaha makes to this Agreement will be effective after you agree with the updated terms of this Agreement or use this SOFTWARE.
Last updated :January 28, 2020
Du brauchst ausserdem
- Previous versions information
- CL1 Firmware V5.80
- CL1 Firmware V5.70
- CL1 Firmware V5.60
- CL1 Firmware V5.51
- CL1 Firmware V5.50
- CL1 Firmware V5.10
- CL1 Firmware V5.01
- CL1 Firmware V5.00
- CL1 Firmware V4.51
- CL1 Firmware V4.50
- CL1 Firmware V4.10-2
- CL1 Firmware V4.04-2
- CL1 Firmware V4.02
- CL1 Firmware V4.01
- CL1 Firmware V4.00
- CL1 Firmware V3.11-2
- CL1 Firmware V3.10
- CL1 Firmware V3.02 (from V1.70 and later)
- CL1 Firmware V3.02 (from V1.61 and older)
- CL1 Firmware V2.04 (from V1.70 and later)
- CL1 Firmware V2.04 (from V1.61 and older)
- CL1 Firmware V2.03
- CL1 Firmware V1.70-2
- CL1 Firmware V1.61