Known Issues | Q-SYS Designer Software v.9.12.0
Learn about the known issues associated with Q-SYS Designer Software version 9.12.0.
Warning
An update to Q-SYS Designer Software can result in “Missing” peripherals and/or Q-LAN streaming faults in systems based on the Core 5200, 6000, 3100, and 1100. This issue does not appear in systems based on any other Q-SYS Core model.
At this time, we do not recommend updating any system to v9.12.0 using these Cores. This will be resolved in a maintenance release currently undergoing validation.
Audio Peripherals and Components
FLEX4A amplifier not initializing correctly
Issue: The FLEX4A amplifier may not initialize correctly with 9.12.x. When the initialization fails, the output is corrupted and the behavior is nondeterministic.
Workaround: Power cycle the unit if the amplifier output is corrupted.
Earliest Reported Version: 9.12.0. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Softphone not responding to 407 requests after a BYE message
Issue: Symptoms experienced will show that when a call is made from the Core and a hangup is made from the Core, the call will not disconnect. If the call is disconnected from the far end then it will disconnect properly. Sending a BYE message results in the system sending a 407 request, which the Softphone does not respond to.
Workaround: Hanging up from the Softphone or far end caller works, but not from the Core.
Earliest Reported Version: 9.9.0. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Video Peripherals and Components
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: This issue is under investigation.
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.
(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.
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.
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.
NV-21-HU
Note
Since the NV-21-HU requires QDS version 9.8.0 or higher, none of the following issues impact any of the LTS branches.
NV-21-HU Frame Misalignment
Issue: When connecting an HDMI source to the NV-21-HU HDMI input, the frame may become misaligned. This issue occurs with both hot-plugging the video source and normal AC power cycling.
Workaround: Hot-plug the source until frame alignment is correct
Earliest Reported Version: 9.12.0.
Version Fixed: This issue is under investigation.
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.8.2.
Version Fixed: This issue is under investigation.
USB-C Audio Requires USB Soundcard
Issue: When a Generic AV Source is connected to the NV-21-HU’s USB-C input, the Audio Channels are set to zero and grayed out. The USB-C input does not support audio via the DisplayPort alt-mode path.
Workaround: To enable audio via USB-C, a USB Soundcard must be added to the design. This requires activation of a Q-SYS AV Bridging License. For more information on the workaround, visit Routing Audio Using USB Audio Bridging or see example design below.
Earliest Reported Version: 9.8.1
Version Fixed: This issue is under investigation.
USB Bridging
Intermittent Mediacast video freezing during camera switching
Issue: The Mediacast video feed freezes randomly when switching cameras using the gooseneck audio input. The video output shows as offline in Zoom, although the cameras appear functional in Configurator.
Workaround: Reboot the core to restore functionality.
Earliest Reported Version: 9.10.0. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Intermittent camera switching issues in Dividable Room System
Issue: You may experience inconsistent camera switching behavior when alternating between ‘Divide’ and ‘Combine’ room states on the UCI of an MTR. The issue manifests as black squares instead of camera feeds, delayed image updates, or incorrect camera feeds being displayed despite different selections.
Workaround: A temporary fix is to use a single camera preview on a common layer accessible by both ‘Divide’ and ‘Combine’ states, which seems to resolve the issue. Additionally, ensuring that the Mediacast Router component does not display actual images of the attached cameras on its buttons may help.
Earliest Reported Version: 9.10.1. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Cameras
Peak Frame Bitrate control synchronization
Issue: The Peak Frame Bitrate Control does not stay in sync between the USB Video Bridge and the selected camera. When the Peak Frame Bitrate control is manipulated in either the bridge or the camera component, the corresponding control in the other component does not change as expected. This issue has been observed with a 100% frequency on build 9.12. The workaround is to adjust the Peak Frame bitrate at each camera control instead of on the bridge.
Workaround: Adjust the Peak Frame bitrate at each camera control instead of on the bridge.
Earliest Reported Version: 9.12.0. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Control Peripherals and Components
Lua comments and strings are blue in the legacy editor
Issue: In the legacy editor (File->Preferences->General->Script Editor->”Legacy”), Lua comments appear in the same blue color as keywords like if, then, else, local, and do. This makes the comments harder to read, although it doesn't affect functionality.
Workaround: Use the VSCode editor.
Earliest Reported Version: 9.12.0. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Network.Interface call not showing all interfaces when in Emulation Mode
Issue: The script is failing to consistently detect and list all network interfaces.
Workaround: None. This will be resolved in an upcoming release.
Earliest Reported Version: 9.7.0. This does not affect the LTS (9.4.x) branch.
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.
Q-SYS Control for MTR App
Issue: The 2nd page experience is incorrectly shown on the UCI when joining a Zoom call.
Workaround: None. This will be resolved in an upcoming release.
Earliest Reported Version: 9.10.0 and 9.4.6 LTS.
Version Fixed: This issue is under investigation.
Microsoft Teams Room: Loses connection if the device is accessed by hostname and its IP changes
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. This does not affect the LTS (9.4.x) branch.
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 under investigation.
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
HID Component issue with HID keyboard or HID Media component blocks
Issue: The HID component stops working with the G7500 when HID Keyboard or HID Media blocks are included in the design.
Workaround: To resolve this, remove the HID Keyboard and HID Media blocks from your design.
Version Introduced: 9.10.0. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Audio Loss on reboot with I/O 8-Flex
Issue: After rebooting the PC connected via USB cable to an I/O 8-Flex, audio may not be detected, resulting in inactive LEDs despite the connection showing as “Connected.” Cores with USB Bridging capabilities may experience the same issue.
Workaround: Disconnect and reconnect the USB cable from the laptop to restore audio functionality.
Earliest Reported Version: 9.8.2. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Management
Old and new device name showing in Q-SYS Configurator
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. This does not affect the LTS (9.4.x) branch.
Version Fixed: This issue is under investigation.
Reflect Redundant Core shows Inventory as "Unavailable"
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.
Reflect '+ 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.