MIDI Bluetooth Low Energy devices do not show up in GP (neither do they in most other DAWs). This is due to the fact that Microsoft only expose these devices using the WinRT/UWP APIs, not by the old MME APIs. Most DAWs and also GP use MME and thus do not ‘see’ the BLE devices. The reason for using MME is probably because it is rather stable and somewhat mature and developers has learned to live with it 
. Further more the WinRT/UWP subsystem is new (2016).
To overcome this issue, I’ve written a small program. It makes it possible to receive MIDI messages at one MIDI device and send them out on another device. These devices can be ‘normal’ MIDI device and/or BLE devices.
To make it work, you also need a virtual midi cable such as Tobias Erichsen’s loopMIDI (loopMIDI | Tobias Erichsen). When you create a virtual cable with the name ‘cable-a’ the flow looks like this:
Setup the router:
-
Unzip it to a folder
-
Scan the content for viruses: better safe than sorry!
-
Read the PDF, because you have to make a router config file and (hopefully) this tells you how
-
Start MidiUWPRouter.exe without extra arguments: That way you get all the device data that can be used in the filters. You can save these also to a csv by right-clicking in the device list
-
Create the router config file. There is one next to the application: routerconfig.txt, but that one was specific to my computer. Nonetheless, it might serve as a starting-point
-
Start MidiUWPRouter.exe with an extra argument that points to the configfile you created, for example:
MidiUWPRouter.exe d:\music\gp\MidiUWPRouter\routerconfig.txt -
You should see the program listing again all available devices, but also a log telling which devices got a assigned and alias and which routes were activated
- In Gigperformer do not use the output device of the virtual cable you created in LoopMIDI: it must be available for the router to use!
A screenshot what this looks like at my computer:
Double-click the guitar-pedal icon in the upper-left corner to close the program.
I’ve also created an installer. That one takes care of downloading the right dotnet version, etc. (if needed), but I’m not too fond of installers myself, although I need them often enough.
This one I have to add (although I did my best):
Disclaimer: Use at your own risk!
SHA256: 9EDA0542A4A258B606EB622A63570B5BCC1F2F9654ACBC840FD1AF296DF5A68E
MidiUDPRouter-0.9.0.4.zip (878.0 KB)
(UDP is a typo: should be MIDIUWPRouter-0.9.0.4.zip).
SHA256: 218223019A5140BC558CEC48CE80825BEF6F0C929919D1E584AEEF483154228A
MidiUWPRouter-NoInstall.zip (647.1 KB)
Source code: GitHub - frank1119/MidiListUWP: A MIDI router using the UWP on Windows
