Forum Discussion

RobertoTafuro's avatar
RobertoTafuro
Copper Contributor
Dec 19, 2025

Midi issues on latest version

Good morning everyone, I hope someone can help me.
I work on a company machine that had the Insider Preview option enabled. Thanks to your help, I managed to leave the Insider channel and move to the Beta channel, waiting for the new official release. Unfortunately, I wasn’t able to move to the official release by mounting the ISO image.

I’ll try to be brief and explain what’s happening as clearly as possible. Everything starts from the need not to format the machine. The installed version of Windows is the latest Insider build with all updates. I believe the system has switched to MIDI 2.0, and this is causing major issues with my setup.

I have several MIDI devices: TD-17, APC64, Launch Control XL3, MPC One+, and a Midi Fighter Twister mapped via CSS as a controller for Ableton Live parameters. In Live everything works correctly, and in Device Manager everything is recognized.

I recently bought a Stream Deck, which I mainly use as a small mixer for Live. To work properly, it needs two Mackie ports to be set in Live. Unfortunately, I cannot get LoopMIDI to work at all.

Here’s what happens: when I install LoopMIDI, either as administrator or not, the ports are not recognized in Device Manager. In the registry I keep finding only a single MIDI entry (Windows NT – Current Version…) pointing to what I believe is the new wdmaud2.drv driver. I’ve read practically everything I could find online.

At that point, I tested some drivers called Springbeats, which install eight MIDI ports. These ports are finally recognized by the system, I can configure the Stream Deck, everything works. However, after rebooting the PC, with no background processes running, Live shows the Mackie port as already in use.

Yesterday I decided to uninstall everything, clean the registry of all entries, and reinstall LoopMIDI. The two Mackie ports (in and out) were recognized, everything worked correctly even after a reboot. Then I added a third MIDI port needed for a VST, and this morning, after rebooting the machine, LoopMIDI was gone again.

In Device Manager the ports were shown in gray. I uninstalled everything again, removed the new MIDI registry entries (pointing to wdmaud2.drv), cleaned the registry once more, and reinstalled LoopMIDI. But now, once again, LoopMIDI is not recognized, and neither are its ports. The program runs, but the driver is not recognized.

I’ve really exhausted all my options and I can’t understand how everything can be so unstable and unpredictable. I hope someone can help me solve this. Thank you very much.

 

 

1 Reply

  • Rendiyu's avatar
    Rendiyu
    Iron Contributor

    The wdmaud2.drv driver you mentioned is part of Windows' newer audio/MIDI stack, especially with MIDI 2.0. This driver can cause issues with traditional MIDI device management.

    LoopMIDI and similar virtual MIDI drivers often depend on the older, more stable Windows MIDI stack, which can conflict with newer drivers.

Resources