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: When connected to a busy network with 30+ cores and 50+ peripherals, the amplifier status may show "Compromised—High CPU Usage: 100%." This problem is not observed on small, isolated networks. 

Workaround: None at this time. This will be resolved in a future release.

Earliest Reported Version: 9.10.2 and 9.4.6 LTS Branch. 

Version Fixed: 9.4.7. For more information, see the What's New section in Q-SYS Help for v9.4. This has not yet been resolved for the mainline release.

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: 9.10.0 and 9.4.8 LTS. For more information, see the What's New section in Q-SYS Help for v9.10.0 and the What's New section in Q-SYS Help for v9.4.x. 

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 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: 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: 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: 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: 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: 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: 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: 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: 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 issues has been resolved in v9.4.7 (LTS). For more information, see the What's New section in Q-SYS Help for v9.4. It has not yet been resolved in the mainline version.

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: 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: In a redundant Core configuration, after upgrading the Core firmware, the Reflect > 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.