Category: GlobalTuningTool

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.

Importing Set File

The GTT allows you to import a set file, these set file is in human-readable set format. There are multiple ways to import the set file.

Using Device Import

Using device import you can import a .set or .setr file.

1. On the Device Designer tab, click on the Import > Tuning Data. This opens a dialog box to select the .setr file (human readable set file).
   
2. Browse the location, select the .set or .setr file, and click Open. Once the set or .setr file selected, the device processing blocks will be updated with the tuning information extracted from the imported file.
   
   

Using State Variables Explorer

1. On the Device Designer tab, click on the State Variables. This opens a State Variables explorer.
   
2. On the State Variables explorer, click on File > Load Set option.
   
3. Browse the location of .set or .setr file and click Open. This loads the set or .setr file in State Variables explorer.

Using Parameter Sets

To load set file:

1. Select any parameter set column, right-click and select Load Set File. This opens the windows directory.
   
2. Browse the location of .set or .setr file and click Open. Tuning data will be loaded onto the chosen set after selecting the .set or .setr file.
   

Tuning data is loaded onto the chosen set upon selection of the .setr file. When you click “Undo”, the load action is reversed, and the screen displays the previous preset values. Only matching (CoreId, InstanceId, BlockId, and SublockId) objects tuning data will be loaded.

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

The following notifications are displayed in the cases mentioned below:

• If there are additional objects in .setr file then set group a notification message will be displayed.
• If there are additional objects in the set group, then in .setr file a notification message will be displayed.
  
• If there is a mismatch in the size of the AO a notification message will be displayed.
• If there is mismatch in state variable names, a notification message will be displayed.
  
• If there are mismatching objects in both .setr file and set group, a notification message will be displayed.
  
• If an error occurs while loading to Device from Import > Tuning Data or State Variables > Load Set , below message will be displayed.
  

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

Exporting Set File

GTT stores the tuning data in set files these files are in Intel Hex format. Due to the complexity to analyze the data stored in set files a human readable set file is generated. This type of file is generated when you check the check box in the parameter sets workspace.

A confirmation message appears when you save a set file using the device context menu or the state variable explorer. This file will have the same file name that set file but with extension “.setr”. The human readable set file is in XML format, this file contains three main nodes:

Header: Generic file information

Data in GTT	Data in human readable set file

User data: User data defined in preset settings.

Data in GTT	Data in human readable set file

Tuning data: Values associated to each state variable for each audio object.

Data in GTT	Data in human readable set file

Each processing block corresponds to each Audio Object in current configuration.

Using the below options you can configure the Parameter Set Data

• Configure Set group
• Create Set File
• Load Set File

Configure Set group

To configure 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 in any header metadata or user data will immediately be reflected in 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 Hex Values section would clear content of 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 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.

Create Set File

To create a set file:

1. Select any parameter set column, right-click, and select Save Set File. This opens the windows directory.

Store the parameter data in the directory with the file extension *.set.

Load Set File

To load the set file:

1. Select any parameter set column, right-click, and select Load Set File. This opens the windows directory.

Locate the set file and open the file. Tuning data will be loaded onto the chosen set after selecting the .set file. When you click Undo, the load action is reversed, and the screen displays the previous preset values.

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

Following are the notifications you will get during the load:

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

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

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

Similarly, you can also load a human-readable set file (.setr file).

Tuning data is loaded onto the chosen set upon selection of the .setr file. When you click Undo, the load action is reversed, and the screen displays the previous preset values.

Only tuning data for objects with matching (CoreId, InstanceId, BlockId, and SublockId) identifiers will be loaded. The following message appears following the loading of the tuning data from Setr.

The following notifications are displayed in the cases mentioned below:

• If there are additional objects in the .setr file than the set group a notification message will be displayed.
• If there are additional objects in the set group, then in .setr file a notification message will be displayed.
  
• If there is a mismatch in the size of the AO a notification message will be displayed.
• If there are mismatching objects in both the .setr file and the set group, a notification message will be displayed.
  

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

 

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.

You can send the tuning values to the device using “Apply Delta” or “Apply” function.

• Apply Delta function: Only sends the tuning values which updated in the selected set.
• Apply function: Sends  all the tuning values of the selected set.

To Apply Delta in Parameter Sets:

1. Open the Signal Flow Designer and create a signal flow.
   
2. Double-click on the Gain audio object to open the native panel. The native panel displays gain values. Now keep the Parameter Sets window and Gain window side-by-side.

   Make sure to drag and drop the Gain AO from the Explorer tree to the Parameter set group workspace before you start comparing. You will see the gain values as set in Parameter Sets with respect to the Gain native panel.

   

3. On the Parameter set group workspace, change the values in the parameter set and click Apply Delta. You will see the native panel updated with respect to the parameter set value.
   

Similarly, if you click on Apply, all the tuning values of the selected set will be send.

Follow the below steps to create parameter sets.

1. Open the Parameter Sets tab.
2. Go to the Parameter Sets view and click on the (+) icon. This adds a new parameter group in the Parameter Sets view.
   
