I’m running Hapax hosting MRCC, and computer hosting Hapax.
Therefore I need to deploy some THRU lanes from MRCC thru Hapax into computer.
However it seems that currently, setting Host->Device MIDI thru merges messages from all 16 host lanes into the first device lane.
While I see how this could be useful for some and how it is possibly the best default option, I also believe this needs to be extended from simple on/off switch to multiple routing options:
- 16:1 = current behavior of merging all incoming lanes into first outgoing lane
- 16:16 = H1 → D1, H2 → D2… H16 → D16
- 4:1 = H1+H2+H3+H4 → D1… other lanes don’t go thru
- 4:4 = H1 → D1… H4-> D4… other lanes don’t go thru
- 4:2 = H1+H2 → D1, H3+H4 → D2… other lanes don’t go thru
- possibly some other configurations
What do you think? Anyone else find the current behavior limiting?
This would be applicable Host-Device as well as to Device-Host.
x:1 varieties would be applicable to Host/Device to MIDI X thru routings.