Known Issues | Q-SYS Designer Software v.9.13.2 LTS

Learn about the known issues associated with Q-SYS Designer Software version 9.13.2

Updated at August 13th, 2026

Video Peripherals and Components

NV-32-H: Does not receive 4K60 video with Intel Iris Xe Graphics

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.

 
 

NV-32-H: Packet loss when Shift AV and USB Video Bridge are both active on an NV decoder

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: 9.13.0. For more information, visit the What's New section in Q-SYS Help for v9.13. This has not yet been resolved in the 9.4.x (LTS) branch.

 
 
 
 

Control Peripherals and Components

Lowercase UCI Variable Names Cause UCI Viewer and TSC Crashes

Issue: When a UCI variable is created using a lowercase "v" (e.g., var_1) instead of the default uppercase "V" (e.g., Var_1), it causes the Windows-based UCI Viewer and TSC to crash. The crash occurs when attempting to view the UCI via the UCI Viewer for Windows or when pushing to a Core and accessing it on a TSC.

Workaround: Ensure all UCI variable names begin with an uppercase "V" (e.g., use the default Var_1 naming convention). Do not rename UCI variables to use a lowercase "v" prefix.

Affected Version: Longstanding/legacy issue

Version Fixed: Fixed in 10.4

 
 

Custom Control generic integer knob CSS rendering issue on UCI

Issue: When using a Generic Integer Knob from a Custom Control Component on a UCI, the -qsc-render-style: layer CSS styles do not render correctly when the presentation is set to "fader" or "meter." Meters do not render the gradient defined in the CSS and instead display the fill color from the UCI Control's properties in Q-SYS Designer. Additionally, the bottom translucent layer is not rendered. Faders render the layers as expected but are fixed at the .5 position regardless of the actual control state.

Workaround: No known workaround.

Earliest Reported Version: 9.13.1, 10.0, 10.1, 10.2, 10.2.1, 10.3

Version Fixed: Fixed in 10.4

 
 

A custom font is not rendering correctly in Text Block of iOS UCI Viewer

Issue: When using the custom imported font “NeueHaasDisplayBold” for text in a Text Block on a UCI, the text does not render as expected in the iOS UCI Viewer app. Text will be cut off around the sides and will not follow the padding or vertical/horizontal alignment settings. Other fonts are unaffected.

Workaround: Use a different font.

Earliest Reported Version: iOS 3.12.1

Version Fixed: This issue is under investigation.

 
 

TSC-G2 devices are showing offline

Issue: Using the TSC-G2 touchscreen controllers with any multi-gigabit switch may show "Offline" and/or "No Link" when checking the test screen.

Workaround: Connect the touchscreen controller to another switch and downgrade to QDS version 9.10.1.

Earliest Reported Version: 9.10.2 and 9.4.7 LTS.

Version Fixed:  This issue is under investigation.

 
 

UCI Style Controller custom font styles are not applied properly for the Controls & Tools

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 fixed in 10.0

 
 

Call Sync not disabled with vCore

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.

 
 
 
 

Platform

Redundant Core pair may enter a compromised state after upgrading or downgrading between Q-SYS 9.13 and 10.x with Secure Communications enabled

Issue: When upgrading or downgrading between Q-SYS 9.13 LTS and 10.x on a redundant Core pair that has Secure Communications and Access Control enabled, both Cores may intermittently end up in a "compromised" state, meaning both act as the primary Core at the same time instead of one being active and one being on standby. This happens because the firmware change process can inadvertently disable Access Control while leaving Secure Communications on, putting the system in an inconsistent security state. When this occurs, event logs may also be cleared, and the previous firmware version may appear as "unknown."

Workaround: It is recommended that secure communication be disabled when downgrading to a release prior to the feature’s first supported release of 10.0. Contact Q-SYS Technical Support for assistance recovering the redundant Core pair.

Version Introduced: 9.13.1 LTS

Version Fixed:  This issue is under investigation.

 
 

Downgrade from Q-SYS 10.x to 9.13.2 may fail with Access Control enabled

Issue: When downgrading from any Q-SYS 10.x release (e.g., 10.4.x) directly to 9.13.2 with Access Control enabled, the downgrade may fail during peripheral firmware installation. This can leave the Q-SYS Core and connected peripherals in a non-functional state. The issue does not occur when downgrading from 10.x to 9.13.1, when upgrading firmware versions, or when downgrading to 9.13.2 with Access Control disabled.

Workaround: Use the following downgrade path when Access Control is enabled: 10.x → 9.13.1 → 9.13.2. See Downgrade Notices in Q-SYS Help for full details. If the failure has already occurred, restore the Core to 10.x. A manual device reboot may be required if the Core is unreachable.

Version Introduced: 9.13.2

Version Fixed:  This issue is under investigation.

 
 

Core loses network connectivity after connection issues with Q-SYS Reflect

Issue: On Cores registered to Q-SYS Reflect, connection issues between the Core and Reflect can cause the Core to exhaust its TCP memory over time. The Core repeatedly attempts to reconnect, and after several days, it runs out of network resources, causing peripherals to go offline and the Core to become unresponsive. This is more likely to occur after a power outage where the Core boots before the network switch initializes.

Workaround: Verify proper network switch and Core configuration.

Version Introduced: 9.13.1

Version Fixed:  To be fixed in a future release.

 
 

Preview of Color Picker in Q-SYS Designer is incorrect when the Hue value is 360

Issue: When using the Color Picker component in Q-SYS Designer, if the Hue fader is moved to the very top so that the Hue value is 360, the Color Picker preview window shows a Magenta color, when it should be a Red color. However, the correct color (#FF…) is selected, and the Color Picker is correctly rendered within UCI Viewer and TSCs.

Workaround: None.

Version Introduced: 9.4.8, 9.13.1, 10.0

Version Fixed:  This issue is fixed in 10.4

 
 

Q-SYS Designer Software runs inconsistently on displays set to high refresh rates (> 60 Hz)

Issue: Q-SYS Designer Software runs inconsistently on displays set to high refresh rates (> 60 Hz)

Workaround: Set refresh rate to 60 Hz. Disable VSync setting in PC video card.

Version Introduced: 10.0.0, 9.13, and 9.13.1 LTS

Version Fixed: This issue will be fixed in a future release.