Category: GlobalTuningTool

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.

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.

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.

GTT provides an option to use file-based devices. A default custom file with file extension .deviceInfo  available under Devices folder (C:Program FilesHarmanHarmanAudioworXtoolsGTTDevices).

Also, you need a .ddf  file, which you can keep under the Custom Device folder.

You can create a .ddf  file in GTT. Once you have created a project, click on the Export option, and select  DDF Data. Now browse to C:Program FilesHarmanHarmanAudioworXtoolsGTTDevicesCustomDevice location and save the file.

Once the above files are placed in the folder. The custom device will be shown in the Devices view tab in GTT. You can drag-drop this device into the venue explorer. This is similar to any other device created inside GTT.

This file-based device has some limitations. In the normal device (created inside GTT), double-click will open the signal flow designer. But this is not the case with custom devices. This device is not stored in a database. So, the signal flow designer will not be opened.

It is possible to create a custom panel and use the device. However, because it is a file-based device, it is not stored in the GTT database. To reuse the project, export it as a file and then import it whenever needed.

The custom devices created will not be part of the existing project as the devices displayed in the location are retrieved from the GTT database, and custom devices are not stored in the GTT database.

Regardless of the sorting order, the Add Device Dialog always displays the Custom Device as the top option if it is available.

The Custom Device is loaded when the application is launched. Therefore, if any changes are made to the associated .DDF file after launching GTT, it is necessary to relaunch GTT and add the custom device again to ensure the modifications are reflected.

The source for the Custom Device is the .DDF file, which launches the State Variable window. This window displays the audio object definitions that are contained within the associated .DDF file and these definitions can be utilized during panel designing.

When working with multiple xAF audio library versions (DLL version) in GTT, any new device added to the project will be automatically linked with the default audio library version (DLL version).

If the linking of existing devices with their respective DLLs was done in the “O” version of GTT or if the DLLs were loaded before the project was imported to GTT, those devices will still function with their respective DLLs without any issues.

On the property view of the device instance, you can see the audio library version of the respective device.

Changing Device Audio Library

To change the audio library version of the device:

1. Select the device instance in the device view. This opens the property view of the device.
   
2. Click on the Audio Library Version, select the desired DLL version from the drop-down, and click Save.
   

The device will start working with the updated DLL version.

If a device has a signal flow with audio objects created in a previous version, compatible audio objects are automatically upgraded.

Once you update the DLL version, if any non-compatible audio objects are there, it will be highlighted in blue and the warning displayed in the compiler report.

You can fix the non-compatible audio objects in the signal flow. Right-click on the highlighted audio object and select upgraded audio object from the context menu.

Change of association DLL for one device will not impact other device instance.

xAF Audio Library Use Cases

While importing a project file in GTT, make sure the xAF audio library version is already available in GTT.

• Use Case 1: When you import a project, if the xAF DLL associated with the project is already loaded in the GTT audio library. Regardless of whether the associated DLL is the default library or not, the project will import without error or warning. Later, you can switch to the latest DLL.
• Use Case 2: While importing a project, if the xAF DLL associated with the project is not loaded in the GTT audio library, then the project will be linked to the default xAF DLL in GTT.

When you open the project after importing it, a message will appear. This displays the default audio library of project and details of previous audio library that is associated with the imported project.

Once you open the Signal Flow Designer of the imported project, the below message will appear every time you open the Signal Flow Designer of the project.

You can get rid of the message by using the methods listed below.

• Once you open the Signal Flow Designer of the project, go to the non-compatible audio objects, which are highlighted in blue. Right-click on the highlighted audio object, select upgraded audio object from the context menu, and save the changes. This will upgrade the non-compatible audio objects in the project.
• The message will not appear if you import the previous DLL (which is associated with the imported project) into the GTT audio library manager.

Use Case 3: While importing a project, if the xAF DLL associated with the project is not loaded in GTT audio library and the default xAF DLL is not compatible. An error message will be displayed, and project import will be cancelled.

Use Case 4: After importing a project and switching to a different audio library, you may encounter missing audio objects in the Signal Flow Designer. These missing objects will be highlighted in red, and an error message with a list of the missing audio objects will be displayed. The same error message will also be included in the compiler report.

In order to resolve the error, it is necessary to delete the missing audio object from the Signal Flow Designer. Once the missing audio object is removed, the error will be cleared.

Additionals options on home screen:

• Export Project: To export a project, for more details refer to
• Import/Export Project Settings: To export and import project settings of RTA, Central Viewer and Measurement Module, or more details refer to
• Clone Project: To clone a project, for more details refer to
• Renew License: To renew a global tuning tool license, for more details refer to
• 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 OK 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 OK to save the change.

