Q-SYS 8.3.3

This topic covers release information for Q-SYS 8.3 and any maintenance releases.

For a list of known issues affecting this release, see the Known Issues page. (Online only)

Note: Version 8.3.3 replaces version 8.3.0. It was discovered that some systems settings, including Network Services and Core Users, would be lost when upgrading to 8.3.0 from earlier versions. If you previously upgraded to 8.3.0, QSC strongly recommends upgrading to 8.3.3 as it includes some important stability improvements.

Version 8.3.3 is a maintenance release of the Q-SYS platform. It includes fixes to issues affecting previous Q-SYS releases.

Resolved Known Issues

  • Audio: Q-SYS peripherals configured for network redundancy now properly fail over to LAN B if LAN A is disconnected. This fixes an issue that affected all previous 8.3 releases.

Version 8.3.2 is a maintenance release of the Q-SYS platform. It primarily includes fixes to issues affecting previous Q-SYS releases.

Resolved Known Issues

  • Audio: Deploying a design to the Q-SYS Core that contains an I/O-Frame or I/O-Frame8S no longer produces an initialization fault error.
  • Enterprise Manager: Protocol summary information now automatically refreshes on the Sites > Systems > Network Services page if you navigate between a v8.3.x Core and another Core running earlier firmware.
  • Enterprise Manager: You can now change the Core Disconnected Image on the Video Endpoints > Settings page in Enterprise Manager.

Other Updates

The USB Audio Bridge for Q-SYS Core 110f processors and NV-32-H video endpoints includes a new 'Zoom Compatibility' property to allow for controlling Zoom using the HID Conferencing [BETA] component. (This update addresses prior mute sync issues on macOS devices.)

See USB Audio Bridge and HID Conferencing [BETA] for more information.

Learn more about Zoom Rooms and Q-SYS integration in the ProAV All Hands Space.

Newer DPA-Q and DPA-Qn Cinema Network Amplifiers are now available in the standard, non-Cinema version of Q-SYS Designer software.

See New DPA-Q Series.

Version 8.3.1 includes these new features, updates, and resolved issues.

Audio

The Q-SYS Ecosystem now provides software-based Dante™ network audio integration without the need for additional hardware. The capabilities of software-based Dante are similar to the CDN64 Dante Audio Bridge Card, except that the sample rate is fixed at 48 kHz. In the 8.3 release, software-based Dante is supported by the Q-SYS Core 110f processor.

Components

Two new Inventory items are now available from the Streaming I/O category:

  • The Software Dante TX component transmits audio from supported Q-SYS Core models to Dante-enabled devices on the network.
  • The Software Dante RX component receives audio streams from Dante-enabled devices on the network.

Licensing

The Software Dante components are licensed elements that require a Q-SYS Feature License when included in a design deployed to a Q-SYS Core 110f processor. Core 110f processors manufactured with Q-SYS 8.3 include an 8x8 license, with 16x16 and 32x32 licenses available for purchase. All Software Dante licenses are available for purchase for older Core 110f processors. To learn more, see the Licensing topic in the Q-SYS Core Manager help.

Networking Requirements

Before integrating software-based Dante into your design, review the Dante networking requirements. See the Other Networked Audio topic in the Q-SYS Networking section.

FAQs

To learn more about Software-based Dante for the Q-SYS Ecosystem, and to see a list of FAQs, refer to the product page on the QSC website.

The new AD-P.HALO loudspeaker is now available from the Inventory menu under the AcousticDesign - Pendant Mount category.

For information about this loudspeaker, including specifications, see the AD-P.HALO product page on the QSC website.

The Timeline (Beta) component now accepts timecode directly from the SMPTE LTC Generator component. You can enable this ability via the new Time Source property.

