I got a refund for Cubase 13.
Maybe I’ll come back to it later when the issues are resolved.
2 Likes
Wise move. I’ll leave it at that before I get banned.
1 Like
Good move. 
Got to be careful these days.
As I wrote in my other reply I tried that fix extensively and was about to post that it worked for me and that I didn’t have any locks at the Hub screen appearing.
Unfortunately it wasn’t, but I now have found the real cause for my problems. It was something at my end and as it often is with Computer technology it was something you wouldn’t think of any connection to your problem.
The story:
When I tried your suggested workaround, by pure coincidence at the same time I shot my Masterkeyboard due to connecting a wrong external power supply. The Masterkeyboard in question was a Studiologic SL 88 Grand and I used it via USB. I noticed some strange behaviour of MIDI in general and had the suspicion the SL 88 and maybe it’s buspower was the course.
Anyway, when I tried your fix, the SL 88 was just broken and I had disconnected it. During that period everything worked very stable and I thought, it was because of the preference setting for the Hub.
I had ordered a replacement and bought another SL 88 Grand and when that one arrived, as soon as I connected that over USB to my PC and started Cubase, it sure froze at the Hub like it did before.
So in my case it wasn’t anything network related and also no grafic glitch, it was MIDI-over-USB in combination with a crappy firmware of the device.
I sent the SL 88 back because the one I got as a replacement had additional problems and now Cubase is running perfectly again. Now I’m contemplating which 88-hammer-key Masterkeyboard I should get instead 
So what does that mean for Cubase and the problems, the OP and other people in this thread have::
It’s obvious that Cubase initializes some stuff around the time it shows the Hub. And when something goes wrong during that time, it will lead to a freeze.
Maybe it could be interesting and helpful for chasing bugs on the users end, when we knew what exactely is initialized at that time. Even better would be if Cubase just displays a message like “can’t initialize your friggin’ Studiologic Keyboard you dirtbag. Now I give up permanently” 
or something like that.
Is that possible?
3 Likes
Since the .21 release I’ve actually been able to use Cubase - two 4-hour sessions in 2 days and not a single glitch, let alone a crash. As always, ymmv.
So Kudos, Cubase devs.
3 Likes
Hi @Rainer_Hain
and thank you for your invaluable feedback. I’m glad to hear you could identify the root cause. I am forwarding this to the relevant team.
Cheers,
Armand
1 Like
Hi @Rainer_Hain . Thanks for sharing your observations with us. I totally agree, that it would be desireable that Cubase would display such a message. The problem is, that this would be very hard to do, especially doing it in a way that doesn’t have a negative impact on performance. I’ve analyzed quite some of these freezes and the typical situation that we observe is, that Cubase tells Windows to send a MIDI message and then it gets stuck within Windows MIDI subsystem. There’s no way to specify a timeout like: “try one second to send the message, otherwise cancel it”. We told Microsoft about the problems we observed, but they have problems to reproduce the issue(s). We’ll continue trying to find a solution. Thank you!
3 Likes
Tell 'em to get a Studiologic SL88 Grand and they should be able to reproduce it in no time 
Firmware I used was 1.70, but they need to upgrade to that anyway to get the keyboard actually working.
Anyway, it makes perfect sense what you wrote about it being also a Windows issue. I didn’t have the problems with the frozen hub right from the beginning of C13 and I also didn’t have other USB-MIDI-problems (some of my devices didn’t work until I resetted them by switched them off and on again).
It started at one point, but unfortunately I didn’t take notes when that was. I’m at the Windows Insiders program and running W11 23.xxxx (beta-)builts that get frequently updated. If I try to recall what happend was the problem with some USB-MIDI not initialized at the first try started with some W11 update. It also seems they tried to fix it with a later built and then the “freeze-at-hub-time” started.
So yes, it might be related to Windows MIDI.
BTW: I nver had that with C12 or even before. But when that problem started I tried C12 which I still had and sure enough the problem now also was there in C12. The hub froze on first start…
I vaguely remember that Pete Brown wrote on Gearspace that MS is actively working on MIDI in current development cycles, so it might be they did break something while in there
1 Like
Groove Agent craps itself in 96k mode,nearly kills Cubase with it.
SD2 an old software,loads instantly.
Create midi map from instrument broken as well (Windows 11).
I’m regularily in contact with Pete, also in context of the recent Windows MIDI development. But no, we see the issues with older builds of Windows 10 as well.
I guess I was lucky then. In all those years I’m doing this, starting with Cubase 1 PC on a Windows 3.11 and a later Win95 with a Unitor-8 and a Midex-8 up to now with W11 and all my devices connected over USB, the only thing that never gave me any headaches was MIDI. That always worked, no matter what. This problem now was the first time in over 30 years.
DO these issues only apply to MIDI connected directly to an USB-port of the host or does it also happen if one uses the classic MIDI-port on a dedicated MIDI-interface?
I’m not aware of any relevant difference here. Too my knowledge it should make no difference. But I cannot know, because it’s within Windows.
Cubase 13 is a bug-ridden mess. I just tried again with 13.0.21. It’s just intolerably buggy. I can’t do this.
You all should not have released this. You just shouldn’t. The leads responsible for pushing this out the door this need to have a stern talking to at the very least. This is level of poor quality just isn’t unacceptable.
What an irritating evening. I pull Cubase 12.0.70 back up and the very MIDI bug I was trying for way too long to try and diagnose is magically gone.
Like I said: bugridden mess. Should not have been released in this state. Whatever testing you are doing, it’s far from enough.
2 Likes