3. Drag and drop the required AOs from the Explorer tree to the set group workspace.
   
   The AO will be displayed in a table form.
   
4. Click New to add a new set to this set group. This adds a new set in the Set Group.
   

You can create multiple set groups and multiple sets for one set group.

The second toolset contains image design tools. This toolset includes the following tools.

• Image
• Straight Line
• Curved Line
• Rectangle
• Ellipse

Image

The Image control is a basic Custom Panel control used for custom images such as a company logo or icon.

Property Type	Options
General	Control Info: Shows control type. Read only Locked: Specifies if the control is locked out so that it cannot be moved or re-sized. Checked = Locked Unchecked = Unlocked
Appearance	Location: Control location (in pixels) of the control on the Custom Panel. Change X (horizontal) and Y (vertical) values in relation to upper left corner. You can also drag the control to a different location Size: Control size (in pixels). Change width and height values. You can also re-size the control manually. Image: Brings up the Select Image file window. Image Layout: The image layout used by the control. None, Tile, Center, Stretch, or Zoom Background Color: Background color of the image control. Brings up the Select Color window.

Straight Line

Allows to add a straight line in the custom panel.

Property Type	Options
General	Control Info: Shows control type. Read only Locked: Specifies if the control is locked out so that it cannot be moved or re-sized. Checked = Locked Unchecked = Unlocked
Appearance	Location: Control location (in pixels) of the control on the Custom Panel. Change X (horizontal) and Y (vertical) values in relation to upper left corner. You can also drag the control to a different location Size: Control size (in pixels). Change width and height values. You can also re-size the control manually. Fore Color: The color of the line. Brings up the Select Color window.
Line Properties	Anti-alias: When checked, turns on the anti-aliasing filter. Start Point: The location on the panel of the line starting point. End Point: The location on the panel of the line ending point. Thickness: The thickness, in pixels of the line. Line Template: The orientation of the line. Horizontal, Vertical, Diagonal Ascending, and Diagonal Descending
Line Properties	Anti-alias: When checked, turns on the anti-aliasing filter. Start Point: The location on the panel of the line starting point. End Point: The location on the panel of the line ending point. Thickness: The thickness, in pixels of the line. Line Template: The orientation of the line. Horizontal, Vertical, Diagonal Ascending, and Diagonal Descending

Curved Line

Allows to add a curved line in the custom panel.

Property Type	Options
General	Control Info: Shows control type. Read only Locked: Specifies if the control is locked out so that it cannot be moved or re-sized. Checked = Locked Unchecked = Unlocked
Appearance	Location: Control location (in pixels) of the control on the Custom Panel. Change X (horizontal) and Y (vertical) values in relation to upper left corner. You can also drag the control to a different location Size: Control size (in pixels). Change width and height values. You can also re-size the control manually. Fore Color: The color of the line. Brings up the Select Color window.
Line Properties	Curve Type: The quadrant that the curved line occupies. Choose from drop down list Anti-alias: When checked, turns on the anti-aliasing filter. Thickness: The thickness, in pixels of the line.

Rectangle

Allows to add a rectangle in the custom panel.

Property Type	Options
General	Control Info: Shows control type. Read only Locked: Specifies if the control is locked out so that it cannot be moved or re-sized. Checked = Locked Unchecked = Unlocked
Appearance	Location: Control location (in pixels) of the control on the Custom Panel. Change X (horizontal) and Y (vertical) values in relation to upper left corner. You can also drag the control to a different location Size: Control size (in pixels). Change width and height values. You can also re-size the control manually. Fore Color: The color of the line. Brings up the Select Color window. Gradient Color Start: The starting color of a gradient fill or the color of a solid fill. Brings up the Select Color window. Gradient Color End: The ending color of a gradient fill. Not used for a solid fill. Brings up the Select Color window. Gradient Mode: The direction that a color gradient fill will flow. Horizontal, Vertical, Forward Diagonal or Backward Diagonal Paint Style: The type of background fill. Empty Brush, Solid Brush or Gradient Brush Rounded Corners: When checked the corners of the box will be rounded by the Corner Radius amount. Corner Radius: The radius of the corners.
Line Properties	Anti-alias: When checked, turns on the anti-aliasing filter. Thickness: The thickness, in pixels of the line.

Ellipse

Allows to add ellipse in the custom panel.

Property Type	Options
General	Control Info: Shows control type. Read only Locked: Specifies if the control is locked out so that it cannot be moved or re-sized. Checked = Locked Unchecked = Unlocked
Appearance	Location: Control location (in pixels) of the control on the Custom Panel. Change X (horizontal) and Y (vertical) values in relation to upper left corner. You can also drag the control to a different location Size: Control size (in pixels). Change width and height values. You can also re-size the control manually. Fore Color: The color of the line. Brings up the Select Color window. Gradient Color Start: The starting color of a gradient fill or the color of a solid fill. Brings up the Select Color window. Gradient Color End: The ending color of a gradient fill. Not used for a solid fill. Brings up the Select Color window. Gradient Mode: The direction that a color gradient fill will flow. Horizontal, Vertical, Forward Diagonal or Backward Diagonal Paint Style: The type of background fill. Empty Brush, Solid Brush or Gradient Brush
Line Properties	Anti-alias: When checked, turns on the anti-aliasing filter. Thickness: The thickness, in pixels of the line.

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

