MRCC as a PC MIDI Interface

[PDofCC]

We've just posted a draft of the User Manual and we would like to know if you can find the answer to your questions there. If not, we need to add that to the manual and would appreciate your input!
MRCC Draft User Manual

To answer your question, the 12 ports available on the PC MIDI Interface connection are 12 independent inputs and 12 independent outputs on the MRCC, and also appear as 12 independent inputs and 12 independent outputs on the PC. You can route from any inputs to any outputs.


We don't really have a good excuse to include this many USB MIDI virtual ports on the PC interface, it would be great to know if anyone has a use case for this. Our only use case is using independent USB MIDI virtual outputs from MRCC to standalone soft-synths which on a Windows PC can't share ports. We aren't DAW experts, but we've seen evidence that using MIDI channels in a DAW is prefered to using independant virtual ports. 

While we are on the topic, each of the MRCC host ports have 4 USB MIDI virtual inputs, and 1 USB MIDI virtual output. We did not see a use case for multiple virtual outputs, though we have discovered 1 device (besides other MIDI routers) with 2 USB MIDI virtual inputs, the Korg SQ-1.

Hi Darryl, many thanks for this reply and the draft manual, they are very helpful.  This looks to be really flexible, which is great.  I have several input devices (keyboards, Roli Seaboard, sequencer, NDLR) some of which use 5-pin MIDI and some use USB-MIDI.  I envisage having these all plugged permanently into the MRCC physical inputs.  I then have several synths, using both 5-pin and USB MIDI, and a MIDI to CV converter for interfacing to Eurorack.  Again I envisage having these all plugged permanently into the MRCC physical outputs.  When I'm recording to or playing back from my DAW, with the MRCC connected to the PC via its PC USB host port, I believe I'm going to see 12 MRCC Ins and 12 MRCC outs in the DAW list of available MIDI ports, as shown in your reply above, and I would then assign on the MRCC which physical input and output is attached to which PC MRCC input and output.  And it looks like running VSTis alongside hardware synths in the DAW environment is just a matter of assigning the appropriate input for playing the VSTi.   I'd need to be consistent on all of the output assignments otherwise different DAW songs might start playing back tracks on different physical outputs but I don't see that as a problem, and it looks like I can save particular routings as Presets on the MRCC which will also help.  All in all it looks great, and I can't wait to get an MRCC!  Many thanks for your help.