Software & Firmware Archives

IMPROVEMENTS

• Customizable controls for Shure wireless products
• User interface improvements
• Bug fixes

NOTES 

• User Guide
• Compatible with Android 8.0 or later

INITIAL RELEASE

NOTES

• User guide
• Firmware updates for AONIC 50 will be available in the ShurePlus PLAY app

IMPROVEMENTS

• Bug fixes

NOTES 

• User Guide
• MV88+ User Guide
• Compatible with Android 6.0 and higher.
• NOTE FOR MV88+ USERS: Learn about compatibility with your Android device at www.shure.com/MOTIVcompatibility.

Improvements

• Support for new frequency bands:
  • Axient Digital
    • 1240 MHz – 1260 MHz (Z16)
  • PSM1000
    • 518 MHz – 584 MHz (H22)

Notes

• User Guide
• To operate Axient 2.1.31 devices with other Shure systems and software, see the following list of minimum versions:
  • Axient Digital 1.2.35
  • UR4 UHF-R receiver 1.171
  • UR3 Plug-on Transmitter 1.0.0.16
  • UR5 Portable Diversity Receiver 1.0.0.13
  • ULX-D ULXD4X Receivers 2.4.9
  • QLX-D QLXD4 Receiver 2.3.22
  • PSM1000 P10T Transmitter 1.7.6
  • SBRC Shure Battery Rack Charger 1.1.5
  • Shure Update Utility 2.4.6
  • ShurePlus Channels 1.4.2
  • Wireless Workbench 6.13.1

Improvements

• Support for new frequency bands:
  • Axient Digital
    • 1240 MHz – 1260 MHz (Z16)
  • PSM1000
    • 518 MHz – 584 MHz (H22)

Notes

• User Guide
• To operate Axient 2.1.31 devices with other Shure systems and software, see the following list of minimum versions:
  • Shure Update Utility 2.4.6
  • Wireless Workbench 6.13.1

Initial Release

Known Issues

• The use of packet scanning security software may cause audio performance issues with IntelliMix Room.
• When transitioning from a trial license to a paid license, the total trial term will be used unless the user manually deactivates and reactivates the endpoint using Designer software.
• In some circumstances, the system tray application will not run automatically. Navigate to C:\Program Files\Shure\IntelliMixRoom and run the “IntelliMixRoomTrayApp.exe”. This only needs to be done once per instance of IntelliMix Room.
• When using Dante Domain Manager (DDM) and the permissions for the device are set to read only or the DDM server is offline, you can still update IntelliMix Room.
• If you change the channel count of an installation, the Dante output channel names do not change.
• When using Shure Networked Audio Encryption, you'll see a "key error" for channels without established Dante audio routes. This does not affect device performance and can be ignored.
• Some text in the system tray application only appears in English.
• Changing the System Name of the host computer after installation of IntelliMix Room also changes the Dante Device name, as seen in Dante Controller. The Shure device name stays the same.
• If experiencing issues changing the channel count of an IMX Room instance within Designer Software, deactivate the IMX Room instance first, then change the channel count and re-activate.

Notes

• User Guide
• Installation and Deployment Guide
• Quick Start Guide
• System requirements
  • Windows 10 Pro, Enterprise, or IoT Enterprise (64 bit)
  • Processor: i5 quad core 1.9 GHz minimum
  • 8 GB RAM minimum
  • Solid state drive
• IMX Room 1.0 is compatible with the following software and firmware versions:
  • Designer 4.1
  • MXA910 4.1.41
  • MXA310 4.1.37
  • P300 4.1.11
  • ANIUSB-MATRIX 4.1.39
  • ANI22 4.1.39
  • ANI4IN 4.1.39
  • ANI4OUT 4.1.39
  • Microflex Wireless 8.0.3

Important

• This software release is used for new SW6000 installations or to update all previous SW6000 installed versions, however it cannot be used to update systems using CU 6005, CU 6010 or CU 6011 Central Units
• This version is compatible with SW6000 Software License file v1.7 only
• No new SW6000 license is needed if updating from SW6000 v6.0.xxx or later versions
• A new SW6000 license is needed if updating from SW6000 v5.8.xxx or previous versions

New Features

• CAA
  • New conference variables to be used in voting configuration
    • Button1 (1-5) - result without voting weight
    • TotalButton1 (1-5) - result without voting weight
    • DelegatesVoted - result without voting weight
  • UI revised to add culture code in setup of language for MXC unit
  • Option in Meeting options to enable use of ‘ShowName’ for conference units with a graphical user interface
  • Support sending messages to participants using conference units with paired MXCSIGN
