Win 11, MIDI 2.0 update : Workaround-Crash with Inmusic (Akai,m-audio) devices (combined MIDI/Audio)

Hello, Unfortunately, there seem to be massive problems with legacy audio hardware that uses a combined driver under Windows 11. This affects, among others, all older M-Audio (my M-Audio Firewire 1814 sadly comfirmed) interfaces fortunately not Focusrite Saffire FireWire (successfully tested with Saffire Liquid Channel 56) cards. The following symptoms occur in Cubase: The audio interface works without any problems, however, when closing Cubase OR when deselecting the affected MIDI channel, Cubase freezes, and often only a complete PC restart helps.
Here is the first workaround: Disabling MIDI in the Cubase preferences directly:
Ok, got it:
First: Focusrite even the old firewire devices should run FINE, tested!
Second: (Comfirmed - working!):

########## **Quick fix for Cubase for faulty MIDI devices **########
Open “Port Setup.xml”
in
C:\Users\AppData\Roaming\Steinberg\Cubase 14_64 (or your version number)
find your bad MIDI device, like

<item>
string name="ID" value="I|Windows MIDI|BAD DRIVER MIDI"/>
</item>

add a
<int name="Hidden" value="1"/>

so it should be:
<item>
<string name="ID" value="I|Windows MIDI|BAD DRIVER MIDI"/>
<int name="Hidden" value="1"/>
</item>

**Third: **another approach would be disabling bad MIDI devices directly in registry , but there are too many entries, didn’t dig too much into it.
Problem could be, that it would be activated again if you restart and or plug the device out and in…

Thanks and best regards, Matthias

Please no pointless discussion about “outdated” or “legacy” hardware….

The problem is with inmusic brand drivers (m-audio, AKAI, etc.). Not all older devices. Not all combined devices. We have no reports of Focusrite devices failing.

I would appreciate it if we could stick to what is known.

Pete
Microsoft

@Pete: I edited subject/text, sorry, I’m not carefully enough - I noticed in many posts that the emotions are running high.

1 Like