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?
The post above points you to the Windows MIDI Services discord server. The fix is there in preview (it will be in Windows at the end of the month). You didnât need to go through everything you did.
Iâm surprised you found these issues on at least two separate forums, but never saw the posts about the workarounds and the Discord server with the support. I donât know what more I can do to get this information out there.
Iâve asked a few times now to start a thread on the Discord server so we can get you sorted out. The fix works if the instructions are followed. Dozens of people have tried it already, and itâs exactly what is going to go into Windows.
Itâs nearly impossible to follow-up across all the other places where you have posted this. I get your frustration, but I canât help you if you wonât do this.
Iâm just now getting back into some projects using Windows to run a setup that uses loopMIDI and rtpMIDI a good bit.
I have zero experience messing with release candidates and âsdkâ packages, so I have a few basic basic questions before I mess with anything.
Will it be be much longer until the fix with all the âtoolsâ that go with it comes down the pipeline on its own?
If I do decide I need to try RC4 in the next week or so, will the automatic update releases that come out every month simply take its place or do I have to watch and manage it all manually until the end of time?
I gather Windows MIDI Service now supports virtual ports with some extra tools installed; but, is there something in the kit that can also replace rtpMIDI? If I do still need to keep rtpMIDI, would there be any major advantage to dropping loopMIDI in favor of the Windows virtual ports (Donât they both use bonjour or something instead of the native Microsoft hooks)?
I downloaded the KSA preview and installed all downloads as per Microsoft Peteâs instructions and loopMIDI, used for my StreamDeck profiles, worked perfectly once more (it had been randomly losing connection with Cubase after the faulty WIN 11 update).
I then took a brave pill and de-installed LoopMIDI, rebooted, then entered all of my old loopMIDI port names directly into windows MIDI via the downloaded Windows MIDI Setting App, and my StreamDeck is working perfectly again with Cubase. The MIDI Setting App is great once you realise how it works! No going back.
The tools and SDK will be released outside of Windows for at least the next year, if not longer. We need to be able to rapidly iterate there to meet customer/partner needs.
The tools and SDK are needed for apps that support MIDI 2.0. So, for example, when Cubase supports MIDI 2.0, youâll need a compatible version of the SDK Runtime installed. But weâve not at 1.0 yet, so the package isnât signed.
The tools, like MIDI settings, are needed only if you want to do things like change port names, create native loopback endpoints, debug issues, etc. It does a lot of the things that tools like MIDI-OX do, and also includes troubleshooting tools and info for, for example, fixing issues caused by KORG driver installer/uninstallers.
And, if you want to see which version of a service plugin is running, this page tells you the version info and path. If itâs in Windows\System32, itâs what was delivered with the update. If itâs in Program Files, itâs a preview.
Command-line tools for working with MIDI, including the MIDI console
Scriptable PowerShell cmdlets for MIDI
Other more technical utilities often used by support or people trying to get more insight into MIDI on their PC. For example, the midiksinfo tool shows the device information from our USB/KS stack so that someone can verify that the device is represented correctly, or the midimdnsinfo tool which shows all the Network MIDI 2.0 endpoints on the network.
The mididiag utility used to create a dump of everything MIDI-related to share with support folks. This is also run from a button in the MIDI Settings app
The midifixreg utility for fixing the KORG driver uninstaller problems (also run via a button in the MIDI Settings app)
So, thereâs a lot there that has been asked of us over the years.
No. Windows update doesnât do anything with that.
The KSA preview fix, which is just an installer like any other app, will get overwritten by updates. This is documented on Discord. On the plus side, that KSA preview fix will be in Windows starting at the end of this month. But thereâs a 30 day window during which the new feature may or may not be enabled on your PC. If not yet enabled, youâll get the old broken behavior. If you wish, you can uninstall and reinstall the preview to ensure you have a working version, and then after the 30 day window has closed, use the instructions on Discord to revert back to the in-box version.
We have no control over that 30 day CFR process. Itâs how feature updates work now.
Please note that uninstalling updates really causes a ton of confusion for everyone. I know that has been the go-to approach in the past, but right now, it just uninstalls fixes and just about every customer Iâve worked with has no idea exactly which updates they uninstalled and when. The new MIDI stack went out at the end of January. Everyone with updates enabled on non-domain joined PCs, has it now.
The only reason we have the previews available is to help customers who need it now. Normal approach would be to just wait for the Windows update. You are free to do that if you want to and are able to.
Use what works for you. Our in-box loopbacks work on x64 and Arm64 whereas the third-party solutions do not. Our in-box solution does not require any additional kernel drivers. However, our internal implementation also does not do any infinite loop detection currently, like what loopBE does. Beyond that, itâs up to you.
If you ask me what I want people to use? Well, Iâd prefer to be done with all third-party drivers for MIDI and audio, and would rather invest the time in making our in-box stuff better and reducing the dependency on third-party drivers. But that is not something weâre forcing.
Although itâs being considered, weâre not offering an rtpMIDI implementation any time in the near future. However, we will have Network MIDI 2.0, currently in preview in Windows (and also in Beta on macOS) which you can use on x64 and Arm64 Windows 11 PCs.
Our native Network MIDI 2.0 implementation does not rely on Bonjour; we use the native Windows mDNS implementation.