• CAA/CUA
  • Support for extended audio range for MXCMIU units when using XLR input
• CAA/MXCSIGN - Expanded functionality
  • Updated template format:
    • Supporting complex alphabets like:
      • All alphabets included in MXC Global languages
      • Hebrew
    • Option to rotate the image 180 degrees
    • Option to assign colors (grayscale) to text and background, both globally and in text boxes
  • Option to pair an MXCSIGN with an interpreter booth and display interpretation related information:
    • Booth number
    • Booth language
    • Booth language channel
    • Booth language abbreviation
  • The use of the word ‘Delegate’ is changed to ‘Participant,’ which needs to be changed in old templates intended to be used
  • Expanded information that can be displayed for participants:
    • First name
    • Last name
    • ShowName
    • Message
  • Option to show meeting info:
    • Meeting name
    • Active subject
• CDA
  • Include Reply label and description as displayable options in reply lists:
    • ReplyDescription
    • ReplyLabel

Bug Fixes

• CUA
  • Cannot adjust microphone audio levels for individual seats using CUA
  • Change in language assignment is not reflected for an interpreted channel or number of channels available if the assigned language is changed using CAA
  • Votes cast using the conference unit are not displayed in the voting buttons in a CUA assigned to the unit when the CUA voting buttons are disabled
  • Dragging and droping in the request list will not correctly move the reply colors between subjects
  • If a voting formula with a calculation error is used (e.g. divide by zero) the CUA will crash when trying to display the voting result.
  • An error may be displayed if a participant is logged in or out using mimic while the CUA is displaying the microphones screen with participants’ extension control open.
  • Unplugging/plugging in an MXCSIGN could cause an exception if CUA displays the Microphones control with Participants extension control activated
• CUA/CDA
  • Muting a microphone causes the speech time counter to stop. It should continue until the microphone is switched off
• CDA
  • Voting screen does not display voting status and number of votes after the first vote is cast
  • Command line parameter ‘-canresize’ caused a white line to appear when CDA is running on Windows 10
  • Command line parameter ‘-IP’ is not working
  • Interim voting result is not displayed on the mimic for a participant if the participant has proxy voting rights
  • Skin editor alignment ‘grid’ is too closely placed when running the application in Windows 10
  • Language name for Slovenia has been changed from Slovenski to Slovenský
• CAA
  • Microphone seat list does not prevent the user from adding the same computer name as a standalone computer and as a terminal server with console numbers
  • Deleting a ‘meeting role’ which is only used in a room setup will cause an exception
  • Will throw exception if a user tries to add entries to the participant list of a meeting if no participants have been defined in the database
  • Deleting a large agenda with more than 480 subjects caused an exception, and deletion failed
  • Deleting a MXCSIGN template that’s in use caused errors when the MXCSIGN tried to reference the no-longer-existing template
  • Adding conference units for the first time to a system with SW6000 applications running caused a wrong seat name to be displayed for the newly-added units
  • When running a meeting with ‘no login’ mode using an agenda and setting subjects active, the meeting report will not display the agenda item changes
  • Equipment list does not update microphone status on meeting stop. A microphone in request will be removed from request list when the meeting is stopped, but this is not updated in the CAA | Setup | Equipment |Conference units window
  • Using CAA | Setup | Equipment | Interpreter consoles sort desks by clicking on desk number and trying to replace a unit with replace functionality an Exception is seen
  • Using CAA | Setup | Equipment | Interpreter consoles window and changing sort order by clicking on column header for serial#/booth#/desk# while updating settings for an interpreter set can cause an exception
  • Agenda details for no subject may appear multiple times in report if user repeatedly sets agenda item active/not active
  • Importing meeting participants from XML can cause a random group to be added to some participants, even though groups are not defined in the import
• CUI
  • Webservice - result node is missing in the individual voting result event
  • Webservice - A participant logout event for a participant without an import id creates a webservice call with an <import_id> node with value -1
  • Cannot discover new MXCSIGNs if standard templates have been deleted in the database
  • Cannot connect to CCU using Bonjour when using a hostname with a trailing dot
  • Webservice - Seat names are not correctly inserted in a webservice speaker change call if no participant is logged in to the seat
  • Participant names are always sent to the CCU using default language regardless of what language is specified for the ‘Units with graphical user interface’
  • Pausing a meeting with a request list having 2 or more participants in the request list cause an internal error, visible in error messages
