After installing updates KB5077241 and KB5077181, the virtual MIDI ports from loopMidi and rtpMidi were no longer recognised on my computer either.
I then performed the workaround by restarting the Windows MIDI service. The virtual MIDI ports from loopMidi and rtpMidi worked again, but the Fireface - ARC USB connection (even after switching the FF 802 or ARC USB off and on again) no longer worked. I tried various things, including rebooting and switching the devices off and on again, but nothing worked. So I had no choice but to uninstall the two Windows updates and hope that a bug fix will be available soon. The new virtual Windows MIDI ports could replace loopMidi for me, but not rtpMidi.
I use an SSL Nucleus that is controlled via ipMIDI. The Windows update KB5077181 causes a crash/blue screen when ipMIDI is started! If you uninstall the update, everything works fine again. I have now paused automatic Windows updates.
At the same time, I get a warning that paused updates are a security risk. Thatâs not satisfactory.
Iâm not sure if the workaround described above also works with ipMIDI.
Thank you for your comment. After installing updates KB5077241 and KB5077181, as well as âWindows MIDI Services Basic Loopback Previewâ, âWindows MIDI Services Runtime and Toolsâ and âKSA Transport Previewâ, all my HW MIDI controllers (Behringer X-Touch, AKAI MPD 218, RME ARC USB, Studiologic SL 73 and SLMixFace) are functioning. TouchDaw (Android app) also works via rtpMidi and AVID Control (Android app) via EUCON. My StreamDeck also works via Windows MIDI Loopback Endpoints, but not via loopMidi. I havenât been able to get loopMidi to work. After uninstalling all of the above updates and previews, loopMidi works again, but after reinstalling all updates and previews, it doesnât work again. Uninstalling and reinstalling loopMidi and restarting the Windows MIDI services doesnât help either. However, since the loopback endpoints of the Windows MIDI services work perfectly with my StreamDeck, I donât have a problem with loopMidi not working for me.
Unfortunately, after installing updates KB5077241 and KB5077181, as well as âWindows MIDI Services Basic Loopback Previewâ, âWindows MIDI Services Runtime and Toolsâ and the âKSA Transport Previewâ, the system did not work properly for long. At first, there were sporadic issues when initialising my Behringer X-Touch (unknown device, error code 43). Eventually, I couldnât get the X-Touch to work at all. I then uninstalled âWindows MIDI Services Basic Loopback Previewâ, âWindows MIDI Services Runtime and Toolsâ and âKSA Transport Previewâ, switched from TouchDaw to TouchOSC and no longer use a MIDI plugin with my StreamDeck. So I no longer need rtpMidi and loopMidi at the moment, but I have to do without some features. I hope there will soon be a stable MIDI environment with virtual MIDI connections for Windows again.
With the KSA preview installed and then uninstalled, youâre going to lose access to all MIDI 1 devices unless you follow the instructions in the Discord channel about how to restore the in-box version.
âDidnât work properly for longâ doesnât really tell me anything I can use, unfortunately.
The Behringer X-Touch giving a driver error will be unrelated to the new MIDI stack.
The KSA transport preview fixes loopMIDI/rtpMIDI and related issues.
Unfortunately, I didnât think things through properly and ended up mixing up USB device detection with the MIDI issue. And Iâm sorry that, due to my haphazard approach, I wasnât able to provide any helpful information about my problems in the end.
Subsequently, I deleted numerous unused USB devices that were still listed in the software devices, and then made a fresh attempt by installing âWindows MIDI Services Basic Loopback Previewâ and âWindows MIDI Services Runtime and Toolsâ. Everything is working perfectly.
However, after installing âWindows MIDI Services Runtime and Toolsâ, I had the problem that the âWindows Musician Settings Preview (MidiSettings.exe)â window wasnât visible on the desktop. The fix described on GitHub ( [Bug][Preview 13] MidiSettings.exe opens on phantom Desktop 2 (window invisible) ¡ Issue #784 ¡ microsoft/MIDI ¡ GitHub ) didnât work. I suspect this is because I work with virtual desktops and the standard registry entry does not exist in this case. What worked for me was manually moving the âinvisibleâ window (click on the icon in the taskbar, then use the âAlt + Spaceâ shortcut and select âMoveâ from the context menu, then move it with the cursor and mouse to the current desktop).
I really love the clear display of MIDI devices and endpoints and the monitoring options in the MIDI settings app.
Regards, Detlev
Translated with DeepL.com (free version)
I got everything working after putting in the new midi two updates.
However, I do see some problems with the sysex thatâs going out for the x-touch colours - sometimes they update, sometimes just one is incorrectâŚ
Sometimes the naming does not update either.
Are there timing issues with the new midi2?
Anyone had these issues?