TC-Helicon VoiceLive Sysex Manual - Manual (Page 2)

Page 2
TC-Helicon Vocal Technologies
www.tc-helicon.com
Preset numbers
Preset numbers are represented in SYSEX messages as 2 bytes (combined
14 bit value). The first byte is the 7 least significant bits and the
second is the 7 most significant bits. Preset numbers are mapped as
follows:
Preset number zero references the current operating preset. Presets
numbered 1 through 99 (0x63) reference all stored presets. For
example, preset number 67 (0x43) would be translated into
bytes 0x43 (LSB) and 0x00 (MSB).
Checksum
Checksums are 1 byte holding the 7 least significant bits of the sum of
all bytes contributing to the checksum.
Example: If the byte values used in a checksum calculation were the
series 1,2,3,...,126 their sum total would be 8001. Dividing 8001 by
128 leaves a remainder of 65 which becomes the checksum byte.
Message data format
The format of data for each of the different SYSEX messages depends on
the type of message. Below are descriptions for each message type
explaining their specific data formatting requirements.
SYSEX message type Identifier
Request Preset 0x45 (69)
Request Parameter 0x47 (71)
Request Shift Map 0x51 (81)
Request Song 0x14 (20)
Request Setup 0x15 (21)
Preset Received Notification
0x34 (52)
Preset Data 0x20 (32)
Parameter Data 0x22 (34)
Shift Map Data 0x31 (49)
Song Data 0x12 (18)
Setup Data 0x13 (19)
VoiceLive Data Request messages
Request Preset – 0x 45 :
is 2 bytes representing the number of the preset requested. See
above for a description of preset number representation. The data
transmitted by VoiceLive upon receiving this message will be formatted
as a
Preset Data message.
Request Paramter – 0x
47 :
is 2 bytes. The first byte defines the group to which the
parameter belongs and the second byte identifies the parameter within
the group. See the
Parameter Grouping and Listing table for a complete
list of all groups and parameters. The data transmitted by VoiceLive