• Database
  • Not able to install database using ‘Remove All’ button during installation
  • Fix for updating the ‘Participant list history’
• Installer
  • Installation on Windows Server 2016. MXMQ services do not automatically install
  • Installation on Windows Server 2016. MSMQ services required by SW6000 were not enabled by the install script
• Backup tool
  • Restoring a database using the backup tool and using SQL authentication fails. Note it succeeds when using Windows credentials

Known Issues

• The view of the new templates for the NAMESIGN in ‘CAA | Setup | Configurations | Name sign templates’ is not easily readable as ‘line shift’ between the items is missing

Notes

• UN Name sign are still supported using the templates from version 6.9, however, the word ‘Delegate’ must be changed to ‘Participant’ in the templates
• To operate MXC devices with SW6000 version 6.10, see the following list of minimum software and firmware versions:
  • MXC firmware release 8.6.0

Important

• This firmware release can be used to update Microflex Complete (MXC), DCS 6000, or DCS 5900 systems using DIS-CCU, CU 5905, CU 6105, or CU 6110 Central Units.
• Systems using CU 6000, CU 6005, CU 6010 and CU 6011 Central Units are not supported in this release.
• The Firmware Upgrade Utility (FUU) which is included in the release, is required to update MXC devices.

New Features

• MXCSIGN features in CCU standalone operation:
  • The sign content to be shown can be selected either from the ‘Participant list/NFC’ or from a separate list with ‘Text lines’
  • Option to change font size
• MXCSIGN
  • Support for all alphabets (including complex alphabets) used in the MXC global languages
  • Hebrew is supported when used with SW6000
• Voice activation functionality with time compression in MXC conference units
• Mix-minus functionality in loudspeaker in MXC conference units
• TPCI additions:
  • Meeting start/stop
  • Autofloor on/off
  • Speech time alarm
  • Reporting of participants individual votes
  • MXCSIGN support
    • Control of the content in standalone systems
    • Support for pairing the MXCSIGN to a seat
    • Import of content into the text lines for MXCSIGN
• MXCMIU: Ambient support

Bug Fixes

• MXCSIGN
  • SW6000/MXCSIGN: Disconnecting-connecting a sign gives an error message

Known Issues

• MXC640
  • Manually entered voting results are not shown if a normal voting session has not been started first
  • The agenda subject name for a manually entered result may be wrong
  • It is not possible to use an MXC640 configured as dual delegate with SW6000 if the use of NFC cards is enabled

Notes

• MXC and DCS 6000 firmware files are packaged together in the same release file.
• To operate MXC devices with version 8.6.0 with other Shure networked systems, see the following list of minimum software and firmware versions:
  • SW6000 6.10.14
  • Shure NFC Programming App 1.0.3

Important

• When upgrading Designer versions, the installer may prompt that the destination folder is not empty; please change the folder name or delete the existing folder and it will automatically be re-created during the upgrade.
• In order to push from virtual devices to online devices, or vice versa, the virtual device and online version must be running the same version. For example, all new virtual devices created in Designer 4.1 are on version 4.1.X; those virtual devices can only be associated with online devices that are also on version 4.1.X.
• Designer 4.1 is not backwards compatible with Designer 3.2. The database will not be maintained upon downgrading, and Designer 4.1 files cannot be imported into version 3.2.

Improvements

• Support for IntelliMix® Room Audio Processing Software version 1.0
• Support for MXA910, MXA310, P300, and ANIUSB-MATRIX 4.1.X firmware
• Auto route feature added on the Signal Flow tab
• Multi-select added on P300 and IntelliMix Room schematic views
• Performance improvements
• Bug fixes
• For enhanced security, first-time browser user interface access will prompt the user to set up a passphrase. Users have the option of continuing without a passphrase, allowing for Shure Designer configuration software to securely configure multiple devices at once within a Designer location.
• Passphrase length must be at least eight characters, up to a maximum of 64, with all characters allowed
• Downgrade caution:
• After the 4.1.X upgrade, a device’s new Designer location passphrase (and/or its audio encryption passphrase) might exceed the allowed length of its prior firmware version. In that case, downgrading requires the following procedure to ensure passphrase compatibility:
• Prior to downgrading, disable the location and/or audio encryption passphrase or change the passphrase to the character length allowed by the prior firmware to be downgraded to.
• Perform the device firmware downgrade. Enable passphrase(s) as desired.

Known Issues

