Category: GlobalTuningTool

The File Controller allows you to send any type of file(s) from GTT to the device. It does not restrict file type or extension and allows file sizes up to 4GB.

The audio object is responsible for validating that the file being loaded is of the correct type. The file controller does not check the IDs used in audio objects.
Developers and system designers must verify the correct file type when using the file controller. For example, a configuration file should not be loaded into a file player, or a WAV file should not be used as an audio object configuration.
The audio object will return an error state if any invalid file type is detected, and this error must be handled appropriately.

The following are the options available in the file controller.

• Select Workspace
• Add Files
• Delete File
• Replace File
• Send to Device
• Verify Checksum
• Export Options
• Export and Import File Controller Data

The file controller feature is available from W release onwards.

Select Workspace

The Select Workspace option allows you to browse and select a workspace or root folder from the local directory. Once the folder is selected, you can add the respective audio files.

Also, you can copy and paste the path of your workspace folder in the “Workspace” field.

Add Files

Once the workspace folder is selected, click on the “Add” to launch file browser. You can navigate to the respective folder and add audio files (.pcm/.wav) in file controller from the workspace folder.

The file browser will open the workspace folder by default.

After adding the files, the following details of the files will be displayed in the file controller.

• File ID:  This ID is generated from GTT; its range is from 1 to 254.
• File Name: If the file name is exceeding length of 15 characters (including file extension), GTT will trim it to 15 characters.
• Path: Relative path of file, based on the workspace folder selected.
• Size: Size of the file in KB. If the file size is less than 1KB, the size will be displayed in bytes.
• Checksum: Checksum calculated using file content.

In case if you add any file from a non-workspace folder, the following prompt will appear.

• Copy: To create a duplicate copy of the file within your workspace folder.
• Move: To relocate the selected file to your workspace folder, removing it from its original location.
• Cancel: To stop the ongoing operation.

This facilitates the sharing of project files and files added to the file controller by ensuring that all files added to the file controller are present in the workspace folder.

The number of files added will be displayed in the File Controller.

A maximum of 254 files can be added in the file controller.

Once after adding files to the file controller, on relaunching the file controller, if any file is not found to load, the error is indicated by showing “0 Bytes” size and invalid checksum as below,

Delete Files

The file controller offers two ways to manage your files:

• Click “Delete All” to remove all files at once.
• Use the “Delete” button for each file to remove them individually.

The delete operation will delete the file entry from the file controller, not the file from the file system.

Replace File

You can replace file in the file controller. Click on the “Replace” button, this will open the file browser, allowing you to select the new file you wish to use.
Also, allows you to reuse the file ID for different files easily.

Send to Device

The “Send to Device” allows sending the loaded files in the file controller to the device.
While sending files to device, the file map will be sent to device first. It contains metadata (number of files and sizes) about the files being sent.
If it fails to send the file map, the files will not be transferred to the device.

Verify Checksum

The “Verify Checksum” feature helps ensure you’re working with the correct files. The Verify Checksum option uses the file content checksum to confirm that a file with the same file ID is present on the device.

Use the “Verify All” button to check all files at once, or the individual “Verify” button in each row for specific files.

	Indicates the default state is “Not Verified”.
	Indicates when the file is found on a device with the same file ID. Also, when the file is sent to the device successfully.
	Indicates when the file is not found on the device with the same file ID.

Export Options

To export files from the file controller, the following options are available.

• Export File Map
• Export Audio Files
• Export All Files

These options will be displayed on clicking the “Export Options” button.

Upon selecting any of these options, a folder browser will open, allowing you to select the destination folder.

• Export File Map: This option is to export the file map and human-readable file map.
  
• Export Audio Files: This option is to export audio files added in the file controller.
  
• Export All Files: This option is to export all files, including the file map and human-readable file map.
  

Export and Import File Controller Data

The selected workspace and metadata of loaded files in file controller can be exported through project file (.gttd). This metadata includes file ID, name and relative path of file. After importing the gttd file with file controller data, if the workspace folder is not found, files will be displayed with “0 bytes” Size and invalid checksum as shown below.

You can select workspace folder with same sub folder structure to automatically reload files loaded in file controller. The files should be present in same hierarchy and name.

The Tools group allows you to monitor all services running on GTT, view the event and xTP logs, and perform the sound card configuration.

