So one of the things that is limiting me in the midihub is the way that midi mapped parameters work.
Midi message is mapped as “port x, CC y,”
My expected behaviour is that the midi CCs would be picked up from the stream within the pipeline. This means it doesn’t care which controller the CC came from, or which port.
Some of the issues this would resolve for me:
I use the midihub live attached to my MPC One by USB, but I program my patches (as I HAVE to) with the USB port connected to the PC. This means any mappings I do from MPC Midi programs don’t work, because they’re mapping to a DIN MIDI port, not a USB MIDI port. I can’t continue using DIN MIDI mappings, as I need the DIN MIDI port on my MPC for other tasks. I need to access the USB port on the midihub.
Moving the midi ports - if I map a CC then happen to have that controller plugged into a different MIDI port, the map doesn’t work because it’s expecting “Port A,” or whatever. We already have channels in MIDI to separate messages, this is the system that should be used by midi mapping.
It also opens up a lot of macro/hyper control possibilities if the mapped CCs are read from the pipeline.