Issue? Occasional unreproducible NO AUDIO inside Cubase 15 - anyone else?

I can’t reproduce it, but occasionally I find that Cubase 15.0.6 does not have audio when I start it up. The RME ASIO driver is visible, Cubase is still pointing to the right driver, but there is simply NO sound. I just have to restart Cubase, and then it works fine indefinitely at any latency under all kinds of projects. Weird.

Anyone else? It’s rare enough I can’t see a pattern or force it to happen.

It’s also not disruptive enough at this point to really cause me to press the issue further, since it’s a very quick fix when it does happen. And BTW this is NOT happening with any other DAW or audio app on the same machine that I have noticed so far. I’m watching closely though and will update this thread.

I haven’t tested if this is happening on all my other systems, but this is happening on Win 11 Pro, Cubase 15.0.6, AMD Ryzen 9 9950X CPU, RME latest drivers.

Everything works great on this machine, no issues, no headaches, solid machine, no issues with other DAWs as mentioned, no latency issues, no driver issues, no graphics issues, no performance issues (other than the obvious known threading optimizations that are needed with Cubase discussed in other threads in this forum), and actually this is also a fairly fresh installation of Windows, super clean and stable. I just can’t reproduce this weird thing.

If I do find a pattern, I will post more details. I have not experienced this to my recollection in Cubase 14 and Nuendo 14 on this machine. It’s just annoying enough and weird enough that I thought I would post and see if anyone else is experiencing something similar?

Cheers!

This is most likely the same issue me and some others ran into, with the combination of Cubase, some AMD Ryzen CPUs/boards and RME drivers. There is currently no solution (Steinberg and RME are aware, though) but to try different USB ports on your computer. Usually, you’ll find one that works

1 Like

Interesting. I’ll look into it. The thing is, it does work 99%+ of the time, and it doesn’t have the issue with other DAWs or Apps that I can see so far, including Cubase 14 and Nuendo 14. Just Cubase 15. Go figure.

However, I will be keeping a close eye on it. I might have some edge case variation of the issue you mentioned.

For the heck of it, I was thinking of buying one of those Inateck or Sonnet USB cards with the “Fresco” chipset on it, which is supposed to be really stable. However, I’ve also read conflicting info about its compatibility with more recent versions of Windows. Those errors might be user error though, since it seems “Fresco”-based USB cards are supposed to be broadly compatible and work great in DAWs.

Anyway, thanks for your response!

The behavior here for me was seemingly completely random as well, some days went without any problem, then the next day every second project I opened with Cubase the ASIO driver failed to initialize properly and there was no sound (also nothing on the meters anywhere in the project). Drove me nuts. The suspicion is that is might be some USB timing issue.

I had the problem with C14, though, and iirc with C12, too.

Just try a different USB port, preferably one which has the whole USB hub for itself with no other devices on it, maybe it helps.

1 Like

Thanks, will play with it some more.

And funnily enough, it just happened right now. This time, it was after a fresh boot cycle, and the first time I loaded C15 today. No sound. Then I quit Cubase, loaded it again, and all is well. Weird. Weird. Weird. :face_with_diagonal_mouth:

Yep, I know, completely maddening. Instead of restarting Cubase, opening the Studio setup and resetting the ASIO driver worked too, and faster. But since I switched to another USB port, I never experienced “no sound” Cubase anymore.

1 Like

Thank you, will try resetting ASIO driver next time. If this keeps happening more frequently, I’ll likely just buy that Fresco-based USB card. I believe it was mentioned in the RME forum somewhere too, but I didn’t realize at the time I read about it that I might have a related issue. I’ll have to track that thread down and re-read it. Thanks again! At least there are easy enough workarounds.