• Service Monitor
• Event Log
• xTp Log
• Soundcard Setup
• Microphone Setup

Service Monitor

Global Tuning Tool provides a comprehensive set of tools for monitoring the following services:

• SQL Server Service
• Measurement Service
• Harman Audio Library 32
• Harman Audio Library 64
• AI Module

The choice of tool depends on the type of monitoring or tuning to be done and the events to be monitored.

Event Log Viewer

The Event Log window tab shows events that have occurred within the Global Tuning Tool and on connected devices. The log may be utilized by individual devices to perform certain operations. You can also use the logs for troubleshooting.

The Event Log Indicator will notify you in real-time as events occur.

xTP Log Viewer

Any error on the device is displayed in GTT in the XTP viewer and Event log.

The xTP-Viewer has two sections:

• Left side section: Display message flow view and show raw data of several messages.
• Right side section: Detailed view of a selected message on the right side (is empty if message interpretation is not implemented up to now for the specific message).

Sound Card Configuration

The Sound Card Setting allows you to configure the host API (audio driver), device, sample rate, block length, and the master output for the audio processing. Based on device selection, input and output channels are available for configuration.
Using “Master Output” you can set master and device output modes for speaker configuration in the Measurement Module.
The configured sound card configuration is used throughout the RTA and Measurement Acquisition features.

Before you start the Measurement wizard or set the “Sound In” and “Sound Out” devices in the RTA, make sure you have configured sound card settings like Host API (Driver Protocol), Device, Sample Rate, and Block length of the sound card.

On the “Streams” section list of available channels for input and outputs is displayed. Those can be routed to any physical sound card channels. All devices are available as two-channel devices. The stream area displayed the Channel column, indicating the mapping of Sound In or Sound Out devices to specific channel pairs.

In the example above, the mapping is configured as follows:

• SoundIn1, SoundIn2: Analog (1 + 2)
• SoundIn3, SoundIn4: Analog (3 + 4)
• SoundIn5, SoundIn6: Analog (5 + 6)
• SoundOut1, SoundOut2: Analog (1 + 2)

GTT supports four host APIs: MME, Windows DirectSound, ASIO™, and Windows WASAPI.

Host API	Description
MME	This is the standard Windows audio API. It allows the operation of multiple audio devices at the same time. Sample rates are handled by the operating system. Can be set to any sample rate. If the sample rate of the physical audio device is different, then the OS takes care of the sample rate conversion. This mode is recommended if multiple devices are running at the same time, e.g measuring with a USB microphone while playing back generator signals with an internal sound card. For MME, it’s required to select input and output devices separately, and all selected input and output devices support a maximum of 2 channels.  Recommendation: Keep the block length at the maximum value of 4096 and the sample rate at 44.1 kHz or 48 kHz.
ASIO™	This API is used with multi-channel sound cards. It enables low latencies and ensures that all input and output channels are in sync. Depending on the latency requirements of the audio signal processing provided by a loaded plugin (future feature) the block length can be reduced down to 64 samples. The RTA sample rate setting has to be equal to the audio device driver sample rate. It’s not required to select separate input and output devices for ASIO™.
Windows Direct Sound	This Windows API has improved latency compared to MME as it has more precise buffer control. Sample rate mismatches are handled by the operating system, similar to MME. Input and Output devices are to be selected separately, and they support a maximum of 2 channels.
Windows WASAPI	Is Microsoft’s most recent API. Latency has improved compared to MME and Direct Sound. This API does not support an output-only selection, as it requires a clock signal from the input. The operating system does not handle sample rate mismatches; instead, the user is responsible for ensuring that the sample rate of the physical device aligns with the RTA sample rate. Input and output devices must be selected separately, and both support a maximum of two channels. The following are the limitations of Windows WASAPI Bluetooth devices are not supported. For loopback devices, please ensure that the input device and output device are the same, with the input device name appended with ‘Loopback’.

 – It is recommended to use an ASIO™ sound card instead of Windows drivers if possible.
– When using Windows drivers, it is advised to use a block length greater than 1024 in order to avoid the noise distortion effect and high cpu load issues.
– The setting for the sample rate does not change the actual setting in the sound card driver. The alignment of the sample rate setting has to be ensured by the user.

