Known Issues | Q-SYS Designer Software v9.5.0

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

Updated at May 24th, 2024

Audio Peripherals and Components

QIO does not function in Layer 3 systems

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

 
 

QIO Error, "Grandmaster mismatch error"

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

 
 

QIO "Packet Missing Streaming Errors"

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

 
 

Non-Redundant Dante Transmitter Not Discoverable in Redundant CDN64 Receiver

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.

 
 

Status control pin in NL Series Loudspeaker Output component

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.

 
 
 
 

Loudspeakers

Error updating AD-P.SUB" when changing loudspeaker model"

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

 
 

Loudspeaker blocks disappear when grouped

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.

 
 

Generic 70/100V Speaker: Custom Voicing name not updating

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. This does not affect the LTS (9.4.x) branch.

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.

 
 
 
 

Video Peripherals and Components

NV-32-H (Core Capable): Fault error, "event_base_manager blocked"

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.

 
 

NV-32-H: Temporary flicker when reconnecting a display to a Decoder with dual outputs

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. This does not affect the LTS (9.4.x) branch.

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

 
 

NV-32-H: Multicast Shift AV intermittent Packet Loss on LAN A when switching AV streams

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.

 
 

NV-32-H: HDMI output stops working after switching HDMI I/O Device Type: Encoder to/from Decoder 

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.

 
 
 
 

Control Peripherals and Components

UCI Toolbox

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.

 
 

UCI viewer on iOS App 3.6 not connecting to the core

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.

 
 

UCI Viewer or MTR app quits when switching cameras in Mediacast Router

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. This does not affect the LTS (9.4.x) branch.

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

 
 

MTR Component "Hide" and "Show" buttons not working

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.

 
 

MTR not communicating through a proxy

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.

 
 

Pinpad component does not have Help information

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

 
 

Block Controller blocks disappear after save or upgrade

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.

 
 

Moving UCI Layer up/down may cause the CSS style to disappear

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.

 
 
 
 

Platform

Delay Matrix Mixer high compute usage

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.

 
 

Moving grouped items forces aligned signal lines to move

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.

 
 

Error: “Failed to get firmware value for key firmware_hash”

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.

 
 
 
 

Management

Enterprise Manager Redundant Core shows Inventory as "Unavailable"

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.

 
 

Enterprise Manager '+ Add Core' button disabled on Sites > Systems page

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.