• Class Name: Display type of device and this property is read-only,
• Audio Library Version: Display the audio library version used in the selected device. You can change the audio library version. On the property panel, click on the audio library version, select the desired audio library version, and click save.
  
  If a device has a signal flow with audio objects created in an older version, compatible audio objects will upgrade automatically. Non-compatible audio objects in Signal Flow Designer will be highlighted in blue or displayed as a warning in the compiler; these audio objects can be upgraded using the audio object context menu.In the following cases device association with a dll cannot be changed.
  • If a device’s signal flow is open.
  • If you have a monitoring window open, such as a streaming or profiler window.

  A change in dll association for one device has no effect on other device instances.

• Device Id: Enter the ID of the selected device. Make sure the device ID should be unique.
• Node Address: The Node address of the selected device. Each device has a unique node address assigned to it.
• Name: Name of the device.
• MaxTuningDataSize: Maximum tuning data.
• System Context: Set the system context Init or Runtime.

The Device View is used to view and modify detailed information and settings for a specific device. Double-click on the desired device from the list to open a device template in the Device View.

If the core object is not supported in the core type of physical core, then the core object will be shown in red, and the user has to correct the device view before saving the flow.

Under Device view following topics are discussed:

• Master Control
• Device Object Properties
• Magnifier Options
• Undo and Redo Operation

This section explains the device operation features available at the bottom of the Device Designer workspace.

• Load Device Config
• Connect Blocks
• Edit Device
• Send Device Config
• Send Signal Flow
• Export
• Control IDS

Load Device Config

---

When there are no core objects in the cores, the Load Device Config option is enabled. The Physical Cores and Virtual Cores (available within a Physical Core) as well as their connection points that were fetched from the target during device discovery are visible after the device has been loaded. Since they are read from the device, the number of virtual cores and their connection points cannot be changed.
You can connect core objects by dragging them onto the virtual cores. Alternatively, you can select the “Load Device Config” option, which will read the target’s device routing information as well as the layout and routing between core objects and display it on the GUI.

In the device view, a property section has been added to display and change the properties of chosen Core or Core Objects. When the virtual core or core object is selected, their respective properties are shown on the screen.

If you don’t clear the device view first, you won’t be able to save or access SFD.

The device identification feature is enabled for audio libraries version 13 and higher.

Connect Blocks

---

You can auto-connect selected devices, cores, and core objects using Connect Blocks.

Choose at least two cores and click Connect Blocks.

You can auto-connect the following components.

• Device – Virtual Core(s)
• Virtual Core(s) – Virtual Core(s)
• Virtual Core – Core Objects (within selected Virtual Core)
• Core Object(s) (within same Virtual Core)

Edit Device

---

In Device File Editor you can modify the device configuration, then perform “Save Device Template” or “Update Device” operation.

Send Device Config

---

You can create your own configuration and write this configuration to the target device. The Send Device Config option sends the device configuration (Core Objects, Device Routing, and Virtual Core routing) to the target device.
Before sending the device configuration, all the input and output connection points of the core objects must be connected. If any of the pins are not connected, an error message is displayed.

The Device view (number of Cores, Physical Cores, Connection points, Sample Rate, and Block Length) inside GTT and the data inside the Device. The flash file on the target should match before Sending the Device configuration. If the data doesn’t match, then the below transmission error is seen

The data in the device view (number of cores, physical cores, connection points, sample rate, and block length) and the data in the device. The flash file on the target device should match before the device configuration is sent. If the data doesn’t match, you will see the transmission error.

If any changes are made to the configuration, the send device config must be completed before sending the signal flow.

The device identification feature is enabled for audio libraries version 13 and higher.

Feedback Loop

In the device view, feedback connections are allowed. You can connect the output of any core object as input to any other core object.

Core object Id defines the order of execution of core objects. Execution order of any core object depends on the IO dependency. IO side dependency is not considered when there are feedback loops.

Self-loop is not supported as feedback.

In the image, connection highlighted in green color is a feedback connection.

Send Signal Flow

