After over 15 months of development, NoteWorthy Composer Version 2.75 has been released. A summary of the additions in this release can be seen on NoteWorthy Composer’s history page.
Current users of any licensed, older NoteWorthy Composer 2.* edition can update to version 2.75 by completing these three steps:
- From inside the program, select the Access NoteworthySoftware.com command in the Help menu. You will automatically be directed to the 2.75 upgrade page.
- Download and install the latest NWC User Tool Starter Kit.
- Download and install the NWC 2.75 Viewer.
After these steps are completed, your NoteWorthy Composer 2 system environment will now be running with the newest release. There are several sources for additional documentation on this release:
- NoteWorthy Composer User Guides
- NoteWorthy Composer Help
If you are new to NoteWorthy Composer, you can try out a demo of the program, as well as utilize our free Viewer to open files created by other users.
Anyone using NWC version 2.51 or later now has a built-in user tool scripting engine, with no extra download/install sequence required. Version 2.51 introduces a built-in Lua scripting engine that integrates a basic API for handling user tool input and output processing. Every copy of NoteWorthy Composer 2.51 includes two new user tools, found in the new .Automatic section of the User Tools command::
- Show Note Names.lua
This returns a list of note names for the current selection. This is primarily intended as a demonstration of the Lua scripting engine.
Like the PHP based user tool kit before it, this was the first Lua based user tool while version 2.51 was in development. It will reverse the notes in a selection, which can sometimes be inspiring when working with a composition.
There are several online resources that can help with getting started with your own Lua scripts:
- The new API available from within a Lua based user tool is currently documented online at: lua.noteworthycomposer.com.
- Much of the NWC Lua API is actually written in Lua. It can be explored from our gist on github.