1. Parameter Set Ribbon: The ribbon is composed of six groups, each of which represents a subset of program functionality. In addition to these programs there are also additional contextual programs that automatically appear depending on what is currently selected.
2. Parameter Sets view: This section displays the list of projects. In addition, you can add and delete a parameter set group.
3. Venue Explorer: This section displays core objects. Core objects that are part of the Audio Core (virtual core) and operate at a higher level than audio objects.
4. Tuning Panel: The workspace is used to add audio object/ xAF instance and program the device core.

Parameter Set Ribbon

Set	New: Creates a new preset with default values. For more details, refer Create a Parameter Set. Duplicate: Use the “Duplicate” option to create a copy of the set and set group. To duplicate a set: Select a set column and click Duplicate. A duplicate set column will be added next to existing set. To duplicate a set group: Select a set group and click Duplicate. A duplicate set group will be added in the parameter set view.
Default Values	Use the “Default Values” option to reset all the parameters of the selected set to their default values.
Preset	Retrieve : Retrieve the current set values from the state variables. For more details, refer Retrieve Parameter Sets. Apply Delta : To send only the Preset parameter values which are updated in the selected set (i.e. the values of changed parameters) . The tuning values of the presets are send to the device via XTP messages. For more details, refer Apply Delta in Parameter Sets. Apply :  To send the all preset parameters values of the selected set to the device. Verify: To compare the presets loaded on a device with the presets available in the GTT  in order to ensure their accuracy. For more details, refer Verify Parameter Sets.
Set File	Save: To set the configured parameter sets. For more details, refer Saving Parameter Sets. Load: To load the tuning data on to the selected set. For more details, refer Load .set file.
Edit	Delete: Deletes the current selection. Undo: Allows you to undo changes (Ctrl+ Z). Redo: Allows you to redo several actions (Ctrl+ Y).
Venue	Sort By Name: Allow user to sort parameter sets explorer data in alphabetic order. It will sort all items by Name. Sort By HiQNetId: Allow user to sort explorer data in HiQNetId order. By default, parameter sets explorer show data in HiQNetId order.
Preset Controller	The Preset Controller is basically a group of parameter sets in a single view, with all of the functionalities 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. For more details, refer Preset Controller.
Preset Comparison	Compare Presets: Sequential compare of 2 selected Presets. Next: Navigate to the next mismatch cell value. Previous: Navigate to the previous mismatch cell value. Clear Comparison: Discard and disable all the presets comparison functionality. By default, Presets Comparison ribbon buttons will be disabled. For more details about Presets Comparison, refer to Preset Comparison.

Parameter Sets View

The Parameter Sets section allows you to perform the following actions:

• Add a new parameter set group.
• Provides options to remove the set group.

Venue Explorer

In venue explorer allows you to navigate and explore various parameter set groups and audio objects. Drag and drop the desired objects you wish to have presets configured in onto the workspace.

Tuning Panel

The tuning panel shows the tuning data of the audio objects used in the SFD. You can perform the following actions on the tuning panel.

• Modify the tuning data of the audio objects.
• Manage or filter the columns and set groups.
• Search the audio objects.
• Stores the tuning data in set files. These files are in Intel Hex format.

Save the modification or progress of tuning of audio objects.

AO Visualization: To view audio objects added in parameter sets, the “AO Visualization” view can be used.

You can view the compact view of the device, cores, and audio objects by checking  “AO Visualization” checkbox in the header.  On unchecking this checkbox, the default view of parameter sets will be shown. This compact view is specific to each set group, so you can enable this for one set group and view the default view for another.

Operations such as adding new parameters by drag & drop, deleting parameters, and creating new sets are allowed in the AO Visualization view, but the view will be reset back to default.

AO Visualization view supports the search feature and you can search audio objects by name. The matching cells will be highlighted in yellow color.

Checksum Visualization: Checksum visualization allows you to view more sets data by hiding left side columns.

Parameter Sets Checksum: A checksum is an alphanumeric string that serves as a fingerprint for data. Later this data can be used for comparisons to detect errors in the data. checksum is significant because it helps to validate the data. This feature allows you to view the checksum of each set and export the checksum along with the set files.
You can use this set checksum to verify exported set files to validate whether set files data and parameter sets set data is same or not.

Refresh Checksum: Refresh checksum option get enabled when any changes are made in set data and user data. You can click on refresh icon to calculate latest checksum.

Export Checksum in Set file: GTT allows you to export set checksum in set and setr files.

Checksum will not be saved in .set and .setr files in below cases:
– While saving .set and .setr files in State Variable explorer.
– While exporting .set and .setr files from Export Tuning Data.

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.