---

The Send Signal Flow option sends the configuration of the signal flow design to the target device. You can also use this to test how the target device responds to specific test signals. In a test scenario, you can configure specific test signals and send them to the amplifier.

Export

---

Using the Export option in the device view, you can export the device configuration data and the signal flow design details.

*.Core files would be created for each Virtual Core available in the device. One *.route file will be created for Device routing data. One .mcd file will be generated for master control data and one .SFD file will be generated per instance per core.

• One core file per virtual core in the signal flow.
• The core objects within the virtual core.
• The routing within those objects.
• The destination of the output pins of the virtual core.
• One signal flow file per xAF instance.
• This is the same legacy file.
• One input device routing file.
• This basically describes how the device input buffers are connected to the virtual cores and/or the device outputs.

Control IDs

---

The Control IDs are used to configure Custom Control IDs. You can add, edit, export, and import Custom Control IDs data. For more details, refer to Configure Control IDS.

The preset controller is the central place for managing and organizing how you will load presets in your signal flow.  It also contains other related features such as creating .set files, storing sets, and recalling sets of parameter sets available.
A “Slot” is a group of parameters set one level above. You can create multiple such slots and do any actions like create set files, store , recall etc.
In addition to GTT functionalities, it is also possible to send Xtp commands to device. There are XTP commands to send slot map and Load the slot on to device. You need to export all .set files and manually flash on to the amp.

To know more about  the Preset Controller functionality, refer to below topics.

• Configuring Controller Slot
• Core Object Settings
• Custom Actions Settings
• Exporting Preset Configurations
• Maintain Folder Structure
• Loading Slots on the Device
• Handling Dual Responses
• Send Preset Data Online

Limitations in Preset Controller

• After the set map is configured, if parameter sets are deleted, a generic sets window should be reopened to see the changes.
• Generic sets window can be opened only one at a time. If a new window has to be opened for a new device, the currently opened window will be automatically closed (changes made will be retained).
• Parameter sets are project specific. Generic sets are device-specific.
• Only basic validations are done. Illegal values are yet to be handled. Ex: Entering a string value for fade in –out is considered illegal and will not be handled.
• Signal flow and presets saved on the device should be in sync.
• The slot map and set files export is offline. The user shall make sure that these files are in sync with GTT for better visualization.
• All the presets configuration, slot map, and preset data are sent together in “Send To Device”. There is no option to send these data individually.
• For any changes in presets or maps, the user is expected to send all data (config, map, and presets).

Virtual device naming conventions. The set files should always follow the “preset [preset id]” naming convention. Example preset0, preset1, etc. when checkbox “Maintain Folder Structure” is unchecked.

When exporting the slot map file for Virtual Device usage, the name should always be sect262144.flash.

If set groups overlap for a given audio object, the one loaded last will override the first.  The order is not guaranteed so it is not recommended to do this.

The MIPS window presents the CPU load of cores, core objects and audio objects of the connected device.

MIPS profiling data is fetched from the device (hardware) using xTP Commands and the user can optimize signal flow based on this information.

MIPS window is enabled only when the device xAF dll version is 18.x.x.xxx or higher.

Signal flow should be flashed before launching MIPS.

MIPS profiling data of non-xAF instance core objects (Buffer,Splitter…etc) is available only from X release(24.x.x.xxxx) audio library onwards.

Launch MIPS Profiling

Steps to launch MIPS profiling:

1. Select the device node and click MIPS. This opens the MIPS window for the selected device.
   MIPS measurement on (0x64000501) and Audio Object level MIPS measurement off command (0x64000504) will be sent while opening the MIPS window and a progress window will be seen as per the below screenshot.
   

The following command will be displayed in the xTP Log Viewer.

Summary Tab

• Present virtual core and core object MIPS data (Average MIPS and Maximum MIPS) retrieved from the device using the xTP Command.
• MIPS data displayed on the physical core are the aggregated values of its virtual cores.
• Audio Object level MIPS measurement off command (0x64000504) will be sent while switching to the Summary tab from the Instance tab and a progress window will be seen as per the below screenshot.

