Category: GlobalTuningTool

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. On the device view, click on the Audio Library Version. This opens the property view of the device.
   
2. 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.

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.

Follow the below steps to create a new project:

1. On the GTT home screen, select the Project tab, and click Create Project (+ icon). This opens Create Project dialog box.
2. Select the Empty Template option, enter the Project Name and Description, and the click Create.
   A new project is created, and you will be redirected to the Device Designer window.
   

Create a Device Template

On the Device Designer tab, click on the (+) icon to open the Add Device window.

On the Add Device window. You can use any of the following options to create a device template. Refer to Devices and Template View to know more about create a device template.

• Discover Device: Click on the Discover Device option, if you have the pre-configured device template available.
  In case of discovered device, we can make a connection (routing) adhering to defined rules. For more details refers to Device Routing.
• Create Light Device: Click on the Create Light Device option, if you want to create a new template.
• Create Device File: Click on the Device file option, if you want to create a device file.

Add Device Template to the Project

There are two types of templates available in the Add Device window: the new ones and the existing ones. Use any of the templates you wish to deploy as per your requirements.

Follow the below steps to add a device template to the project:

1. On the Add Device window, select the template from the device template list and click OK.
   

   You can see the physical core of the template. The below figure shows a multi-core template and single-core template.

   Multi-core template
   
   

   Single core template
   
   

2. Drag and drop the Xaf Instance from the Core objects to the physical core window.
   
   This action opens the Configure I/O Channels message box with Ok button preselected.
3. Enter the Input channel and Output channel number and click OK.
   
   The audio objects inside the signal flow designer are filtered based on the Data Format of the core. For more information related to the Data format of the core, please check the below Create Device Template documentation.

   If there is a tuning version mismatch between audio objects of signal flow and audio objects in the toolbox, then a warning message pops up showing tuning version differences, and those audio objects are shown in blue color.

   Each core object has different properties. For more details refer to the Devices. Once all the properties of the core are verified, click Save to save the changes.
   One of the most common uses of GTT is to design the signal flow and tune the signal as desired. The Signal Flow Designer makes it easier to create dynamic signal flow as well as allows you to send audio signals to the amplifier.
   In addition, it supports the creation of dynamic state variables for audio blocks present in a flow, as well as the launching of tuning panels (both native and custom).

The AudioworX Signal Flow Designer (SFD) allows you to deploy features across DSPs, SoCs, and ECUs. Harman and third-party technologies are available for drag-and-drop audio flow construction using a library of standard audio building blocks.

This audio processing can be simulated on a PC or target hardware while computing and memory measurements for each block are collected.

Follow the steps below to create a signal flow design:

1. Double-click on the xAF instance in Device View to open the Signal Flow designer.
   
2. Go to the Toolbox section, expand Interface, and drag the AudioIO audio object to the Signal Flow view. Similarly, add another AudioIO audio object to the Signal Flow view.

    – When adding an xAF instance to a discovered device, this AudioIO can be added. Thus, this step is only necessary if these two AudioIO objects are absent.
   – The toolbox will filter audio objects based on the core type of the physical core where this Framework instance is added. The audio object will be marked with an exclamation mark to indicate that it cannot be used for building signal flow. You can hover over it to see which core types are supported.
   

3. Select one of the AudioIO audio object and set the Object Mode parameter to Audio In. Similarly, select another AudioIO audio object and set the Object Mode parameter to Audio Out.
4. Expand Basic and drag Gain audio object to the Signal Flow view. You can use any of the audio objects, for example Gain audio object is used.

   Try to keep the Gain audio object between two AudioIO audio objects, or else you cannot connect the input or output pin with the Gain audio object.
   

   Now, you can modify the audio object properties as per your requirement.
   

