After the update, Cubase would no longer find the midi devices connected via RME UFX midi ports and tc helicon Voice Live Play GTX. Workaround: Close Cubase and open it again.
Uninstalling all USB drivers in the Device Manager fixed the issue with the RME UFX, but not with the tc helicon. Workaround: moved the tc helicon to 5pin-Midi and got rid of the USB connection. It works, but only one-way (which is all I need in my case).
Cubase still hangs for about 20 seconds on first startup at the item “MIDI”, which went by so fast before the Midi 2.0 update that I did not even notice. This happens only on the first startup of Cubase, after that it loads fast as before. I had no crashes at any time, though.
Takeaway: If you run into problems with the Midi 2.0 update, uninstall drivers and reboot, if that does not help, check all your USB midi devices one by one.
Hopefully, MS will have a look at the tc helicon Voice Live Play drivers.
My system is now absolutely stable again (as before).
Be creative and have fun!
Pondstreetstudios
Win 11, Intel i7, Cubase 13
USB Midi devices (all working!): RME UFX, Nord Grand, Nymphes, Intech Grid, ESI M8UeX, Morningstar MC8 Pro
Sounds like it comes with drivers, then? It’s hard to find info about this device, and the manual is pretty sparse on tech details.
When you say Cubase would no longer find the MIDI devices, are you saying that the devices (even potentially under a different name) don’t appear in the MIDI setup page, or are you saying Cubase warned of a disconnected device on startup? IIRC, the latter can mean that the port name changed.
20 second startup: This is expected and will vary based on how many MIDI ports you have. Right now, I have over 100 inputs and 100 outputs, and it takes close to a minute. It’s why the MIDI Settings app prompts you to set the service to auto-start with Windows. However, with the loopMIDI/dynamic ports etc. bug right now that is not doable. In any case, we’re also looking to see how we can speed that up.
Having it auto-start with Windows by default was not an option. We’re not allowed to add even a second to the Windows startup time
Thanks, @Pondstreetstudios . I have the TC Helicon VLP (I guess it’s a Music Tribe item now, in terms of support). Good to know. Sounds like if I want to keep using my VLP then any update to W11 will require a new interface, since mine doesn’t have a 5-pin MIDI input.
“Cubase no longer finds Midi devices” = the “midi connection not found” message in Cubase does not appear on startup of Cubase, only when opening a project; this is normal Cubase behaviour e.g. if a synth is linked to a midi port in the project (or via the “midi device manager” in Cubase) and the midi interface is not switched on - you’ll be familiar with that.
In my case, the midi port of the VLP GTX was is not missing (neither in W11 nor in Cubase), and Cubase would find the connection after closing Cubase and starting it again; the problem re-appears after each reboot of W11
Correct, not all VLPs have 5-pin Midi, the VLP GTX does. In my case, the workaround was quite simple: Close Cubase and start it again. I just don’t like workarounds…
So, no need to discard your VLP or to stay away from W11! In the W11 device manager, the VLP would appear normally after the Midi 2.0 updated, and no driver issues were reported. So, I can’t quite explain why Cubase would report a lost connection.