Supported Soundcards
 -Fireface® UCXII
– TASCAM® US16-08
– Fireface® UC
– Ultralite® AVB, 18 x 18 USB/AVB Audio Interface (Motu)
– Focusrite® – Scarlett 2i4, 2nd Gen
– Creative Soundblaster® X4

During sound card configuration, channel streams should be automatically assigned with available input and output devices if the user has not already assigned any sound input or output devices to RTA Channel streams.

If the user attempts to unassign all sound card channels, a toast message should be displayed with a message like “You have unassigned all sound card channels. This will disable the internal IVP processing, because no lock master is available. Please assign at least one channel pair to re-enable the processing”.

If there are any modifications to the Sample Rate, Block Length, or Host API, it is necessary to reconnect the device Sound card settings impact in RTA

Microphone Setup

The Microphone Setup allows the calibration of microphones and assigns a mic compensation file for each microphone. The configured values will be applied across the GTT wherever microphones are involved, such as in the RTA and measurement modules.  This view can be accessed from the “Microphone Setup” button in the “Design” ribbon tab.

Every microphone element (1 or 6 microphone array) must be calibrated separately. The central element of the calibration menu is the list of microphones contained in the current microphone element.

The list has the following columns:

• Microphone: The number of the microphone within the element.
• Sound-In: The stream channel number is configured with the physical channel of the sound card in the Sound Card Setup view. Duplicate channel assignments to microphones are indicated in orange.
• Previous value: Offset measured during the previous calibration, displayed as a comparison.
• Current value: The offset measured during this calibration.
• Compensation File: This is the File provided by the mic manufacturer, which will be used for magnitude curve correction. The current supported format is a .txt file. The supported file format is attached here: M4261-Microphone-4881.
  

The type of the microphone element and the currently selected microphone within the element are indicated using an icon (green rectangle).
The soundcard and the selected microphone is displayed (yellow rectangle).
The reference sound pressure level of the calibrator can be selected in the upper right (red rectangle).

Multiple microphone carriers can be added or removed (purple rectangle). The currently selected/configurable microphone carrier is highlighted in blue.

To calibrate a microphone:

1. Choose the Microphone carrier and select the microphone you want to calibrate.
2. Assign the channel number. Auto-completion will assist in assigning available incremented channels.
3. Attach the microphone to the designated channel on the calibration device. This will connect the calibrator to the microphone itself.
4. Select the appropriate reference sound pressure level (SPL) for your calibration.
5. Click on Calibrate. The calibration process should take approximately 2 seconds.
   While calibration is running, observe the level meter (indicated as a black rectangle) for activity on the chosen input channel.
   The calibration will result in an offset value (displayed in red in the “current value” column).
6. Click on Apply to accept the value (which will turn the value green) or repeat the calibration process if the value is not satisfactory.
7. Click Apply confirms the calibration value, turns it green, and automatically selects the next microphone that needs calibration (if applicable).

Repeat the procedure for all microphones in the array.

Individual microphones can be recalibrated at any time. Once all calibration offsets are applied, the menu can be closed using “Ok”.

When configuring multiple microphone carriers, you can easily switch between them, and any changes you have previously configured will be automatically applied.

For any changes in the mic row, the user must click Apply to save the changes before clicking OK.

Import: The “Import” option allows you to import an existing calibration and compensation file path. This sets the current value for all microphones to the stored offsets. The values must be applied. Settings will be imported to the selected microphone carrier.

Export: Using “Export,” you can export a full set of applied calibrations along with the compensation file path to disk. Settings will be exported from the selected microphone carrier. The exported JSON files will contain the Channel Number, Offset, and mic compensation file of the calibrated microphones.

On the Device Synchronization dialogue box, you will get the below option.

• Send: Sends tuning data or control data from GTT to target device.
• Receive: Receives tuning data or control data from target device to GTT.
• Not_Sync: No exchange of tuning data between target device and GTT.

The Device Synchronization dialogue box also includes two check boxes.

• Include state data while receive.
  • If this option is checked and “Receive” operation is selected – The state data will be received from target device along with tuning data to GTT.
  • If this option is not checked and receive operation is selected – Only tuning data will be received from target device to GTT.
  • Checkbox value will be persist per device in GTT.