To learn more, see Timeline (BETA).

  • Output from the SMPTE LTC Generator component can now be input directly to the Timeline (BETA) component.
  • Generator Frame Rate (fps) is now a run-time parameter, configurable in the component control panel instead of Properties. This allows for using Snapshots or external control automation to switch the frame rate while a design is running.
  • SMPTE LTC Reader now automatically detects and displays the incoming Frame Rate (fps) in the component control panel.
  • When you give a PA zone a custom name in Q-SYS Administrator, that name is now visible in the PA Router component. For more information, see the PA Zones (Administrator) and PA Router topics.
  • In addition to zone numbers, zone name strings can now be specified when making calls to the PA Remote API. For more information, see Q-SYS PA Remote API (PARAPI).

The WideLine-8 loudspeaker component includes a new Legacy Voicing property:

  • Select 'No' to use the newer voicing that offers improved balance. This is the default in Q-SYS version 8.3 and later for new WideLine-8 loudspeaker components.
  • Select 'Yes' to use the older voicing profile. This is the default for designs with existing WideLine-8 components that have been upgraded to version 8.3 and later. For existing components, you can optionally switch to the newer voicing.

Designs containing the legacy Acoustic Echo Canceler (AEC) component now display a warning when loading from or saving to the Q-SYS Core. To ensure ongoing support, users are encouraged to update their designs to use the new AEC component.

For the Q-SYS Core 110f and 110c only:

  • Each Q-LAN Transmitter or Receiver with network redundancy enabled now consumes two streams instead of one.
  • Each Q-SYS peripheral with network redundancy enabled also consumes two Q-LAN streams instead of one.

Use File > Check Design to see your design's Network Audio counts.

Video

  • In addition to the existing support for RGB 4:4:4, NV-32-H Network Video Endpoints now support HDMI video sources that output YCbCr 4:4:4 and YCbCr 4:2:2 color. (YCbCr 4:2:0 is not supported.)
  • The Generic HDMI Source component now has a new Color Format control that indicates the detected color format – RGB or YCbCr – along with parameters for pixel component quantization (RGB and YCbCr) and the supported color sub-sampling mode and color space (YCbCr only). For more information, see Generic HDMI Source.
  • The Generic HDMI Display component also has a new Color Format control that you can use to override the color format as reported in the display's EDID file. This is useful for correcting displays with incorrect format processing. You can force YCbCr or various RGB modes. For more information, see Generic HDMI Display.

The NV-32-H Network Video Endpoint now detects whether it is connected to a PoE++ (802.3bt Type 4) compatible switch port and does not boot unless proper power is detected.

  • Power detection LEDs in the NV-32-H Status component indicate the detected power: PoE++ (802.3bt Type 4), PoE (any standard that is not 802.3bt Type 4), or Aux (48V DC) power.
  • "Missing - Insufficient PoE power" fault status indicates if the NV-32-H is either not connected to a PoE++ (802.3bt Type 4) capable port or the port is incapable of negotiating this capability.
  • The Operate with any PoE PSE option in Q-SYS Configurator allows the NV-32-H to boot and run when connected to a switch port that technically supplies adequate power but does not correctly negotiate this capability with the NV-32-H. This is the case for some network switch power sourcing equipment (PSE).

For more information, see the Status (NV-32-H) and Q-SYS Configurator topics.

You can now configure what image and text appears when "Idle Screen" is configured in the Generic HDMI Display component's Idle Mode or Sleep Mode controls. The Idle Screen is useful for providing guidance to users when no HDMI signal is detected.

  • Shared Settings are used across all connected Network Video Endpoints. You can specify a company name, date and time (with customizable format), custom line of text, company logo, and a background image.
  • Device-Specific Settings are configured on a per-Network Video Endpoint basis. These include the room name where the Network Video Endpoint is located, a support number for users to call, and additional custom lines of text.

Configure these new idle screen settings in Q-SYS Core Manager > Video Endpoints > Idle Screen. To learn more, see the Video Endpoints topic in Core Manager Help.

You can now select what image appears on a connected HDMI display when a Network Video Endpoint does not currently have a network connection to the Q-SYS Core processor:

  • Boot Image (default) displays the device name, firmware version, model, and LAN interface information.
  • Graphic 1, 2, 3 displays a graphic of your choice, as selected in the Images section.

