▲

[MB_SOFT]

Over the past few months I have often received reports of issues from my users due to BASS_MIDI_InGetDeviceInfo not working after Windows 11 updates. Ai told me that: The BASS_MIDI_InGetDeviceInfo function fails because Windows 11 updates introduced the new Windows MIDI Services stack. This update conflicts with legacy drivers or causes the new service to capture MIDI devices , hiding them from BASS library calls.

Would it be possible improve BASS_MIDI in order to be compatible with this new Windows MIDI Services stack?
In my app i use BASS_MIDI_Input to receive notes from midi controllers.

[Falcosoft]

Ai told you false information. On Windows BASS_MIDI_InGetDeviceInfo is just a wrapper around WinMM's midiInGetDevCaps function. It's not a driver so it should not be modified in any way since the new Midi 2.0 stack should emulate the old behavior for legacy applications instead. The problem is that the previous and current versions of the new Midi 2.0 stack has many problems but they are not BASS_MIDI_InGetDeviceInfo specific. Your users most likely had problems with any applications that use WinMM Midi In enumeration and other WinMM Midi in related functions. Most common problem is that legacy Midi In ports disapperar or simply become unavailable.
You can reach the development thread on Github where you can follow and report problems related to the Midi 2.0 stack:
https://github.com/microsoft/MIDI/issues

And here are some known workarounds for known problems:
https://devblogs.microsoft.com/windows-music-dev/windows-midi-services-rollout-known-issues-and-workarounds/

 

[MB_SOFT]

The situation has further worsened. While BASS_MIDI_InGetDeviceInfo still doesn't list any devices, any other application (e.g., Reaper 32 bits) lists the devices normally:



i tried everything to get BASS_MIDI_InGetDeviceInfo back to wrk but failed.

At least, now that BASS_MIDI_InGetDeviceInfo stopped working also in my computers, i can run any test or debug version if Ian need it.

[MB_SOFT]

for now i was able to fix the problem with this:

Location `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32`
Registry Value Name: `UseLegacyMidi`
Registry Value Type: `REG_DWORD`
Value: `1`

[Ian @ un4seen]

This looks like a midiInGetDevCaps regression, where it fails unless midiInGetNumDevs is called first. Probably related to this issue:

   https://github.com/microsoft/MIDI/issues/972

It looks like a fix will be coming soon in another Windows update, but here's a BASSMIDI update that does call midiInGetNumDevs before midiInGetDevCaps anyway:

    www.un4seen.com/stuff/bassmidi.zip

Let me know if you still see the problem with it.

[MB_SOFT]

yes, this has fixed the problem for me!

thank you