• Include control data while send and receive.
  • If this option is checked and “Receive” operation is selected – The control data will be received from target device along with tuning data to GTT.
  • If this option is not checked and “Receive” operation is selected – Only tuning data will be received from target device to GTT.
  • If this option is checked and “Send” operation is selected – Control data will be sent from GTT along with tuning data to target device.
  • If this option is not checked and “Send” operation is selected – Only tuning data will be sent from GTT to target device.
  • Checkbox value will be persist per device in GTT.

The selected data is stored and can be transferred using a .gttd file format for export and import purposes.

Switching off “Include state data while receive” during receive operation might impact synchronization of some audio object panels.

Sending or receiving data is indicated by a progress window along with a percentage of completion of sending or receiving data. The progress bar will close automatically once the send / receive process is completed.

The progress bar window title will be either “Sending data” or “Receiving data” depending on the functionality you have selected.

You can also perform “Send” and “Receive” operation from ribbon bar. To achieve this, the device should already be in a connected state. Following are the options provided as part of context menu.

• Send Tuning Data: Send tuning data will only send tuning data from GTT to target device.
• Receive Tuning Data: Receive tuning data will only receive tuning data from target device to GTT.
• Receive State Data: Receive state data will only receive state data from target device to GTT.
  

If EOC object is present in the signal flow, Progress window will not show the real progress.

In case there is issue with data transfer between device and GTT. a warning message appears asking you to abort or ignore the operation. You can check the device setup and retry the operation.

While sending the data from GTT to connected device, if there is a data transfer issue between the device and the GTT.  A warning will appear asking whether to abort the operation or ignore the error and continue.
You can troubleshoot the issue by verifying your device configuration and then retry the operation.

While sending the data from GTT to connected device, if there is a version mismatch between GTT and the connected device. A warning message will appears asking whether to continue or abort the operation.

Removing Device Instance

1. Select device and click on Delete. A warning message will be displayed.
2. Click OK to remove the device instance from the project.

Removing a device instance carries significant consequences, including the deletion of all associated data such as tuning and signal flows.

Steps to connect a Device.

1. Navigate to the IVP RTA tab and select Advanced from the ribbon bar. This opens the RTA Settings dialogue box.
2. On the RTA Settings dialogue box, select the Plugins tab, and click on the folder icon to browse the xAF library path.
3. Set the port number under the Port box.
4. Enable the Bypass option (optional), if you prefer the input to be passed directly to the next plugin or output without undergoing any processing.
5. Click on Apply. The number of inputs, number of outputs, and plugin type will be automatically updated based on the provided signal flow. Similarly, you can set remaining plugins.
   Click on Reset (optional), to set back all the values in a specific row to their default values. Now you can configure the analyzer settings like the plugging host, Sound Card Settings, Generator Settings. For more information, refer to RTA Settings.
6. Switch to Device Designer tab and click on Connect Device to connect to device.
   
7. On successful connection with device the Device synchronization dialogue box will appear.

In GTT you can open multiple signal flow design simultaneously and tune the audio objects associated with different xAF Instances from either the same or different devices.

To open multiple signal flow design:

1. Right-click on any of the Xaf Instance and click Open signal Flow for Tuning.
   

This opens the signal flow designer in a separate floating window. Similarly, you can open multiple signal flow designer in a separate floating window and perform tuning operations.

The signal flow designer window can be identified by its title bar, which displays the name of the respective device associated with that window.
Device name -> Virtual core name -> xAF Instance name.

The Signal flow designer floating windows will be in read-only mode. In the read-only mode, you can search and select audio objects. Although you cannot make any modifications to the signal flow itself, you can navigate through the audio objects and tune them.

On the read-only signal flow designer floating window, double-click on the audio object to view their properties and launch corresponding panels. This functionality enables you to perform tuning operations on multiple signal flows simultaneously.

You can either copy partially or complete signal flow from read-only mode and then paste it into editable signal flows.

Tuning Compound Audio Object in Multiple Signal Flow Design

If the signal flow contains instances of compound audio object (CAO), you can open the signal flow of the compound audio object by selecting it from the context menu. This allows you to perform tuning on the inner audio objects of the CAO as well as apply tuning data specific to the preset type of the compound audio object.

When device is connected, then processing state can be set from all opened signal flows.

