Issue: QIO, NL, and NM Series devices show green in Configurator but display the error “LAN A Connection Failure” on the status of the devices and the inventory in QDS.

Workaround: Reboot the Core to fix the issue. 

Earliest Reported Version: 9.10.0

Version Fixed: This issue is under investigation.

Issue: After a network failure, or if the network cable is unplugged from the primary active core, the QIO box goes missing and does not recover. 

Workaround: Rebooting the backup Core allows all devices to reconnect. 

Earliest Reported Version: 9.4.5. This issue only affects the LTS Branch.

Version Fixed: This issue is under investigation.

Issue: A hostname that ends with a hyphen (-) is invalid. If the hostname is longer than 32 characters, truncation will occur which can result in the hostname ending in a hyphen. 

Workaround: None. 

Earliest Reported Version: 9.6 and 9.4.3 LTS Branch

Version Fixed: This issue is under investigation.

Issue: Audio coming out of Channel Groups connected to any Peripheral may not be heard.

Workaround: Insert a Gain (or other DSP) component between the Channel Group and the Peripheral output.

Earliest Reported Version: 9.7.0

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: CDN64 in redundant mode with separate primary and secondary networks may force the Non-Redundant device streams to be not discoverable

Workaround: Disconnect the CDN64 secondary device, connect the stream, and restore the secondary connection. Connection should be "sticky" after that

Earliest Reported Version: 9.5.0

Version Fixed: 9.8. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: The Loudspeaker Output component for NL Series loudspeakers inadvertently includes a Status control pin that provides unusable Boolean output.

Workaround: Do not use the Status control pin. It will be removed in a future release.

Earliest Reported Version: 9.4.0

Version Fixed: 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.7. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: High Pass and Low Pass filters in a custom voicing block may display as not bypassed, although they are bypassed. This behavior also occurs when transferring between primary and backup cores.

Workaround: Toggling the bypass button off and on resolves the issue temporarily. However, reloading the design causes all filters to be bypassed again, yet they still show as not bypassed. 

Earliest Reported Version: 9.9.0 and 9.4.5 LTS Branch. 

Version Fixed: This issue is under investigation.

Issue: When transitioning designs from any DPA amplifier to any CX-Q amplifier using Properties, the second channel becomes inaccessible, leading to unconfigurable E-H settings.

Workaround: Add CX-Q amplifier directly instead of changing the model through Properties. This will be resolved in a future release.

Earliest Reported Version: 9.9.0 and 9.4.5 LTS Branch. 

Version Fixed: This issue is under investigation.

Issue: If you attempt to group components (Tools > Group) that include Loudspeaker blocks, the Loudspeaker blocks disappear.

Workaround: None.

Earliest Reported Version: 9.4.0

Version Fixed: 9.9.0. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue:  If you change the name of a Custom Voicing that is currently mapped to a 70/100V Speaker, the name does not update in the 70/100V Speaker component.

Workaround: Within the 70/100V Speaker component properties, change the Custom Voicing property to "NONE," and then select the updated name.

Earliest Reported Version: 8.2.1

Version Fixed: 9.9.0. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: HID Conferencing Controller may cause USB Bridging to stop functioning. The NV-32-H Encoder must have USB Video Bridging, USB Audio Speakerphone Bridging, USB HID Conferencing, and HDMI Encoder to another NV-32-H Encoder active in the design.

Workaround: Remove HID Conferencing.

Earliest Reported Version: 9.8.2 and 9.4.5 LTS.

Version Fixed:  This issue is under investigation.

Issue: An issue has been identified with the TSC-101-G3 panels. If a button (sized 200,80) is placed low on the page (at position 10,1094, for example), the button becomes insensitive to a press touch.

Workaround: Raise the button up by approximately 20 pixels to ensure proper press recognition.

Earliest Reported Version: 9.5.0 and 9.4.3 LTS branch

Version Fixed: This issue is under investigation.

Issue: NC-110 fails to save the 802.1x configuration. Error: “802.1x settings save failed for LAN A.”

Workaround: Change the certificate format to PEM.

Earliest Reported Version: 9.7.0 and 9.4.4 LTS. 

Version Fixed: This issue is under investigation.

Issue: Netgear 26G4F M4250 drops packets when Shift AV and USB Video Bridge are both active on an NV decoder.

Workaround: Increase NC camera bitrate to 16 Mbps or higher, decrease Shift AV bitrate to 600Mbps

