Author: Debanka

The Configure Default Controls option allows you to specify which default control ids should appear in the “Control In” control list.

To Configure the Configure Default Controls:

1. Click on Default Control-Ids. This opens the Configure Default Controls window.
   If no configuration is defined, all Control IDs are selected in the Configure Default Controls window.
   
   In the Configure Default Controls window, you can select or unselect control IDs.

   You cannot deselect the Control ID used in the Signal Flow Designer.

2. Select or deselect the required control Ids and click Save to update the configuration.
   

Use the search text box to search and filter the control Ids.

Once you have modified the Configure Default Controls data, you can verify the changes.

Go to the Signal flow designer window and open the Control In property window to verify the configured default control IDs along with custom control IDs.

Sort Control In Pin Data

The Control In panel shows all user-configured control pins data.

You can click on any of the column headings to sort the data. Clicking alternately will change the sorting direction from ascending to descending or vice-versa.

The ascending order of the Pin column is the default sort order for the Control In panel.

Click on any column header to sort the respective data on the Control In panel.

The Device Designer comprises of various tools and interfaces that are used to create and run audio processing systems on hardware. The Device Designer contains the canvas and modules needed to create the signal processing template, while the SFD interface handles most of the target and audio object interactions.

When you launch a project in GTT, the Device Designer screen appears, which includes the following elements:

1. Ribbon and Group: The ribbon is composed of six groups, each of which represents a subset of program functionality. In addition to these programs, there are also additional contextual programs that automatically appear depending on what is currently selected.
   The GTT ribbon comprises six groups: Tools, Connection, File, Tuning, Device Panels, and External Endpoints. Each group has specific tools of related functions. It gives you quick access to the tools and functions you need to complete a task.
   
   • Tools: This group includes three tools: Services Monitor, Event Log, and xTP Log. The event log and xTP log in GTT can both be checked and monitored using all these tools.
   • Connection: This group includes tools to set up the connection between the physical or virtual device, such as configuring socket connections and port settings. Additionally, it facilitates you to establish the connection once it has been configured.
   • Import/Export: This group allows you to import and export device files, tuning data files, device description data files, and corporate pin data.
   • Tuning: This group includes Tuning Data and Virtual Tuning. Using Tuning Data, you can open and tune the audio files. Virtual Tuning enables the measurement of impulse responses of an acoustic environment using the AudioworX measurement Module.
   • Device Panels: This group includes the following tools: State Variables, Default Control-Ids, Present Controller, Controller, Linking Window, Mips, Memory, Memory Latency, Streaming, and File Controller. Each of these tools is equipped with a unique set of functions.
   • External Endpoints: This feature allows external tuning to communicate with the device. The GTT will receive the requests from external tuning tools and send them to the device via GTT. This is made possible by a WCF service endpoint that third-party tools can access.
2. Devices List: This section displays the list of projects. In addition, you can add and delete a device.
3. Toolbox: This section display core levels of processing, such as block length conversion, merger/splitter, and sample rate conversion within the audio processing pipeline.
4. Device Operations: This section contains several functions related to physical/virtual devices like Load Device Config, Edit Device, Send Device Config, Send Signal Flow, Export SFD, and Control Ids.
5. Properties Panel: A Device Template is a combination of three layers – Physical Layer, Virtual Core, and Core Object. When you select one of the cores, the properties of the core are displayed on the right side. If required you can modify the core properties.
6. Device View: The workspace is used to add devices and program the device core. You can use the magnifier function to adjust and change the size of the design workspace.

Tuning Data

You need to connect a device to GTT to send/receive tuning or state data.

When the device is connected you will get the following options.

• Send Tuning Data
• Receive Tuning Data
• Receive State Data

Virtual Tuning

This feature will be removed in the future Global Tuning Tool release.

Virtual Tuning allows you to measure impulse responses of an acoustic environment using the AudioworX Measurement Module. Based on these measurements, a production signal flow can be virtually tuned.

For this purpose, two new audio objects are implemented in AudioworX:

• IppMimoConvolver
• Time Multiplexer

IppMimoConvolver: The IppMimoConvolver audio object provides MIMO convolution with FIR filters using the Intel Integrated Performance Primitives (IPP) library, a multi-threaded software library of multimedia and data processing applications. It is highly optimized for various Intel® architectures and is a comprehensive library of out-of-the-box, domain-specific functions. The library is available for the Linux, MacOS, Windows and Android operating systems.