When probe-points are enabled for the core, you also have the option to add, remove, enable, or disable probe points.

To modify the properties of the device core or core object, it is necessary to close any open signal flows associated with them. A confirmation message will appear and selecting “Ok” will close all signal flow windows related to the chosen device. If “Cancel” is clicked, the property change will be aborted.

FFT Analysis capabilities are also available in the streaming window, wherein the FFT analysis of incoming audio signals is undertaken in real-time, depending upon the block size, additional calculations, etc).
The “Display Type” selection under the General tab provides the option to switch between Time and Frequency domain display.
When the Display Type is set to “Frequency Domain”, the Spectrum functionality of Streaming can be viewed.

In Spectrum view the X-axis ranges from “0 to Sampling Frequency / 2”, and Y-Axis ranges from “0 to -90 dbFS”.
Providing the correct sampling frequency is the responsibility of the audio engineer, and it should match the sampling frequency of the streaming state variable.
The Spectrum properties such as Block size, Sampling Frequency, Smoothing, and Averaging can be configured according to your requirements.

The variable “MaxWinSize” determines the maximum window size for smoothing in the Spectrum functionality. It has three options: Low (20), Medium (40), and High (1000). Choosing a larger number will result in a smoother curve.
For instance, if you set the limit to 500 Hz, all bins in the upper frequency range will be smoothed by averaging a window width of 500 Hz.

Example: Smoothing set to Off.

Example: Smoothing set to Low.

Example: Smoothing set to Medium.

Example: Smoothing set to High.

The streaming data can be recorded and stored in a file using the record button available. There are two supported file formats.

• Csv file format (.log)
• PCM file format (.pcm)

The default recording folder is C:UsersUsernameAppDataLocalHarmanGTTPCMStreamingLogs. To change the folder location for the recording, you need to click on “…” button.

Record Streaming Data in csv format

The csv format logs are supported by both polling and streaming state variables. Once you click on the record button, it opens file explorer to choose the location and file name for storing streaming data.

The default file format for storing streaming recordings is CSV.

The recording process is indicated by a continuously blinking button, indicating that streaming is currently being recorded. To stop the recording, simply use the same button.

During the recording process, adding or stopping streaming is not permitted.

The file stores the following information in the streaming data:

• Buffer Size and Update Rate.
• Streaming variables names with comma (,) separator.
• Streaming variable data with comma (,) separator and if any variables have an array of data it is separated by spaces.
  

Record Streaming Data in PCM format

The PCM format recording only supported by streaming state variable. Once you click on the record button, it opens file explorer to choose the location and file name for storing streaming data.
Prior to commencing PCM format recording, you must ensure the following conditions are met:

• The State Variable used for streaming is of a streamable type.
• PCM format is selected as the file format.
  

The recording process is indicated by a continuously blinking button, an indication that streaming is currently being recorded. To stop the recording, simply use the same button.

During the recording process, adding or stopping streaming is not permitted.

Each state variable’s streaming data is stored in a separate file containing raw data, which can be imported into tools such as Audacity for further analysis or processing.
A date-time stamped folder is automatically created for each recording under the root folder. Inside this folder, a separate file is generated for each state variable being streamed.

File Name Format: {state variable Name} {Channel Name} {Audio Object Name} {sample rate} {duration in seconds}. pcm

Example of sample recorded file.

Pause and Play Streaming

The streaming data can be paused by using the pause button. When the stream is paused, it indicates that GTT Tool stops receiving data from the device internally, and no bandwidth is utilized during this pause period.

To resume streaming, the same button can be used, and it will convert to a play button once data is paused.

It is not permitted to add new state variables or change the update rate while the streaming is paused. However, stopping an active state variable is allowed.

Ensure that the following requirements are met before beginning the streaming process.

• Make sure the device is connected to GTT.
• If you want to stream streamable state variable, then you can enable Streaming option, for more details refer Streaming.
• While performing streaming make sure the parameter supports streaming. You can verify this by opening the state variable explorer and confirming that the “Category” is set to “state” and “Streamable” is set to “true” for the parameter.
  

To start live streaming, follow the below steps:

1. Open GTT project, click on the Streaming option from the Device Designer tab. This opens the streaming window.
2. On the General option, set the Display Type, Update Rate, and Buffer Length.
   The Update Rate will be applied to all live streams, and Buffer length (the maximum streaming data that can be stored) can be changed any time during the live streaming.
   