Earliest Reported Version: 9.6.0 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: NV-32-H and NV-21-HU shows green video on initial encoder start up. The green video will disappear after 5 seconds.

Workaround: None. This will be fixed in an upcoming release.

Earliest Reported Version: 9.8.1 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: NV-32-H cannot receive valid 4k60 video with Intel Iris Xe Graphics.

Workaround: None. This will be fixed in an upcoming release. 

Earliest Reported Version: 9.8.1 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: A design that includes AEC and NV-32-H, the Core will no longer receive embedded audio over HDMI.

Workaround: Reverting to 9.6 or removing AEC component fixes this issue. 

Earliest Reported Version: 9.7.0 and 9.4.5 LTS

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: When in idle or sleep mode, the Video Mute and Video Freeze buttons are enabled rather than disabled. 

Workaround: None. This will be resolved in an upcoming release.

Earliest Reported Version: 9.8.0 and 9.4.5 LTS. 

Version Fixed: 9.9.0. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: If you select the 21x9 EDID in the Generic AV Source component for an HDMI source that does not support 21x9, video output from an NV Encoder or Decoder may flicker or not display at all.

Workaround: Use the 21x9 EDID only for sources that support 21x9 resolutions.

Earliest Reported Version: 9.7.0 and 9.4.5 LTS.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: When CEC is enabled in a Generic HDMI Display component connected to an NV-32-H (Core Capable) Encoder or Decoder with heavy Shift AV processing (for example, simultaneous encoding of three 1080p60 streams), two issues are known to occur:

• CEC On/Off power toggles do not work reliably with certain displays.
• The Display Power Status LED may occasionally indicate as false when the display is actually on with certain displays

Workaround: Deactivate Shift AV streaming by switching all outputs to local HDMI or Graphic before initiating a CEC On/Off command. There is no workaround for the Display Power Status LED. This issue will be fixed in an upcoming release.

Earliest Reported Version: 9.6.0 and 9.4.4 LTS. 

Version Fixed: 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.7. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: When HDMI output is connected between NV-32-H HDMI and a 21:9 monitor, video distortions may occur when boot screen is active.

Workaround: None. This issue will be resolved in a future release.

Earliest Reported Version: 9.8.0 and 9.4.5 LTS.

Version Fixed: 9.9.0. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: Under certain circumstances, the Event Log for an NV-32-H (Core Capable) design might indicate "event_base_manager blocked", followed by the Core becoming unresponsive after a period of time.

Workaround: Reboot the NV-32-H (Core Capable).

Earliest Reported Version: 9.3.1, which affects all versions of the LTS Branch.

Version Fixed: This issue is under investigation.

Issue: If an NV-32-H is configured as a Decoder with dual HDMI outputs, disconnecting and reconnecting one display can cause a temporary flicker, black screen, or other color change on the other connected display. This typically only lasts for about one second.

Workaround: In the Generic HDMI Display component > Color Format control, select a "Force RGB" format.

Earliest Reported Version: 9.5.0 and 9.4.3 LTS.

Version Fixed: This issue is under investigation.

Issue: The NV-32-H Shift AV may experience occasional audio packet loss in LAN A when switching between AV streams. This might cause intermittent disruptions in the audio transmission.

Workaround: None. This will be resolved in an upcoming release.

Earliest Reported Version: 9.1, which affects all versions in the LTS branch.

Version Fixed: This issue is under investigation.

Issue: If you change the HDMI I/O component Device Type property from Encoder to Decoder or vice versa and then redeploy the design, HDMI output may stop working.

Workaround: In rare cases, the affected NV-32-H unit may require a power cycle after changing Encoder / Decoder modes. Unplug the NV-32-H from power for a few seconds and then plug it back in.

Earliest Reported Version: 8.2, which includes all versions of the LTS Branch.

Version Fixed: This issue is under investigation.

Issue: When the USB Video Bridge component is deleted from the design, it may not auto-populate in the inventory. 

Workaround: Disabling and re-enabling USB Video Bridge in the Core Properties pan will populate the component back into the inventory.

Earliest Reported Version: 9.7.0 and 9.4.4 LTS Branch.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: The buttons on Auto Focus in USB Video Bridging are interactive; however since they are not supported on the NC-110, they do not function

Workaround: None. This issue will be resolved in an upcoming release.

Earliest Reported Version: 9.7.0 and 9.4.4 LTS Branch.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: USB Video Bridges may stop bridging video after a period of time. In this condition, the USB connection status in the USB Video Bridge component will show as disconnected.

Workaround: A reboot of the peripheral or Core (or both, if applicable) should resolve the issue.