In the SFD, you can select the following object parameters at design time:

• Number of input channels
• Number of output channels
• Number of taps of filters

Tuning: For each filter combination in IppMimoConvolver, this object exposes these one tuning parameters set to the GTT

• Coefficients: The coefficients of the filters can be imported from .csv files. The filter taps that are set in the GTT must match the taps of the filter that is imported from the .csv file.

Filter coefficients can also be loaded directly from a Measurement Module session that has been pre-measured in AudioworX.

Time Multiplexer: The Time Multiplexer combines multiple input audio signals into a single audio signal by dividing the input channels into equal fixed length time slots and mixing them into a common output channel with fading between channels.

The length of the time slots and the fading characteristics can be configured at runtime.

The output signal is the signal of one input channel at a time. The next input channel becomes the first input channel again when the last input channel is reached. Depending on the fading mode, there might be a block length of fading between 2 channels.

In the SFD, you can select the following object parameters at design time:

• Number of input channels

Tuning: This audio object exposes four tuning parameters to the GTT.

• Mode: The mode can be set to:
  • Normal Mode: Performing multiplexing
  • Active Channel Mode: Single channel passed to the output
  • Off: No output
• Multiplex number of blocks : Only evaluated in “Normal mode”. It presents a number of blocks (block length) after which to switch to the next input.
• Fading mode: Only evaluated in “Normal mode”. It sets a type of fading method:
  • Cosine square fading
  • Linear fading
  • No fading (hard switch)
• Active channel
  • If in mode “Active channel mode” – The channel number of the input channel that will be routed to the output channel.
  • If in mode “Normal mode” – Set the selected channel as current input and continue with the next channel in normal/multiplex mode after the configured number of blocks.

Virtual Tuning Configuration Prerequisites

The steps listed below describe how to configure an IppMimoConvolver object using GTT.

1. Create a signal flow with the IppMimoConvolver object with m inputs, n outputs, and j number of taps for filters.
2. Create a measurement with n mics and m speakers.
3. Adjust measurement length, sample rate, etc to get exactly the required amount of coefficients (ir data points) before starting measurement.

Once the above steps are done, select the device (which contains a mimo object) from the device list to activate the device tab.

Steps to launch Virtual Tuning:

1. Select a device, and click Virtual Tuning. This opens the Virtual tuning configuration screen.
   

Apply Coefficients to Virtual Tuning

Steps to apply coefficients to Virtual Tuning:

1. Open Virtual Tuning and select suitable Measurement Session.
2. Select Convolution Object to which the Coefficients to be applied.
3. Click Apply.

The selected measurement’s IRData is retrieved and applied to the convolver object. A toast message appears, stating that the coefficients were successfully applied.

Virtual Tuning Panel: The IppMimoConvolver panel is used to view the coefficients assigned to the object. This panel provides the following functions.

• Flat
• Import
• Export
• Import All

Import

• Tuning Data: Use this option to import an existing tuning file (*.set or *.setr).

Users can use the following hints to see if the “imported tuning file” has made any changes to the device:

• Check the State Variable Explorer to see if the values of the corresponding state variables have changed.
• If the device and GTT are in sync, sending tuning data should cause the frequency response to change.
• The user can manually create a set column to obtain the current state of the state variables after importing the tuning data file on the device.
• The user can use the set column that is already present after importing the tuning data file on the device and pressing the “store” button. If the set column in the set file contains state variables, the user can view the modifications.

Export

• Tuning Data: Use this option to export a tuning file (*.set or *.setr).

This method creates a .set file which contains all the object tuning data, that includes all of the device’s state variables. For example, if certain objects are not tuned, their default tuning values will be exported to the set file.

• Export DDF Data: Use this option to export a device description data file (*.ddf ).
• Export Control Pin Data: Use this option to export Control Pin Data (*.csv).

If no configured control pin data is available its shows the message “Control pin not configured for device”.

• Device Template: Use this option to save device template file  (*.flash).

Important The Device File option is hidden by default. Steps to make Device File option visible under in Import/Export option: 1. Go to GTT installation path and locate GlobalTuningTool.exe.Config file. Location: C:Program FilesHarmanHarmanAudioworXtoolsGTT 2. Open the file in any text editor (notepad) and update “AudioObjectDeveloperMode” attribute under “appSettings” node as shown below. 3. Set Value = true to enable Device File option. Similarly, set Value = false to disable Device File option. Restart the GTT to take effect of updated setting.

