Hmm, looks like Microsoft are getting their act together around MIDI:
Now MIDI 2.0 may become relevant - @brad, is there a roadmap for MIDI 2.0 in Cantabile somewhere in your mind?
Until now the roadmap has been based on discussions with Pete Brown (author of that post) and was: wait till Microsoft gets its act together.
2 Likes
I’m afriad I won’t be holding my breath ../Steve
Heads-up: the new services are already being rolled out via Windows update - and they have some breaking bugs: amongst others, all my virtual MIDI ports (loopMIDI, loopBE, …) have suddenly stopped working - they’re just not seen anymore by the Windows system…
This seems to be due to an issue with the new MIDI stack.
If this affects you, there is a quick and dirty hack - should work as long as you have less than 16 virtual MIDI ports. You simply stop and re-start the Windows MIDI Service, either using the Windows Services Dialog (CTRL-R → services.msc) or using an admin-level commandline:
net stop midisrv
net start midisrv
Or you can use my script 
, which does the same, automatically enabling admin level…
Restart MIDI.zip (583 Bytes)
To be sure: this applies only if you already have the new MIDI stack - you can find out by downloading the checker tool here:
Looks like this when the new service is installed:
Find out more here:
The positive: the new Windows MIDI services bring their own loopback mechanism, so tools like loopMIDI aren’t really needed anymore. Just a bit of migration work will be required…
2 Likes
I’ve hit a number of problems with the new MIDI services. The most serious, so far, are connected with the Stream Deck. I have yet to try Cantabile, but I’ll report back when I have.
I noticed a few nights ago that I had no MIDI in either Cantabile or Cubase, but it was back the following evening, but I think I need to do a full check tomorrow
For me I wasn’t able to restart the service until both loopmidi and rtpmidi were removed, then a reboot. I am not sure which did the trick, but since not using either at the moment, no loss (my understanding is that the SDK tools let you create “simple loopback”, they are talking about “network midi” but based on a quick scan through some references, this is not compatible with rtp/applemidi, happy to be corrected).
yes, this is a different approach, but from some MS posts I gathered that RTP Midi is under consideration for a later release.
interesting - on my system it just took a restart of the service after loopMidi and rtpMidi were active. After the restart, both ports were available again and functioning nicely.
OK, it looks like I have not been upgraded yet - I ran the checking application, so I still have no clue why I had no MIDI the other night. It all seems to be working again…
I am a little concerned with this direction as rtpMIDI is really important to me. I have used loopMIDI but that is not so essential so long as rtpMIDI remains functional.
I have the new MIDI system active. LoopMIDI seems to have stopped working on my system, despite my following workaround guidelines. But the new built-in loopback ports do seem to be working as an alternative.
A few things are broken on my system since the update, including my MIDI-over-MADI ports and the Stream Deck MIDI plug-in. I’m working my way through the problems to find solutions I can live with. I have yet to try Cantabile on the new system, but will ASAP.
I have found it useful to delay starting the StreamDeck app until all virtual MIDI ports are properly initialized, otherwise the MIDI plugin (and the Cubase plugin) complains. So far, I have forced the StreamDeck autostart to wait for 3 minutes after login; that has been very useful.
Maybe it is a good idea to de-activate autostart and start the Streamdeck app manually after a MIDI Service restart - at least until Microsoft have implemented their fixes to the MIDI service - ETA appears to be late March…