Below command will be seen in xTP Log Viewer.

Instance Tabs

• A new tab corresponding to the selected instance will be loaded, displaying audio-object MIPS data retrieved via the xTP Command.
• Inner audio objects will be displayed alongside compound audio objects for compound audio objects.
• Audio Object level MIPS measurement on command (0x64000503) will be sent while opening a new Instance tab or switching to the Instance tab from the Summary tab and a progress window will be seen as per the below screenshot.

Below command will be seen in xTP Log Viewer.

Reset

When you click the Reset option, the MIPS number for the device will get reset for the selected tab and Reset command (0x64000500) will be sent and a progress window will be displayed as per the below screenshot.

Below command will be seen in xTP Log Viewer.

Refresh MIPS: When you click the Refresh Mips option, the MIPS data for the current tab will be refreshed.

Export to CSV: When you select the Export option, the Mips data for the current tab will be exported to a CSV file. The CSV format is shown below.

Closing MIPS Window: When you click on cross (x) to close the MIPS window, the MIPS measurement off command (0x64000502) will be sent and a progress window will be displayed as per the below screenshot.

Below command will be seen in xTP Log Viewer.

The Linking Window is designed to assist you by reducing the number of audio parameter configurations. It enables you to organize the filters and channels. When you set one item in a group, the remaining items in the group will have the same value.

By default, all the groups link are enabled. If you want to disable the specific group link, click on the toggle button to disable it.  GTT will store the group linking status in project file.

If you want to disable all the groups link, select the Disable Linking checkbox.

Create a New Group

Steps to create a new group:

1. Open Linking Window, expand the task, and drag-drop the object to the right-side section under Groups. A new group is created, expand the new group. Under the new group, you can view the added object.
   

Renaming Groups: Double-click on a group name to rename it.

Only groups can be renamed; Audio objects cannot be renamed.

Removing Objects: Click on the remove icon to remove the object. This will also delete all child objects.

Removing Groups: Click the remove icon to the right of the group. This will also delete all child objects.

Add Object to Existing Group

Steps to add object to an existing group:

1. Open Linking Window, expand the task, and drag-drop the object to the right-side section under target group. A new group is created, expand the new group. Under the new group, you can view the added object.

If an object cannot be added to a specific group, the color of that group will change to grey.

If the object is added to the group, the color of the group will change to blue.

Linking Rules

• Each of the audio objects can be part of only one group.
• If a child audio object is part of a group, the parent element cannot be part of that group.
• Groups can contain only one type of audio object. For example, you cannot link a Biquad with a Delay. Each group can contain more than one AO.
• Objects in groups are linked according to their order. For example, if you link two EQ channels, the first Biquad from the first channel will be linked with the first Biquad from the second channel.
• Changing links is done live. You do not need to close the window for the changes to be working.

The controller window is used to send instance commands.

The controller feature is enabled only when the device xAF dll version is lower than 18.x.x.xxx.

Steps to setup controller:

1. Enter a valid Core Id and Instance Id and click on Get Status to get the current available slot of the device. The response from the device will be displayed in the Response section.
   
2. Click Save to save the current instance data on the device to the memory slot entered.
3. Click Load to load the data from the memory slot to the device RAM.

If there is any error in the device connection or if any invalid Core Id and/or Instance Id were entered, the error message “Request failed!!!! Please make sure […]” will be displayed.

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

To Configure the Configure Default Controls:

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

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

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

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

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

The ControlIn object does not support control id configurations from “Y-Release” onwards. The control id configuration is now available on the device level of the Master Control entity. For more information, please refer Master Control.

The State Variable Explorer window allows you to view the memory layout of each device instance. It can also be used to send and receive tuning data.

To copy values of FloatArraySV type state variable to the Windows clipboard, press CTRL+ C in the table . The float values are located in the clipboard. The same can be achieved by using the context menu (Copy All) of the table.

