Cubase 11 - RME Babyface - Asio driver not running

Cubase
1

Hi all,

I’m having issues with my Cubase 11 pro/RME Babyface pro combo.
It all worked perfectly up until now, for a few years.
At this point, whenever I press “record”, I instantly get: “Recording error: Asio Driver is not running.”.

I’ve just moved houses (so rewired things a little bit) and installed a fractal FM3 (which I know can also be used as an audio device).

However, I’ve tried everything I could find in related posts: uninstalling the Fireface devices, updating drivers, disabling the FM3 (don’t know whether it’s linked, but it’s one of the few things that changed). Starting in safe mode also offered no solution.
Some months ago, I remember I had one issue requiring me to restart the driver everytime, but that turned out to be a “Use USB2 instead of 3” (or vice versa) issue, and that did solve it.

Device manager is recognizing everything. Studio setup seems perfect, also recognizing the fireface device as it always has.
What else could I be missing?
(For now, I’m trying everything with the FM3 turned off, just in case that’s the culprit!)

Thanks in advance for your advice!
Alex

Sidenote: That hub where you see articles when opening cubase? It shows “connecting” indefinitely. Probably unlinked, but strange nevertheless.

2

Update! I can solve it by updating my buffer size through studio setup/control panel.
Strangely enough:

  • Starting at 48 samples. Error.
  • Going to 64. Error;
  • Going to 512: everything works like a charm.
  • Going back to 48 samples: no more error message, but nothing being recorded.
    If I then restart cubase, I need to start the above from scratch again.

Of course, I’d prefer not to do this song & dance every time.
Any thoughts on what might be going wrong?

(Hub still not connecting, for those who care about that part of the story :slight_smile: )

3

Have you checked you are on the latest RME drivers? I would download and install the latest. Even if you are on the latest I would try and reinstall. I use the exact same interface as you on win 11 and I’m not seeing this problem.

4

I have. This thing has been updated/reinstalled/uninstalled a few times :slight_smile: Through the RME update app though…

But perhaps it’s just a buffer issue?

5

So even on an empty project you can’t get below 512? I can get down to 48 with just one vsti. I run at 64 and 128 depending on the size of the project. Even if I get breakup I don’t see the message you do. Have you raised this on the RME forum? You will get the engineers answering on there as well as other informed people.

If you do make sure you state your computer and the exact version you are using of the driver as that’s the first thing they will ask.

6

Thanks, that’s an excellent suggestion. Will do!

7

Strange.
After a few days, I’m not managing to reproduce the error.
However, when trying to record, the situation gets stranger.

E.g. I try to record something at buffer size 48, but the recording image stays blank and doesn’t remember anything.
Then I go up, in increments, through 96 etc… Same thing, until I get to 512. There, I do see a recording image, and the sound is recorded.
Next step: I go back down from 512, and suddenly, I can record things at 256, 128, 96… But at 48 samples, again: nothing. And going back up again, also not at 96, 128…

Is this explainable?

Other thing: none of the cubase input meters (not on the lanes, not on the transport window) is showing anything, although I am receiving an input signal. Is that normal?