Configure this new setting in Q-SYS Core Manager > Video Endpoints > Settings > Network. To learn more, see the Video Endpoints topic in Core Manager Help.

Q-SYS Core Manager, Q-SYS Reflect Enterprise Manager

The Q-SYS Core Manager and Enterprise Manager > Network Services page includes a new Q-SYS Core Redundancy service. Enabled by default on Cores upgraded to version 8.3 or later and those that have been factory reset, this new service allows for secure communication between the Primary and Backup Cores in a redundant Core configuration. This service is required if Core Redundancy is configured in the Q-SYS design file.

To learn more about Q-SYS Network Services, see the Network Services topic in Core Manager Help.

As a security enhancement, SNMP is now disabled by default on new Q-SYS Core processors and those that have been factory reset.

To learn more about SNMP, see the Network Services topic in Core Manager Help.

  • When filtering the tables for Events, Status > Inventory, and Enterprise Manager > Alerts & Notifications, the quantities for each selectable parameter are now shown. This makes it easy to quantify, for example, how many Error events are in the log, the number of devices of the same model in the design, and so on.
  • You can now filter the Status > Inventory table by Manufacturer. This is useful for filtering for non-QSC devices, such as those being monitored by the Monitoring Proxy component.

The Sites page now features a Cards View, which provides a more visual way of seeing the Systems status for each Site. This is the default view, but you can switch to the existing Table View, if desired.

  • On the Alerts & Notifications page, alerts are now grouped by Source. Multiple different faults from a source are consolidated to a single line item, which is the last alert for that source. Groups are indicated both with an icon and the number of unique alerts in the source's Alert History. Click the icon to open the Alert History.
  • The Clear Alerts button now clears all alerts for a given Source, including its Alert History.

You can now show or hide columns in many areas of Core Manager and Enterprise Manager where dense tables are used – for example, Alerts & Notifications, Event Log, Audit Log, and so on. Click the Columns button to toggle visibility.

Updated icons indicate the severity of each event:

Normal
Warning
Error

For more information, see the Event Log topic in Core Manager Help.

Other Improvements

  • By default, devices in Q-SYS Configurator are now grouped by category (Cores, Amplifiers, I/O Devices, etc.), with sub-categorization by model. This makes it much easier to locate devices in the list when the network contains many Q-SYS Cores and peripherals.
  • Use the "Group By" buttons to enable or disable device grouping by category and model.
  • Use the Search bar to locate devices by name.
  • A new indicator appears in the Snapshots pane whenever the Global snapshot bank is currently being auto-saved. For more information, see Global Snapshot Auto-save.
  • Text information now describes when the Global snapshot bank was last saved or loaded.
  • Other Snapshots (user-defined) now indicate when they have been saved or loaded.

Resolved Known Issues

These known issues affecting the initial 8.3 release are resolved in version 8.3.1:

  • Core Manager > Users: Upgrading from version 8.0.0 or 8.1.1 no longer clears configured Users on the Q-SYS Core.
  • Core Manager > Network Services: Upgrading from version 8.0.0 or 8.1.1 no longer resets Network Services settings to default. (SNMP settings are not retained. This is a known issue. Refer to the Known Issues page for details.)
  • Core Manager > Event Log: Upgrading from version 8.0.0 or 8.1.1 no longer clears the Event Log.
  • Core: An issue that caused the Core to become unresponsive after deploying a design with USB Video Bridging enabled and containing a Softphone has been resolved.
  • Software Dante: An issue affecting Software Dante audio quality in designs where Software Dante audio is processed by multiple DSP components has been resolved.