• When using Windows 7, no more than five windows can be open simultaneously.
• With more than 20 devices in location or 60 on the network, some actions will take longer due to increased network traffic.
• When deleting a virtual device, Designer will warn that encryption and password settings will be changed; however, the discovered devices’ encryption and password settings will not be affected.
• When importing a Designer preset file into the MXA910 web application, attempts to immediately export that file out of the web application will fail if it is not first loaded and saved to the MXA910.
• Pull and push operation may cause sync status to say “not synced,” although the operation was successful; close and reopen the location to fix this
• When soloing a channel on an MXA310, all channels will show as gated on
• When configuring a single MXA910, rotation of the device will only appear in Location > Coverage Map; go to the location to view the rotated device
• If experiencing issues changing the channel count of an IntelliMix Room instance within Designer Software, deactivate the IntelliMix Room instance first, then change the channel count and re-activate
• When using Shure Networked Audio Encryption for IntelliMix Room, you'll see a "key error" for channels without established Dante audio routes. This does not affect device performance and can be ignored.
• When one or more devices in a location are locked by Dante Domain Manager or Dante Device Lock, operations that affect Dante settings may be unreliable, such as audio routing, pushing virtual to online devices, or enabling audio encryption
• When using the P300’s Matrix Mixer on its Schematic tab, vertical scrolling won’t work correctly; navigate to the Matrix Mixer tab to see all channels.
• Attempts to save templates when devices have routes outside of a location will fail. Add all routed devices to a location to successfully save the template.
• Unsupported firmware may show an indication that the device is locked by Dante Domain Manager or Dante Device Lock. See the minimum supported firmware versions below.

Notes

• Internet access is required during the installation process
• Designer User Guide
• Designer 4.1 is compatible with the following software and firmware versions:
  • IntelliMix Room version 1.0.4.2
  • MXA910 4.1.41
  • MXA310 4.1.37
  • P300 4.1.11
  • ANIUSB-MATRIX 4.1.39
• Requires 64-bit Windows 7, 8.1 or 10

New Features

• Support for Dante Domain Manager
• Dante Device Lock
• Direct outputs from channels 1 – 8
• Now has 8 Dante outputs (was 6)
• Component user interfaces (web UIs) for the P300 and ANIUSB-MATRIX will be feature-reduced to support basic troubleshooting of network and device settings only. Designer version 3.2 will remain available for download to support legacy 3.1.x and 4.0.12 devices. 
  
  NOTE: Please ensure that field technicians and anyone providing in-field support on these devices downloads and installs the latest version of Designer. Device configuration and optimization capabilities will be minimal without Designer.

Improvements

• Additional USB mute sync compatibility
• Additional TPCI commands
• For enhanced security, first-time user interface access will prompt the user to set up a passphrase. Users have the option of continuing without a passphrase, allowing for Shure Designer configuration software to securely configure the device within a location.
  • Passphrase length must be at least 8 characters up to a maximum of 64, all characters allowed
  • The passphrase may be disabled after the first login
  • Downgrade caution:
    • After the 4.1.37 upgrade, the device’s new passphrase (and/or its audio encryption passphrase) might exceed the allowed length of its prior firmware version. In that case, downgrading requires the following procedure to ensure passphrase compatibility:
      • Prior to downgrading, log in and disable the passphrase(s) or the change the passphrase(s) to the character length allowed by the prior firmware to be downgraded to.
      • Perform the firmware downgrade. Enable passphrase(s) as desired.
  • Using Designer software:
• When multiple devices at different firmware levels are put into a location using Shure Designer software, the location passphrase for those devices must abide by the length and character set limitations of the older firmware. Advice: Update all devices in the location to the latest firmware in order to use a more robust passphrase.

Known Issue

• Shure Audio Encryption is not backwards compatible; all devices must be on version 4.1 firmware to use this feature

Bug Fixes

• Bug fixes

Notes

• User Guide
• Command Strings
• To operate P300-IMX version 4.1.11 with Dante Controller, reference the following minimum versions: v3.10.2.4 (Windows) and v3.10.2.3 (macOS)
• To operate P300-IMX version 4.1.11 with other Shure networked systems, reference the following list of minimum versions supported:
  • Shure Designer 4.1
  • Shure SystemOn 3.2
  • ANI22 4.1.39
  • ANIUSB-MATRIX 4.1.39
  • ANI4IN 4.1.39
  • ANI4OUT 4.1.39
  • MXA310 4.1.37
  • MXA910 4.1.41
  • Microflex Wireless 8.0.3
  • Shure Update Utility 2.4.6
  • Shure Web Device Discovery 1.2.5