Release 1.4.3 (September 5, 2008)

There is a new option for compiling a project: incremental compilation.

By default, each time a project is emulate or deployed, the NWare compiler recalculates the optimal allocation of processing tasks to available DSPs within a NioNode. With many devices in a large project, this process is extremely complex, and can mean emulation or deployment takes a long time. To increase the speed, you can use the incremental compilation feature. This instructs the compiler to only calculate DSP assignments for new devices that have been added to the design since the last successful compile. The other devices remain assigned to DSPs as they were previously. This may result in a slightly higher DSP usage figure than an optimal compile, but will take a fraction of the time.

Note: If a device has been assigned to a DSP manually by the user, this assignment will be kept regardless of whether the incremental compilation feature has been selected.

Note: If you use the incremental compilation feature with a very large project, with a very large number of devices, it may not succeed. Perform an optimal compile instead.

Note: If a compilation fails when incremental compilation is switched on, the user is given the option to perform a full compile. If the incremental compile failed due to resource limitations, the full compile may succeed. However, if the incremental compile failed for another reason, such as a feedback loop in the design, a full compile will not succeed.

Note: If the incremental compile fails, the message box that prompts the user to perform a full compile can sometimes be displayed behind other windows on the screen.

Note: Due to the complexity of the compile process, it is possible, although unlikely, that an incremental compile will succeed, but a full compile will fail.

Tip: Incremental compilation requires spare DSP resources in order to function. As the utilization of each DSP in a NION increases, an incremental compile is less likely to succeed. We therefore recommend that you do not use 100% of the processing capacity of each NION when using incremental compile.

Tip: To get the lowest possible DSP usage and latency figures for a design, ensure that incremental compile is switched off before emulating or deploying, but be aware that the compilation process may take a long time for a large design.

Tip: We recommend that you always do a full compile before finalizing the installation and leaving the customer site.

To select incremental compile mode, click the Incremental Compilation button on the NWare toolbar before compiling. When the button is pressed in, this indicates that the mode has been selected.

The NioNode Properties dialog box in NWare shows a new option for specifying a NIO-4x4 card in each of the expansion slots.

When a NIO-4x4 card is specified for a NION expansion slot, the Flyoffs tab shows four inputs and four outputs for the card.

You can now specify a CobraNet conductor priority of Never to prevent a NioNode becoming a conductor.

This is useful when the NION is a part of an XDAB cluster connected to a CobraNet network. If the CobraNet priority on the NION is not set to Never, an interruption in the CobraNet clock packets (beat packets) will often cause the CM-1 to briefly attempt to become the conductor, resulting in an XDAB re-arbitration. This in turn results in a larger than necessary dropout in the audio.

Previously, under the NION device properties, you could only choose 0..1 for the lowest conductor priority. This set the conductor priority to 1 for the NION that is the XDAB master (all the rest were set to 0). The 0..1 option has been replaced with Never.

The layout of part of the device tree has been improved. Under NION Audio Processor, there are now just three options for creating NioNodes: N3, N6 and NX.

These options are equivalent to the Custom options for each type of NioNode in previous versions of NWare.

The tabs at the bottom of the NioNode properties window now have more descriptive labels for each type of card installed.

Features:

• Four analog mic/line level audio input channels
• Four analog line level audio output channels
• 24 bit A/D (inputs), 24 bit D/A (outputs)
• 48 or 96 kHz audio sampling rate supported
• High reliability DIN connector to backplane, using slide rail for alignment
• Mini-Euro connectors for easy input connection.

Previously, under Windows Vista, when you selected the Save As option in NWare and attempted to overwrite a file, the program closed unexpectedly. This has now been fixed.

The delay compensation feature is now working as expected. It did not function correctly in releases prior to NWare 1.4.3.

This feature is designed to compensate for delays caused by signal communication between DSPs in a NION. It is enabled by clicking Project Properties on the File menu, and then selecting the Auto-compensate signal delays check box on the Project Properties dialog box.

Note: If you have used this feature in a version of NWare prior to 1.4.3, when you compile your project in NWare 1.4.3, you may find that the delays have changed. This could affect the signal timing in some projects.

The Serial Bridge Network device (for CAB serial bridging) did not function correctly in NWare release 1.4.0 and all subsequent releases up to and including 1.4.2. It has now been fixed in NWare 1.4.3.

Note: This device is only relevant to designs that use ControlMatrix devices.

When you set the CobraNet conductor priority to Never, it does not prevent the NioNode from becoming a conductor.

If you open the HTML help in NWare (by pressing F1 or clicking Help on the Help menu), then click one of the PDF links on the front page, NWare will close unexpectedly.

As a workaround, you can access the PDF files from the Knowledge Center on the Peavey Oxford website.

• To uninstall NWare under Windows Vista, you must complete the following procedure:
  1. Right-click on the MSI file that you used to install NWare to bring up the shortcut menu.
  2. Click Uninstall.

     Note: It is currently not possible to uninstall NWare via Windows Control Panel, even if you are logged on as Administrator.

When you delete media files listed on the Media tab, they are no longer shown on the tab, but may still be stored in the NWare project file. The delete operation does not reduce the size of the file.

This problem occurs when you are editing a project file created in an earlier version of NWare. If you create a new project file in the current version, it does not occur.

As a workaround, you can delete the media files manually from the following folders:

When you save your project file, the size will be reduced.