Version 2.3 Release Notes

Design and AIM File Issues

Design File and AIM File dialogs may not display stored files. Save As and New functions may also be inoperative.

• Workaround 1: Close and restart SysNav

• Workaround 2: Reinstall SysNav. Note that choosing this option will delete any existing files on the device. To save them, temporarily move the Design and AIM folders out of the System Navigator folder on the device and return them once SysNav reinstallation is complete.

  • Windows - Files are located in the User Documents\QSC\System Navigator folder.

  • iPadOS - Files can be found in the Files app, under SystemNavigator.

Auto-Reconciliation occurs despite changes

If a previously Reconciled array is reconnected to SysNav it will auto-reconcile even if changes to the parameters listed below were made (offline in SysNav or on the physical loudspeaker(s) via the RUI) between SysNav connections. The values from the SysNav Design will be applied.

• Array Name

• Array Shading Generally it is good practice to have the same signal processing parameters applied to all loudspeakers in an array. Array Shading is an exception. Array Shading is accomplished by adjusting the high-frequency level of individual array loudspeakers in order to achieve more uniform coverage. Frequency

• Array Shading In/Out

• Array Shading Gain

Auto-Reconciliation failure

• There are conditions that can cause Auto-Reconciliation Reconciliation is the act of matching a physical loudspeaker or array that has been discovered on the SysNav network with a like virtual loudspeaker or array that is part of the Design. Reconciliation applies the Design settings to the loudspeaker or array and allows it to be controlled and monitored by SysNav. failure.

• Workaround 1: Restart SysNav after recalling the design.

• Workaround 2: To retain the settings of the physical loudspeaker or array…

  • Open the Inventory screen.

  • Under “Add items from” select Discovered.

  • Select the loudspeaker or array from the Available Items list.

  • Add it to the Design using “To Inventory”

  • Optional - select and Remove old virtual loudspeaker or array from the Inventory Items.

• Workaround 3: To apply the Design settings to the physical loudspeaker or array…

  • Open the Inventory screen.

  • Under “Add items from” select Discovered.

  • Select the loudspeaker or array from the Available Items list.

  • Select the virtual counterpart of the loudspeaker or array from the Inventory Items list.

  • Bring it into the Inventory using the Reconcile button.

Adding single loudspeakers from previous array reverts some parameters to defaults

Sometimes a single loudspeaker that is added from a previous array will revert some parameters to default values, including Gain, HPF, Delay and Sensitivity.

Array name display blank

• Occasionally, a Discovered array name may be lost when the array is added to the Inventory.

  • Workaround: Change the name

Array rename does not update

• The previous array name may continue to be displayed on the Inventory items screen after a new name has been entered. When this happens, opening the Array’s Settings page will cause the name to be properly displayed everywhere.

• Occasionally a previous array name will be displayed for an array that has been removed from Inventory Items using the Undo Reconcile or Remove controls.

Undo Reconcile and Remove sometimes works on array members

Generally, Undo Reconcile and Remove is not allowed for individual loudspeakers that are members of an array. Undo Reconcile or Remove should be performed on the entire array. However, there are some instances where the app will allow such an operation to occur resulting in a "broken" array. To recover from this condition, follow these steps:

1. Remove the array from the Design in the Inventory screen

2. Shutdown SysNav

3. Power cycle the array

4. Wait for the loudspeakers in the array to discover each other fully (20 seconds per loudspeaker in the array)

5. Start SysNav and add the array back to the Design

Selection issues on Inventory page

Sometimes, selecting items will take multiple clicks or taps to make a selection stick in the Inventory page. Some buttons may not properly be enabled (like Reconcile) even if an item appears selected and will require the user to select again.

Removed virtual loudspeaker from array remains

When adding an array in the Inventory screen, if one or more loudspeakers are then removed from the array, the Control - List View, and Control - Drilldown, Array tab, will show the removed loudspeaker until SysNav is restarted.

When adding individual loudspeakers, quantity is not as specified

When individual loudspeakers are added to the Inventory Items after an array has been added, SysNav may use the quantity specified for the array rather than that specified using the Manage Inventory counter.

Array does not show in Discovered after creating new Design

If an array has been Reconciled in a Design and a new Design is created, the previously Reconciled array may show in the Discovered tab until restarting SysNav.

Solo Mode

If SysNav is closed with Solo mode enabled, reopening SysNav may not indicate that Solo mode is active and all connected loudspeakers may be muted.

• Workaround 1: Exit Solo mode before closing SysNav.

• Workaround 2: Toggle the Mute / Solo control.

Array loudspeakers unexpected behavior after firmware update

Firmware updates to loudspeakers that are members of an Array may result in unwanted behavior. To restore proper operation close SysNav, power cycle the Array and relaunch SysNav once the array has discovered itself.

Update page not showing devices

To update the firmware, the user must first add loudspeakers to a Design. It may be necessary to close and restart SysNav in order to display all Discovered and Reconciled devices on the Update page.

Speakers removed from design remain in Updates

When a physical loudspeaker is added to a Design and then removed, it will continue to show in the Updates page until SysNav has been restarted.

App parameters become unresponsive after minimize

Sometimes, if the app is minimized (not fully closed) and reopened, the parameters in the UI become unresponsive.

• Workaround: Fully close the application and reopen

Optimize "Apply" button not working

There are two possible causes for this symptom.

1. A bug that causes the Apply button to be unresponsive.

   • Workaround: Toggle the Optimization An array is Optimized when the DSP settings of the array members all match and the appropriate filters have been applied based on information provided by QSC AWARE™ regarding the number of array member loudspeakers and total splay. Also see Ar-Q. Out/In button to restore operation of the Apply button.

2. The Deployed Splay The angle between two adjacent loudspeakers in an array. angles sum to an invalid value.

   • Workaround: Use the Designed Angles settings on the Control Drilldown Array screen.

‘Save As’ not working for AIM files

If the app does not have any saved AIM files or the user has deleted the currently loaded AIM file, the app may show "Untitled" under the AIM Model. In this state, the Save As control may not be available on the Edit Array or Edit Venue screens. The AIM design may be saved using the AIM Files control and dialog.

Loudspeakers added at zero degrees

If loudspeakers are added to an array in AIM, they are added with a default Splay Angle of 0 degrees, instead of one of the valid Splay Angles. This will not be apparent in the Splay Angle controls. The bug shows in two ways:

1. The center lines in the venue graph area coming from the loudspeakers will be perfectly parallel instead of spreading out

2. In a Flying deployment, the "Unsupported Deployment" dialog will be displayed

• Workaround: Input supported splay angles using the Splay controls.

App sometimes crashes

Sometimes, after creating more than 20 AIM files, on iOS only, the App will crash.

Old loudspeakers appear after switching networks

If the SysNav network is attached while the system is running, SysNav will continue to show the loudspeakers in the previous network.

• Workaround: Restart SysNav.