I am trying to see if there is anybody who would be able to give an advice on this.
Electra is a MIDI class compliant device. It means no drivers needed to get it working when you connect it to a computer. This works perfectly on Mac OS X and Linux. It also works on Windows but there is a big drawback. The Windows MIDI driver allows only one application to access/use the device at the time. So if you want to use the editor and the DAW in the same time you will fail. This problem was reported long ago by the @ColdSteel. I was trying to find some decent way to resolve it, develop own driver or find some work around (loopback driver), anything. But I am not very familiar with Windows…
I am developing a new console app. Over the time this application will become the native editor app. The application is developed in the JUCE framework. I was hoping I could create a virtual port there - but again - not supported on Windows even in JUCE.
Does anybody have any pointers on how this could be solved. I am perfectly ok with developing own driver in C++. But there is almost now documentation available from Microsoft on that. I also tried to reach Tobias from virtualMIDI | Tobias Erichsen but no response.
Immediate workaround would be to do it over midi instead of USB, than the midi interface would need to be multi client (which the iconnectivity stuff is).
Iirc iconnectivity licensed their driver from thesycon (don’t remember the exact name). You could ask them.
Re writing your own’ ask Pete from Microsoft (psychlist1972 on every forum)
I don’t use windows … but I know a few friends that do…
they seem to always be recommending LoopBe to handle this side.
I’ll ask them for more details, but from memory, they just seem to accept that windows is not great in this area - and so have these workarounds.
(I think as mac users we sometimes take for granted how good core audio/midi is!)
Yes, this is an unnerving topic on Windows. According to this: MIDI Enhancements in Windows 10 - Windows Developer Blog as long as the code is using the old Win32 MME DLLs, as most likely all code out there still does (JUCE as well), there is no multi-client USB for Midi.
Only the “new” (in 2016) Windows 10 UWP MIDI API allows multi-client. Not even sure if JUCE is compatible with UWP apps (which is seemingly the new Microsoft API).
@martin FYI I bought an ERM Multiclock, which comes with multi-client midi drivers for Windows. I checked the install files and apparently they licensed the driver called “MIDIJunction2” from usb-audio.de (Ploytec)