A new Tally plugin has been added in this version. It is located under Plugins / Peavey / Control / Tools in the device tree. This device allows you to count the number of times a button is clicked. Help is available via the Info button on the control surface.
The Python string.py and struct.so libraries are now included with this version.
Note: The nControl and nTouch 180++ firmware include a full set of Python libraries.
The defaults for new projects have been changed to improve performance on NioNodes. The control frame rate is now 10 updates per second (changed from 30).
The AEC card tab has a number of enhancements in this version:
New AEC Input Clipping LED that indicates when the input level from the near end reaches an internally set threshold and is automatically clipped.
Note: When clipping occurs, AEC performance will be impaired.
For more information on the AEC card control surface, see Slot x: AEC in the NWare Device Reference.
The Slot x: AES tab on the NioNode control surface now includes Origin and Destination boxes for input and output channels. These boxes display identifiers for the origin devices used with input channels and the destination devices used with output channels.
For more information, see Slot x: AES in the NWare Device Reference.
When you want to start NWare Kiosk in full screen mode, you can now specify the line <item name="full_screen_mode" value="true" /> in the NWare Kiosk personality file. This is an alternative to using the /fullscreen=1 switch on the command line.
For more information, see Starting Kiosk in full screen mode in the NWare User Guide.
When you add a Generic Control to your design, you can now select button - left from the Style list to create a button with an arrow pointing to the left.
The available storage for NION log files has been increased. Entries are now added to the log until 2MB of storage has been used (and approximately 22,000 lines have been stored). 1MB of the oldest log data is then deleted automatically, making room available for new entries.
You will now be able to view a much larger number of log messages in NWare and download them using Lumberjack.
When you select DHCP on the Network page of the NION web interface, the IP address, subnet mask, gateway and DNS settings are now shown.
Currently, non-administrator users cannot run NWare or Kiosk without additional steps being completed after the installation.
The administrator must change the permissions of the \program files\mediamatrix\nware <version>\plugins\nware\xml folder to allow write access for the non-administrator users. Once this has been done, NWare and Kiosk will operate normally.
For more information, see Allowing non-admin users to run NWare and Kiosk in the NWare User Guide.
If a block is open on the design page, you cannot define a plugin by right-clicking in the Plugins tree - the menu item is grayed out. Right-clicking the device you want to add to the plugins menu or selecting Define Plugin from the Tools menu works fine.
If you export a page, ready to make it available to Kiosk users, and that page contains an nTouch 60 node, this will prevent the pages inside the nTouch 60 block from being viewed on the nTouch 60.
If you deploy a project containing CAB devices to an nControl, you must also select which Ethernet port the CAB control will use. By default, no port is selected. If you attempt to deploy with no port selected, the message role start failed: adapter not initialized will be displayed on the Role Deployment dialog box.
For information on selecting a port, see Interfacing with a CAB device in the nControl Hardware Manual.
When you deploy a project containing a number of pages, you cannot specify which one will be displayed when Kiosk starts. The last page that was exported is always displayed first.
A workaround for this problem is to open NWare, click the page you want to display first, remove it from the exported pages group, click OK to confirm, then add it to the group again. When you redeploy the project, the correct page will be displayed first.
When NWare is installed, it adds exceptions to the Windows Firewall. If you use a 3rd party firewall, you may need to add these exceptions manually.
We have seen an occasional problem with the MediaMatrix Subnet Bridge device. If you deploy a role containing this device to a NioNode, then deploy a new role to the NioNode that does not contain this device, it is no longer possible to restart the NioNode from the web UI, and it is no longer listed on the NWare Remote Log tab. You must erase the role and then power cycle the NION, then it will be available for use.
We recommend using a different browser, such as Internet Explorer or Firefox.
When the daily setting was selected on the Schedule Generator, then the Every setting was gestured up or down, the schedule string did not change.
When the daily settings on a Schedule Generator device were changed, the schedule string did not change to correspond to the new settings.
When the once setting on a Schedule Generator device was selected, and a year greater than or equal to 2000 was specified, an incorrect year was shown in the schedule string.
Corrected comms processor device documentation to reflect that it does not operate under emulation and clarification about TCP comms.
The Pause button on the nControl Media Player did not function correctly. It has been removed in this version.
After a redeploy, the IP address on the MediaMatrix Subnet Bridge had to be cleared and reentered before the device would function correctly.
Page groups created when exporting pages for Kiosk could contain forward slash "/" and backward slash "\" characters in their names. Subsequently, you could not display the pages in Kiosk when the program was started. In this version, if you try to use these characters in a page group name, an error message will be displayed.
The NWare log included messages about the NION audio network module that contained unreadable characters. These messages are no longer generated.
When two controls that were peer-wired together and assigned to one NioNode were wired to a control assigned to a different NioNode, they did not function correctly.
When a Python script included code for working with SNMP on the nControl or nTouch 180++, it generated an error message about a missing MIB file, even when the code was functionally correct.
The following user interface issues have been fixed:
When certain network configurations were used, it was not possible to poll an nControl node and view the log messages.
Previously, the data stream transmitted by the NION AES card did not contain correct information about the data format in the header.
If the signal received by a microphone input on the AEC card arrived more than 12.5ms after the reference signal, the card was unable to cancel the echo.
When a role containing a MediaMatrix Subnet Bridge device was running on a NION, and a new role was then deployed to the NION, this caused it to lock up.
When a role was deployed to a NION nE, then the unit was restarted, the role would not start.
The User Management page in the nControl web UI showed a user called nTouch 60 user, which should not have been visible.
The Network page in the nControl web interface was showing incorrect information for the available network interfaces.