System Exclusive Protocol; K2Vx System Exclusive Implementation - Kurzweil K2000 - MUSICIANS GUIDE Musician's Manual

Chapter 30

System Exclusive Protocol

K2vx System Exclusive Implementation

The MIDI System Exclusive capabilities of the K2vx allow you to manipulate objects in the
K2vxÕs memory from a computer system, another K2vx, or a MIDI data recorder. The following
is a reference to the SysEx protocol used by the K2vx. This information can be used to build a
simple object librarian software program. A word of adviceÑbefore you begin experimenting
with SysEx, make sure you have saved anything of value in RAM to disk.
NOTE: To support new features and changes in the K2vx line of products, the internal program
structure has been changed from that of the K2vx. Due to these changes, you cannot transfer a K2vx
program to a K2vx, or a K2vx program to a K2vx via MIDI system exclusive. The K2vx software will
continue to be enhanced, and in the future the K2vx will be capable of accepting K2vx programs over
MIDI. As a result of this, computer based K2vx editor/librarians will not currently work with the K2vx,
unless they have been revised to accommodate the changes.
Common Format
In the following discussion, the Þelds of the K2vx System Exclusive Protocol messages are
notated asÉ
field(length)
Éwhere ÔÞeldÕ is the name of the particular information Þeld in the message, and ÔlengthÕ is
either 1, 2, 3, or n, representing the number of sequential MIDI bytes that make up the Þeld. A
length of ÔnÕ means that the Þeld is of a variable length that is determined by its contents or sub-
Þelds.
All K2vx SysEx messages have the common format:
sox(1) kid(1) dev-id(1) pid(1) msg-type(1) message(n) eox(1)
ÔsoxÕ is always F0h, and represents start of System Exclusive.
ÔkidÕ must be 07h, and is the Kurzweil Manufacturer ID.
Ôdev-idÕ is Device ID. The K2vx will recognize a SysEx message if the Ôdev-idÕ is the same is the
SysX ID parameter from the MIDI Receive page (from the top level, press the MIDI mode
button and the RECV soft button.) If the K2vxÕs SysX ID parameter is set to 127, it will
recognize SysEx messages no matter what the Ôdev-idÕ is.
ÔpidÕ is the Product IdentiÞer, and must be 78h (120 decimal), indicating the SysEx message is
for the K2vx.
Ômsg-typeÕ is the identiÞer of one of the K2vx SysEx messages deÞned below, and ÔmessageÕ is
the variable-length message contents.
ÔeoxÕ is always F7h, for end of System Exclusive.
Data Formats
K2vx SysEx messages are subdivided into Þelds that contain data in different formats. The
various Þelds are shown in the Messages section below. Within a message, any Þelds for values
that can be bigger than 7 bits are broken into 7 bit chunks. Thus two MIDI bytes gives 14 bits,
three bytes gives 21 bits. The signiÞcant bits are right justiÞed in the Þeld. All bytes in a Þeld
must be present no matter what the value is. For example, an object type of 132 would be split
into two MIDI bytes in a ÔtypeÕ Þeld as 01 04:
System Exclusive Protocol
K2vx System Exclusive Implementation
30-1