Properties	Descriptions
File	Using the file options you can load and save the set file. Load Set: To load a set file, click on “Load Set”. Browse the location of .set or .setr file and click “Open”. This loads the set or .setr file in State Variables explorer. Save Set As: To save a set file, click on “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.
Target	Using target options you can send or receive tuning data from the connected device. When the device is connected you will get the following options. Send Tuning Data Receive Tuning Data Receive State Data
Sort by	Using sort options you can sort the state variables and audio objects in the state variable explorer. Name: To sort the audio objects or state variables based on their names Block Id: To sort the audio objects or state variables based on audio objects block Id. Object Type: To sort the audio objects or state variables based on audio object types. HiQnet Id: To sort the audio objects or state variables based on audio object HiQNetIds. When you click it the first time, it will sort in ascending order; the next time, it will sort in descending order, and so on.
Search	Using the search option, you can locate and highlight a matching record and move on to the next or previous matching data set. It will search audio objects and state variables based on Name, Block Id and HiQnet Id.
Reset	The Reset option will clear all search and sort data and reset state variable explorer to default state.

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.

The Devices section allows you to perform the following actions:

• Add a new device to the project.
• The Discover Device option allows you to discover connected physical or virtual devices and GTT will interact with the target device to obtain the device information available on the device.
• Display lists all the devices in a project.
• Provides options to remove the device from the project.
  

On the Device Designer tab, click on the (+) icon to add the device. This opens the Add Device dialog box.

On the Add Device, you can perform the following operations.

• The Add Device dialog box lists existing device templates available in GTT.
• You can add new device templates using any of the methods; Discover Device, Create Light Device, or Create Device File options.
• You can delete existing device templates if they are not used in a project.
• Custom Device is also listed in the Device template list as the first template. You can select a custom device and add it to the project like other templates.

GTT supports 1 custom device at a time as per the current design.

You can use any of the options to add a device template to the project.

• Discover Device: Click on Discover Device, if you have the preconfigured device template available and connected to the physical or virtual device.
• Create Light Device: Click on Create Light Device, if you want to create a new template.
• Create Device File: Click on the Device file, if you want to create a device file.
• Device Template Rename: Rename the selected device template post creating a light device, discover the device template, create a device file, or any existing device template.

Discover Device

The Discover Device feature allows you to read and write the device configuration from or to the device.

This function allows you to read information from a device that is connected to the Global Tuning Tool. This information is used to create a device template that reflects the internal layout structure of the device, which includes its physical cores, virtual cores, and routing information from device input to virtual cores between virtual cores and core objects.

You can also write (download) your configuration to the device using this feature.

Below are the few details that GTT will get from the device to construct the inner layout.

• Physical cores information.
• Core information.
• Core objects information.
• Device and Virtual Core Routing (For more details refer to Device Routing)

Below are the prerequisites to start a Discover a Device.

• Copy the flash file (device.flash) and the audio library xAFVirtualAmp.dll file available in AWXInstalledLocation/HarmanAudioworX/AudioFrameworkDLLs to your working folder.
• Launch IVP, open to “Advanced” settings, go to the “Plugins” tab and select the correct path to the xAFVirtualAmp64.dll.
  

Before using this feature, delete all the *.flash files from the working folder. IVP may crash, if it has the old tuning flash files.

Follow the below steps to discover a device:

1. On the Add Device window, click on Discover Device. The GTT will start to communicate with the target device, gather the device information, and add the device to the device templates.
   

The device identification feature is enabled for audio libraries version 13 and higher.

Only after you have completed the prerequisites the Discover Device feature function will work properly.

Create Light Device

Using the Create Light Device option, you can create a new template.

Follow the below steps to create a device template:

1. On the Add Device window, click Create Light Device. This opens the Add Device dialog box.
   
