Category: ReleaseNotes

Posted on

23.1.0.2438 GTT Minor W Release

Securing AWX Audio Object

Custom Actions on Slot Load

  • Ability to configure Swoosh Mode in Core Object Configuration in slot map.
  • Automatically modify core object id in preset controller
  • Auto delete configured custom action when the instance is deleted from device designer /when Audio Objects deleted from signal flow
  • UIUX enhancements for custom actions
  • Control Refresh in custom action.

Halosonic Feature Updates

  • End Of Line Native Panel Request
  • GNS Panel ‘Add Grain’ sets field to 0
  • RNC flexible configuration native panel

Native Panel and Update

  • Power Manager Panel Updates
  • Biquad Panel Updates
  • LUT Panel Undo Redo Feature
  • LUT Customizable Label for axes

GTT Performance Improvements

  • Save SFD Optimization
  • Device View Optimization
  • Import Project Optimization

IVP/RTA Feature Updates

  • Example projects for IVP, StarterKit and VST3 with pre-configured for better user experience
  • Ability to share Calibration between MM and RTA.
  • Zoom to gates for X and Y-axis in RTA
  • Ability to perform Math Functions with Target Curves in RTA
  • Average SPL value on the averaged graph in RTA
  • Implement D weighting for live traces.
  • Option to include comments/notes in RTA Export graph for Text Format

Auto Eq Updates

  • Show crossover filters in chart
  • EQF file export
  • Ability to access Use case configuration of mic weighting, delay/time alignment and inter region gain alignment from(.ini) file,
  • Enhanced Display for Summed Speaker Frequency Response
  • Plot Target curve from 20 Hz to SuperUserParams/Max Frequency -Panel

Central Viewer Feature Updates

  • Ability to Customize the measurement curves (color, thickness, etc)
  • Central Viewer Graph Axis Improvements for better User experience.
  • Zoom to gates for X and Y-axis in Central Viewer
  • Central viewer to accept RTA measurements.
  • Include comments/notes in Export Graph Data in Text Format Central Viewer

Measurement Module Updates

  • Common Name for measurement data for between rows
  • Ability to show session notes in MM Window
  • Export incomplete or faulty measurement with warning

Change Requests Addressed

  • COCINTC-6553-CAO content ignored when importing a new project with the same CAO name
  • COCINTC-6860-[HALOSonic][RNC] RNC flexible configuration native panel development
  • COCINTC-8206-[HALOSonic][EOL] End Of Line Native Panel Request
  • COCINTC-8153-GNS Panel ‘Add Grain’ sets fileid to 0
  • COCINTC-8207-Some concerns regarding CRC checksum and versioning “copy button”
  • COCINTC-8208-GTT LUT Undo feature
  • COCINTC-8210-GTT LUT Customizable axis labels
  • COCINTC-7476-AutoEQ: Use case configuration: mic weighting, delay/time alignment, inter-region gain alignment
  • COCINTC-8312-Enhanced Display for Summed Speaker Frequency Response
  • COCINTC-7596-AutoEq – Plot target curve from 20 Hz to SupUserParams/Max Frequency
  • COCINTC-7263-Expose Help button to Menu Bar
  • COCINTC-8217-Improve memory report headers
  • COCINTC-7844-Add “AudioObject Type” column to exported files
  • COCINTC-6014-Clone Project
  • COCINTC-8158-We need GTT the central viewer to accept RTA measurements.
  • COCINTC-8170-Text format export graph data to have comments/notes in RTA and Central Viewer
  • COCINTC-8279-RTA Implement D weighting for live traces
  • COCINTC-8220-Should be able to export incomplete or faulty measurement with warning
  • COCINTC-8243-Request GTT to support modify XTP Response Timeout time based on AWX-T+
  • COCINTC-8255-Failing to open GTT Project
  • COCINTC-7546 -AWX to support control “refresh” after set file loading
  • COCINTC-7543 -AWX to support object bypass/mute/stop without dependency on platform/BSP
  • COCINTC-5826 – Improvement for sending Master Control signal after EQ switch
  • COCINTC-8102 Very long project loading time of pipeline
Posted on

Details on New AWX Features

Below features are developed across the domains of AudioworX ( xAF and GTT).

Features Updates
Master Control This feature enables users to route control signal(s) on device level. This means, that now controls can be routed across xAF instances and (Virtual) Cores.



