Release 1.7.0 (November 29, 2013)

In this section

Live Update

Features

Enhancements

Known issues

Bug fixes

See also

Release 1.7.2 (March 27, 2015)

Release 1.7.1 (July 23, 2014)

Release 1.7.0b (July 23, 2014)

Release 1.7.0a (January 16, 2014)

Release 1.6.6d (March 31, 2014)

Release 1.6.6c (November 6, 2013)

Release 1.6.6b (August 7, 2013)

Release 1.6.6a (February 1, 2013)

Release 1.6.6 (January 25, 2013)

Release 1.6.5 (September 7, 2012)

Release 1.6.4c (June 25, 2012)

Release 1.6.4b (June 18, 2012)

Release 1.6.4a (May 2, 2012)

Release 1.6.4 (March 6, 2012)

Release 1.6.3 (August 5, 2011)

Release 1.6.2a (May 17, 2011)

Release 1.6.2 (May 5, 2011)

Release 1.6.1f (January 21, 2011)

Release 1.6.1d (December 8, 2010)

Release 1.6.1 (October 7, 2010)

Release 1.6.0 (April 9, 2010)

Release 1.5.3.A (November 16, 2009)

Release 1.5.3 (September 29, 2009)

Live Update

Sometimes, more up-to-date release notes are available online. Click here to download the latest version from the Peavey Oxford website, then press F5 to refresh the display.

Features

Kiosk2Go

This is a new product available with this release. It is a web-based interface for controlling NWare projects. It provides similar functionality to Kiosk, but is optimized for both touch devices, like iPads, iPhones and Android tablets, and PC-based browsers.

You can run Kiosk2Go on a NION, nControl or nTouch 180, and you can also use it with an emulated project.

For how-to information, see Setting up Kiosk2Go in the NWare User Guide.

For reference information, see Kiosk2Go Layouts in the NWare Device Reference.

nTouch 180 and nControl

Project control via the serial ports

You can now control an NWare project running on an nControl or nTouch 180 remotely. Both devices support the RATC, RATC2, PASHA/PageMatrix, PASHA/xControl and PASHA/Legacy protocols via the serial ports. New options for specifying the protocols for the serial ports are available on the device properties of the nControl and nTouch 180 NWare devices.

Enhancements

NWare

Project file now automatically saved to target node on deployment

When you create a new project and deploy it, the Save Project to Target check box is now automatically selected on the Role Deployment dialog box. This will save the project file (.npa) to the target device, enabling you to upload it after deployment and make changes.

Configuration options for both NioNode serial ports

New options for specifying the protocols for both serial ports are now available on the device properties of the NioNode.

Notes:

Known issues

Kiosk2Go

Issue

Affected operating systems and browsers

iOS 6.1/7

Android

Windows 7

OSX

Linux

Issue 650. Pages containing lots of knob controls take a long time to display

 

 

Internet Explorer 10

 

 

Issue 642. If you place an image control on top of a string control, the string control will not work.

 

 

Internet Explorer 10

 

 

Issue 466. Slave controls can be gestured. Normally, this is not possible in Kiosk. As a workaround, clear the Control Accepts User Input check box on the control properties of the slave control.

All operating systems and browsers

NWare

266 - Foreign language characters are corrupted by NWare

When you type characters with diacritics, such as š and ý, into a string control, they are corrupted when the project is emulated or deployed.

412 - Global preset does not enforce system mute on restart of NioNode

If you add a Global Preset device to your project, select the System Mute option on the NioNode control surface, and then save the default global preset, when the NioNode is restarted, the system mute is not applied, even though it was saved in the preset.

648 - Role resets if you specify COM ports 3 or 4 for a Comms Processor device

If you deploy a project containing a Comms Processor device to a Nionode, and then try to use the ports COM3 or COM4, the role will restart.

Bug fixes

NWare

588 - CKi amplifier VU meters showed incorrect readings

The meter readings available on the Channels tab of the control surface of the CKi amplifier device were incorrect.

600 - RATC only returned the result of the last command in a sequence

When several RATC commands were sent to the NION in a sequence, only the result from the last command was sent back to the sender.

NION

474 - JL Cooper Fader device caused the NION to crash

If a project included a JL Cooper Fader Controls device configured to use TCP communications, the NION failed after about half an hour. The log showed the message sound_engine exception.