03-04-2022, 02:56 PM
Oh dear.. I specifically picked up the MRCC to permanently connect a rig of ~10 modules/effects, all of which require sysex for editing.
It's a beautiful and polished device in many ways, but this is a significant limitation; considering that even the most modern synths typically still use sysex for various purposes (bulk dumps, firmware updates etc).
So the cleanest workaround then (without physically re-patching the cables), would probably be to connect a second, midi splitter/merger to one of the sysex-capable port I/Os and connect devices like effect modules or monotimbral synths to that, with different channel assignments.
Is there any chance it would be technically feasible / simpler for the short-term to create an option for ports to be switchable to this type of configuration? For example, repeating all port 6 I/O traffic to port 7, sharing the same com port.
It's a beautiful and polished device in many ways, but this is a significant limitation; considering that even the most modern synths typically still use sysex for various purposes (bulk dumps, firmware updates etc).
So the cleanest workaround then (without physically re-patching the cables), would probably be to connect a second, midi splitter/merger to one of the sysex-capable port I/Os and connect devices like effect modules or monotimbral synths to that, with different channel assignments.
Is there any chance it would be technically feasible / simpler for the short-term to create an option for ports to be switchable to this type of configuration? For example, repeating all port 6 I/O traffic to port 7, sharing the same com port.