Overview:
Memory latency indicates the time it takes for CPU from initiating a request for assessing memory to actual reading/writing data at requested memory. The latency of the memory requested in AWX is abstract and is only relative; Level1 – Fastest memory available in platform and Level5 – slowest.
Memory Latency feature provides a way to configure latency level for individual audio object memory record from GTT.
During design time, GTT retrieves Memory record for audio object from audio library in following cases:
- Adding Audio Object
- Modifying AudioObject i.e changing number of inputs, outputs, number of elements, selected mode
- Modifying Additional parameter value
- Upgrading AudioObject
- Import of project which defaults to a different dll other than the created one
- Upgrading device framework to version 17 dll or above.
- Changing target type (i.e core type) of Core
- Changing Sample Rate or Block Length of instance
Prerequisites:
GTT supports Memory Latency feature if XAF dll version is 17.x.x.xxx or above.
How To Use:
Memory Records will have default latency selected by Audio Object developer.
GTT provides option to set the latency for every memory record of the audio object in Memory Latency Editor
Editing Memory Latency
Select Device node
Click on Ribbon Button Mem Latency Editor
Mem Latency Editor is launched
Save Button is disabled till there is a change detected in latency
Only Latency can be selected other attributes of memory record are read-only
Click on Save will persist Latency for the memory record
Send Memory Records to Device
Send Signal Flow will take care of sending Memory records with selected latency to Device. Once the signal flow send is successful, Device will boot up with specified memory latency.
Import Export of Project having Memory Record
Memory Latency is kept intact if the export and import happens on same xaf dll by version
If the dll version is different Import will get fresh memory record based on new target xaf dll version
Copy Paste of Audio Object or Core Object Containing Memory Latency
If the source and targets are same by properties then Memory latency is retained in the pasted object
CSV Import/Export
The memory latency allows to export and import memory map to CSV file. The main use case of this feature is to export memory latency to CSV, then adjust memory levels and import back to the GTT with updated memory levels.
When the memory map form file does not match the current one in GTT, the user is prompted for approval to import only the matching items.
