I updated my iMac’s iOS to Sequoia 15.2. After the update, my Cubase 12 Pro stopped working — it can’t open an empty project or recent songs. I decided to upgrade to Cubase 14 Pro, but the same issue persists. The loading wheel keeps spinning on the Cubase startup screen when I try to create an empty project or open a recent song. None of my four Cubase versions are working now. I’ve tried restarting, but the problem remains. Does anyone have suggestions on what might be wrong?
Br, Dennis
Anyone?
Dennis, I just saw this, thinking I am about to do the same upgrade, did you resolve?
I’m still in Sonoma. No worries for update the OS.
I have the same problem, but with library manager which does not work at all, I know how to put my vst but not the sounds, now I come to update to sequoia 15.3 we will see, I have the impression that apple wants us to take logic pro 11 because it is blocked the road to steinberg I think, I had cubase pro 14 in trials, they deleted the license I think that’s it they want us to move to logic pro 11 delivered with the macbook pro m4 max this is my case !!!
Same here! Cubase 14 won’t load up at all! This is insane… Steinberg need to come up with a fix!
I bought a new Mac Studio and have had nothing but problems with Cubase. I have tried getting in touch with support, no luck. It’s been a joke. The only thing that has worked was posting crash logs here that were passed along to the team, but this has been the most frustrating, worst experiences I’ve had with a company in a very long time. I’ve given up on Cubase for the time being and have just been using Ableton Live again. I also have demo’d Studio One since it was built by former Cubase developers and there are a lot of similarities. You can get a crossgrade license for S1 pretty cheap. I just haven’t had a lot of time or energy to get used to a new DAW and used Live before going to Cubase ages ago so that’s what I’m back to, maybe for good, sadly.
I love Cubase - it’s been such a great tool, but constant crashes, weird bugs, etc… Completely unusable and they don’t seem to care at all 
sounds like the M4’s & the Studio isn’t ready yet. from what I’ve gathered Apple changed how audio drivers load with the latest version of Sequoia - they no longer run as the system but in a user context as a way to harden the OS. It does this but I’ve never heard of any audio driver ever being hacked. So it hardens the OS at the expense of audio producers. Even RME were caught off guard & are having issues with their drivers on the latest OS.
seems M1-M3 are the only reliable systems for now.
Not quite true.. Apple is very much still allowing kernel extensions and has not forced anyone to move to the new Driver Extension format yet. My MOTU 828x still runs on a kernel driver and works same as it always has.
That change actually happened a few years back around Catalina, but is not enforced by Apple in any way. RME had a handful of people with a couple of hiccups with a couple of interfaces with the 4.2 drivers. My Digiface USB, all 32 channels of it, is working flawlessly with driver extension 4.26 and Cubase Pro 14. The Driver Extension has been pretty rock solid for the most part.
guy i’m not here to fight anyone but I think its you that is mistaken. please look at the RME forum. the problem relates to all interfaces on the latest version of OSx (15.5 ? the one that M4’s come with). RME just released an emergency wrapper.
Im there almost every day. You make it sound as if the world is coming down with RME devices, but its not. Its a HANDFUL of people complaining about dropouts using the UCX/UFX and Fireface devices.
I had some little ‘glitches’ with 4.20 and AudioFinder, but not much else. Driver 4.26 has been working perfectly since it was released a week or so ago, and Im getting on every day in Cubase just fine with no issues at 64 samples, and my Mac is always updated as soon as OS updates come out for better or worse..
I don’t see any post announcing an ‘emergency wrapper’ and the Digiface’s driver page is still showing 4.26…
I’m on an M3 Ultra, so maybe not all M3’s. I agree, though, seems like there is something fundamentally wrong with the newer chips and how Cubase is handling a lot of processes. I’ve done so much troubleshooting and had others troubleshoot as well and it seems fundamental to system and how Cubase interacts with it. I’ve also been able to repeat the issue I’ve been having in Cubase 13 (totally fresh install), so either there are shared preferences between 13 and 14 or it’s the system underlying the issue.
my guy please ease up with the hostility.
just because you don’t have problems doesn’t mean other people don’t
I said the issue is with ALL interfaces not just RME.
RME area actually trying to work around the problem but if you read the thread about the wrapper & you can see they are still trying to work out the issues.
look up " Stop - Watch This Before Buying an M4 or RME interface" on youtube & read the comments.
" Mac OS changes to its security features, audio drivers no longer have access to kernel extensions. "
then go to the RME forum & it’s all confirmed.
man, i’m sorry. what’s the oldest version of the OS you can install on your Mac? I would try that one.
Yeah, I’m really sorry you continue to have those issues. I’ve got an M3 Ultra as well, and as we’ve discussed before I don’t see any of those issues.
I just got a new RME too, and no issues there either - FWIW both the UAD Apollo drivers and the RME drivers still require manual “Reduced Security” to be set in MacOS Startup Utilities, but other than that bit of a pain, all is good over here.
I have no idea what other aspect of the install it could be for you, and I really wish I did.
Thor what version of Sequoia are you on? Hopefully its an older one he can try.
You’re going to need to point us to a link to this thread, as I’ve been searching in the USB forum all morning and see nothing about an ‘emergency wrapper’. I’m very curious to see this as an RME user myself.
Again Apple has not changed ANYTHING in regards to ‘audio drivers’ since Catalina. You are STILL able to install kernel extensions, as @Thor.HOG just informed you that he is using it with his on a new M3 Ultra machine, and I am using the driver extension here simply because I don’t feel like booting into recovery to change it like I used to have to do with my MOTU. I am on Sequoia 15.5 and can install either version of the driver just fine. Nothing has changed, kernel extensions still have direct kernel access, driver extensions still need to go through ‘security’ to get to it, the same as its been since they were introduced in 2020 when Catalina and the brand new M1 Mac’s came out.
Coincidentally, my MOTU was running up until I unplugged it when I got the new RME last year, and when I booted into Recovery to turn the security setting back to default, they already were and somehow my kernel extension driver was still working this entire time. When I got this M2 Pro Mini 2 years ago, it looks like I may have not even changed those settings to install it in the first place.
I’m on 15.5 on both my MBP M3 Max and my Studio M3 Ultra - I’ve been running the MBP M3 Max for almost 2 years now without any issues at all. I couldn’t be happier, actually - and why I was eager to get the M3 Ultra as well.
I’ve got 2 different studio workstations, one system on each, one with Apollo x8 and Twin Quad with Roli Seaboard and Push 2 (using Virtual Channels and Blue Cat for Cubendo/Ableton “integration”) and the M3 Ultra with an x8 plus my new RME UFX III (what I call my “main” rig).
I was upgrading the MBP to the latest OS along the way - the Ultra arrived with 15.5 on it.
I know it’s not any help, but I go into that level of detail to establish I’ve got rather complex rigs, and to potentially identify what differences dude may have in his setup.
Thank you - I’m stumped. I’ve tried doing full reinstalls, forcing Cubase to delete preferences, etc… I honestly don’t know what I’m doing.
Maybe it is something related to the specific plugins, but I’ve reproduced the issue with multiple brands’ plugins (as you can see in my original thread). And at least A) I could get in touch with Slate Digital, B) they actually looked at the crash logs and gave me some guidance about what’s causing the issue to bring to Steinberg C) allowed me to send project files to them that are showing the issue so they could try to reproduce. Granted, they didn’t have an M3 Ultra to test on, but they were at least helpful.
Steinberg is impossible to reach (Best option for filing a tech support ticket in the United States? - #12 by Reco29) and when I called in the tiny 9am-1pm EST window they’re available to talk to them, they just said, “not our problem”.
If I did something wrong in installation, reinstallation, in the fresh install of Cubase 13, or if there is something wrong with my setup, I’d love to fix it, but I’ve spent 25 hours troubleshooting, testing, literally opening Cubase project files in text editors to see if I can see anything to point me to a potential resolution path and I am stuck.
I’m happy to help if the project is such you can pass along, or at least a version of it you don’t mind sharing. I’ve got all the Slate/SSL plugins (I’ve got the full subscription) installed, but they are on my MBP M3 Max. But that shouldn’t matter as the core architecture of the Max vs Ultra is the same - the 32-core Ultra is, for all intents and purposes, two of the 16-core M3 Max processors unified within the “UltraFusion” fabric as a single monolithic processor.
I’ve purposely limited my plugin installation on the Ultra as I’m working within “forced constraints” going forward.
I’ll see if I can catch up on your threads again tomorrow and will report back.