3. Expand the state variable you want to stream and drag-drop the variable from the object tree to graph. This starts live streaming of the variable.
   Active streams can be matched with the curve on graph by the colors of the curve and the rectangular block next to the state variable.
   
   The graph can be zoomed on both the x and y axes by scrolling.
4. Click on the Stop option, if you want to stop streaming of the variable.

You can open multiple streaming windows for a device and stream on multiple devices. However state variable can be streamed in only one window at a time and not in multiple window.

If the “Streaming” feature is disabled for any core, streamable state variables (push mode) will be excluded from the available state variable list for that core.

Viewing Streaming Data in Custom Panel

You can view live streaming data in a custom panel. Map the streaming state variable address to any control on the custom panel and start the live streaming from the streaming window. Then, launch the custom control panel.

The live streaming of the state variable will be displayed on a custom panel.
Only the current value of the state variable will be displayed on the custom panel.

Search Variable

You can search for a specific variable from the object tree in the Streaming window and then drag and drop it onto the chart.

To find a variable in the Streaming window, enter at least two keywords of the variable in the search bar. The GTT will use these keywords to search and display the filter results in the object tree.

Limitations in Streaming

Below are the limitations associated with streaming.

• Last selected update rate will be applied to all active streams.
• The update rate is not configurable, you need to select one of the predefined values from the drop-down menu. It is not possible to enter a custom update rate.
• Maximum buffer length allowed is 65536.
• Streaming state variables are read only.
• Zooming the graph with more than 8 active streams in parallel may cause performance issues.

Opening multiple streaming windows may result in increased CPU load, potentially leading to performance issues. To avoid such concerns, you can configure the option to receive notifications and restrict streaming when CPU load exceeds a certain threshold.
By default, the maximum allowed CPU load is set to 100%. However, you can configure restrictions at specific load levels by modifying the “MaxAllowedCpuLoadForMonitoring” value in the configuration file.

The option menu allows you to configure various settings in GTT, such as the general settings, project settings, custom panel grid settings, native panel, and event log settings.

You can configure the following settings.

• General Settings
• Project Settings
• Custom Panel Designer Settings
• User Interface Settings
• Tuning Data Settings
• Native Panel Settings
• Event Log Settings

General Settings

In the general settings dialogue box, you have the option to customize measurement settings, venue menu settings, explorer settings, address settings, and system conversion settings.

General Settings	Description
Measurement Settings	Measurement Session Raw Data Folder: Specify a desired location where you would like to store the raw data for the measurement session. Predefined Stimulus Signals Folder: Specify a desired location where you would like to store the predefined stimulus signals.
Venue View Settings	– Show Warnings: If enabled, all device alerts will be displayed in the venue.  – Show Incompatible HiQnet App Warning: If enabled, a warning dialog will appear upon startup if another HiQnet application is already running.  – Load Previous File On Startup: If checked, the venue file that was last used or saved will be automatically loaded upon startup. If unchecked, the venue file needs to be loaded manually (default)
Explorer Settings	If enabled, a drop-down arrow appears next to discovered devices in the venue explorer. When the arrow is clicked, the complete device information is displayed.
Address Settings	– Display Addresses in Hex. If checked, displays device and object addresses in hexadecimal. If unchecked, it displays the device and object addresses in decimal.  – Display Object Addresses as Octals. If checked, it displays the object addresses in three period-separated values. If unchecked, it displays object addresses as a single value.
System Conversions	This option makes all instances of parametric EQ displayed either as bandwidth in Octaves or as bandwidth as Q at the user’s discretion. Switching from one option to the other will be on a global basis for the entire application.
Advanced	– Increase Window Handle Limit to Maximum: This option allows you to set the handle limit to its maximum value (checking the checkbox), this will increase the maximum number of controls/planes allowed by the operating system. By default, this option is unchecked. If GTT exhausts its handle resources and is unable to launch a panel, it will notify you of the issue and prompt you to close any unused panels in order to free up resources.  – Select wiring controls in real-time when using lasso selecting: When using the lasso to select objects, having this box checked allows the selection of wiring. This option makes all instances of parametric EQ displayed either as bandwidth in Octaves or as bandwidth as Q at the user’s discretion. Switching from one option to the other will be on a global basis for the entire application role.  – Error Reporting: This option enables GTT to send important error information automatically to Harman. On the Harman Crash Reporting Disclaimer dialogue box, check the “Send important error information automatically to Harman” option. This feature will send application and computer information to the Harman GTT team in the event of an application crash. Uncheck the checkbox if you do not want any information sent.

