[BUG] MIDI Service gets locked.

[m-komo]

Describe the bug
If I detach/attach a device while monitoring with midi.exe, monitor stops working and MIDI service seems to be locked.

• reproducible

  • USB MIDI 2.0 device running with the USB MIDI 2.0 driver (USBMidi2.sys).

• not reproducible

  • USB MIDI 2.0 device running with the USB MIDI 1.0 driver (USBAUDIO.sys).
  • USB MIDI 1.0 device running with the USB MIDI 2.0 driver (USBMidi2.sys).
  • USB MIDI 1.0 device running with the USB MIDI 1.0 driver (USBAUDIO.sys).

To Reproduce

1. Load the attached UUT_USB_MIDI_ECHO.uf2.zip firmware to the ProtoZOA.
2. Attach the ProtoZOA to the PC and update the driver to the USB MIDI 2.0 driver (UsbMidi2.sys).
3. Open midi.exe in two windows.
4. From one, monitor ProtoZOA.
5. From the other, run 'midi ep send 0x20901234' and choose ProtoZOA.
6. Make sure the monitor shows loop-backed message '0x20901234'.
7. Detach the ProtoZOA from the USB port.
   Monitor detects disconnection.
8. Attach the ProtoZOA again.
   Monitor detects re-connection.
9. Run 'midi ep send 0x20901234' again.

Monitor does not show any messages.

10. Run 'midi ep send 0x20901234 -c 5000'.

'send' command stops in the middle of sending process.
On the monitor window, press escape to stop monitoring, but monitoring cannot be terminated.
And also, it is unable to restart MIDI service. It is necessary to restart OS to recover.

Expected behavior
MIDI Service and Monitor command continues to work after reconnecting the device.

Installer Name or Version

• Windows.MIDI.Services.In-Box.Service.-.Developer.Preview.6.1.0.24194.2233-x64.exe

Desktop (please complete the following information):

• OS: Windows 11 24H2
• OS Build: 26100.1150

Device information, if this is with an external MIDI device:

• Any USB MIDI 2.0 device compatible with the USB MIDI 2.0 driver(USBMidi2.sys)
• Driver: [interim preview build] 240713-USBMidi2-x86-TESTSIGNED.zip (DriverVer = 07/13/2024,23.1.50.504)

Application Information

• 'midi.exe' console app.

[MusicMaker]

I have a similar issue with DP6 plug/unplug that took a day to figure out. (was working normally on DP5) This is on my own DIY MCU hardware. what worked was use "midi service stop" and then "midi service start", the service will send the discovery messages again on plug in or when the device stays plugged in.

[Psychlist1972]

"And also, it is unable to restart MIDI service. It is necessary to restart OS to recover."

If the service is locked up, open Task Manager, go to Details, find MidiSrv, and then right-click "end process tree". You will not need to reboot.

[sat-okada]

I confirmed the same behavior as this issue.
After OS has started, once I run "midi service restart", this problem does not occur even if I unplug and plug.

[starfishmod]

Want to add that I am getting this issue too in DP7.
If I use:
midi endpoint monitor
I then pull out the USB and then replug it back in - It will not receive any data on any application until I run midi service restart
Other USB MIDI 2.0 Devices can still send messages

[Psychlist1972]

Just wanted to update this so folks know we haven't forgotten. Just scheduling this investigation in with other high priority bugs.

[Psychlist1972]

Testing this with the latest bits I have here, I am not able to reproduce the issue with the Montage M. I haven't done anything specifically to address this problem, so I'm wondering if there's something else at play.

When I get a chance, I'll load the firmware on the protozoa and do the above test, in case there's something special about having two clients connected, or something specific with the protozoa.

But here's the Montage M info, connected to usbmidi2.sys. You can see that it sends regular active sensing, and you can also see its replies to discovery when reconnected.