
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 you can import a .set or .setr file.
To load set 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:
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.