SysEx with values over than 7F

Question

Hi,

Inside a SysEx string, is not possible to have values more than 7F.
Values inside SysEx massage must be from 00 to 7F.
This is a Midi SysEx rules.

In your example, you wrote:

F0 <sysex reciever ID> B0 00 01 20 01 7F

When you want to send B0 00 01 20 01, is better to use (CC) Control Change commands. For your reference, your above example follow running status rules.
The original (without running status rules) is:
B0 00 01 B0 20 01
CC00 001 , CC32 001
Here you can use CC00 and CC32 (Bank Select) messages, following with PC (Program Change), maybe...

Also:

F0 <sysex reciever ID> 90 3C 3A 40 78 3C 6E 7F

90 3C 3A 40 78 3C 6E, follow running status rules.
The original is:
90 3C 3A, 90 40 78, 90 3C 6E
Here you can use Note On messages.

Solution.
On MD you can use a combination of buttons. Each button can transmit different kind of message and value. In this way you trigger just one button but the linked buttons transmit the rest of your midi data.

I am not shure for this, but maybe other solution is to program just one button on the MD but thinking SysEx and using the following trick.
Program any button to send SysEx data.
The MD send the first F0 and the last F7. Both F0 and F7 are hidden on MD because send this values internally. So, the values to be put, will be as follows:
90 3C 3A 40 78 3C 6E
I hope the MD will send F0 90 3C 3A 40 78 3C 6E F7

Last but not least.
Many devices use values over than 7F.
In this case, values larger than 7F,  you have to split or/and divide the value to e.g. upper and lower midi byte (MSB-LSB).

♪♫♪

Comments

Hmmm, Well sorry but you are wrong, there are higher values in a sysex string. The start and stop value confirms this. And I cant send a control message or note to a seperate device in a midichain without the sysex with any mididevice. Every device in that chain with the same midichannel active will excecute the command....

As you recomended late in the message to send sysex, well that's the problem... You can't type anyting higher than 127(7F) it won't work. And that's what the question was all about in the first place...

---

Dear sigglung,
Please, I am not wrong...

Maybe you mean simple MIDI commands (Note ON, Start/Stop, Control Change, etc), not SysEx message string.

YES, as you wrote, there are higher values as for example 0xFA (start), 0xFC (stop), etc.
BUT, these values are not included in a SysEx message string. These midi commands are not a part of SysEx message string. These midi commands are emitted individually, following a little bit different (easier) rules from the side of the midi player.

Also controllers and program changes (0xBn and 0xCn) are over as values BUT the transmission of these data follow completely different way - rules, mean are NOT between 0xF0...0xF7, mean are NOT inside a SysEx message string.

When we say SysEx message string, we mean something like this:
0xF0, Manufacturer ID, Device ID, Model ID, Command ID, Address (MSB...LSB), Data (0x00-0x7F), CheckSum, 0xF7
On the above example is not possible to have value (e.g. Data) over 0x7F. All values between 0xF0 and 0xF7 must be from 0x00 to 0x7F (0 to 127).

In some special cases where we need values over 0x7F, we must divide these values using MSB and LSB, depending the case and the specification of the receiver (Midi Device, e.g. sound module).

In the MIDI protocol we have some different types of commands - messages e.g.:
Note On/Off = 3 bytes length fixed
Control Change = 3 bytes length fixed
Program Change = 2 bytes length fixed
Start/Stop = 1 byte length fixed
SysEx = vary length <<< not fixed

In each of the above, the "Midi player" handle - manipulate the command - message in different way. Especially the SysEx message string, because its length is not fixed.

Thanks.

♪♫♪

---

Ok, fair enough. I guess I'm wrong. =) I'm not an experienced programmer in that way.

I guess I believed that channel messages and MTC and like, could be individually adressed(To a single mididevice) via a sysex string. And that is not possible then i guess?

//Sigge

---

Depending the case...

Basically, channel messages received by all midi devices are in the same midi chain and have open (Receive ON) the specific midi channel without any midi filtering from midi device side (e.g. Note, CC, SysEx, e.t.c.).

If you send channel messages to more than one midi device (in the same midi chain), you can filter the messages that will be accepted or ignored by the midi device itself, using his filtering midi options.
Of course, depending the programming capabilities of the (each) midi device.

Example of "same midi chain":
Controller Midi Out > Device 1 Midi In > Device 1 Midi Thru > Device 2 Midi In > Device 2 Midi Thru > Device 3 Midi In > e.t.c.

♪♫♪

Answer 1

=) Well yes that´s basic midi, and that I understand. We can leave this subject now if there are no other interrested in this matter. I got the questions I wanted answered, and since its a very special device I'm trying to make a controller to, I have to figure out adifferent way.

Answer 2

=) Well yes that´s basic midi, and that I understand. We can leave this subject now if there are no other interrested in this matter. I got the questions I wanted answered, and since its a very special device I'm trying to make a controller to, I have to figure out adifferent way.