You must connect the device instance containing the tuning data to the physical/virtual device to send tuning data to the physical device.

Connect Device

Use the Connect Device option to connect to a device.

To connect a device, select the device from the device list, and then click Connect Device.

If there is no instance of AmpSrv2 running with the required port, then a new instance of AmpSrv2 will start. Otherwise, it will use the current AmpSrv2 instance.

The communication port between GTT and AmpSrv2 is calculated automatically on the GTT side: 24575 + HiQnet node address of the device instance.

If AmpSrv2 is started by GTT, then AmpSrv2 settings will not be stored.

If AmpSrv2 settings change permanently, then a manual start of AmpSrv2 is required.

The automatic startup of AmpSrv2 only works for single-device instances. If you want to connect to multiple device instances in parallel, you will need to manually start multiple AmpSrv2 instances (running on the requested port addresses).

From Herbie Hancock release onward, the default port of the virtual device has changed. The default port is now 25001 (before it was 8080).
If an old audio library is used, the settings should be adapted manually. In AmpSrv2 > File > Options > click Socket.

Disconnect Device: Click the Disconnect Device button in the ribbon bar.

If AmpSrv2 was launched by GTT, AmpSrv2 will be closed. Otherwise, AmpSrv2 will keep on running.

AmpSrv2 Settings

AmpSrv2 is software to connect the tuning tool to either a physical target device or a virtual amplifier.

The AmpSrv2 shows the following menus:

• File: Click on the File menu to open the Options window or close the AmpSrv2.
• View: Click on the View menu to open dialogues and protocols functionalities.
• Extra: Click on the Extra menu to import CAN SID, OS-Msg Description, GATI/xTP Description, and Protocol file.
  

• Info: To get the AmpSrv2 version and license details.

AmpSrv2 License

The AmpSrv2 dialogues and protocols functionalities are licensed-based. If any dialog or protocol is grayed out or not available, this means you have a limited license.

The AmpSrv2 is shipped with a limited license (Customer.lic).

To check AmpSrv2 license:

1. On the AmpSrv2 window, click Info, and then click About. This displays the AmpSrv2 info screen. Verify the license information.
   

To activate the new AmpSrv2 license:

1. Navigate to the C:Program FilesHarmanHarmanAudioworXtoolsAmpSrv2.
2. Locate the Customer.lic file (license file) and delete the existing license file.
3. Copy and paste the new license file (xxx.lic) into the same AmpSrv2 directory.

To changing AmpSrv2 Settings:

1. On the AmpSrv2 window, click File, and then click the option. This opens the Options window.
2. On the Socket tab, set the protocol to GATI.
   

If you experience network conflicts, choose a different port above 50000 because port 8080 is very popular. Your selection must appear in the VST client (probably AudioMulch).

1. On the Tuning GATI tab, set the Databytes per to 192, and click Ok.
2. On the AmpSrv2 window, check the checkbox.
   

When you start GTT and connect to AmpSrv2, the AmpSrv2 window will show the number of connected clients.

Once you have completed the necessary Ampsrv2 modifications, go to AmpSrv2 Settings and save the Ampsrv2 modifications.

This saved configuration will now be used for this specific device on Connect Device. The saved configuration will also be exported/imported using the GTT project Export/Import functionality.

If no AmpSrv2 settings are connected with the device, the default settings will be used. You can modify the GTT default AmpSrv2 settings. Follow the steps mentioned in the above topic “To changing AmpSrv2 Settings”.

The AmpSrv2 window will appear, and the user can modify the settings, which will be considered the Default Settings for GTT.

In the case of a Discover device, you should first open AmpSrv2 Settings, modify settings as needed, and then click on Discover Device. This modified configuration will be used to discover the device.

In the AmpSrv2 window, the port number of the server is not saved in the General tab.

Two AmpSrv2 windows with the same port number cannot be opened or an error message will be displayed.

The Device Panel group offers a set of tools that lets you perform various functions on a device.

The following tools are available on the Device panel.