Project Settings

In Project Settings, have an option to include measurement sessions in Project, to select Project Data Folder, and Decimal Separator for Exported files.

Project Settings	Description
Project	In the project settings, you have the option to designate a folder where you would like to store the project file. If you want to exclude Measurement Session data from the project export, uncheck the “Include Measurement Sessions in Project Export” option.
Decimal Separator for Exported Files	You can select between a dot or a comma to specify the separator of any quantity for the files you export in GTT. Currently, this option is only supported for traces exported in .txt and .txtrclist in the RTA module.

Make sure to configure the project settings prior to initiating the export process.

Custom Panel Designer Settings

In GTT, you can modify the settings for the custom control panel design view, such as the grid, snap lines, and control transparency configuration.
However, it is important to note that once you make changes to these settings, you must close any open custom control panel designer and reopen it for the changes to take effect.

Custom Panel Design Settings	Description
Grid Layout	The design grid allows you to arrange controls relative to specific marks on the design view of the Custom Panel. Show Grid: If checked, it will display the design grid. This feature is overridden with the “Snap Lines” feature below. Snap to Grid: If checked, it will snap design objects to the design grid (if selected). Grid Size: It is the distance between grid lines (in pixels); x = horizontal, y = vertical
Advanced	Enable Control Transparency Control transparency gives the controls on Custom Panels transparent backgrounds. While this option makes the control panel designer more attractive, it may slow the computer system performance significantly to process all the graphics. If you are having problems with the graphics building too slowly on the screen, uncheck the box “Enable Control Transparency.” While they will show up as overlapped on the Custom Panel designer, they will show up as transparent on the Custom Panel if the background is transparent (defined in Control Properties).

User Interface Settings

In these settings, have an option to select the Font Size.

User Interface Settings	Description
Font Size	Choose the desired font size: Small (12 points): Select this if you prefer a smaller font. This is the default setting. Medium (16 points): This size is suitable for a moderate, more comfortable reading experience. Large (20 points): Choose this if you prefer a larger, more readable font. Currently, font size changes will impact only in the Central Viewer Browsing and Permanent curve name font sizes.
Windows Setting	– Show all sub-windows on top: Check this option to ensure all sub-windows are always visible above the main window.

Tuning Data Settings

Tuning Data	Description
Retain Tuning Data	By default, tuning data of the Audio object will be lost when the Mode, Additional Parameter, or Number of Elements property changes in the signal flow. To retain tuning data in the above cases, please check the appropriate option based on your needs.

Native Panel Settings

In these settings, have an option to set the delay step size.

Event Log Settings

In these settings, have an option to set Event log view, view update rate, and see Event log archive, and can customize warnings.

Event Log Settings	Descriptions
Event Log View	Clear Log at Startup: Enabling this option will result in the event log being automatically cleared every time GTT is started up. Maximum number of events in view: Sets the maximum number of events shown in the event log window. View Update Rate: You can configure the update rate to be either instantaneous or delayed. View Archive: Brings up the “Event Log Archive” dialogue box. The Event Log window tab shows events that have occurred on HiQnet devices. The log may be utilized by individual devices to perform certain operations. You can also use the logs for troubleshooting. The Event Log Indicator will notify you in real-time as events occur. You can also group information by heading. Click and hold on the heading and drag it to the top, just below the log file to the “Group(s)” option. The screen will now display the heading you selected. To remove the grouping, click and hold on the heading and drag it off the “Group(s)” option. The Event Log Archive is a store of the Event Log from when the application was opened.
Miscellaneous	Disable Logging: Turns off the Event Log. Capture BSS Logfiles: Include the Log Files that have been saved in the BSS devices in the Audio. Customize Warnings: This window allows you to set the minimum warning priority level, which warning types you want to receive a warning from, and which category you want to receive warnings from.

The File Menu on left side of the home screen provides following additional options:

