12-08-2022, 06:58 AM
(This post was last modified: 12-08-2022, 07:09 AM by fredeke.
Edit Reason: no reason, i just like clicking edit buttons
)
Hello again.
Here's the thing: Windows is frustratingly limited in its MIDI implementation. Several times, I've found myself in a situation where I needed to install a software virtual MIDI interface, just to route the signal through some software operators. And those virtual thingies are all clunky and a pain to use.
I hoped I could use the MRCC instead: get the MIDI signal from the PC, filter/modify it, and send it back through (an)other virtual port(s). But apparently I can't. You can't route one of the 12 virtual PC ports to another.
I don't understand the reason for this limitation. I find it disappointing, and am considering returning my MRCC because it was an important part in my motivation to get one.
I know there are workarounds, like connecting a physical MIDI cable from one DIN socket to another, but then I don't need the MRCC for that.
Peace.
Here's the thing: Windows is frustratingly limited in its MIDI implementation. Several times, I've found myself in a situation where I needed to install a software virtual MIDI interface, just to route the signal through some software operators. And those virtual thingies are all clunky and a pain to use.
I hoped I could use the MRCC instead: get the MIDI signal from the PC, filter/modify it, and send it back through (an)other virtual port(s). But apparently I can't. You can't route one of the 12 virtual PC ports to another.
I don't understand the reason for this limitation. I find it disappointing, and am considering returning my MRCC because it was an important part in my motivation to get one.
I know there are workarounds, like connecting a physical MIDI cable from one DIN socket to another, but then I don't need the MRCC for that.
Peace.