• State Variables:  To view the memory layout of each device instance
• Default Control-Ids: To specify which default control ids should appear in the “Control In” control list.
• Preset Controller: The preset controller is the central place for managing and organizing how you will load presets in your signal flow.
• Controller:  To send instance commands.
• Link Window:  To assist you by reducing the number of audio parameter configurations.
• MIPS: To view the CPU load of cores, instances, and audio objects of the connected device.
• Memory:To the CPU memory of cores, instances, and audio objects of the device in a single multi-level grid.
• Memory Latency: To shows the amount of time taken by the CPU from initiating a request for assessing memory to actual reading or writing data at the requested memory.
• Streaming: To stream live data from the device.
• File Controller:  To send audio files from GTT to device.

You can stream live data from the device. The state variables which support streaming and polling are displayed in the state variable explorer tree with “Category” other than “Tuning”.
The streaming and polling are used to monitor the signal flow of different parameters in a Signal Flow Designer.

Streaming can be beneficial when you need to constantly monitor a signal for a specific channel. If any changes are made to the signal flow design, the updated values will automatically be displayed through streaming. However, for non-streamable parameters, GTT will transmit a single command and receive the corresponding value from the device in response.

To access this feature, you will need a license for unlocking. Kindly contact the license administrator to obtain the necessary license.

The object tree displays filtered state variables that support streaming and polling.

Streaming state variables are highlighted in white, while polling state variables are highlighted in orange.

The default display of state variables in the object tree is set to show “after calculation” data for streaming out. However, if you want to display “before calculation” state variables, select the “Display IN Channels” option. The IN state variables indicated with a blue color and OUT state variables indicated with a red color, with keywords denoting their specified type.

Below table describes the audio objects that support streaming.

Audio Object	Parameter Name	State Variable	Streamable
Level Monitor	Level_Value	Yes	True
Compressor	Attenuation	Yes	True
VNC Control	VNCControlStates	Yes	True
NoiseESt	StreamingParam	Yes	True
AlaControl	AlaControlStates	Yes	True
FFTCalc	FFTCalcState	Yes	True
Ducker	State params	Yes	True
dbXLimiter	States	Yes	True
AudioToControl	AudioToControlState	Yes	True
Limiter	Attenuation	Yes	True

Configure Streaming

If you want to stream streamable state variable, then you can enable Streaming option.

To enable Streaming per core:

1. Open the Device View and select the Virtual core layer of the device.
2. Go the Virtual core properties, select the Streaming checkbox, and set a number of State Variables per core.

Maximum 32 state variables can be configured for streaming.

If you want to perform the operation using non-streamable state variables, then there is no need to enable these options

Memory latency shows the amount of time taken by the CPU from initiating a request for assessing memory to actual reading or writing data at the requested memory.

In AudioworX, the latency of the memory request is abstracted and only measured in relative levels.

• Level 1 – fastest memory available in the platform.
• Level 16 – slowest.

The Memory Latency Editor provides a way to configure latency levels for individual audio object memory records from GTT.

During design time, GTT retrieves memory records for audio objects from the audio library in the following cases:

• While adding an audio object.
• Modifying audio object i.e changing the number of inputs, outputs, number of elements, or selected mode.
• Modifying additional parameter value.
• Upgrading audio object.
• Import of project which defaults to a different dll other than the created one.
• Upgrading device framework to version 17 dll or above.
• The changing target type of Core.
• Changing Sample Rate or Block Length of instance.

GTT supports Memory Latency feature only if the xAF dll version is 17.x.x.xxx or above.

Editing Memory Latency

Memory records will have default latency selected by the Audio Object developer. GTT provides the option to set the latency for every memory record of the audio object in the Memory Latency Editor.

1. Select the device node and click Memory Latency. This opens the Memory Latency window for the selected device. When the Memory window is launched, a multi-level collapsible grid with core, instance, and audio objects will be displayed.

1 – Header, 2 – Column Filter, 3 – Header, 4 – Latency Sector

• Multiple memory latency record selection: You can select multiple records in the memory latency window.
  • To select the specific rows – Hold Ctrl and click on the required rows. This method is useful when you want to preform action on specifics rows.
  • To select a set of row – Click on the first row of the set, hold Shift, and then select last row of the set. This method is most useful when selecting a large number of rows in a range.

Sum of all the selected memory latency record size will be shown as “Total size of the selected records in bytes” in the memory latency window.

“Total size of the selected records in bytes” will be visible only on selecting any memory latency record in the window.

