Just saying that the bug where ASIO-Guard gets disabled internally when creating a new project after opening Cubase, and then we need to remove the initial output bus and create a new one in order to fix it, is still present as of 14.0.10. I am tired of going through this procedure every single time!
Perhaps shall we expect a permanent fix by the end of 2025 ? (possibly before Cubase 15 gets released?)
Thank you for the hard work on many fixes so far since C13, but bigger issues like this one should be put on top of the list. The thing is that 99% of Cubase users have absolutely no clue about this bug and will constantly reach to the forums to complain about poor performance, until it gets fixed.
The exact steps to trigger this bug are : (assuming ASIO-Guard is enabled)
Launch Cubase
In the Hub, type in a new folder name under Project Folder
Click Create Empty
Expand the Audio Performance window
→ As a result, the ASIO-Guard meter should be inactive and the project will exhibit unusually poor performance as you start inserting more and more plugins. (the ASIO-Guard meter is only present in Cubase 12 and higher)
In order to bring ASIO-Guard back to a working state, the following steps have to be applied :
Open the Audio Connections window
Delete the topmost Output bus
Create a new Output bus
→ As a result, ASIO-Guard should now be working properly.
This has been discussed in the past and even @Chriss from Cubase’s development team has acknowledged the issue back in November 2022 with this post.
I read the entire thread now. Since I don’t have this exact issue I feel I’d need to delete everything and start with a clean install in order to be able to reproduce it. This is a bit out of scope, it would set me back hours or days even. Sorry, that I can’t be of help here.
So you mean that it wasn’t active at first, right? What happens when you remove the track?
When I add an audio track I can see the ASIO-Guard meter increase a little but only by a few pixels. Your screenshot shows how it is supposed to be without the bug.
Don’t worry, it’s not necessary to reinstall everything just to test that.
No, it just shows one pixel or so because there is nothing in the project. It is active even without adding a track. But what would be the problem if it activates only when a track is present?
Ok so that means it wasn’t active, I mean, the bug was occurring, because even with nothing in the project it’s supposed to be fully visible and move like the other meters.
Try to do the test again without adding any track and just remove/add the output bus to fix it. You’ll see that the ASIO-Guard meter will increase, meaning that it now works properly.
I have no idea why it works fine when you add a track, considering both of us are using Cubase 14 for the test. The audio track might be properly processed by ASIO-Guard but then the output channel is possibly still affected by the bug. Perhaps it’s because you have multiple outputs assigned, I don’t know.
Ok, fine, but there is no practical point. I don’t care about audio drop outs in a completely empty project, as there is nothing to hear.
I made sure that I only have one output bus, no control room. As soon as I use a track ASIO Guard is active. I don’t have to delete/change any output busses.
I am also not sure why we get rather different results in this matter.
Because I did not put any plugin on the track
Alright I just checked again with plugins this time, and you’re right, audio tracks are indeed processed with ASIO-Guard.
However, as I expected, the output channel is still affected by the bug. When you place the plugins on the output channel, ASIO-Guard definitely does not work.
We are aware of this issue and will take care of it.
The behavior is actually “as designed”, and required for certain use cases. I don’t expect a solution tomorrow.