5. Select the Gain audio object and set the # of channels parameter to 2. The number of channels determines how many connectors the AO will be allotted. You can assign as many channels as you want to your device in GTT.
6. Hold the CTRL key, select all the audio objects from the Signal Flow view, and click Connect Blocks to connect all the audio objects. Or you can drag a connection from the output pin of an AO and drop to the input pin of another AO
   
   Now you have an input and output object, as well as an object to tune gain, invert, and mute parameters for each channel of the signal flow designer.
7. Click Save to save the signal flow design and click Go Back.
8. Launch IVP and click on Send Signal Flow in device view.
   A message “Signal flow successfully submitted” will be displayed. The Signal Flow is sent to the virtual amplifier.

Messages While Saving Signal Flow Design

• If there is a version mismatch between the current audio library version and the version data on the device, a warning message appears asking whether to continue or stop saving.
  
• If there is a tuning version mismatch between audio objects in the signal flow and audio objects in the toolbox, a warning message will be displayed, showing the tuning version differences, and those audio objects are highlighted in blue. Right-click on the particular AO and click on Upgrade Audio Object to resolve these errors or warnings.
  
• If the existing audio object in the signal flow does not match the block length, sample rate, or core type, a compiler error will be displayed at the bottom of the signal flow window.
  
  
• If the Sample Rate/Block Length does not match, a message will be displayed asking if you want to continue or stop saving.
  

For more details about Signal Flow Design, refer to the Signal Flow Design user guide.

The native panel is one of the most important part of the Signal Flow Designer. The native panel has interactive widgets that help to tune complex audio objects easily.

Launch Native Panel

1. On the Signal Flow Designer window, double-click on any audio object to open a Native Panel.
   
   Use the interactive widgets on the Native panel to make the desired changes to audio object properties.

   When Native Panels is open, if there is any modification to Signal Flow Designer, a popup message will appear asking to save the changes.

   When Native Panels is open, you cannot make any changes to the Signal Flow Designer tab. But you can open other native panel from the Signal Flow Designer tab.

2. If preset bar is present in the panel, select the free preset slot numbers, enter the name of the slot, and click Store preset. This saves and stores the current tuning data to the selected slot.
   

If you do not enter a name of the slot, then it will take the default named “New Preset”.

You can switch between presets and apply their values to the native panel by simply clicking on them. You can also change the values in the native panel and/or the preset name after you’ve clicked it to override the preset.

Click Reset Selected to clear the preset that is currently selected. Click Reset All to clear every preset in the corresponding native panel.

Visualize a Signal Flow

You can check the tuning effects of the designed audio signal flow on the virtual device in IVP.

For more information, refer to Analyzer and Generator.

Perform Tuning

The Audio objects that do not have their own native panel can create a custom panel and link the panel with the respective audio object.

If an audio object doesn’t have its own native panel, you can create a custom panel and link it to the appropriate audio object under the “Available Custom Panels” option.

Follow the below steps to view the signal flow performance:

1. Go to the RTA tab, start Generator, Analyzer, and PluginHost.
   
2. Go to the Device Designer tab, click on Send Signal Flow to send tuning data.
   
3. Open the native panel and go back to the IVP tab. On the native panel, tune the signals. The signal flow in the IVP tab will change accordingly.
   

Using the settings you can configure the Parameter Set Data.

To configure the parameter set data:

1. Select any parameter set column, right-click, and select Settings. This displays the settings dialog box.
   

• The “Edit” option is a toggle button that defaults to a disabled state to prevent unintentional edits.
  
• When the “Edit” option is enabled, you can edit all fields except the Tuning tool version and String Value.
  