These known issues affecting Q-SYS 8.2.2 are resolved in the initial 8.3 release and 8.3.1 release:

  • Amplifier: The low impedance warning on CXD-Q amplifiers has been re-calibrated to prevent false errors.
  • Dante: CDN64 cards no longer disappear from Dante Controller after upgrading a Q-SYS system that was previously upgraded with a CDN64 card in External Configuration mode.
  • Timeline Player: The Timeline (Beta) component has multiple bug fixes in this release:
    • Renaming a track no longer causes track names and audio lanes to be offset.
    • The component now properly refreshes when changing its configuration – for example, with Snapshots or a scripting component.
    • Stopping and starting the Timeline component set to External Sync at 30 fps no longer produces short remnants of previously played audio when playback begins.
    • The Reload control pin now works properly, regardless of whether External Sync is set or not. Use this control pin to trigger loading of new configuration data written to the Data control pin.
  • NV-32-H: Network Video Endpoints now support HDMI video sources that output YCbCr 4:4:4 and YCbCr 4:2:2 (YCC) color, in addition to the existing support for RGB 4:4:4. YCC color devices that sent video with a pink overlay in previous Q-SYS releases should now display properly. (YCbCr 4:2:0 is not supported.)
  • NV-32-H: Network Video Endpoints now support PoE type detection, and do not boot unless connected to proper power. This feature fixes the issue of NV-32-H devices being undiscoverable or rebooting due to insufficient power. See NV-32-H: PoE Type Detection for details.
  • USB Bridging: An issue that may have caused audio distortion when streaming H.264 video from a PTZ camera with a Core 110f's USB Bridge (both Windows and Mac) or with an I/O USB Bridge when using Skype for Business (Mac only) has been fixed. The previous workaround settings for this issue can be updated, if desired:
    • If using the Core 110f's video bridge, IP Stream 2 no longer needs to be 'None' in Q-SYS Core Manager.
    • If using an I/O USB Bridge and Skype for Business on a Mac, the USB Transfer Mode property no longer needs to be 'Bulk'.
  • USB Bridging: Error, "Core is in Fault because USB Video Bridge Camera <camera name> RTP IP Stream is not available" no longer occurs immediately after starting or stopping USB video bridging.
  • User Control Interface: Multiple fixes and improvements to CSS UCI styles and the browser-based UCI viewer accessible via Q-SYS Core Manager.
  • Event Log: The browser no longer disconnects with a "TypeError" when searching Event Log messages.
  • Event Log: In Enterprise Manager, viewing the Event Log for a System (Core) that is currently offline no longer results in an "Internal Server Error" message.
  • Reflect Registration: If you update an Organization or Site name in Enterprise Manager, Core Manager now properly shows the updated names in the Reflect Registration Details.
  • Users: Q-SYS Core usernames containing spaces no longer cause issues with saving or loading designs to/from the Core.
  • Design Files: An issue where deploying large designs sometimes caused a "Timeout waiting for Design to start" error message has been fixed.

Q-SYS 8.x releases include the new Q-SYS Core Manager, which replaces many Q-SYS Administrator functions and all Q-SYS Configurator functions for Q-SYS Core processors.

Read the following sections carefully before upgrading to or downgrading from Q-SYS 8.x. See the Upgrade Path Requirements section for special requirements when upgrading from specific versions.

Design File Compatibility

CAUTION: Before upgrading, save a backup copy of system designs.

Design files saved in version 8.x cannot be opened in Q-SYS version 7.2 or lower.

About Q-SYS Core Manager

Q-SYS Core Manager replaces most Q-SYS Administrator functions and all Q-SYS Configurator functions for Q-SYS Core processors.

  • UCI user PINs, event log management, audio file management, SNMP configuration, and camera management have all moved from Q-SYS Administrator to Q-SYS Core Manager.
  • Configuration of LAN adapters, changing the Q-SYS Core's time and date, rebooting the Core, downloading logs, installing Q-SYS Feature Licenses, and configuring Network Services are all now handled within Core Manager.

To learn how to access Q-SYS Core Manager after upgrading, and to see a list of all its management functions, see Q-SYS Core Manager.

Core Device Passwords

CAUTION: After upgrading, the Q-SYS Core is unprotected. To restrict access to the Q-SYS Core, you must create users and assign permissions in Q-SYS Core Manager.

