Midi mapping mystery

Midihub Support
2

Thanks for posting your patches


Unfortunately, this won’t affect your mappings:

  • In B.mhp, like A.mhp, they are fixed to specific MIDI channels coming in MRCC (DIN-A)

  • Once a mapping is learnt, Midihub will listen on Port X Channel Y to CC Z for the next mapping value as it enters Midihub

  • You might also do something else with that event as part of your patch, but this won’t affect the original mapping value
    (For Midihub to do this it would need to listen to a Virtual port which would bring a whole tranche of complications)

  • Conversely, incidentally, a “mapping port” doesn’t even need to be one of the input ports in the patch; so a patch might have only MIDI DINS, but all the mappings be from say USB-D. (For me, this fact helps pin down the distinction between mapping & ‘processed’ events)

Hope that clarifies.


To achieve what you want would need scaleable/internal/local mappings which aren’t yet available on Midihub.

In the meantime you would need to use a physical loopback.
In your context this would involve something like:

  1. sending Ch.9 CC 102/103 into the loop
    (Ch Filter allow only Ch9 in)

  2. use ChRemap mapped to MIDI MRCC Ch9 CC104 like now

  3. Ch Filter allow only Ch1-8 CC 102/103 out

  4. using a temporary append of the Loopback Mapping Tool to set your 16 TempoDiv & LFO mappings to the Ch.1-8 CC 102/103 values coming back into your loopback. (Hell, you can even map your MRCC Ch9 CC104 to its ChRemap to reduce the tedium!)

A loopback needs an in & out but with your set-up that looks quite feasible, possibly via the MRCC itself with judicious patching!



PS. Filter out the Clock!