SSL is telling me the problems I’m having getting Cubase to record analog audio from my new SSL 12 interface are probably because Cubase is not compatible with my new Mac Studio Sequoia. We have tried everything and although Cubase will play back audio through the interface, and working with VI’s etc are just fine. I cannot get Cubase to “see” any analog audio from the SSL. Also, upon launch Cubase 14.20 switches the Mac audio Sound setting from “SSL 12” for input and output to “Internal speakers”, so no audio can come in from Apple Music or YT.
Pro Tools and Logic both work fine with the SSL 12.
I’ve been running Cubendo on Sequoia before they officially approved it with no issues. There isn’t any compatibility issues whatsoever, and I’m on 15.4. The only issues I have are the occasional UAD driver failures which I can’t figure out the root cause of. I just cycle the physical TB connection and that fixes it, so it’s not a huge thing.
Have you tried running in Rosetta to see if their driver behaves any differently?
Tried Rosetta, doesn’t work, immediately changes interface in SOUND control panel back to Mac Internal speakers. Still plays through the SSL in Cubase though. Moving to Pro Tools until this gets figured out. Thanks. SSL said they would try some tests later today with Cubase.
1 Like
Hey Thor! Mind if I barge in and ask you to expand on that a bit? Feel free to hammer it home for me. 
Having some occasional issue with UAD drivers as well (specifically on sample rates changes)
System Settings, Privacy & Security, Microphone. Click on for Cubase. For some reason, Apple have made this a necessity for Audio in via interface. (Assuming, of course, that you haven’t already enabled this.)
All the best
Jonathan
Already on. So Cubase works with my Avid Mbox Studio, SSL works with PT, Logic, but not Cubase.
Interesting - happens to me as well during sample rate changes (MacOS). But it also seems to happen when I’m doing a lot of “maintenance” work reconfiguring I/O channels to test different cue/phones/mix configs in Control Room too. Like, I came across a thread where @Johnny_Moneto posted some pictures of his mix down config (part of a reply I can’t find now in relation to CR) and have been trying to wrap my head around a general 7.1 audio connection setup with monitors and/or mix downs to 2.1 and 5.1. Anyway, as I switch channels around in Audio Connections, I’ll hear that telltale “click” from the x8’s and then I’ll get a Spin Cursor for about 10 seconds, which tells me UAD has wonked my core audio. Sometimes I’ll do a:
sudo killall coreaudiod
but mostly I’ll just unplug the “main” x8 give it 3 or 4 seconds, and plug it back in. Everything goes right back to normal after that.
If I DON’T do that, any time I go to do any audio process (like play a song in Music) I’ll get a spinner for a bit and nothing happens.
Sometimes rather than the spinner my SoundID reference will pop us saying Core Audio has been disabled, which is because I have the integrated SoundID with UAD’s room correction for MAIN and HPs (which is really nice).
I don’t get a “crash” per se, but I will get a diagnosis report I can view in Console (which I feel is a very underutilized utility).
Any of that sound familiar on your side?
1 Like
Thanks so much for sharing your experience! I definitely see some similarities. For instance, just clicking on the list of available inputs after changing an I/O setting sometimes sends Cubase into a spin—so long that I often think it’s about to crash (it can take 3 or 4 minutes to recover).
My setup isn’t exactly simple: I use Control Room extensively and run an aggregate device on Mac that includes three devices (Apollo, ListenHub, and Audio Movers Omnibus), plus several virtual drivers like VSX and SoundID (though not on UAD).
I’m mainly dealing with two issues:
- The spin I mentioned earlier mostly happens in sessions with heavy routing—lots of group and FX channels. Clean sessions don’t seem to trigger it.
- Occasionally on startup, the Apollo wouldn’t be recognized properly and the sample rate would jump to 192kHz, even though my default is set to 44.1kHz. That issue seems to have gone away since I uninstalled Loopback and switched to Omnibus (they both require a virtual audio driver). Not sure if this next part matters, but it also “seems” like the order in which devices start up might influence things.
I’m on the latest Sonoma, Mac Studio M2 Ultra.
I’ve never had that issue with Loopback; I still use it and really like it. I had started out with a rather complex virtual instrument routing which also included my dual Apple Studio monitors so that I could use CR to easily switch between different outputs to audition mixes. It worked well enough, but I found that I really didn’t need it. I made things far too complicated on my base configuration for a “perceived” need which, as it turns out, wasn’t necessary. So I reverted back to “direct” (non-virtual) audio connections in Cubendo and not only is it much simpler, but more stable. I’ll get project mis-match notifications when I launch Live with Cubase (I like using both at the same time) but that’s on me.
Now I just swap 2.1/7.1 in the UAD console, with the appropriate integrated SoundID profile for each. As such, I’ve kind of given up trying to have one main audio connection profile to suit all possible use cases, and now just load specific 2.1 and 7.1 as needed. Not because of CR, but rather, because the way “surround” outputs work on the x8 is that the speaker profile changes the Monitor path in the UAD hardware. Meaning, if I had some panner routing to output channels for surround, if the console is in 2.1 mode, well those channel outs become line-level outs that bypass the monitor gain, and that can be really dangerous.
Anyway, your virtual config may be contributing to it, but hard to tell. I’ve never used Omnibus before.
1 Like