Just a heads up, Microsoft is starting to roll out some MIDI updates, and this can cause problems. Apparently things like LoopMIDI can be affected.

https://devblogs.microsoft.com/wind...ervices-rollout-known-issues-and-workarounds/ (related to these previously announced updates)

While I welcome the updates (multiclient MIDI interfaces, yeeeah!), might be worthwhile to postpone these updates until there's some time to fix it (i.e. not during a big project).

 

good to know!

sharing info from github repo:

MIDI Feature Enablement Checker for Retail 24H2 and 25H2

Windows MIDI Services in-box components are rolling out to supported retail versions of Windows (not Insider builds) throughout the end of January and into February, via Windows Update. It takes approximately 30 days for the rollout to complete and the feature to be enabled on all PCs.

Please let the process complete normally, and do not install any Service builds on your PC, or else you will need to reset/reinstall your PC to have a functional MIDI system. There is no way to force the feature to be enabled on your PC ahead of time.

We'll have a new version of the SDK and Tools available after or near completion of the rollout. The previously available rc1 version will continue to work with the in-box components only if the feature is enabled on your install, but we recommend that non-developer customers wait for the February release of the SDK and tools.

This tool will tell you if Windows MIDI Services in-box components are installed and enabled per our controlled feature rollout process.

https://github.com/microsoft/MIDI/releases/tag/enablement-checker