Still this strange close behavior in Cubase 15.0.10 on W11

I am a little disapointed, no change on what appears to me a bug :

Let’s say I am working on a project and I openned a permanent popup as the perofrmance monitor.
If I save and close the project the popup stay open (but could be hidden) and I get the Hub Window. I would expect that the popup have closed with my project, but no chance.
If I try to close Cubase by closing the Hub, the hub seems to close but Cubase process do no close because the perfmon popup is still open.
When I close the popup the Hub re-appears and only at that step I can close the hub and end Cubase process. Complex, isn’t it ?
There were certainly major bugs to fix in this 15.0.10 and I hope this one will be catched by the next update.

Do you mean the performance monitor by pressing F12? If it was that just press F12 again and it will disappear at all, now and with the next opening.

On what OS are you?

I have just tried to reproduce the problem on Windows 11. I open a project, press F12, close and save the project and the monitor windows stays open. So far I can see the same as what you see.

However, if I then close the Hub it takes a couple of seconds and it completely closes down, the Cubase process and all related processes are cleanly shutdown.

So the only thing that I can see is the performance monitor dialog that is open, but that is not an issue at all. I can close it separately or it goes away with the rest of Cubase.

Same behaviour for me on Win 11 with C15 trial. My stubborn popup at close down tends to be a midi remote window, which btw I had never even opened!

Plus I’m still having ASIO freezes in the hub at start-up. Only a reboot will resolve. Not buying C15 until they fix the hub.

If you press F12 and close it will remain on just press F12 again before closing the project.

F12 is just a key command to fast watch the performance but you can have it (performance) implemented in the tool bar as well.

That’s a normal behaviour not a bug.

I didn’t say it is a bug

csurieux

I am a little disapointed, no change on what appears to me a bug.

I’ve just said that because of it.

Can you please add more info like: What kind of ASIO did you select and what’s your audio device?

So this kind of close process is normal ? :wink:

Recording 2026-01-31 123956.mp4

Audio device is Yamaha THR30 guitar amp modeller. Using the latest Yamaha driver. No problem with C14.

Sometimes the C15 Hub freezes completely. Sometimes only sound missing, then, if I select the SB generic driver, then switch back to the frozen Yamaha ASIO, it recovers.

It is written in title, isn’t it ?

Here a small video on W11

Hmm…. I should really read the title :slight_smile:

1 Like

Are the Yamaha ASIO selected in your studio settings?

Ok, from your video I can reproduce the same effect.

The difference to my previous test is, you tried to shutdown Cubase by clicking on the cross in the upper right corner. By doing this here I get the same effect.

If I shutdown with the File→Exit menu it does not do this, instead it ends correctly.

The weight of habits :slight_smile:

Ok, I see, so it is … a bug.

No, not a bug.
If you close the project window it is not the same as quitting the program. Since Cubase has windows that can be opened without a project being open (and therefore can exist without a project), closing the project window is just that - it closes a window.

The word bug gets used far too casually.

Looked at the wrong case. Therefore my answer did not fit the issue.

3 Likes

The behaviour in my W11 is:

If a close a project with Perfmon open it opens the hub with Perfmon still open.

If I close the hub everything closes.

If I open the project again it opens with the Perfmon open.

It´s ok for me, I think it´s the expected behaviour.

Have you viewed the video ?

Yes, ASIO THRII is selected in Studio settings. It’s the only ASIO I use these days, although I have Generic Low Latency ASIO, Realtek ASIO, and Steinberg Built-in ASIO to choose from in the dropdown list.

Further to the detail of the full Hub freeze, in Task Manager, Cubase has loaded to the extent of around 450 Mb. When The Hub loads normally, Cubase occupies 710 Mb of RAM.

When ending Cubase from task manager after a full freeze, the Hub window closes but Cubase persists within task manger with around 450 Mb in RAM. It’s impossible to remove Cubase from Task manager, hence reboot required.

Clearly, C15 is loading ASIO THRII inconsistently /incompletely upto ~450 Mb. Hence, sometimes a full Hub freeze, sometimes a sound freeze, recovery possible by forcing Cubase to load another ASIO from the list, then reselecting ASIO THRII correctly, and sometimes loading fully to 710 Mb without issue.

Clearly there are 2 different answers of Cubase depending on the way you close.

And sorry but closing the hub should close everything, that’s not the case.

We may differ but for me it is one more way to fool the user and for such a complex app it should be avoided, so it is a bug not a casual expression.

4 Likes