Earliest Reported Version: 9.6.0 and 9.4.3 LTS Branch.

Version Fixed: 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.7. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: Some controls within a State Trigger Button and/or ComboBox within a UCI Toolbox cannot be activated when accessing the UCI from a physical TSC, Windows UCIViewer Application, or a mobile device (Android and iPhone accessing WebUCI).

Workaround: Utilize traditional, non-Toolbox methods for State Trigger Button and ComboBox objects.

Earliest Reported Version: 9.5.0 and 9.4.3 LTS.

Version Fixed:  WebUCI was fixed in 9.10; however UCIViewer and TSC's are still under investigation.

Issue: The Core may experience a disruption in operation after the AVer plugin runs for 30 minutes to 1 hour.

Workaround: Ensure the latest version of the Plugin is installed. This issue is under investigation.

Earliest Reported Version: 9.7.0 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: Following an update to Windows 11, users may encounter an issue where accessing the "Room Controls" UCI on the touch panel results in a black screen and unresponsive controls.

Workaround: This problem can be temporarily resolved by following MTR 2nd page Troubleshooting.

Earliest Reported Version: 9.9.0 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: When a Camera is added to a design, moving it into a Container from another part of a design returns it to the Inventory. If it is placed directly into a Container and removed from the Container, it also returns to the Inventory.

Workaround: Either place the Camera directly into the Inventory or place the Camera Status Block where you want it in the design.

Earliest Reported Version: 9.9.0 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: When the MTR component is configured to connect via hostname, and the MTR compute is scheduled for automatic ,nightly reboots, it is possible that the underlying IP address may change with a new assignment from the DHCP server over extended durations. If the IP address changes does change, the MTR component will lose connectivity to the MTR compute and enter a fault state.

Workaround: A reboot is required to pick up the correct address. This will be resolved in a future release.

Earliest Reported Version: 9.9.0 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: For users running the app on iOS version 14.0+, the app may no longer discover Cores on the network. This is due to changes in multicast support at the iOS level.

Workaround: As a workaround, configure Hard Link IP Addresses in the Q-SYS Control App (iOS) to communicate with the desired Cores. A fix is being investigated.

Earliest Reported Version: iOS version 14+

Version Fixed: This issue is under investigation.

Issue: Connecting to a WebSocket server via name may block scripts from running during the connection phase. 

Workaround: Connecting to a WebSocket server via IP address can work. This may not be possible with some cloud services, however. 

Earliest Reported Version: 9.9.0 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: With UCI’s that share the same CSS all change visual style when a single UCI changes style dynamically.

Workaround: Having multiple CSS copies for every UCI will prevent this from occurring. 

Earliest Reported Version: 9.8.0 and 9.4.4 LTS. 

Version Fixed: 9.9. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: When using the UCI Viewer, it is possible on some devices to see a message that shows the core has been "disconnected." 

Workaround: None. This will be fixed in a future iOS app update. 

Earliest Reported Version: 9.6.0.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: If you switch cameras frequently in Mediacast Router, the UCI Viewer or Q-SYS Control for MTR app might become unstable and quit unexpectedly if connected to a Core via LAN B or AUX LAN.

Workaround: Use the Core's LAN A interface instead. This will be fixed in an upcoming release.

Earliest Reported Version: 9.5.

Version Fixed: 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.7. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: Custom Font Styles are not applied properly for the Controls & Tools via UCI Style Controller.

Workaround: Specify different font-family names for your imported @font-faces.

Earliest Reported Version: 9.8.2 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: An issue has been identified in larger, more complex designs, that may involve matrix IO control utilizing Trigger State buttons.  Left mouse click is not effective in making IO selection.  Specifically, selection can be made by subtle manipulation, up or down, of the mouse wheel.

Workaround: None. This fix is scheduled for an upcoming release of Q-SYS Design Software.

Earliest Reported Version: 9.6.0 and 9.4.3 LTS.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: The “show” and “hide” button swap the MTR's touch panel between showing the MTR UCI and the QSC UCI; however, it may appear it is nonfunctional if the correct versions are not installed.

Workaround: Q-SYS Designer Must be at least v9.5 and the “QSYS Control for MTR” application installed on the compute PC MUST be at least v9.5.

Earliest Reported Version: 9.4.0

Version Fixed: 9.9.0. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: If a design schematic contains a Call Sync component and the Core Model is changed to 'vCore Control', the Call Sync component remains enabled while any wired Call Systems or Endpoints become properly disabled (grayed out).

