Biamp LTR - Manual (Page 204)

Nexia Manual LTR
Nexia uses an Instance ID number to specify the exact DSP block to be controlled. Custom
names (Instance ID Tags) may be assigned to DSP blocks, and used in lieu of Instance ID
numbers within NTP command strings. Instance ID Tags may be up to 32 characters, but may not
start with a number. If the Instance ID Tag includes spaces, it must be double-quote delimited
("Instance ID Tag") when used in a command string. The Instance ID number (and Instance ID
Tag) can be found by right-clicking the DSP block and selecting "Properties". Both identifiers are
available on the DSP Attributes 1 tab.
The property sheet can only be accessed in an off-line screen.
**Note** Nexia software assigns an Instance ID number to each DSP block on the initial system
Compile . Subsequent compiles will not change the Instance ID numbers unless the "Reassign
Instance IDs" check box is selected in the ‘ Compile ’ tab of the ‘ Options ’ screen (located on the
Tools menu) in Nexia software.
If one or more DSP block is disconnected from the audio path (when connections are not made to
at least one input or output) Instance ID numbers will be unassigned. Instance ID numbers will be
reassigned once the DSP blocks are properly connected again. The use of Instance ID Tags (in
lieu of Instance ID numbers) may help prevent command string conflicts caused by reassignment
of Instance ID numbers.
Index
Index refers to inputs, outputs, or cross points of an Attribute . Some Attributes will need an
Index1 (Input or Row) and/or an Index2 (Output or Column). The tables in the Attribute section
will define which, if any, indexes are required for the string.
Example: INC 1 AMLVLIN 4 1 1
In an Auto Mixer on Device 1 we are increasing the level of input 1 on instance ID 4 by 1dB.
Index1 is used to represent the input number.
190