A search on WinRT MIDI gave the following topic in the Steinberg Support (for Cubase 12):
Benefits of WinRT MIDI
Native support of Bluetooth MIDI on Windows
Better Plug & Play
Better handling of connected identical devices
Drawbacks of WinRT MIDI
Old MIDI hardware can run into compatibility issue because the MIDI ports are simply named “MIDI”. This is an issue that hasn’t been addressed in Windows, however, some components (e.g. some MIDI Remote implementations) rely on specific MIDI port names and they might stop working if WinRT MIDI is used. It is possible though to rename the MIDI ports in the Studio Setup allowing you to identify your ports at least.
var inputPort1 = driver.mPorts.makeMidiInput('PortName1')
var outputPort1 = driver.mPorts.makeMidiOutput('PortName1')
var inputPort2 = driver.mPorts.makeMidiInput('PortName2')
var outputPort2 = driver.mPorts.makeMidiOutput('PortName2')
var detUnit = driver.makeDetectionUnit()
var detectPortPair1 = detUnit.detectPortPair(inputPort1, outputPort1)
detectPortPair1
.expectInputNameEquals('MIDI Port 1')
.expectOutputNameEquals('MIDI Port 1')
var detectPortPair2 = detUnit.detectPortPair(inputPort2, outputPort2)
detectPortPair2
.expectInputNameEquals('MIDI Port 2')
.expectOutputNameEquals('MIDI Port 2')
Talking maybe about devices with identical port names? In this case, I really don’t know what will happen. But if they’re correctly recognized by the OS, we can always set the second pair to different names, using outside routing
In this same tab, click on Import Script and then select the installation file you downloaded earlier
Go to the low section of the project window, to the MIDI Remote tab. Click as usual on the big plus button. You will find under the Korg manufacturer, the device nanoKONTROL2 multi. Select it, and you’ll be prompted to enter 2 sets of MIDI in and out ports. Enter the ports of your devices
But no succes so far…
The part of disabling the existing script and importing your script worked exactly as you described.
Then I tried to configure your Multi remote .
But in the MIDI remote Port selection dropdown I only get to choose one NanoKontrol2 entry.
Then I tried to rename both units in the MIDI Port Setup window with suffixes 1 and 2.
This makes no difference in the MIDI Remote setup. Still one entry in the Port selection dropdown menus.
I think that if anyone would be able to ‘hack’ into the Korg internal itself, and change its “Internal MIDI ID Name” from nanoKONTROL2 to a user definable ‘something else’ name, then this problem would be solved i guess.
One other option I’m thinking about is that maybe I can connect three likewise devices from different manufacturers. That way they all have unique MIDI ID’s.
What do you think? Is this a way to create the 24 channel Mackie Control setup?
Just to be clear, once you select this port in the first combobox (midi input 0) and then you move to the second one (midi input 1), does the combobox shows this port name again or it’s not visible anymore?
It shows the same name again.
Now that you state your question like you did, i’m not sure whether it’s really the same port, or the other port with the same name.
Other issue i didn’t mention earlier is the follwing.
If I rename the units’ “Shown As” names in the MIDI Port Setup window (the suffixes 1 and 2 as seen above) it’s only a temporary distinction.
If I restart Cubase, there are two NK2 units with the same suffix (in my case they both had suffix 2).
Please select this port to both midi input fields. And then do the same for the midi outputs, and let’s see how this goes.
This is just for making it clearer to the user which port is which, based on his/her liking. Unfortunately it has nothing to do with the real names we’re interested in.
OK, you may want to download Bome MIDI Translator Pro trial, so that we can see if it’s possible (I think it is) to route one nano to some virtual ports. This way, we can then use these ports instead in the MIDI Remote setup.
Note that there are other utilities to perform such tasks, I just happen to not have used them yet.
OK, now create a new template in BMT, and click on the MIDI Icon on the top right corner.
You should now see at the bottom of this right-side tab, an area MIDI Router.
There you have to find ONE of your Nanos Midi Input and draw a line to, say, Bome MIDI Translator 1 Virtual Out.
At the same time, find ONE of your Nanos MIDI Output (on the right side) and draw a line again to Bome MIDI Translator 1 Virtual In.
Now, we should have a cross-midi of these ports.
Keep BMT open, and go to Cubase. Open the MIDI Remote window for adding our script (big plus icon) and let’s now see if you can set the second midi Input/Output pair to the Bome MIDI Translator 1, Ports.
