Question About Midi Mapping.

[Conner_Bw]

Maybe you can make a compromise with the following solutions?

Channel Router And Note Router:

New Tools: Channel Router And Note Router

Here are two tools for routing midi notes to separate tracks and instruments. Channel Router splits midi notes by channel: notes on midi channel 1 are sent to track 1, instrument 0; notes on channel 2 are sent to track 2, instrument 1, etc. Note Router only transmits C4 notes. The base note (C4 by default) triggers instrument 0 on track 1; the next note triggers instrument 1 on track 2, etc. Both tools require that the OSC server is running in TCP mode on port 8000. This is the first version…

Scaled Midi Octave Input:

New Tool (2.7): Scaled Midi Octave Input

Hi, After getting frustrated with the midi mapping of midi controllers to octave selection (see here) I decided to write this tiny tool to provide an alternative implemetation. Anyway, I’m putting this out there as others appeared to be interested in the original thread. This implementation works as follows: In the default midi mapping the midi CC value is directly set as the octave selection as follows: CC Octave 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 8 . . . . 127…

Hope this helps.