n = MIDI channel number: 0H–FH (ch.1–16)
mm = upper byte (MSB) of parameter number specied by RPN
ll = lower byte (LSB) of parameter number specied by RPN
<<< RPN >>>
Control Changes include RPN (Registered Parameter Numbers), which are extended.
When using RPNs, rst RPN (Controller numbers 100 and 101; they can be sent in any
order) should be sent in order to select the parameter, then Data Entry (Controller
numbers 6 and 38) should be sent to set the value. Once RPN messages are received,
Data Entry messages that is received at the same MIDI channel after that are
recognized as changing toward the value of the RPN messages. In order not to make
any mistakes, transmitting RPN Null is recommended after setting parameters you
need.
Pitch Bend Sensitivity
mm: 00H–18H (0–24 semitones)
ll: ignored (processed as 00H)
Up to 2 octave can be specied in
semitone steps.
Channel Fine Tuning
mm, ll: 20 00H–40 00H–60 00H
(-4096 x 100 / 8192–0–+4096 x 100 / 8192
cent)
Channel Coarse Tuning
mm: 10H–40H–70H (-48–0–+48
semitones)
ll: ignored (processed as 00H)
Modulation Depth Range
mm, ll: 00 00H–06 00H (0–16384 x 600 /
16384 cent)
RPN null
RPN and NRPN will be set as “unspecied.”
Once this setting has been made,
subsequent Parameter values that were
previously set will not change.
mm, ll: ignored
Program Change
Status 2nd byte
CnH ppH
n = MIDI channel number: 0H–FH (ch.1–16)
pp = Program number: 00H–7FH (prog.1–prog.128)
Pitch Bend Change
Status 2nd byte 3rd byte
EnH llH mmH
n = MIDI channel number: 0H–FH (ch.1–16)
mm, ll = Pitch Bend value: 00 00H–40 00H–7F 7FH (-8192–0–+8191)
MIDI Implementation
Channel Mode Messages
All Sounds O (Controller number 120)
Status 2nd byte 3rd byte
BnH 78H 00H
n = MIDI channel number: 0H–FH (ch.1–16)
* When this message is received, all notes currently sounding on the corresponding
channel will be turned o.
Reset All Controllers (Controller number 121)
Status 2nd byte 3rd byte
BnH 79H 00H
n = MIDI channel number: 0H–FH (ch.1–16)
* When this message is received, the following controllers will be set to their reset
values.
Controller Reset value
Pitch Bend Change ±0 (center)
Channel Pressure 0 (o)
Modulation 0 (o)
Breath Type 0 (min)
Expression 127 (max)
Hold 1 0 (o)
Sostenuto 0 (o )
Soft 0 (o )
RPN unset; previously set data will not change
NRPN unset; previously set data will not change
All Notes O (Controller number 123)
Status 2nd byte 3rd byte
BnH 7BH 00H
n = MIDI channel number: 0H–FH (ch.1–16)
POLY (Controller number 127)
Status 2nd byte 3rd byte
BnH 7FH 00H
n = MIDI channel number: 0H–FH (ch.1–16)
* The same processing will be carried out as when All Notes O is received.
System Realtime Message
Timing Clock
Active Sensing
Status
FEH
* When Active Sensing is received, the unit will begin monitoring the intervals of
all further messages. While monitoring, if the interval between messages exceeds
420 ms, the same processing will be carried out as when All Sounds O, All Notes
O and Reset All Controllers are received, and message interval monitoring will be
halted.
System Exclusive Message
Status 2nd byte 3rd byte
F0H iiH, ddH, ......,eeH F7H
F0H: System Exclusive Message status
ii = ID number:
dd,...,ee = data: 00H–7FH (0–127)
F7H: EOX (End Of Exclusive)
an ID number (manufacturer ID) to indicate the manufacturer
whose Exclusive message this is. Roland’s manufacturer ID is
41H.
ID numbers 7EH and 7FH are extensions of the MIDI standard;
Universal Non-realtime Messages (7EH) and Universal Realtime
Messages (7FH).
* When All Notes O is received, all notes on the corresponding channel will be
turned o. However, if Hold 1 or Sostenuto is ON, the sound will be continued until
these are turned o.
OMNI OFF (Controller number 124)
Status 2nd byte 3rd byte
BnH 7CH 00H
n = MIDI channel number: 0H–FH (ch.1–16)
* The same processing will be carried out as when All Notes O is received.
OMNI ON (Controller number 125)
Status 2nd byte 3rd byte
BnH 7DH 00H
n = MIDI channel number: 0H–FH (ch.1–16)
* The same processing will be carried out as when All Notes O is received. OMNI ON
will not be turned on.
MONO (Controller number 126)
Status 2nd byte 3rd byte
BnH 7EH mmH
n = MIDI channel number: 0H–FH (ch.1–16)
mm = mono number: 00H–10H (0–16)
* The same processing will be carried out as when All Notes O is received.
Of the System Exclusive messages received by this device, the Universal Non-realtime
messages and the Universal Realtime messages and the Data Request (RQ1)
messages and the Data Set (DT1) messages will be set automatically.
Universal Non-realtime System Exclusive Messages
Byte Explanation
F0H Exclusive status
7EH ID number (Universal Non-realtime Message)
dev Device ID (dev: 10H–1FH, 7FH, the initial value is 10H (17))
06H Sub ID#1 (General Information)
01H Sub ID#2 (Identity Request)
F7H EOX (End Of Exclusive)
* When this message is received, “Identity Reply Message” (p. 8) will be transmitted.
Byte Explanation
F0H Exclusive status
7FH ID number (universal realtime message)
7FH Device ID (Broadcast)
04H Sub ID#1 (Device Control)
03H Sub ID#2 (Master Fine Tuning)
llH Master Fine Tuning LSB
mmH Master Fine Tuning MSB
F7H EOX (End Of Exclusive)
mm, ll: 00 00H–40 00H–7F 7FH (-100–0–+99.9 [cents])
Byte Explanation
F0H Exclusive status
7FH ID number (universal realtime message)
7FH Device ID (Broadcast)
0AH Sub ID#1 (Key-Based Instrument Control)
01H Sub ID#2 (Controller)
0nH MIDI Channel (00–0F)
kkH Key Number
nnH Control Number
vvH Value
nn = 07H Level
vv = 00H–7FH 0–200% (Relative)
nn = 0AH Pan
vv = 00H–7FH Left–Right (Absolute)
: :
F7 EOX (End Of Exclusive)
* This parameter aects drum instruments only.
ll: ignored (processed as 00H)
mm: 28H–40H–58H (-24–0–+24 [semitones])
4
MIDI Implementation
Data Transmission
This instrument can use exclusive messages to exchange many varieties of internal
settings with other devices.
The model ID of the exclusive messages used by this instrument is 00H 00H 2BH.
Data Request 1 (RQ1)
This message requests the other device to transmit data. The address and size
indicate the type and amount of data that is requested.
When a Data Request message is received, if the device is in a state in which it is able
to transmit data, and if the address and size are appropriate, the requested data is
transmitted as a Data Set 1 (DT1) message. If the conditions are not met, nothing is
transmitted.
Byte Explanation
F0H Exclusive status
41H ID number (Roland)
dev Device ID (dev: 10H–1FH, 7FH)
00H Model ID #1 (RD-800)
00H Model ID #2 (RD-800)
75H model ID #3 (RD-800)
11H Command ID (RQ1)
aaH Address MSB
bbH Address
ccH Address
ddH Address LSB
ssH Size MSB
ttH Size
uuH Size
vvH Size LSB
sum Checksum
F7H EOX (End Of Exclusive)
* The size of data that can be transmitted at one time is xed for each type of data.
And data requests must be made with a xed starting address and size. Refer to the
address and size given in “3. Parameter Address Map” (p. 9).
* For the checksum, refer to 15 page.
Data Set 1 (DT1)
This is the message that actually performs data transmission, and is used when you
wish to transmit the data.
Status 2nd byte 3rd byte
F0H 41H, dev, 00H, 00H, 75H, 12H, aaH, bbH, F7H
ccH, ddH, eeH, ... H, sum
Byte Explanation
F0H Exclusive status
41H ID number (Roland)
dev Device ID (dev: 10H–1FH, 7FH, Initial value is 10H)
00H Model ID #1 (RD-800)
00H Model ID #2 (RD-800)
75H Model ID #3 (RD-800)
12H Command ID (DT1)
aaH
bbH
ccH
ddH
eeH
: :
H Data
sum Checksum
F7H EOX (End Of Exclusive)
* The amount of data that can be transmitted at one time depends on the type of
data, and data will be transmitted from the specied starting address and size.
Refer to the address and size given in “3. Parameter Address Map” (p. 9).
* Data larger than 256 bytes will be divided into packets of 256 bytes or less, and
each packet will be sent at an interval of about 20 ms.
* Regarding the checksum, please refer to p. 15.
Address MSB: upper byte of the starting address of the data to
be sent
Address: upper middle byte of the starting address of the data
to be sent
Address: lower middle byte of the starting address of the data
to be sent
Address LSB: lower byte of the starting address of the data to
be sent.
Data: the actual data to be sent. Multiple bytes of data are
transmitted in order starting from the address.
5
MIDI Implementation
2. Data Transmission
Channel Voice Messages
Note o
Status 2nd byte 3rd byte
8nH kkH vvH
n = MIDI channel number: 0H–FH (ch.1–16)
kk = note number: 00H–7FH (0–127)
vv = note of velocity: 00H–7FH (0–127)
Note on
Status 2nd byte 3rd byte
9nH kkH vvH
n = MIDI channel number: 0H–FH (ch.1–16)
kk = note number: 00H–7FH (0–127)
vv = note on velocity: 01H–7FH (1–127)
Control Change
* By selecting a controller number that corresponds to the setting of parameters
of controllers (Pedal, Assign 1–5, S1, S2), the 6 can transmit any control change
message.
Bank Select (Controller number 0, 32)
Status 2nd byte 3rd byte
BnH 00H mmH
BnH 20H llH
n = MIDI channel number: 0H–FH (ch.1–16)
mm, ll = Bank number: 00 00H–7F 7FH (bank.1–bank.16384)
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Control value: 00H–7FH (0–127)
* These messages are transmitted when Damper pedal is operated.
Portamento (Controller number 65)
Status 2nd byte 3rd byte
BnH 41H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Control value: 00H–7FH (0–127)
* These messages are transmitted when Portamento Switch is set in External Layer.
Sostenuto (Controller number 66)
Status 2nd byte 3rd byte
BnH 42H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Control value: 00H–7FH (0–127)
Soft (Controller number 67)
Status 2nd byte 3rd byte
BnH 43H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Control value: 00H–7FH (0–127)
Legato Footswitch (Controller number 68)
Status 2nd byte 3rd byte
BnH 44H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Control value: 00H–7FH (0–127) 0–63 = OFF, 64–127 = ON
Resonance (Controller number 71)
Status 2nd byte 3rd byte
BnH 47H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Resonance value (relative change): 00H–7FH (-64–0–+63)
* These messages are transmitted when Resonance value is set in External Layer.
6
MIDI Implementation
Release Time (Controller number 72)
Status 2nd byte 3rd byte
BnH 48H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Release Time value (relative change): 00H–7FH (-64–0–+63)
* These messages are transmitted when Release Time is set in External Layer.
Attack Time (Controller number 73)
Status 2nd byte 3rd byte
BnH 49H vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Attack time value (relative change): 00H–7FH (-64–0–+63)
* These messages are transmitted when Attack Time is set in External Layer.
Cuto (Controller number 74)
Status 2nd byte 3rd byte
BnH 4AH vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Cuto value (relative change): 00H–7FH (-64–0–+63)
* These messages are transmitted when Cuto value is set in External Layer.
Decay Time (Controller number 75)
Status 2nd byte 3rd byte
BnH 4BH vvH
n = MIDI channel number: 0H–FH (ch.1–16)
vv = Decay Time value (relative change): 00H–40H–7FH (-64–0–+63)
* These messages are transmitted when Decay Time value is set in External Layer.
<<< RPN >>>
Control Changes include RPN (Registered Parameter Numbers), which are extended.
When using RPNs, rst RPN (Controller numbers 100 and 101; they can be sent in any
order) should be sent in order to select the parameter, then Data Entry (Controller
numbers 6 and 38) should be sent to set the value. Once RPN messages are received,
Data Entry messages that is received at the same MIDI channel after that are
recognized as changing toward the value of the RPN messages. In order not to make
any mistakes, transmitting RPN Null is recommended after setting parameters you
need.
This device transmits the following RPNs.
RPN Data entry
MSB, LSB MSB, LSB Notes
00H, 00H mmH, llH Pitch Bend Sensitivity
mm: 00H–18H (0–24 semitones)
ll: ignored (processed as 00H)
00H, 01H mmH, llH
00H, 02H mmH, llH
00H, 05H mmH, llH Modulation Depth Range
mm, ll: 00 00H–06 00H
(0–16384 x 600 / 16384 cent)
7FH, 7FH ---, ---
Channel Fine Tuning
mm, ll: 20 00H–40 00H–60 00H
(-4096 x 100 / 8192–0–+4096 x 100 / 8192
cent)
Channel Coarse Tuning
mm: 10H–40H–70H (-48–0–+48
semitones)
ll: ignored (processed as 00H)
RPN null
RPN and NRPN will be set as “unspecied.”
Once this setting has been made,
subsequent
Program Change
Status 2nd byte
CnH ppH
High Resolution Velocity Prex (Controller number 88)
Status 2nd byte 3rd byte
BnH 58H kkH
n = MIDI channel number: 0H–FH (ch.1–16)
kk = High Resolution Velocity Prex: 00H–7FH (0–127)
Eect 1 (Reverb Send Level) (Controller number 91)
* These messages are transmitted when Chorus value is set in External Layer.
RPN MSB/LSB (Controller number 100, 101)
Status 2nd byte 3rd byte
BnH 65H mmH
BnH 64H llH
n = MIDI channel number: 0H–FH (ch.1–16)
mm = upper byte (MSB) of parameter number specied by RPN
ll = lower byte (LSB) of parameter number specied by RPN
n = MIDI channel number: 0H–FH (ch.1–16)
pp = Program number: 00H–7FH (prog.1–prog.128)
* When Rec Mode is ON (EDIT: Utility: Rec Setting: Rec Mode), these messages are
transmitted when Tone is selected.
Pitch Bend Change
Status 2nd byte 3rd byte
EnH llH mmH
n = MIDI channel number: 0H–FH (ch.1–16)
mm, ll = Pitch Bend value: 00 00H–40 00H–7F 7FH (-8192–0–+8191)
Channel Mode Messages
MONO (Controller number 126)
Status 2nd byte 3rd byte
BnH 7EH 01H
n = MIDI channel number: 0H–FH (ch.1–16)
* These messages are transmitted when Mono/Poly value is set to MONO in External
Layer.
POLY (Controller number 127)
Status 2nd byte 3rd byte
BnH 7FH 00H
n = MIDI channel number: 0H–FH (ch.1–16)
* These messages are transmitted when Mono/Poly value is set to POLY in External
Layer.
7
MIDI Implementation
System Exclusive Messages
Universal Non-realtime System Exclusive Message and Data Set 1 (DT1) are the only
System Exclusive messages transmitted by the RD-800.
Universal Non-realtime System Exclusive Message
Identity Reply Message
Receiving Identity Request Message, the RD-800 send this message.
Byte Explanation
F0H Exclusive status
7EH ID number (Universal Non-realtime Message)
dev Device ID (use the same as the device ID of Roland)
06H Sub ID#1 (General Information)
02H Sub ID#2 (Identity Reply)
41H ID number (Roland)
75H 02H Device family code (RD-800)
00H 00H Device family number code (RD-800)
00H 00H 00H 00H Software revision level
F7H EOX (End of Exclusive)
Byte Explanation
F0H Exclusive status
41H ID number (Roland)
dev Device ID (dev: 00H–1FH, Initial value is 10H)
00H Model ID #1 (RD-800)
00H Model ID #2 (RD-800)
75H Model ID #3 (RD-800)
12H Command ID (DT1)
aaH
bbH
ccH
ddH
eeH
: :
H Data
sum Checksum
F7H EOX (End Of Exclusive)
* The amount of data that can be transmitted at one time depends on the type of
data, and data will be transmitted from the specied starting address and size.
Refer to the address and size given in “3. Parameter Address Map” (p. 9).
* Data larger than 256 bytes will be divided into packets of 256 bytes or less, and
each packet will be sent at an interval of about 20 ms.
Address MSB: upper byte of the starting address of the data to
be sent
Address: upper middle byte of the starting address of the data
to be sent
Address: lower middle byte of the starting address of the data
to be sent
Address LSB: lower byte of the starting address of the data to
be sent.
Data: the actual data to be sent. Multiple bytes of data are
transmitted in order starting from the address.
8
3. Parameter Address Map
* Transmission of “#” marked address is divided to some packets. For example, ABH in
hexadecimal notation will be divided to 0AH and 0BH, and is sent/received in this
order.
1 RD-800 (Model ID = 00H 00H 75H)
Individual Parameters
* Please don’t use a parameter or a address marked <Reserved>.
* The parameters for Live Set are temporary. If you want to leave the parameters after
In MIDI documentation, data values and addresses/sizes of exclusive messages etc.
are expressed as hexadecimal values for each 7 bits.
The following table shows how these correspond to decimal numbers.
* Decimal values such as MIDI channel, bank select, and program change are listed as
one (1) greater than the values given in the above table.
* A 7-bits byte can express data in the range of 128 steps. For data where
greater precision is required, we must use two or more bytes. For example, two
hexadecimal numbers aa bbH expressing two 7-bits bytes would indicate a value
of aa x 128 + bb.
* In the case of values which have a ± sign, 00H = -64, 40H = ±0, and 7FH = +63, so
that the decimal expression would be 64 less than the value given in the above
chart. In the case of two types, 00 00H = -8192, 40 00H = ±0, and 7F 7FH = +8191.
For example if aa bbH were expressed as decimal, this would be aa bbH - 40 00H =
aa x 128 + bb - 64 x 128.
* Data marked “nibbled” is expressed in hexadecimal in 4-bits units. A value
expressed as a 2-byte nibble 0a 0bH has the value of a x 16 + b.
<Example 1>
What is the decimal expression of 5AH?
>From the preceding table, 5AH = 90
<Example 2>
What is the decimal expression of the value 12 34H given as hexadecimal for each 7
bits?
>From the preceding table, since 12H = 18 and 34H = 52
18 x 128 + 52 = 2356
<Example 3>
What is the decimal expression of the nibbled value 0A 03 09 0D?
>From the preceding table, since 0AH = 10, 03H = 3, 09H = 9, 0DH = 13
((10 x 16 + 3) x 16 + 9) x 16 + 13 = 41885
<Example 4>
What is the nibbled expression of the decimal value 1258?
16) 1258
16) 78... 10
16) 4... 14
0... 4
Examples of Actual MIDI Messages
<Example 1> 92 3E 5F
9n is the Note-on status, and n is the MIDI channel number. Since 2H = 2, 3EH = 62,
and 5FH = 95, this is a Note-on message with MIDI CH = 3, note number 62 (note
name is D4), and velocity 95.
<Example 2> CE 49
CnH is the Program Change status, and n is the MIDI channel number. Since EH = 14
and 49H = 73, this is a Program Change message with MIDI CH = 15, program number
74 (Flute in GS).
<Example 3> EA 00 28
EnH is the Pitch Bend Change status, and n is the MIDI channel number. The 2nd byte
(00H = 0) is the LSB and the 3rd byte (28H = 40) is the MSB, but Pitch Bend Value is a
signed number in which 40 00H (= 64 x 128 + 0 = 8192) is 0, so this Pitch Bend Value
is 28 00H - 40 00H = 40 x 128 + 0 - (64 x 128 + 0) = 5120 - 8192 = -3072
If the Pitch Bend Sensitivity is set to 2 semitones, -8192 (00 00H) will cause the pitch
to change 200 cents, so in this case -200 x (-3072) / (-8192) = -75 cents of Pitch Bend is
being applied to MIDI channel 11.
<Example 4> B3 64 00 65 00 06 0C 26 00 64 7F 65 7F
BnH is the Control Change status, and n is the MIDI channel number. For Control
Changes, the 2nd byte is the controller number, and the 3rd byte is the value. In a
case in which two or more messages consecutive messages have the same status,
MIDI has a provision called “running status” which allows the status byte of the
second and following messages to be omitted. Thus, the above messages have the
following meaning.
In other words, the above messages specify a value of 0C 00H for RPN parameter
number 00 00H on MIDI channel 4, and then set the RPN parameter number to 7F
7FH.
RPN parameter number 00 00H is Pitch Bend Sensitivity, and the MSB of the value
indicates semitone units, so a value of 0CH = 12 sets the maximum pitch bend range
to +/- 12 semitones (1 octave). (On GS sound sources the LSB of Pitch Bend Sensitivity
is ignored, but the LSB should be transmitted anyway (with a value of 0) so that
operation will be correct on any device.)
Once the parameter number has been specied for RPN or NRPN, all Data Entry
messages transmitted on that same channel will be valid, so after the desired value
has been transmitted, it is a good idea to set the parameter number to 7F 7FH to
prevent accidents. This is the reason for the (B3) 64 7F (B3) 65 7F at the end.
It is not desirable for performance data (such as Standard MIDI File data) to contain
many events with running status as given in <Example 4>. This is because if playback
is halted during the song and then rewound or fast-forwarded, the sequencer may
not be able to transmit the correct status, and the sound source will then misinterpret the data. Take care to give each event its own status.
It is also necessary that the RPN or NRPN parameter number setting and the value
setting be done in the proper order. On some sequencers, events occurring in the
same (or consecutive) clock may be transmitted in an order dierent than the order
in which they were received. For this reason it is a good idea to slightly skew the time
of each event (about 1 tick for TPQN = 96, and about 5 ticks for TPQN = 480).
* TPQN: Ticks Per Quarter Note
Since from the preceding table, 0 = 00H, 4 = 04H, 14 = 0EH, 10 = 0AH, the answer is
00 04 0E 0AH.
14
MIDI Implementation
Example of an Exclusive Message and Calculating a
Checksum
Roland Exclusive messages are transmitted with a checksum at the end (before F7)
to make sure that the message was correctly received. The value of the checksum is
determined by the address and data (or size) of the transmitted exclusive message.
How to Calculate the Checksum (Hexadecimal Num-
bers are Indicated by ‘H’)
The checksum is a value derived by adding the address, size and checksum itself and
inverting the lower 7 bits.
Here’s an example of how the checksum is calculated. We will assume that in the
exclusive message we are transmitting, the address is aa bb ccH and the data or size
is dd ee H.
aa + bb + cc + dd + ee + = sum
sum / 128 = quotient ... remainder
128 - remainder = checksum
(However, the checksum will be 0 if the remainder is 0.)
<Example1> Setting DELAY TYPE to DELAY"TREMOLO (DT1)
According to the “3. Parameter Address Map” (p. 9), the start address of Temporary Live
Set is 10 00 00 00H, the oset address of DELAY at Live Set is 04 00H, and the address
of DELAY TYPE is 00 02H. Therefore the address of DELAY TYPE of Setup is;
10 00 00 00H
04 00H
+) 00 02H
10 00 04 02H
DELAY"TREMOLO has the value of 03H.
So the system exclusive message should be sent is;
F0 41 10 00 00 75 12 10 00 04 02 03 ?? F7
(1) (2) (3) (4) (5) Address size Checksum (6)
ASCII Code Table
Live Set Name of MIDI data are described the ASCII code in the table below.
This means that F0 41 10 00 75 12 10 00 04 02 03 67 F7 is the message should be sent.
<Example2> Getting Live Set Common data of the Temporary Live Set (RQ1)
According to the “3. Parameter Address Map” (p. 9), the start address of Temporary Live
Set is assigned as following:
10 00 00 00H Live Set Common
And the data size of Live Set Common is 00 00 00 7FH.
Therefore the system exclusive message should be sent is;
F0 41 10 00 00 75 10 00 00 00 00 00 00 7F ?? F7
(1) (2) (3) (4) (5) size checksum (6)
(1) Exclusive Status (2) ID (Roland) (3) Device ID (17)
(4) Model ID (RD-800) (5) Command ID (RQ1) (6) End of Exclusive
Calculating the checksum as shown in <Example 1>, we get a message of F0 41 10 00
00 75 10 00 00 00 00 00 00 7F 71 F7 to be transmitted.
15
Digital Piano
Model RD-800
Function...TransmittedRecognizedRemarks
Basic
Channel
Mode
Note
Number :
Velocity
After
Touch
Pitch BendOO
Control
Change
Program
Change: True Number
System ExclusiveOO
System
Common
System
Real Time
Aux
Messages
Notes
Default
Changed
Default
Messages
Altered
True Voice
Note On
Note O
Key’s
Channel’s
: Song Position
: Song Select
: Tune Request
: Clock
: Commands
: All Sound O
: Reset All Controllers
: Local On/O
: All Notes O
: Active Sensing
: System Reset
MIDI Implementation Chart
1–16
1–16
Mode 3
Mono, Poly
**************
0–127
*************
O
O 8n V = 0–127
X
O *2
O
0, 32
O
1
O
2
O
4
O
5
O
6, 38
O
7
O
8
O
10
O
11
O
16
O
17
O
18
O
19
O
64
O
65
O
66
O
67
O
68
O
69
O
70
O
71
O
72
O
73
O
74
O
75
O
76
O
77
O
78
O
80
O
81
O
82
O
83
O
84
O
88
O
91
O
92
O
93
O
94
O
95
O
98, 99
O
100, 101
O
0–127
O
**************
X
X
X
O
O
O
O
X
O
O
X
*1 Recognized as M
*2 Transmitted if assigned to Foot Controller 1/2, LAYER LEVEL sliders 1–4.
*3 Transmitted if assigned to UserCC
O
O
O
O
O
O
O
O
O
O
X
X
X
X
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
X
X
X
X
O
O
O
O
O
O
O
X
O
X
O
0–127Program No. 1–128
X
X
X
X
X
O (120, 126, 127)
O
X
O (123–127)
O
X
Memorized
*1
Bank select
Modulation
Breath type
Foot type
Portamento time
Data entry
Volume
Balance
Panpot
Expression
General purpose controller 1
General purpose controller 2
General purpose controller 3
General purpose controller 4
Hold 1
Portamento
Sostenuto
Soft
Legato footswitch
Hold 2
Sound variation
Resonance
Release time
Attack Time
Cuto
Decay time
Vibrato rate
Vibrato depth
Vibrato delay
General purpose controller 5
General purpose controller 6
General purpose controller 7
General purpose controller 8
Portamento control
High Resolution Velocity Prex
General purpose eects 1
Tremolo
General purpose eects 3
Celeste
Phaser
NRPN LSB, MSB
RPN LSB, MSB
Date: Jan. 1, 2014
Version: 1.00
Mode 1 : OMNI ON, POLY Mode 2 : OMNI ON, MONO
Mode 3 : OMNI OFF, POLY Mode 4 : OMNI OFF, MONO
16
O : Yes
X : No
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.