Key features

  • Enables core object to core object control routing.
  • Enables block control inputs to core objects.
  • Enables block control outputs from a core object.
  • Enables block control inputs to Virtual Cores
  • Enables block control outputs of a Virtual Core.
  • Enables physical core to physical control routing.
  • Enables control pin configuration on Device level instead of instance level
  • Enables graphical control routing configuration and visualization
  • Simplified streaming configuration.
  • Enables Audio objects/ Core objects to share “data” (FFT, coefficients, states, etc.)

In y-release, group size is restricted to 256 but will be extended to 2^31 in y+1 release.

  • Queued control data to avoid a circular control processing.
Core dependent Audio and Core Object filtering This feature allows the AO developer to specify supported cores for the audio or core object. Third party objects not always support all AWX supported target processors. This feature enables the developer to restrict the usage of the audio object only for the supported targets. This is an extension of the supported block length and sample rate feature.



Key features

  • Enables dynamic metadata to describe all supported features/target processors for audio objects
  • Enables dynamic metadata to describe all supported features/target processors for core objects
IVP Soundcard setup This feature enables the user to use new host APIs for the sound card configuration. For low latency requirements the newer WASAPI host can be used instead of MME if no ASIO ™ device is available.

Key features

  • WASAPI host added
  • DirectSound host added
  • Latest PortAudio features and bugfixes integrated
Third-party framework inside AudioworX as a core audio object This feature enables customer to integrate AWE audio objects into AudioworX without any effort.  With the help of bridge application, user will be able to tune AWE audio objects using AWE designer/Tools.


Key Features

  • Enables multi-threading support for the framework.
  • Enables configuration of number of threads, core speed and Heap sizes.
  • Reduced MIPS by eliminating interleave and deinterleaving data before and after AWE framework.

 

AudioworX Starter Kit Updates

  • Enabled support for HiFiBerry DAC8x and ADC8x Add-on.
  • Improved latency is achieved with the Starter Kit.
  • Starter Kit has been updated to include an option for MIPS measurement from real-time clock.
  • New example GTT project included for the AudioworX Starter Kit with support for 8 inputs and 8 outputs (HiFiBerry DAC8x and ADC8x add-on combination).
  • Implemented and tested SKUtility-UI tool to enable Raspberry pi board control through a graphical Interface.
  • Changed Starter Kit target installation directory on the Raspberry Pi for better portability.
Posted on

FAQ

Q. What is the range supported for BlockID?

A. For audio objects with extended block id support, block id should be in the range – 33024 to 65280 in multiples of 256.

Q. Not able to load the audio library (VirtualAmp.dll or Toolbox dll)

A. If VirtualAmp.dll depends on another dll which is not part of GTT, GTT will fail to load the dll. In this case user needs to copy the dependent dlls to C:\Program Files\Harman\HarmanAudioworX\tools\GTT folder.

Q. GTT stops the audio from other application when launched?

A.  GTT doesn’t stops audio from other application, However If user face any such difficulty.

Change the properties of the sound settings in your laptop/ PC. Uncheck the check box which says, “Allow application to take exclusive control of device.”

Posted on

General Limitations

The table below outlines the general limitations of AudioworX.

Limitations Descriptions
GTT/IVP crash because of propagation of wrong core type
  • Under some circumstances, it might happen that your project gets corrupted and GTT closes after clicking reboot or apply button in IVP. If GTT closes again after starting IVP, the following steps are required to recover:
  • Go to your specified VirtualAmp.dll folder and delete all flash files, and start GTT.
  • Go to your device
    • Change Core type to C66 (or any other than WIN64)
    • Save (important)
    • Change core type back to WIN64
    • Save
  • Open IVP
    • start PluginHost
  • Send device config and/or signal flow