The Core Device Password is not used in Q-SYS 8.x, and has been replaced with individual users and passwords configured in Q-SYS Core Manager. The Core Device Password is not automatically converted to a user in Q-SYS Core Manager.

  • Before upgrading, use Q-SYS Configurator to clear the Core Device Password to avoid being prompted for user credentials. If you are prompted for user credentials when upgrading, use "admin" for User Name, followed by the Core Device Password.
  • The ability to 'Save to Core & Run' (including firmware updates), and 'Load from Core & Connect' are restricted by Q-SYS Core Manager Access Control. Only users with 'Administrator' and 'Technician' roles can perform these actions.
  • Peripheral Device Passwords are unchanged in Q-SYS 8.x.

To learn how to enable Access Control and create users in Q-SYS Core Manager, see the Users topic in the Q-SYS Core Manager help.

User Control Interface PIN Protection

CAUTION: To restrict UCI access after upgrading, you must create new PINs and assign them to UCIs in Q-SYS Core Manager.

User Control Interface (UCI) access control via Q-SYS Administrator users is removed when upgrading to Q-SYS 8.x. To learn how to create PINs and assign them to UCIs in Q-SYS Core Manager, see the User Control Interfaces topic in the Q-SYS Core Manager help.

Redundant Core Configuration

Core Users

In Q-SYS 8.x, Core users (created in Q-SYS Core Manager) are not synchronized between redundant Q-SYS Cores. In a redundant Core setup, you must enable Access Control and create users on both the primary and secondary Core. (User names do not have to be the same).

Event Logging

In previous Q-SYS versions, Q-SYS Administrator merged the Eventlog for each active/standby pair in a redundant Core configuration, which made it difficult to diagnose complex issues across a pair of Cores. In Q-SYS 8.x, the Eventlogs are no longer merged, so you can now view each Core's Eventlog separately to see what events occurred while Active. (No events are recorded on the Core when in Standby state.)

Q-SYS Administrator Changes

Access Control

Access to Q-SYS Administrator is now governed by Q-SYS Core Manager users and user roles:

  • If Access Control is enabled, only users with 'Administrator' or 'Technician' roles can use Q-SYS Administrator and its functions.
  • If Access Control is disabled, anyone can access Q-SYS Administrator and all of its functions.
  • Page-by-page access control is no longer supported in Q-SYS Administrator.

To learn how to control access in Q-SYS Core Manager, see the Users topic in the Q-SYS Core Manager help.

Function Migration to Q-SYS Core Manager

UCI user PINs, event log management, audio file management, SNMP configuration, and camera management have moved to Q-SYS Core Manager.

The following functions remain in Q-SYS Administrator in version 8.x:

  • PA administrative functions, including PA Global Settings, Page Stations, PA Zones, Commands, and Command Scheduling.
  • PIN users for Page Stations, External Control Protocol, and File Management Protocol.

Audio File Management

In Q-SYS 8.x, audio file management is available in the new Q-SYS Core Manager > Audio Files page.

Note: The ability to manage audio files is determined by Q-SYS Core Manager permissions. If Access Control is enabled, any user with the Administrator or Technician role can manage audio files. If Access Control is disabled, anyone can manage audio files.

To learn how to manage audio files in Q-SYS Core Manager, see the Audio Files topic in the Q-SYS Core Manager help.

Emulation Mode Changes

Q-SYS Core Manager is not accessible from Q-SYS Designer when running a design in Emulation mode. Core Manager can always be accessed via network connection and web browser.

Design-specific parameters that remain in Q-SYS Administrator (PA Global Settings, Page Stations, PA Zones, Commands, and Command Scheduling) are still accessible in Emulation mode.

Downgrade Requirements and Considerations