Workaround: None. Call Sync is not supported with vCore despite not showing as disabled in designs that use vCore.

Earliest Reported Version: 9.6.0 and 9.4.4 LTS Branch. 

Version Fixed: This issue is under investigation.

Issue: When a Layer of a UCI is moved up or down in the Z-Order, the CSS style applied to the control on that layer are no longer displayed in Q-SYS Designer.

Workaround: Close the UCI and reopen the UCI to continue editing. This will be fixed in an upcoming release. 

Earliest Reported Version: 9.4.2 LTS and 9.5.0.

Version Fixed: 9.9.0. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: AES67 Rx periodically showing a fault of “Compromised - Packet Missing” or “Compromised - Packet too late” when PTP Transparency Clock (TC) is enabled on the Q-SYS NS2 Netgear switches.

Workaround: Disable PTP TC on Q-SYS NS Netgear switch. 

Earliest Reported Version: 9.6.0 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: Attempting to receive AES67 audio from a third-party Dante device results in a "Compromised - Packet Missing" error and no audio being received. The AES67 Receiver > Details tab also shows a DSCP value of 0 with increasing "missing" counts.

Workaround: There is currently no workaround in Q-SYS 9.7. This will be fixed in an upcoming release. Note that AES67 audio from other Q-SYS Core processors is unaffected.

Earliest Reported Version: 9.7.0 and 9.4.5 LTS Branch.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: If the Core name in the design (hostname) is longer than 31 characters, Software Dante audio can become unresponsive. The Software Dante hostname (Core name) will also not show in Dante Controller.

Workaround: Do not specify a Core name longer than 31 characters in the design, as per Software Dante requirements. See the Software Dante RX or Software Dante TX > Requirements section for more information.

Earliest Reported Version: 9.6.0 and 9.4.5 LTS Branch.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: In a Core-redundant configuration, after forcing a Backup Core to Active status and then forcing the Primary Core back to Active, System Link AV and audio streams do not resume as expected.

Workaround: Redeploy the design to the Primary Core. This will be fixed in an upcoming release.

Earliest Reported Version: 9.4.2 and 9.6.0.

Version Fixed: 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.7. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: The Q-SYS Media Stream Receivers in are unable to accept unicast streams from Visionary Solutions network Video Encoders. 

Workaround: For now, customers integrating Visionary Solutions Video Endpoints must use multicast. 

Earliest Reported Version: 9.9.1 and 9.4.6 LTS. 

Version Fixed: This issue is under investigation.

Issue: When using a Core running QDS 9.4.6 LTS and Encoding and Decoding a Direct TV video stream, if you subsequently change the stream in the AES67 Receiver from any other source to Direct TV, you may encounter the error message “Initializing - Not Connected.”  

Workaround: None.

Earliest Reported Version: 9.4.6 LTS. This does not affect any of the mainline releases.

Version Fixed: This issue is under investigation.

Issue: A Core with Software Dante deployed that was previously enrolled in a Dante Domain may not be discoverable in Dante Controller if the Core was not properly un-enrolled from the Domain.  

Workaround: Delete the DDM.conf and UUID files.

1.  Disconnect Windows the Core from the Design
2. Run the Design in Emulation Mode
3. Open the Windows Explorer Folder and navigate to C:\Users\qsc\AppData\Local\Temp\QSys Temp Files
4. Open the most recent hash folder (For example, C:\Users\username\AppData\Local\Temp\QSys Temp Files\638360882256976981) and open the Settings Folder
5. Delete “DDM.conf” and "UUID" files
6. Save the Design while still in Emulation Mode
7. Disconnect Emulation Mode
8. Save to the Core & Run
9. Open Dante Controller to verify that Software Dante components now show

Earliest Reported Version: 9.9.1 and 9.4.5 LTS.

Version Fixed: This issue is under investigation.

Issue: Q-SYS Designer shows an error that "Design Exceeds the Memory Capability of the Core".

Workaround: Modifying the design may work around the issue for now. This will be resolved in an upcoming release. 

Earliest Reported Version: 9.8.2 and 9.4.5 LTS. 

Version Fixed: This issue is under investigation.

Issue: In designs with 30+ QIO devices (e.g. Network Loudspeakers), working AES67 Rx components may fail to connect after redeploying design.

Workaround: Power cycle the Core and the AES67 endpoints. 

Earliest Reported Version: 9.8.2 and 9.4.5 LTS Branch.