• Export Project: To export a project, for more details refer to Export Project.
• Import/Export Project Settings: To export and import project settings of RTA, Central Viewer and Measurement Module, or more details refer to Import/Export Project Settings.
• Clone Project: To clone a project, for more details refer to Clone Project.
•  License Information: Displays GTT license status. Also, you can renew your GTT license., for more details refer to License Information.
• Options: To configure global tuning tool settings, for more details refer to Application Options.
• About: To know Global Tuning Tool version, release type, and license status.
• Help: To open AudioworX documentation.

Exporting a Project

The Global Tuning Tool allows you to export the signal flow design of the project. This capability enhances your workflow and ensures easy sharing and collaboration.

The Export window includes an option to save the file to a specified path and filename, as well as an option to include project dependencies in the gttd file. By default, the “Audio Library” option is selected. You can unselect or select audio library and measurement data options. These options will only appear if they are available in the project.

Steps to export the project:

1. Go to the Home screen, open the project, and click on the Export Project option.
   
2. On the Export Project window, click on the browse, navigate to the desired location, and then click Save to save the project file.
3. Select the project dependencies Audio library or Measurement data option, if you want to include them in the project and click Ok.
   The Project export will start.
   A message will be displayed after a successful export.

The project file is stored with the file extension *.gttd along with selected project dependencies.

Make sure to provide the path before clicking OK, as this will help avoid any errors and ensure a successful process.

The Audio Library and Measurement Module raw data will be exported as project dependencies in the gttd file, with no additional files included.

Export Project with Measurement Sessions

When a project is exported, by default the project will be exported with measurement sessions and session associated raw data will be stored in the {projectname}.mmdata file in the same destination folder.
If you want to exclude measurement session data from the exported project, make sure to configure the project settings prior to initiating the export process.

Steps to exclude measurement sessions from the export project:

1. Click on the File menu and select Options.
2. In the Application Options dialog box, click on Project Settings, and uncheck Include Measurement Sessions in the Project export / clone options.
3. Click Done to save the change.

From the X release onwards, selecting the Measurement Data option in the Export Project window will export the associated raw data from the measurement session. No .mmdata file will be generated.
Selecting the Measurement Data option will export the data into a gttd file. Project settings are only applied when cloning the project, as shown in the screenshot below.

Import and Export project settings

The Export and Import project settings allows you to share project settings of certain components like RTA, Central Viewer, Auto EQ, and Measurement Module etc to other team or to a end user.

• Export Settings: Allows you to export RTA, Central Viewer, and Measurement Module settings of a project. The settings will be exported as a *.gttdSettings file.
• Import Settings: You can import the previously exported project settings (*.gttdSettings file) after creating a project and wants to replicate the same project environment with the same settings.

During the import process, you can optionally choose to import component-wise settings.

Clone Project

The clone project feature allows to create copy of the project, which includes or excludes the measurement session data.

If you want to include or exclude measurement session data in the cloned project, make sure to configure the project settings prior to initiating the clone process.

Follow the below steps to create a clone of the project:

1. On the GTT home window, open the desired project that needs to be cloned.
2. Click on the File menu and select the Clone Project option. This action will start cloning the project and copy all the data from the opened project.
   
3. Once the clone completes the cloned project will be opened.

By default, the measurement sessions will be included in the cloned project.

Include or Exclude Measurement Sessions while Cloning

While cloning you can include or exclude measurement sessions. Additionally, you can store the session-associated raw data in the {projectname}.mmdata file in the same destination folder.

Follow the below steps to configure the project settings:

1. Click on the File menu and select Options.
2. In the Application Options dialog box and click on Project Settings.
   – If you want measurement sessions to be included in the cloned project, select the Include Measurement Sessions in the Project clone options and set the project folder.
   – If you don’t want measurement sessions to be included in the cloned project, unselect the Include Measurement Sessions in the Project clone options.
   
3. Click Done to save the change.

License Information

You might see the “Renew GTT license” message on your GTT platform home page or dashboard. This happens due to an upcoming expiration date of the GTT license.

Click on License Information menu to see the AWX – GTT subscription license status. The license information window has a Renew Now button which enables you to extend the validity of your GTT license, and you may also request new features as part of the renewal process.

The system will start downloading the latest license. The GTT platform notifies you after a successful license renewal.