I just got the Cubase15 going and picked up a SSL UF8. It does not show up in the midi port selection. Now I read there is a bug with Windows 11 midi. So far it said to delete the KB updates but now this is getting above my computer skills paygrade. Why do they have to …. with things that were probably already working. Am I missing something here? What a nightmare![]()
Deleting a couple of the updates fixed it. Wow that was frightning.
Glad you got it working. I was going to suggest reinstalling the core SSL 360 software and ensuring it’s started and recognized before launching Cubase.
If that uses the SSL 360 link software, it’s an order of startup issue, same as loopMIDI and others.
In the current release of Windows MIDI Services, you need to
- Start the software that creates the ports (SSL 360)
- Restart midisrv
- Open Cubase
In that order.
We’re working on the fix.
Pete
Microsoft
Seems to be working now. Thank you for the reply.
Hi, it stopped working again. I can’t find where to restart the midisrv. Midi 2.0 is not listed in the service list. Is there anything else I can do Im right in the middle of a project![]()
I deleted one of the Kb updates and it works again. Its must have reinstalled the update when I tuned it off last night cause I had already deleted it.![]()
I have similar issues. I’m using the SSL UC1 and UF-1. The startup behavior is very unpredictable and also I get a lot of startup errors when closing/starting Cubase but I’ll wait for the fix of Microsoft and live with it in the next couple of days.
The service name is “Windows MIDI Service”. Short name is midisrv
Pete
Microsoft
After the deinstallation of the Midisport 2x2 usb driver I don’t experience any issue with the startup/shutdown of Cubase anymore.
I hope that this will stay. But I would also like to still be able to use my old Midisport 2x2 device if possible. Don’t work too often with my HW synths attached, therefore I can at the moment live with it, but it would be nice not to spend money into buying a new compatible midi-to-usb converter.
Thanks Paddy
Since I deleted one of the updates the UF8 and Cubase have been working together.![]()
We’re working on debugging the issue with the InMusic drivers (m-audio, AKAI, RANE, etc.). They all crash.
Pete
Microsoft
I’ve had the UF 8 and UF 1 for a few months and all was working well. Noticed a windows update and now no connection at all. They don’t even show up. I hope there is a fix soon.
It may be worth reinstalling your SSL 360 software just to see if that fixes it.
I deleted one of the KB updates and havent had any issues since.
Yes, it seems to be connected to the windows update. I rolled back the latest update and all is working again. Thanks for the tip.
After two weeks of observation now. For me I didn’t need to roll back any windows update. I just needed to deinstall the M-Audio/Midisport Midiman 2x2 driver. Since then everything Cubase related runs rock solid. Really happy about the current stability since I did this.
The KB update is what provides the new MIDI stack, with multi-client MIDI and MIDI 2.0 support.
With the KB uninstalled, those inMusic drivers are still hanging, but you may not notice it because typically they just cause Cubase to hang on close and maybe not save your preferences.
Pete
Microsoft
