|
|
|
|
Using RPNs and NRPNs What are RPN and NRPN messages? MIDI RPN (Registered Parameter Number) and NRPN (Non-Registered Parameter Number) messages are similar in purpose to Controller events, except that both the parameter number and data value can be any number from 0 through 16383 (normal controllers only allow 0 through 127). Each RPN or NRPN message is composed of up to four special controller messages. Together, they are interpreted as an RPN or NRPN change. When recording or loading a file, Cakewalk will gather the individual controller messages into a single RPN or NRPN event inside Cakewalk. Using a single event makes it much easier for you to work with RPNs, and makes RPN search-back much more efficient. When playing or saving a file, Cakewalk splits this event back into the four individual controller messages that make up the RPN or NRPN event. This gives you the convenience of single RPN or NRPN events in Cakewalk, plus compatibility with existing files, hardware, and software. The following table shows which Controller numbers Cakewalk uses for parameter numbers and data values in each RPN or NRPN event.
Figuring out what numbers to enter for
RPN and NRPN events Okay, but how do you translate four controller messages into two numbers representing a parameter number and a data value? There's a simple formula: (MSB x 128) + LSB Where MSB is the data value of the Most Significant Byte controller message, and LSB is the data value of the Least Significant Byte controller message. Still confused? Here's an example showing how this works. Say your hardware wants to see: CC 99 value 127 You can translate these four messages into a NRPN event, by doing the following: 1. Calculate the parameter number
2. Calculate the data value
3. You're done! Back to index of technical articles.
|
||||||||||||||||||
|
|
|||
|
Copyright © 2008 by Twelve Tone Systems, Inc. All rights
reserved. View complete copyright notice. |
|||