DDF Template Validation
In case there are issues with the DDF file generated by the toolbox during creating a device or modifying of the signal flow, an error notification will be displayed. GTT will recognize any audio object that is incomplete or has failed as corrupt.
It is recommended that you should fix the DDF template of the affected audio object and proceed with your work.
- If you import or open a project that contains a corrupted audio object, a warning message will be displayed.
On opening the signal flow which has corrupted object, the corrupted audio object will be highlighted as shown below, and the same will be displayed in the compiler error window.
- If the signal flow has corrupted objects on sending or exporting signal flow, the following message will be displayed.
- If there is a mismatch between Sample Rate/ Block Length of instance signal flow and current audio object in the toolbox, then a warning message pops up and the corresponding object will be disabled in the toolbox.
- 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.
- If the Sample Rate/Block Length does not match, a message will be displayed asking if you want to continue or stop saving.
Additional Parameters Validation
The GTT will perform validation of input data in the additional parameters window, based on the information provided by the xAF dll for specific audio objects.
The below validations are added on xAF and GTT.
- ASCENDING
- DESCENDING
- NOTEQUAL
- EVEN
- ODD
- EVEN_ASCENDING
- EVEN_DESCENDING
- ODD_ASCENDING
- ODD_DESCENDING
The below figure displays the value entered should be an odd value. An error message is displayed to when an even value is entered.