2. Enter the details in the following fields and configure the device core type.
   
   • Reference ID: Enter the reference ID of the template.
   • Device ID: Enter the initial value of the Device ID field for the first device instance created out of that template Device template name.
   • Device Name: Enter the device name.
   • Brand: Enter the brand name required for legacy AA infrastructure.
   • Family: Enter the family name required for legacy AA infrastructure.
   • Number of Channels: Enter the number of channels supported by the device.
   • Max Tuning Data Size: Enter the maximum count of bytes included in a single tuning data message.
   • Communication Type: Select ID-based tuning or address-based tuning.
     • IdBasedTuning –
     • AddressBasedTuning –
   • Core(s): Each device template exposes one or more physical cores.

   For the xAF library before the O release: multiple cores from the given list can be selected.
   
   For the xAF library from O release: Cores can be added/removed. Core types and Data-formats supported by xAF will be listed for configuring the core.
   

3. Click Add Core, select core type and date format from the drop-down list, and then click Ok.
   When the default xAF library version is < 15 (O dll), GTT displays a static set of core types with corresponding data formats.
   Based on the default xAF library selected, you can add multiple cores, and two modes of core selections (Core Type and Date Formate) are available. Below is the example showing the available core type supported by respective xAF dll versions.
     
   While configuring the core type of the device, if you want to remove any core, select the core, and click Remove Core.
   
4. Click OK. The new template is added to the device templates list.

Create Device File

The GTT allows you to create a device flash file using Device File Editor (DFE) in a project. The device file is a combination of Physical Cores, Input Groups, and Output Groups.

Follow the below steps to create a device file:

1. On the Add Device window, click Create Device File.
   
   This opens the Device File Editor window. The editor interface uses a tree-like structure to display items at each level and this structure is defined in the xTP specification. Furthermore, a Virtual Core will have Input and Output Groups as defined by the xTP specification. Each Input Group and Output Group have one group added by default.
   By right-clicking on each item, a context menu will appear that will allow you to add or remove subtree items.
   
2. Select Physical Cores and enter the hardware and software version.
   There could be one or more Physical cores under a Device and each Physical core can have more than one virtual core inside it.
   
3. Right-click Physical Cores and select Add Physical Core.
   
4. Select Physical Cores 0You must specify the Core Type of Physical Core. When the default xAF library is set to O release or above, the supported xAF core-types will be listed or set the default value to ‘0’.
   
5. Right-click on Physical Cores 0 and select Add Virtual Core.
   
6. Select Virtual Core 0, enter the Task Priority, and select the Date Format.
   
   A Virtual Core is made up of Input and Output Groups. You can add one or more Physical Cores, and each Physical Core can have many Virtual Cores.

   It is important that you should specify the Core-type of the Physical Core, Data Format of the Virtual Core, Device Input, or Output Group.

   When the selected default xAF library is “O” release or above, the xAF supported data formats will be listed or the default value set to ‘2’.

7. Expand Input Groups, select Group 0, and configure the respective properties. Similarly, expand Output Groups, and configure Group 0. In order to allow routing from Device Input/Virtual Core to other Virtual Cores or Device Output Groups, select Connectable Cores and Connectable Device Output Groups.
   You can add multiple Groups inside an Input Group.
   
8. Once all the configuration is done, click Save Device File. A save file dialog box appears, enabling you to save the flash file.
   The flash file contains the information related to the  structure of the device like Device ID, hardware version, software version, input groups count (No. of input pins), output groups count (No. of output pins), physical cores count,
   
   To view or modify an existing flash file, click Load Device File. The Device File Editor displays an Open file dialog box, selects the flash file, and clicks Open.
   

Device Template Rename

You can rename the selected device template post creating a light device, discovered device, or any existing device template.

Custom devices would not have the option to rename the template name.

Device name once edited, any device created using this template will have the appropriate name reflected in Class Name, reflecting the template on which the device is based.

To Edit the name, press the edit button, which will show an editable section with the selected device name in it.

Upon editing the name click on “Ok” and the template name will be applied. The device name allows only alphabet, numeric, and hyphen (-) and has a limit of min 1 character and max 55 characters.

When there is a validation error in the name, the “Ok” option will be disabled, and the edit box will be shown as red.

Device template name is also retained when exporting or importing the project. Name of imported device template would be based on existing uniqueness naming rules.