09-25-2025, 12:44 PM
[Wrote the following in August of 2021 and just found the draft...don't know why it didn't ever get posted, but figured better late than never to have it on record.]
Looking over this again, and summarizing a bit, I figure 3 things would need to happen for the MRCC and MidiHub integration to be more or less fully successful, and for the record I don't have high expectations on this as it's a pretty tall order.
1 - The MRCC host ports would have to be 4x4, over the current 4x1.
2 - Whatever USB communications magic that needs to happen for both devices to respond to each other has to be engineered.
3 - The MRCC would have to pass more than just MIDI data from the PC to the MidiHub and back.
On this last point, one of the key elements of MidiHub is the setup and control functionality on the software editor. It's true, once programmed, a MidiHub can be taken out into the wild and used with presets stored in it, without the presence of a PC, however for studio use, experimentation with its modifiers (which is its core differentiator) would be done with it online. It has no facility to control or edit on the box itself. Having recently established that my keyboard controller, the Novation 61SL mk3, works fine over USB through the MRCC for routing MIDI data, but doesn't communicate with its companion editor software the way it does when connected directly to the PC, it seems likely neither will a MidiHub. There's still the possibility of connecting a MidiHub to a PC and routing to and from the MRCC via the virtual ports, which so far in my experience requires tracks in a DAW to be set to send and receive MIDI data to devices. I'm only just making headway with this scenario using an MRCC in Studio One, it will take some more aggravation, I mean fun experimentation, to see if I can get both devices swapping signals through the DAW.
Looking over this again, and summarizing a bit, I figure 3 things would need to happen for the MRCC and MidiHub integration to be more or less fully successful, and for the record I don't have high expectations on this as it's a pretty tall order.
1 - The MRCC host ports would have to be 4x4, over the current 4x1.
2 - Whatever USB communications magic that needs to happen for both devices to respond to each other has to be engineered.
3 - The MRCC would have to pass more than just MIDI data from the PC to the MidiHub and back.
On this last point, one of the key elements of MidiHub is the setup and control functionality on the software editor. It's true, once programmed, a MidiHub can be taken out into the wild and used with presets stored in it, without the presence of a PC, however for studio use, experimentation with its modifiers (which is its core differentiator) would be done with it online. It has no facility to control or edit on the box itself. Having recently established that my keyboard controller, the Novation 61SL mk3, works fine over USB through the MRCC for routing MIDI data, but doesn't communicate with its companion editor software the way it does when connected directly to the PC, it seems likely neither will a MidiHub. There's still the possibility of connecting a MidiHub to a PC and routing to and from the MRCC via the virtual ports, which so far in my experience requires tracks in a DAW to be set to send and receive MIDI data to devices. I'm only just making headway with this scenario using an MRCC in Studio One, it will take some more aggravation, I mean fun experimentation, to see if I can get both devices swapping signals through the DAW.