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: Designs using QIO components in Layer 3 systems forces the QIO to lock up in Peripheral Manager after a few minutes. 

Workaround: Power cycling will make the QIO component responsive again.

Earliest Reported Version: 9.4.0

Version Fixed: 9.4.5, 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8 or Q-SYS Help for v9.4. 

Issue: When wiring the input for QIO, error "grandmaster mismatch error" or "packet missing" error may appear.

Workaround: This issue has been resolved in Q-SYS Designer 9.6.0.4.

Earliest Reported Version: 9.4.0

Version Fixed: 9.7.0 and 9.4.5 LTS. For more information, see the What's New section in Q-SYS Help for v9.7 and the Q-SYS Help for v9.4. 

Issue:  When choosing to Save to Core & Run a design that has an NL-SB42, an error may return that says "Save to Core & Run failed. Internal fault (exception)".

Workaround: Open the design in a newer version of Q-SYS Designer, remove the NL-SB42 control component, and then re-add it to the design. 

Earliest Reported Version: 9.6.0. This does not affect the LTS Branch.

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. 

Issue: On networks with heavy traffic, it is possible to see a "Packet Missing Streaming Error" and distorted audio from QIO input devices.

Workaround: None. This issue will be fixed in the next mainline and LTS release.

Earliest Reported Version: 9.5.0

Version Fixed: 9.7 and 9.4.5 LTS. For more information, see the What's New section in Q-SYS Help for v9.7 or Q-SYS Help for v9.4. 

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: If you attempt to update a loudspeaker component's Model property to AD-P.SUB while the component is in the schematic, an error window appears, and the loudspeaker model does not actually change. If you attempt to open the loudspeaker's control panel, Designer closes unexpectedly

Workaround: Either add an AD-P.SUB directly from the Inventory, or update an existing loudspeaker's Model property to AD-P.SUB before dragging the component into the schematic.

Earliest Reported Version: 9.4.0, and affects all versions in the LTS branch.

Version Fixed: 9.8.0 and 9.4.6. For more information, see the What's New section in Q-SYS Help for v9.8 and the What's New section in Q-SYS Help for v9.4. 

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: 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: If you are bridging USB audio and video in conferencing software on a Mac from an NV-32-H Encoder, after successive calls, bridged audio and video may eventually stop. Removing and reconnecting the USB cable between the Mac host and NV-32-H does not resolve the issue.

Workaround: Reboot the NV-32-H.

Earliest Reported Version: 9.6.0 and 9.4.4 LTS.

Version Fixed: 9.7.0 and 9.4.5 LTS. For more information, see the What's New section in Q-SYS Help for v9.7 and the What's New section in Q-SYS Help for v9.4. 

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

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: 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: 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: 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: After changing a Target Agent IP in QDS, swapping between two identical Agents that are polling with the same SNMP OID address my stop polling.

Workaround: Restarting the script will fix this.

Earliest Reported Version: 9.6.0 and 9.4.3 LTS.

Version Fixed: 9.8 and 9.4.6. For more information, see the What's New section in Q-SYS Help for v9.8 and the What's New section in Q-SYS Help for v9.4. 

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: If the Q-SYS Core processor and Microsoft Teams Room compute are connected to the network via a proxy service, the MTR compute might not provide feedback to the Core (i.e., one-way communication only) or connect with Teams, depending on whether the proxy is turned on or off.

Workaround: If on the LTS branch, upgrade to version 9.4.4. In 9.4.4, MTR now works properly if a network proxy service is configured (and the proxy service has been configured to allow proxy bypass). This fix is also scheduled for the next mainline release.

Earliest Reported Version: 9.4.0.

Version Fixed: 9.4.4 LTS and 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.4 and the What's New section in Q-SYS Help for v9.7.

Issue: The HID Keyboard component is not working with Google Meet hardware.

Workaround: If on the LTS branch, upgrade to version 9.4.4. In version 9.4.4, HID Keyboard component functionality has been restored when using Q-SYS Core processors and peripherals with Google Meet hardware. The fix is also scheduled for the next mainline release.

