Cubase 11 Pro - no sound after updating MacOS to Tahoe 26.2

After updating MacOS to Tahoe 26.2 (from Sequoia 15.7.3) there is no output from my cubase projects (meters don’t move at all). I am using Audient ID14. Tried setting in Studio, buses, reinstalled Audient driver, renamed Cubase folder in Library/Preferences. Nothing.

What’s important is that if I change the driver in Cubase to build-in I hear everything well, once set driver as Audient ID14 again nothing and no meters move (though audient works outside of cubase).

Could you please support me?

Hi,

Cubase 11 is not officially compatible with macOS 26.

Are you on Intel or M processor?

Do you see the given ASIO driver in the Studio > Studio Setup > Audio System?

Thank you for your reply. I have M4 processor.

I know Cubase 11 is not officially compatible with Tahoe but so it was with Sequoia (I don’t want to spend 250 euro for un update yet, especially if this won’t solve the issue :frowning: ). I do see it and also see the buses. No meters are moving in MixConsole - also sounds works fine through audient outside of cubase.

What’s important is that if I change the driver in Cubase to build-in I hear everything well, once set driver as Audient ID14 again nothing and no meters move (though audient works outside of cubase).

Hi,

Is the Audient driver compatible with macOS 26 Tahoe?

I don’t know if it is but it works outside of Cubase (example when playing YouTube).

Hi,

The official page says it clearly:

Therefore, at this moment in time, we do not officially support macOS 26 Tahoe.

I did the checks with audient support person and I can clearly see that audient is working with Mac two ways (I hear sound with it and I can record the sound in quick time) therefore my issue should be on the cubase side.

Hi,

Cubase is using the ASIO Driver (real-time). Quick Time doesn’t. So it’s different task.

Cubase is not using any Audient ASIO driver on Mac as far as I’m aware, it uses CoreAudio in it’s own wrapper that adds ASIO type function like ASIOguard.

So it’s only a different task once inside of Cubase, the driver Cubase works with is the same one.

@Synow did you try to delete and recreate the output buses? Do you have anything unusual going on in Audio Midi setup like aggregate devices that you might have selected rather than the basic Audient device?? It may even be worth seeing if creating an aggregate device and selecting that makes any difference.

1 Like

Hi,

You are right. Mac is using CoreAudio and Cubase wraps it via CoreAudio2Asio to the ASIO. But QuickTime is not using real-time audio anyway.

Thank you for helping. I tried removing buses now but didn’t work. Can you please let me know how to check that:

do you have anything unusual going on in Audio Midi setup like aggregate devices that you might have selected rather than the basic Audient device?? It may even be worth seeing if creating an aggregate device and selecting that makes any difference.

Well if you had an aggregate device you would have needed to create it so if you don’t know how to check I’d imagine you don’t have any.

Could you screencap your audio midi window (you can find in mac applications)

Also, I’m pretty sure this should only affect recording but just in case…in mac system settings/privacy and security/microphone make sure access to Cubase is enabled

this doesn’t say nothing …. a graphics card without the correct drivers will also show up screen but will bug when playing games … do you have the lastest drivers of audient [ are they even fully supported in your current mac os ? if not then yep putting 299 to update cubase will not solve anything