Re: Midi messages

Hi John,

What about a tuning bank select message (rpn 4)?
http://www.midi.org/about-midi/tuning.htm

Actually, seems all the rpns from 5 upwards are free too
as they have never been assigned to anything. As there
are 16,384 of them available to assign, and only 5 have ever
been assigned, all in the original midi spec, I suppose
if one chose a large rpn like 8192, or say, a range of
rpns from 8192 upwards, it is hardly likely any of them
will be registered to mean anything in the very near future.

Perhaps one should hesitate about using a rpn - but doesn't
seem that likely that many more will be added in the immediate
future, I suppose one never knows,...

Or, possibly a nrpn? I'm not sure what issues are involved
in using those.

I wonder if rpns or nrpns are easier to insert than a sysex?

Just a few thoughts.

The rpns are easier to program for at low level api, as
in Windows C anyway, you need to use special function
calls just for sysexes (as the standard lowlevel api ones only
let you send two bytes of data at a time).

Basically, you have to fill a buffer with the sysex, and
then send that, and the way it is done in Windows is quite
complicated.

I don't know the details as I haven't needed to do it yet.
That's for midi relaying - of course they are easy to read
from a midi file.

Of course that level of things doesn't affect most, as the
programmer of whatever program one is
using will have done it (and I'm sure it won't be that
hard to do if I ever do need to to it!).

Robert