Earliest Reported Version: 9.6.0 and 9.4.3 LTS. 

Version Fixed: 9.7.0 and 9.4.4 LTS. For more information, see the What's New section in Q-SYS Help for v9.7 and the What's New section in Q-SYS Help for v9.4. 

Issue: If a TSC-G2 Series touch screen is connected to certain network switches, the device might reboot or the UCI might reload unexpectedly.

Workaround: If on the LTS branch, upgrade to version 9.4.4. In version 9.4.4, TSC-G2 Series touch screens properly auto-negotiate to 100 Mbps regardless of the connected network switch model, resulting in a stable connection. The fix is also scheduled for the next mainline release.

Earliest Reported Version: 9.6.0 and 9.4.3 LTS.

Version Fixed: 9.7.0 and 9.4.4 LTS. For more information, see the What's New section in Q-SYS Help for v9.7 and the What's New section in Q-SYS Help for v9.4. 

Issue: If you attempt to change the Script Access property for multiple components simultaneously, Q-SYS Designer Software (QDS) can quit unexpectedly.

Workaround: Update the Script Access property for a single component at a time.

Earliest Reported Version: 9.6.0. This did not affect the LTS Branch.

Version Fixed: 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.7. 

Issue: In the SNMP Query component, the Read Value for a queried OID is truncated at 100 characters.

Workaround: None. This is a current limitation that is planned to be addressed in a future release.

Earliest Reported Version: 9.4.4 LTS and 9.6.0.

Version Fixed: 9.8.0 and 9.4.6 LTS. For more information, see the What's New section in Q-SYS Help for v9.8 and the What's New section in Q-SYS Help for v9.4. 

Issue: The Pinpad component in the Control Components category was introduced in QDS 9.5; however, it does not have a Help topic.

Workaround: None. Pinpad was intended for internal review/testing and has no supported use case at this time. Pinpad will be removed from upcoming QDS releases.

Earliest Reported Version: 9.5.0. This did not affect the LTS Branch. 

Version Fixed: 9.8.0. For more information, see the What's New section in Q-SYS Help for v9.8. 

Issue: In some cases, making changes to blocks in Block Controller and then saving and re-opening Block Controller results in blocks disappearing. This can also occur after upgrading a design to a new version.

Workaround: None. Though the blocks are not visible, they still function and the design still runs. This will be fixed in an upcoming release.

Earliest Reported Version: 9.3.1.

Version Fixed: 9.4.4 LTS and 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.4 and the What's New section in Q-SYS Help for v9.7.

Issue: If a script within a design contains SNMP requests, memory usage continues to rise, which can eventually cause a Core to become unresponsive.

Workaround: Increasing script memory usage can be detected in Inspector > Scripts. Until this is fixed in a future release, set the script to stop and restart periodically to flush the memory usage.

Earliest Reported Version: 9.4.4 LTS and 9.6.0.

Version Fixed: 9.4.5 LTS and 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.4 and the What's New section in Q-SYS Help for v9.7.

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: 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 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: In designs using Virtual Page Stations, the PA router will play all the input sources when the Virtual Page station is playing a message.

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

Earliest Reported Version: 9.6.0 and 9.4.5 LTS

Version Fixed: 9.8.0 and 9.4.6 LTS. For more information, see the What's New section in Q-SYS Help for v9.8 and the What's New section in Q-SYS Help for v9.4. 

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: If a Q-SYS Core processor's LAN A and LAN B interfaces are both connected to networks, it is possible for UCIs to not be discovered in the Q-SYS Control iOS app.

Workaround: Until this is fixed in a future release, try one of these known workarounds:

• Disconnect one of the LAN connections from the Core
• Swap the LAN A / LAN B connections
• Change the Gateway on LAN A

Earliest Reported Version: 9.4.4 LTS & 9.6.0.

Version Fixed: 9.4.5 LTS & 9.7.0. For more information, see the What's New section in Q-SYS Help for v9.4 and the What's New section in Q-SYS Help for v9.7.

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 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.