[SMART] Label names are lost when it’s associated AO (state variable) is removed from signal flow The linking that is done before the extract will not be available on CAO edit as we are using a dummy device/core hence the hiqnet address would differ. Workaround: Do the smart window mapping only on the CAO edit.
Biquad number of channels Based on the requirement AWXNG-9194, we have a limited number of channels. GTT does not display the limited channels, but if you enter more than 64, it will show as invalid with a tooltip.
Timing based functionality may not work correctly when running signal flows which are over CPU budget for the device. Any functionality that is based on on-device time checks or GTT based timeouts, or other time checks may have failures.  Specifically, during state changes, your ramp time is based on the accumulation of increments, which are calculated up front.  Since calc is running slower, these ramping increments are also happening slower.  Likewise, the pipeline delay functionality is based on the passage of real time, not the number of calculations done, so it would not wait long enough for the cores to actually fill buffers as expected, since they are running slower than they should.  When you load slots in this condition, you may see a GTT timeout message indicating the slot load failed, but it may be it just took too long.
IVP / VST3 builds When connecting cores of different block lengths (which is possible so that it can be done on hardware and buffered outside xAF) note that it will not work in IVP or VST3 in single core processing mode. Processing will not happen when this condition occurs.
Compensation File The compensation file is only considered for magnitude curve correction; it has no impact on calculated metrics such as sound pressure level (SPL) and total harmonic distortion (THD).
Wasapi limitations
  • Bluetooth devices are not supported.
  • While selecting Loopback devices, make sure that the input device and output device are the same, with the input device name appended with ‘Loopback’, as shown below:
Unsupported Bluetooth dongles JBL Quantum 610 and JBL Quantum 800 Bluetooth dongles are currently not supported.

 

Posted on

xAF Known Issues

The table below outlines the xAF know issues.

Issues/ Limitations Description
VST only issues/Limitations The input and output sample rates of the VST must always be 48000 Hz so any audio core with inputs/outputs connected to the device input/output should also be connected to core objects at 48000 Hz.
IVP Using Block Length <1024 with MME driver in sound card settings will have dropouts. Use Asio or block length greater than or equal to 1024.
Posted on

GTT Known Issues

Known Issues with a workaround and will not be fixed

Known Issues Description
GTT Core Linking AWXNG-5049: [SMART] Label names are lost when it’s associated AO (state variable) is removed from signal flow.

The linking that is done before extract will not be available on CAO edit as we are using a dummy device/core hence the hiqnetaddress would differ. Workaround: Do the smart window mapping only on CAO edit.
GTT Signal Flow Volvo project getting a compiler error “Block ID range error with SpeakerProtection AO” (Block id for SpeakerProtection AO need not be 16 bit and hence need to be corrected at project end)

 

Known Issues and will be fixed in next release

Known Issues Description
Checksum In read cases checksums Match When tuning data set is very small.
Probe points
  • Distorted audio spectrum is generated when change the Probe Points during Probing.
  • Probe Points / Streaming: Distorted spectrum for Probe Points in IVP is observed when probe point is initiated after the streaming is paused and played back.
UI/UX Opens multiple windows during 1st time launch.
GTT MPC Keeping the Map file open in Hex Editor Neo and try to export all from MPC (such that it tries to overwrite the map file which is open in Neo editor) results in GTT crashes.
GTT Core /SFD
  • Multi connection from one input group to multi-input core to be avoided.
  • GTT Crashes While Opening Core Object Settings After Deleting Virtual Cores with Existing Core Object Settings by Keeping MPC window open (Workaround: CloseMPC before doing edit device).
GTT Native Panel Legend View of Control Mixer Panel is not updated properly when we re-assign color and label.

Workaround: Reopen the panel, all labels will be visible in the Legend View.
Panel Designer  Help links are mapped incorrectly in some Custom Panel Windows.
MIPS Window MIPS window is limited to 255 audio objects per core.
RTA/IVP RTA – Delay Mode do not show aligned values in Live ribbon bar vs Graph.
Posted on

AudioworX RSDK Known Issues

  • Clearing Flash Files: GTT crashes when try to import another project and send signal without clearing the existing flash files.

Deleting the flash files manually is not required when moving from offline device to online device.

  • Block ID range: The block ID of the AOs that support extended block IDs shall range from 33024 to 65280 in multiples of 256 and the GTT ensures the same with appropriate error messages if invalid.
    For all the other AOs that do not support extended block ID, the range needs to be restricted from 1 to 32767 only. But presently the GTT is not restricting in this range and allowing till 65535.
  • Double-Clicking the gttd project just launches the GTT installer and closes immediately. Fails to open gttd project by double-clicking it.
  • Mandatory “device.flash” file: IVP and VST3 might not work correctly and show number of inputs and outputs or might even crash if no “device.flash” file is present1
  • Legacy device: The legacy device is not supported in this release because of Master Control related changes and dependencies. This will be addressed in y+1-release.
Posted on

Compatibility/Sub-Versioning

This release requires the following software to be installed for SW developers:

  • Microsoft Visual Studio  2017 and 2022
    • For customers using VST3 : Microsoft Visual Studio 2017 or 2022
  • CMake 3.24 and above
  • Python 2.7