• Reset to default latency level: You can reset the selected records to its default latency level.  Right click on selected records or anywhere on latency grid. A context menu “Reset to default” option will be displayed. Click on the “Reset to default” option, all the selected records of the latency level will be set to default value which is “LEVEL5”. Click on “Save” button and it will be saved into database.
  • To reset records to default latency level for the specific rows – Hold Ctrl, select on the required rows, and then right-click on selected records. A context menu “Reset to default” option will be displayed. Click on the “Reset to default” option.
  • To reset records to default latency level for a set of row – Click on the first row of the set, hold Shift, select last row of the set, and then right-click on selected records. A context menu “Reset to default” option will be displayed. Click on the “Reset to default” option.

• Saving Latency memory: Only Latency can be selected. Other attributes of memory records are read-only. When you click on Save, the Latency for the memory record will be saved.

The Save Button is disabled until a change in latency is detected.

• Send Memory Records to Device: Send Signal Flow will handle sending Memory records to the Device with a specified latency. When the signal flow send is successful, the device will boot up with the memory latency specified.
• Import Export of Project having Memory Record: Memory latency is preserved if the export and import occur on the same xAF dll by version.
  If the dll version changes, Import will generate a new memory record based on the new target xAF dll version.
• Copy Paste of Audio Object or Core Object Containing Memory Latency: If the properties of the source and targets are the same, memory latency is retained in the pasted object.
• CSV Import/Export: You can export and import of memory map to CSV files. The primary operation of this feature is to export memory latency to CSV, adjust memory levels, and then import the updated memory levels back into the GTT. When the memory map form file does not match the one in GTT, GTT will request permission to import only the items that match.

The Global Tuning Tool (GTT) is a software tool developed by Harman International, a leading audio and electronics company. The tool is designed to help audio engineers to create audio post-processing pipelines and tune audio the systems to get the best audio performance.

This is a windows-based tool that is part of the Harman AudioworX product suite. The Global Tuning Tool includes a comprehensive set of core audio functions, a powerful signal flow designer, tuning tool, and the framework for processing the entire audio signal path, enabling easy integration of both HARMAN and 3^rd party technologies.

Key Features of Global Tuning Tool

• Real-Time Analysis: The software provides real-time analysis of audio system performance, allowing engineers to quickly tune the system as per requirement.
• System Optimization: The Global Tuning Tool uses advanced algorithms to optimize the audio system performance, based on the specific acoustics of the venue and the desired sound quality.
• Intuitive User Interface: The Global Tuning Tool features an intuitive user interface, with easy-to-use tools and visualizations, making it easier for engineers to make adjustments and optimize the sound system performance.
• Preset Management: The software includes a library of preset configurations for different types of venues and events, making it easier for engineers to get started and save time during the tuning process.
• Signal Flow Designer: The software allows users to drag and drop audio processing modules such as volume, limiter, filters, and mixers onto a virtual canvas, and then connect the input/output pins of modules to create a signal flow diagram. The signal flow diagram provides a visual representation of the path that an audio signal takes through a system, including where it is processed, amplified, and mixed with other signals.

Relative Topics

• Workspace Overview
• Configurations
• Operations
• Create a New Project
• Create Signal Flow
• Designing Custom Panel
• Working with Parameter Set

Your computer must meet the minimum technical specifications outlined below to run and use Global Tuning Tool.

Table 1: Global Tuning Tool System Requirements

Component	Minimum Requirement	Recommended Requirement
Processor	Intel® Core – i3 processor (4.3GHz)	Intel® Core -i5 processor (1.7GHz or above)
Operating System	Windows 10 (64-bit support)
Memory	4 GB RAM	8 GB RAM or above
Hard disk	20 GB of available hard-disk space; additional space is required for installation	50 GB or above
Display Resolution	800 x 600 display	1920 x 1080 display
Graphics	Driver Version – Supported Intel, GPU version greater than 30.0.100.x. 1.5 GB of GPU memory	Driver Version – Supported Intel, GPU version greater than 31.0.101.3959. 4 GB of GPU memory for 4k displays and greater
Browser	The current version of Microsoft Edge, Internet Explorer, Chrome, or Firefox. Internet connection is necessary for GTT registration, license activation, membership validation, and access to online services.

Currently, the Global Tuning Tool is not supported on macOS systems.