Sending Program Change msg to i2M to change Mode

[PaulK]

Hi James

Is each mode assigned a program number in the i2M and what are they?
Must Prog Chg messages be sent on a specific midi channel for the i2M to "see" them?
I have a midi controller (MPK mini) hooked up to my MacBook Pro sending Program Change msgs
which are being received by my computer, verified with a Midi monitor program.

I am hoping I can change i2M modes this way but dont know how to accomplish this.
Hoping you can give me some more info regarding this.

I opened the mac's AudioMidi Setup program. The cable connections you draw here are simply providing information to MIDI applications about what devices are present and how they are connected; they are not creating software MIDI routings.

Cheers
Paul

[james]

Each mode can have a program number assigned to it for use with program change. By default this is "off", but can be set from 1-128.

The program change message can be sent on any MIDI channel, and then the mode according to the program number sent (if there is a match) will be selected. If two modes are set to the same program number, the first matching selection will be activated.

So, for example, if you set mode 1 to "program change" #10, then you can select mode 1 by sending program change 10 to the i2M's MIDI port.

[PaulK]

Thanks James, I managed to do this,
so much easier than having to find the tiny mode switch and having to hold for 2 seconds to get to "orange" modes.
I use all 4 modes during one composition, triggering different bass lines, for each of the 4 sections
in the piece.

I think most controllers work on Midi numbers 0-127. From my MPK mini I send 0 1 2 3 not 1 2 3 4, having set the I2m interface to 1 2 3 4.

Thanks again for a great product.

Paul

[james]

Paul,

I'm glad you got it working.

Regarding the numbering, it used to be pretty standard to display program change from 1-128 (even though the actual value sent is 0-127). The idea was to make it more user-friendly. Standard GM sound sets are usually tabulated with numbers from 1-128 too. So, we went with the same approach.

But, maybe things have changed in recent years?

(As an aside, while looking at this I noticed the range of the velocity filter is wrong: off, 0-128. When in fact it should only go to 127. This will be fixed in the next editor update.)