Renew License

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.
The “Renew license” operation enables you to extend the validity of your GTT license, and you may also request new features as part of the renewal process.

Follow the below steps to renew the GTT license:

1. Click on the File menu and select Renew License.
   

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

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

General Settings

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

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.
Venu 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, the displays device and object addresses in hexadecimal. If unchecked, the displays the device and object addresses in decimal.  – Display Object Addresses as Octals. If checked, the displays the object addresses in three period-separated values. If unchecked, the 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 it s 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 contThis 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.rols.  – 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

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” options.
Decimal Separator for Exported files	You can select between a dot or 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.

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

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 change 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

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.

Event Log Settings

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 by 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 BSS devices into 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.

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.

 

Saving Parameter Sets

When a device is removed or GTT is closed, parameter sets are automatically saved.

There is currently a limitation on saving parameter sets to databases.

The parameter set is not immediately saved to the database. It is saved in the moment when the device is removed from the device list. Therefore, if the signal flow is modified (for which there is an associated parameter set) when the device is not in device list, the old parameter sets are retrieved from the database when the device is dragged to device list next time.

Different Methods for Saving Set Files

Saving Set File from Device

1. Navigate to the Device Designer tab and choose the desired device for storing the set file.
2. Click on Export > Tuning Data.
   
   
3.  A dialog box will be displayed, select the folder where the files (.set/.setr) will be stored, type a file name, and click on Save.
   

Saving Set File from Presets

1. Navigate to the Parameter Sets tab and choose the desired Set column.
2. Right-click on the chosen Set column to open the context menu and select Save Set File.
   

A dialog box will appear, where you can choose the folder to store the files (.set/.setr). Enter a file name and click on the Save button.

Saving Set File from Preset Controller

1. Navigate to the Device Designer tab and click on Preset Controller. This opens Preset Controller window will be opened.
   
2. In the Preset Controller window, right-click on Export Options and click on Export Set Files.
   
   

A dialog box will appear, where you can choose the folder to store the files (.set/.setr). Enter a file name and click on the Save button.

Saving Set File from State Variables Explorer

1. Navigate to the Device Designer tab and select the device from which you would like to select and store the set file.
2. Click on State Variables. This opens the State Variables window.
   
   
3. On the State Variable window, select from File and click Save Set As.
   
   

A dialog box will appear, where you can choose the folder to store the files (.set/.setr). Enter a file name and click on the Save button.

Once you have saved the set file, both the .set and .setr files will be accessible in the folder you selected.

If the set file is generated using a different panel, such as the IESS panel, the .setr file will not be generated by default. However, you can utilize any of the methods mentioned earlier to generate the .setr file if needed.

Loading a Set File

In the context menu of any set Click on “Load Set file”. This opens a dialog to select the .set file to be loaded. On selecting the .set file, tuning data will be loaded on to the selected set. On clicking Undo, load action will be undone and old preset values will be displayed in the screen.

Only matching (CoreId, InstanceId, BlockId, and SublockId) object’s tuning data will be loaded.

Notifications to the user during load:

1. If there are additional objects in .set file than set group a notification message will be displayed.
2. If there are additional objects in set group than in .set file a notification message will be displayed.
3. If there is a mismatch in the size of the AO a notification message will be displayed.
4. If there are mismatching objects in both .set file and set group, a notification message will be displayed.

All the mismatched object details will be displayed in event log.

Tuning data will be loaded only on to the set in the parameter set column. Not on to the state variables.

Retrieve Parameter Sets

The Retrieve function updates the parameter set values, with respect to changes made in the state variable.

Retrieve will change the values in the state variable and transfer the changes to the parameter set

1. Open the native panel and move the slider to change the values.
2. On the Parameter set group workspace and click Retrieve.
3. Click Yes to confirm to complete the operation.

You will see the parameter set value will be updated with respect to the state variable, which are mapped in to the respective native panel.

Verify Parameter Sets

This functionality is designed to compare the presets loaded on a device with those available in the GTT  in order to ensure their accuracy.

This feature is available only in online mode. i.e. only when the device is connected.

To verify preset values, select a preset and then click the ‘Verify’ button. A read command is sent to the device for each state variable within the preset. Once the value has been read, it will be compared with the corresponding value in the preset. If all values match, the verification process is considered successful.
However, if any values do not match, an error message will be displayed, and an error report will be generated.

Sample error report is as attached here Set 1[2].

Verify functionality is available at the Master Preset Controller level as well. You can verify all the presets under a slot in online mode.