• The tuning tool version is installed GTT Tool version and gets auto-populated.
• By default, the product name will be the name of the device.
• You can independently update each of the header metadata, Product name, Sink name, Flowchart version, and Set version.
• You can include or exclude header metadata, which can be controlled by the Include Header option.
• The Include Header option performs a data merge operation when the option is selected. This means that the header metadata is prepended to User Data, and it will be reflected in both the String Values section and in hex format in the Hex Values section.
• Any modification done to any header metadata or user data will immediately be reflected in the String Value and Hex Values at the appropriate index.
• Header metadata can only be included once.
• There is no limitation on the number of characters entered in User data or Hex Values.
• You can either enter values in the User data section or Hex values. Editing in the Hex Values section would clear the content of the User data and vice versa.
• All information is persistent and can be retained and displayed when the settings window is relaunched.
• String Values or Hex Values will be stored and loaded in hex format. And it can be exported or imported from the .Set file and .Setr file.

User settings created using an older version of GTT (W onwards), all the data would be treated as User data, including the header part if it was included.
You must clear the header information manually if the user data already includes header information. The header part can then be included as required. This is because earlier header metadata was editable, which is now controlled due to separate edit sections. This is a one-time process and would not require X release onwards.

This section provides step-by-step instructions to perform the following operations.

• Create and configure the project
• Build a template for the project
• Create a signal flow design
• Tune a signal flow design
• Building a panel
• Adding and configuring parameter sets

Use Case

• Offline Tuning: Set tuning parameters for audio objects without connecting to the device.

• Real-Time Tuning of a Target Device: Live tuning connected to the target device.

• Real Time Tuning of a IVP/VST: Live tuning connected to the virtual device (IVP/Audio Mulch).

• Socket: A socket is an interface type, that can send or receive data within a PC (from one application to another) or over a computer network from one PC to another.

In this case, a socket connection is used to send data from GTT to AmpSrv2 and vice versa.

• VST: Virtual Studio Technology is a software interface definition for audio plugins into music software by Steinberg company. Usually, these plugins are shipped as Windows Dlls that can be used inside of a VST-Host (e.g. AudioMulch).

In this use case, AudioworX provides the file (xAFVirtualAmp.dll) that simulates the audio behavior of an amplifier or head unit.

The first toolset is a group of basic design tools. The tools are grouped into the following toolset.

Text design
Fader design
Rotary design
Button design
Box design
LED design
Meter design
Note design

Text Design

Text Display

A text display is a dynamic text control on a Custom Panel that can be linked to the value of a specific device parameter. It shows the control value as it changes, much like a text box, but cannot be changed by the user.

Use either the Text Label or Note control to add static text to a Custom Panel.

A Text Display control can be managed in the Custom Panel designer and, once the Custom Panel is activated, viewed (but not changed) by the end user.

• Unlinked (Static) Text: If a label is not linked to a control, the text does not change on the control but is merely the default text as defined in the text attributes. Once another control is linked, the value is overridden by the parameter value.
• Linked (Updating) Text: If a label is linked to a control, on the activated Custom Panel it will reflect the value of the control as it changes, much like a text box. However, the value cannot be changed by the user.

Once a label is linked to a control, you can add a label showing the parameter address of the label.

Text Label

A text label is a static text control on a Custom Panel. It is text only, cannot be linked to a device parameter, and is not interactive for the user.
Text Label controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, viewed (but not changed) by the end user.

Text Box

A text box allows the user to specify the exact value of a device parameter by typing it in rather than running through a long list of values. In tablet mode, a keypad loads when a text box is selected.
Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

Common Text Design Properties

Fader Design

Fader Horizontal

Rotary Design

Rotary

A rotary is an adjustable control that manipulates a device parameter. Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

Rotary Encoder

A rotary encoder is an adjustable rotary control that manipulates a device parameter and displays values of a device parameter.

When a Custom Panel is activated, the rotary control (inner ring) changes the linked parameter values as the end user clicks and slides it around it to the desired value position (like twisting a nob). The rotary encoder is controlled by right-clicking with the mouse and moving to the top or right to increase the value and moving to the bottom or left to decrease the value.

The LED meter (outer ring) reflects the selected parameter values, which are usually the same as those linked to and adjusted by the rotary control.

Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

Common Roter Design Properties

