
The Device View is used to view and modify detailed information and settings for a specific device. Double-click on the desired device from the list to open a device template in the Device View.
Related Topics
A device is a combination of four layers: Device Layer, Physical Layer, Virtual Core Layer, and Core Object Layer. When you select any of the layers, you will see the properties of the selected layer on the right side.
Device Layer: Device layer properties include Device Name, Hardware, and Software version.
Device layer properties are not editable.
Physical Core Layer: Physical Core layer properties include Physical Core Name, Physical Core Type, and MIPS.
The “Physical Core Name” property in the Physical Core layer properties can be changed, but the “Physical Core Type” and “MIPS” properties are non-editable.
By default, the “Physical Core Name” property value is the same as the “Physical Core Type”. If you want to change the physical core name, enter the value for “Physical Core Name”, the updated Physical Core layer value will be reflected in the device view, then click on the save button to save the changes.
Only from the Device File editor window, you can update the Physical Core Type.
If you keep the Physical Core Name field empty, GTT will ask you to enter the valid name for “Physical Core Name”.
Virtual Core Layer: Virtual Core layer includes the following properties:
Queue Size and Guard Time will be supported only for Devices with audio library version “O” release and above or “M+2” release and above.
Enable Core Object Processing State and Ramp Time will be supported only for Devices with audio library version “O” release and above.
Processing state for Core objects will be applied only if Enable Core Object Processing State was enabled before Send Device Configuration.
Enable Probe Points and the Number of Probe Points will be supported only for Devices with audio library version S release and above.
Core Object Layer: Each core object has different properties. For more details refer to the ToolBox.
The undo and redo feature allows you to reverse or redo previous actions.
Undo/Redo operation is supported for the following actions:
The scope of undo/redo is within the selected device.
Undo/redo action will not restore the tuning data state.
This feature is limited to 1000 actions.
When a new manual action (dragging new object, changing connection or position etc) is performed, all existing redo records will be cleared. As a result, it will not be possible to redo any previous actions.