If you choose to downgrade from Q-SYS 8.x to an earlier version, note the following:

  • Before downgrading, disable Access Control in Q-SYS Core Manager, or create an Administrator user called "admin". Earlier Q-SYS versions will prompt for the "admin" password (but not the username) when saving and running the design.

    Note: Disabling Access Control removes all Q-SYS 8.x users from the Q-SYS Core. If you do not disable Access Control, these users are retained (but are not used) on the Q-SYS Core after downgrading. If you later decide to upgrade again, you will need to remember these credentials.

  • In the earlier Q-SYS version and design file, open Administrator and temporarily set the Guest account Administrator parameter to 'Yes' and the Load from Core & Connect parameter to 'Yes'. After downgrading, you can set these parameters back to 'No', if desired.
  • Downgrading the Q-SYS Core to previous firmware does not automatically restore legacy UCI PIN protection for UCIs. You must load a backed up design file, saved with a previous Q-SYS version, that has UCI protection enabled in Q-SYS Administrator.

Note the following requirements when upgrading to release 8.x. In all cases, Q-SYS Core processors and peripherals must be at version 7.2.1 before upgrading to 8.x.

CAUTION: Designs you create or update with a newer Q-SYS Designer version and then open in an older version are likely to be incompatible and unusable with the older version of software. Before upgrading, create backup copies of your Q-SYS design files for both the current version and older versions, and back up all media on your Q-SYS Core processor. To avoid overwriting design file backups, do not open backup files with newer versions of Q-SYS Designer.

If you are upgrading from versions 7.2.0, 7.1.x, 7.0.x, 6.2.x, or 6.1.x:

  1. Upgrade to version 7.2.1.
  2. Upgrade to version 8.x.

If you are upgrading from version 5.4.x, 5.3.x, 5.2.x, 5.1.x, or 5.0.x:

  1. Upgrade to version 6.0.0. See the version 6.0.0 Release Notes for upgrade requirements for that version.
  2. Upgrade to version 7.2.1.
  3. Upgrade to version 8.x.

Note: There is no need to update peripherals to version 6.0.0 in advance of updating to 7.2.1. Once the Q-SYS Core is running 7.2.1, it will update connected peripherals running version 5.x to version 7.2.1.

If you are upgrading from a version earlier than 4.2:

  1. Upgrade to version 4.2. See the version 4.2 Release Notes for upgrade requirements for that version.
  2. Upgrade to version 6.0.0. See the version 6.0.0 Release Notes for upgrade requirements for that version.
  3. Upgrade to version 7.2.1.
  4. Upgrade to version 8.x.

For software and firmware updates, see the QSC Software and Firmware page.

Operating System

  • Windows 7 PRO 64-bit
  • Windows 8.1 PRO 64-bit
  • Windows 10 PRO 64-bit

Installation Dependencies

The Q-SYS Designer installation program automatically installs the following components if not currently installed on the Windows PC. Some components require internet access for installation.

  • Microsoft .NET Framework 3.5 SP1 (includes 2.0 SP2, 3.0, and 3.0 SP2)*
  • Microsoft .NET Framework 4.6 SP2*
  • Microsoft Visual C++ Runtime 14.1 update 1 (2015)*
  • Microsoft Windows Installer 3.1
  • Microsoft XML Parser 6.0

* Internet connection required.

Q-LAN relies on the performance of modern network switches to ensure real-time delivery and synchronicity of media streams across all connected Q-SYS devices. See Network Switches & Infrastructure to understand your options in choosing a network switch, as well as the requirements for compatibility with Q-LAN.

Q-SYS Designer release numbering convention is a three-level system – major release.minor release.build number (2.2.100). Larger numbers indicate a newer release. If the "major.minor" release number of a design file and Q-SYS Designer software are the same, the "build" number doesn't matter. You will have to upgrade/downgrade your hardware to the same "build" number as the Q-SYS Designer software to Run the design on the Core processor.

You cannot open a design file with a newer "major.minor" release number than the Q-SYS Designer software. For example, you cannot open a 4.2.nnn design file with 3.3.nnn Q-SYS Designer software.

You can open a design file with an older "major.minor" release number than the Q-SYS Designer software. For example, you can open a 3.3.nnn design file with Release 4.2.nnn Q-SYS Designer software. If you save the file with the newer software, you cannot save it back to an older release.

Note: Make sure your design files are backed up using your current release before starting the upgrade to a newer release.