Button design

Button

Button On/Off

Button Momentary

Button Latching

Button MultiState

Button Radio

Button Region

Button System Functions

Common Button Design Properties

Box Design

Combo Box

A Combo Box allows the user to select the value of a device parameter from a drop-down list.Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

List Box

A List Box allows the user to select the value of a device parameter from a list. Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

Spinner

A Spinner allows the user to change the value of a device parameter by adjusting it up or down; the increment can be specified by the Custom Panel designer. Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

Check Box

A Checkbox turns on or off a device parameter value when pressed. Controls can be managed in the Custom Panel designer and, once the Custom Panel is activated, utilized by the end user. This control must be linked to a parameter to function properly.

Common Roter Design Properties

LED Design

Led Image

Led Preset Trigger

Led Region

Led System Indicator

Common LED Design Properties

Meter Design

Common Roter Design Properties

Note Design

The Panel Designer comprises of various features, that offer you a thoughtfully designed, clean, and easy-to-use workspace. Using Panel Designer, you can quickly create a custom panel with all the elements you need and link the panel with a desired audio object. Let us have a look at some of the components of the Panel Designer workspace.

1. Panel Designer Ribbon: The Panel Designer ribbon contains tools for designing and editing the custom panel. The ribbon is divided into the following groups: Tools, Current Panel, Controls, Clipboard, Editing, Layout, and Parameters.
   The Panel Designer ribbon contains tool for designing and editing the custom panel.
   
   The Panel Designer ribbon comprises the following group.
   • Controls
   • Clipboard
   • Editing
   • Panels
   • Layout
   • Parameters
2. Panels View: The Panels view in Panel Designer displays all the custom panels and allows you to create, delete and import the custom panels. In addition, you can access the Venue Explorer to view available Device(s), Applications, and Parameter Sets.
3. Custom Panel Properties View: The Properties view displays the properties of each component used to design the custom Panel and also allows you to customize the Panel to meet your needs. The Properties view is displayed on the right-hand side of the screen.
4. Designer Workspace: You can use various tools available in the Toolbox to create a custom panel in the Designer workspace.
5. Editor Windows: In the Properties view you can customize the Panel using various editour windows. These editour windows are mapped with corresponding properties.

The Control IDs are used to configure Custom Control IDs. Users can add, edit, export, and import Custom Control IDs data.

To open the Control IDs

1. On the Device View, click on the Control IDs. This opens the Custom Control IDs configuration window.
   The Custom Control IDs window shows all the custom control ID details.
   

To add the custom control ID

1. On the Custom Control IDs panel, click on Add. This opens the Add Control Signal window, where the user can enter the details of the new custom control.
   
   You need to enter details in all fields. The maximum value of control should be greater than the minimum value. The Control ID range should be between 61440 to 65535.
2. Click OK to save the custom control id details.

To edit the custom control ID

1. On the Custom Control IDs panel, click on the Edit icon. This opens the Edit Control Signal window, where the you can update or change the custom control details.
   
2. Click OK to update the custom control id details.

To delete the custom control ID

1. On the Custom Control IDs panel, click on the Delete icon. This deletes custom control and also removes its associated data.
   

To export the custom control ID

Using the export option, all custom control data can be exported in the provided destination directory with the file extension *.csv.

1. On the Custom Control IDs panel, click on Export. This opens the file directory.
   
2. Navigate to the desired location and click Save to export the file.

To import the custom control ID

Using the import option, all the custom control data can be imported to GTT.

1. On the Custom Control IDs panel, click on Import. This action opens the file directory.
   
2. Navigate to the file location and click Open to import the file.

This action will import all the custom control pins from the file (with *.csv extension) in the custom control list.

A message will appear if the file is invalid or does not contain the required data.

If GTT contains custom control IDs, it will ask for confirmation whether the user wants to overwrite them.

An error message will be displayed if the import file contains duplicate control IDs.