Validation of the Topology Map
Message: The Automatic Mixer (object code '__') at [__,__] has no active audio output.
Explanation: An Auto Mixer Main Output is connected to a Mix-Minus Combiner
input, but appropriate audio output connections have not been made.
Mix-Minus Combiners allow Auto Mixers to share
control data only, and do not support audio input or output.
Message: Unintended use of Combiner block detected.
Explanation: A source, other than an Auto Mixer Main Output, is connected to a
Mix-Minus Combiner input. Mix-Minus Combiners allow Auto Mixers to share
control data only, and do not support audio input or output.
Message: The main output of an Auto Mixer is connected to more than one
Combiner block.
Explanation: The main output of an Auto Mixer can be connected to only a single
Combiner input (Mix-Minus or Room). Otherwise, Auto Mixer control
data might be shared with multiple groups of combined mixers, causing
convoluted behavior.
Message: Empty layout !
Explanation: No objects have been placed in the layout.
Messages: There are no audio sources or destinations.
There are no audio sources.
There are no audio destinations.
Explanation: No audio input/output objects have been placed (or connected) in the
Messages: Some DSP blocks do not have inputs. Ignore them ?
Some DSP blocks do not have outputs. Ignore them ?
Explanation: These messages appear only if the flag 'Prompt To Stop Compilation
On Warnings' is set under Tools>Options>Compile. If the choice to
'Ignore' is selected, then the warning "Ignored '...' (object code '...') at
[__, __]" will be listed in the compile results. If the 'Prompt To Stop
Compilation On Warnings' flag is not set, then compilation proceeds
and 'Ignores' automatically.
Messages: The algorithm for the '__' block (object code '__') at [__,__] has been deprecated.
You should replace the existing block with a newly created one which uses the
most up to date algorithm.
You should replace the existing blocks with newly created ones which use the
most up to date algorithms.
Explanation: The first warning is issued for each DSP block in the layout that is considered
outdated. One of the subsequent messages will also appear, depending upon
whether there is only one outdated block or multiple outdated blocks detected.
Messages: The algorithm for the '__' block (object code '__') at [__,__] has been eliminated.
You should replace the existing block with a newly created one which uses the
most up to date algorithm.
You should replace the existing blocks with newly created ones which use the
most up to date algorithms.
Explanation: These messages are similar to the ones above. The difference is that they are
not warnings, but errors.
Message: Nothing to compile !
Explanation: All objects placed in layout have been ignored.
Message: Feedback loop detected.
Explanation: The potential exists for an audio path to be indirectly looped back
upon itself. This condition could be dangerous, and is not allowed.
Allocation of DSP blocks to NEXIA Devices
Message: The allocation of some DSP blocks cannot be resolved. You
should use NexLink I/O blocks to pass audio signals between units.
Explanation: This system design attempts to pass audio signal(s) from one
Nexia unit to another. Use a pair of NexLink Input and Output
blocks to accomplish this.
Message: Too many resources required in the unit #_.
Too many resources required in the units ##_.
Explanation: The design requires more DSP resources than are available
from the Nexia device(s) specified in the Equipment Table.
Message: Due to insufficient DSP resources all disjoint blocks have been ignored.
Explanation: There are not enough DSP resources available in any Nexia unit in the
system. The compiler chose to ignore all blocks which are isolated from
any I/O blocks and, therefore, do not affect the rest of the system in any way.
Message: Total maximal duration of delays exceeded in the unit #_.
Explanation: The number of delay blocks, and their combined delay ranges,
exceeds the maximum capability of this unit. Currently, any single
NEXIA unit can provide a maximum of 15 seconds of delay blocks.
Matrix Mixers with Delay also contribute to this total, consuming
1 second per input channel.
Allocation of DSP blocks to DSPs
Message: Allocating blocks to DSPs...failed to set up a feasible DSP task
schedule in the unit #__.
Explanation: Although the total DSP power in the NEXIA unit is sufficient, compile
was not able to distribute the component objects among the
available DSPs. When the DSP load approaches 100%, it becomes
crucial that the objects be distributed more uniformly. Try moving
certain objects to another unit, or replace them with a comparable
set of smaller objects (within the same unit). Otherwise, it may be
necessary to add an additional NEXIA unit to the system, and move
large DSP blocks into it.
Assigning control blocks to NEXIA units
Message: Some unconnected control blocks have been ignored.
Explanation: Control blocks with no connections have been excluded from the
system. Only Logic Gate , Logic Delay, and Remote Preset Button
blocks can be ignored. When connected to the system, control dialogs
for ignored blocks cannot be accessed.
Message: Feedback detected in the control network.
Explanation: The potential exists for a control path to be indirectly looped back
upon itself. This condition could be dangerous, and is not allowed.
Message: Unit #__ has too many control connections.
Explanation: Although quite large, there is a limit to the quantity of control
connections within a single unit. Connections include both internal
(source and destination within same unit) and external links (source
or destination within this unit). Try moving certain control objects to
another unit (using fixed allocations),
Setting up the NEXIA units after a successful compilation
Messages: Available range of Instance IDs is nearly exhausted.
Range of Instance IDs has been exhausted.
Explanation: The total number of Instance IDs, as assigned to component and
line objects, is limited to 65,535. When component objects are
removed from a design, their Instance IDs are not automatically
re-assigned to new component objects. Therefore, the messages
above indicate that a significant number of Instance IDs has been
wasted. Set 'Reassign Instance IDs' under Tools>Options>Compile
and re-compile to recover wasted Instance IDs. CAUTION: This
will change most component Instance IDs, and will render existing
external control command scripts useless (unless Instance ID Tags
have been used in lieu of Instance ID numbers). Once Instance IDs
have been recovered, turn off 'Reassign Instance IDs' to avoid
further re-assignments.