I already did so !
Thanks. Sorry, a bit behind in the thread. I can’t reply in the translated window because the buttons don’t work. ![]()
Tools documentation: MIDI Tools - Windows MIDI Services
Pete
Microsoft
I really appreciate your support; thank you once again
![]()
I guess @Psychlist1972 has a red light in his room which alerts when you think of his name
I try to catch things in the Cubase/Nuendo/Dorico forums in English. This one was caught by an agent that I have run every morning:
And then I took your crash dumps and this is the response (different agent, now, because everything is AI and I mostly just babysit agents these days). This one I have set up to analyze crash dumps and check for MIDI issues.
The agent recommended disconnecting the CME, but I doubt that’s the issue. Could be, but I doubt it. And the ESI is a device I also have here, so unless you have one of those inexpensive 3-4 fader boxes that always crash cubase, I doubt that’s the issue. In any case, here’s the full response:
Verdict: yes, this is MIDI. It’s the same close-then-open hang we’ve seen with customers F, H and M.
- Dump 1 (quitting Cubase): Cubase’s UI thread is in
midiOutClose. wdmaud2 asked the MIDI service to close the port (DestroyClient) and never got an answer. That’s the “>5 minutes on Unload the Mix Console” he saw. Cubase had only been running for 1 min 36 s. - Dump 2 (12 minutes later, next start): Cubase’s UI thread is in
midiInOpen, waiting on the service to open the port (CreateClient). That’s “Initialize All MIDI Inputs”. The service was still stuck from the close, which is why only a reboot clears it. - Port being opened in dump 2: this was found in wdmaud2’s port table, not guessed. The port is named “cme”, on USB
0227:0227(Cubase lists “MIDIIN2 (cme)” and “MIDIOUT2 (cme)”). It’s probably a CME interface, but that’s an inference from the name. - Port that hung on close: dump 1 doesn’t say which port Cubase was closing. Only a midisrv dump taken during the hang can name the device that stopped answering.
- Other MIDI devices seen:
- ESI M8U XL (
0A92:1031, ports “M8U XL 1-8”). - A Novation device (
1235:0102, Launchkey Mini MK3 / Launchpad). - MOTU 828 MIDI.
- In Cubase’s port list: M-Audio Keystation 61es and Akai MPK mini 3, both inMusic brands.
- ESI M8U XL (
- Machine: PC
STUDIOB, German Windows, build 26300, 24 cores, wdmaud2 26100.9711.
His question, “are there problems with many MIDI connections?”: not the number of connections as such. One device’s driver stops answering, and the MIDI service waits on it forever, which blocks every app until a reboot. More devices just means more chances to hit a bad one.
Ask him:
- What is the “cme” device (which CME model)?
- Next time it hangs, before rebooting, take a memory dump of the MIDI service process (midisrv).
- In the meantime, unplug the CME device first, then the M8U XL, to see which one makes the hang stop.
@JuergenP you’re a celebrity now. You got name-checked by my daily MIDI agent ![]()
Pete
Microsoft
By the way, i love the MIDI Calculator!
@Psychlist1972 Pete, thank you for your additional comments.
The CME is a CME U-Key, obviously an older keyboard. I don’t know how old it is. I’m working to setup a few older synths for a musician who asked me to help him.
Thanks. I just looked up that keyboard, and it is USB MIDI 1.0 class-compliant and so does not need a driver, so it should be good.
Pete
Microsoft
Ok, so next is the Grammy ![]()
Für alle die hier (besorgt) mitlesen:
Ich habe auf 26H2 geupdated und habe keinerlei Probleme!
Danke @JuergenP
p:S.:
Systemspezifikationen in meiner Info
Kann es sein, dass Windows mit dem MIDI-Sequencer allen DAWs hier ne Kampfansage macht?
Wow, ich bin wirklich gespannt was da noch alles kommt.
Could it be that Windows, with its MIDI-Sequencer, is throwing down the gauntlet to all the DAWs out there?
Wow, I’m really looking forward to seeing what else is in store.
![]()