Version Fixed: 9.9.1. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: The Save to Core & Run dialog does not display last lines when the Windows scale setting (Settings > System > Display > Scale) is set to more than 100%. 

Workaround: Reduce Windows Display Scale, ideally to 100%.

Earliest Reported Version: 9.8.1 and 9.4.5 LTS. 

Version Fixed: This issue is under investigation.

Issue: The microphone impedance value does not work correctly when a Core 110f is in Peripheral Mode, and the Flex Out block is absent in the design.

Workaround: Place Flex Out block in design even if not being used. This causes the values to behave correctly again.

Earliest Reported Version: 9.8.0 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation. 

Issue: QIO, NL, and NM Series devices may occasionally show an error "Missing - In use by another design" upon deployment.

Workaround: None. This will be resolved in an upcoming release.

Earliest Reported Version: 9.8.0 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: The Delay Matrix Mixer component compute resource usage may be higher than anticipated by the design compiler.

Workaround: If the design causes processing overruns, reduce the design size by either reducing the size of the Delay Matrix Mixer component(s), reducing the Max Delay property, removing other components from the design or any combination listed.

Earliest Reported Version: 8.0 and 9.4.5 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: When deploying a design with Advanced USB Audio, it is possible to exceed endpoint limits on Core 110f, Core 8 Flex, and Core Nano.

Workaround: None. This will be fixed in a future release.

Earliest Reported Version: 9.4.5 LTS and 9.8.0

Version Fixed: This issue is under investigation.

Issue: In a design where there are grouped items, and aligned signal lines, moving the grouped items forces the signal lines to move and become distorted.

Workaround: None. This will be fixed in a future release. 

Earliest Reported Version: 9.4.2 LTS and 9.5.0

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: The hover-over Windows taskbar preview icon for Q-SYS Designer Software (QDS) is not displaying a green dot to indicate that a design has an active connection to a Core.

Workaround: None. This will be fixed in a future release.

Earliest Reported Version: 9.7.0 and 9.4.5 LTS Branch.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: When attempting to downgrade a Core to a version prior to v9.1.x, you see the aforementioned error message.

Workaround: This error means that the Core is expecting signed firmware (introduced in v9.1.x) but the firmware you are attempting to upload (v9.0.1 or earlier) is unsigned. To downgrade the Core, you must toggle the Allow Legacy Unsigned Firmware (v9.0.1 or lower) option in Core Manager:

1. Log in to Q-SYS Core Manager.
2. From the navigation menu, click Utilities.
3. In the Firmware section, select Allow Legacy Unsigned Firmware (v9.0.1 or lower). Do not reboot the Core.
4. Attempt the downgrade again.

Earliest Reported Version: 9.1.x, which does affect the LTS Branch.

Version Fixed: This issue is under investigation.

Issue: When Designer is signed into Reflect and you make changes in Administrator, sometimes the changes are not saved. You may be able to  make the changes but after hitting ‘Update’ the changes are reverted and not saved properly.

Workaround: Make changes when locally connected to core instead of via QREM if this issue is encountered. This will be resolved in an upcoming release.

Earliest Reported Version: 9.8.2 and LTS Branch.

Version Fixed: 9.9.1. For more information, see the What's New section in Q-SYS Help for v9.9. This has not yet been resolved in the (9.4.x) LTS branch.

Issue: If you rename a Q-SYS device, both the original and new name can sometimes appear in Configurator.

Workaround: Close and re-open Q-SYS Designer Software. This will be fixed in a future release.

Earliest Reported Version: 9.7 and 9.4.4 LTS Branch.

Version Fixed: This issue is under investigation.

Issue: In a redundant Core configuration, after upgrading the Core firmware, the Enterprise Manager > Sites > Systems > Status page may show "Unavailable" in the Inventory section.

Workaround: Reboot the Cores and refresh the Status page in your browser.

Earliest Reported Version: 9.3, and it affects all versions in the LTS Branch.

Version Fixed: This issue is under investigation.

Issue: When attempting to add another Core to a Site, such as when adding the second of two Cores in a redundant pair System, the + Add Core button is grayed out.

Workaround: None. Currently, the maximum number of Cores that can be registered to your Organization equals the number of System licenses enabled on the Organization, regardless of whether a System is redundant. This will be fixed in a future update. Note that the Subscription Details table on the Organizations page correctly shows the number of connected Systems and does not represent the number of connected Cores when using any Redundant Core systems.

Earliest Reported Version: 9.3, and it affects all versions of the LTS Branch. 

Version Fixed: This issue is under investigation.