I have suddenly started to have issues in both CB 14 and CB 15 during startup, they freeze on Midi Initialisation.
I am on Win 11 and I have had no issues before.
I had an Win 11 update yesterday and after that the problems started.
So I began to wonder if it may have to do with Windows new updates for Midi 2.0.
But according to the MS MidiChechService tool the Midi 2.0 implementation seems to be ok.
Is there anyone out there that can have a look at the dmp files to see what is going on, please!?
I had a similar issue with a new build 2 days ago. What midi devices are you using and were you using MidiRT by any chance? if so you can revert back to the default windows midi as midi 2.0 seems to be better. Aslo if you are running RT you need to check āsystem time stampā as well now.
I have a Motu 828ES and a Focusrite Clarett PreX with Midi connections, but I am currently primarily using my old ESI M8UXL midi interface.
Not using Midi RT due to the ESI being a bit old.
I have uninstalled the update and will see if it works better now.
Are you using our in-box MIDI driver, or the ESI driver?
If the latter, have you tried with our in-box MIDI driver? Most third-party drivers are no longer necessary (for class-compliant MIDI devices) because everything in the new MIDI stack is multi-client.
Looking at the downloaded ESI driver, Iām not sure why it would be running into issues. However, it also looks like itās not needed. Using our in-box driver for the ESI interface should be fine because itās class-compliant. It even says in the manual that no driver is needed for Windows.
I had Motu, Clarett, ESI M8UXL and a M-Audio Midisport 2x2 connected to the PC running Win 11 when the issues started.
After disabling ESI and M-Audio devices, and then updating ESI with MS driver, I now have Cubase 14 and 15 working ok with the ESI connected.
I cannot find a suitable driver (MS or other) for the M-Audio device so it is currently disconnected.
I also reinstalled the latest Win update, so everything seems to be OK now, except I guess I have to replace the Midisport device.
The m-audio midisport seems to be the common item in most of the problems weāre seeing reported here.
It has always been a problem on Windows, but because the old driver approach had apps talking pretty much directly the driver, it only affected the app, and they could ignore it, crash, whatever.
Weāre looking into it, but not sure what can be done. If the midisport was created from the early 2000s onward, those are all class-compliant and will work with our in-box driver. (The manual says it works on macOS without a driver, which means itās class-compliant).
If itās one from the 90s with a serial port + usb on the back, those pre-date the USB MIDI 1.0 standard, and so cannot use our in-box driver.
Another customer just tried with that second midiman, and itās not working with the in-box driver. Information online is confusing, because it doesnāt specify which of the dozens of models itās referring to when it comes to class compliance.
I have some used ones ordered from Reverb and will see if I can figure out whatās up. Like I said, the drivers were always buggy, so TBD if we can do anything. But Iāll investigate. It wonāt be short-term regardless.
(And, oddly, that same customer has 3 Windows 11 PCs, all with Windows MIDI Services installed, and this driver and same interface works on 2 of the 3).
Thank you so very much for all the support with this issue.
I have a quite old Midisport 2x2 (metal colour) and I even had problems finding suitable drivers for Win 10 lately, so I guess it will be hard to get it to work now.
But it would be great to know if later versions, like the Anniversary model, may be class-compliant and therefore work under Midi 2.0.
Iāve ordered several of the older midisport/midiman devices to test here. Unfortunately, the seller canceled the order for the one you have. Getting the new version will be the quickest path to resolution for you.
Completely uninstall the older drivers from your PC before plugging in the new device.
The culprit youāre talking about is the new multi-client MIDI stack, and it currently has issues with the midisport when you use the m-audio drivers. Those drivers have always had compatiblity problems, but under the new stack, they impact more than just a single connection.
The new black & green midisports work fine with our in-box drivers. Weāre debugging what we can do with the older ones.
Hi, long time Nuendo user hijacking the thread. I have both the older 2x2 midisport and the black and green anniversary 4x4. The 2x2 was crashing Nuendo so Iāve ditched that. However, I still need the 4x4. I originally I used the old maudio drivers, which worked briefly then locked up Nuendo. So I unplugged, uninstalled the drivers and rebooted windows, hoping the class compliant drivers would take over. However, the 4x4 is now sitting under āother devicesā in device manager and not working. What can I do?
)
