In the SFD when AudioObject is drag into panel, GTT will call getMemRecords() API to collect memory records details from the object to update the memory latency table. This will be repeated for all the AO’s of the SFD. Once the design is complete it shall be saved.
The user can open the memory latency editor and edit the latency levels. After saving the latency levels, if the object properties were edited and saved, the user will loose the saved latency levels for that object because GTT will call getMemRecords() again that will reset to default latency levels.
Scratch memory does not need to be allocated for each audio object since all the audio objects can use the same scratch memory. The GTT calculates the maximum scratch memory, maximum alignment and minimum latency requested by the audio objects, and put it into AudioProcessing chunk.
The elements of this table must be of the data type xAF_MemRec, which is shown below:
| Member | Description |
| alignment | This is the required alignment for the memory region. |
| memType | Type of the memory to be allocated – memType could be:
|
| size | This is the size of the memory to be allocated. |
| memLatency | This can take values from one to five where one – low latency and five – high latency. |
While sending the signal flow to the target device the memory records details will be send as part of audio processing chunk and audio object chunk in the signal flow write command.