06-03-2022, 06:43 PM
The way it's worded probably has to do with the orientation of switching control. An MRCC whose input you wish to route to an output is the one where the buttons determine the destination, either local or remote. However, the system is bidirectional, so the inputs on the other unit can also be routed to both local and remote outputs, you just have to do the actual routing on that one, since it's those inputs you're utilizing. Does that make sense? Probably not! Another way to look at it is, you can't call up inputs from the other device, but you can send to outputs on the other device, and that's true for both units in the pair. As a result, any input on either unit can go to any output on either unit. Also, there are 12 virtual PC inputs and outputs on each MRCC, so you could, for example, have a controller connected to a PC via USB, and route it with your DAW to a virtual port, and then on to a physical output. This could give you even more inputs and outputs, depending on your computer / USB setup.