I began my journey with Cubase 8 and recently upgraded to version 13, eagerly anticipating the enhancements it promised. However, my excitement has been dampened by the multitude of issues I’ve encountered with the Mac version of Cubase 13. The 13 MAC version is plagued with glitches that severely hamper its functionality—group editing, Free Warm, Chord detection, Chord mode, and several other standard features frequently trigger automatic shutdowns. This has compelled me to revert to version 12. The investment in this upgrade, given the current state of the software, leaves me feeling regretful and dissatisfied.
Hope your team can fix them asap that makes me feel the money is worth it!
You should post what OS and Mac system you are using.
I haven’t run into anything like you describe, I’m using 16"MacBook Pro, M2 Max, 64 GB ram, OS Sonoma 14.3.1
First of all, please make sure, you have the latest Cubase 13.0.20 update installed.
Please, post more details, about the issues, you are describing. Search if the issue is not mentioned on the forum already. If not, make a new thread and describe the issue in a step-by-step manner.
Then you can add the links to your threads here, so I can get notified and I can have a look.
Does the entire computer shut down or is it just Cubase that crashes? This “too many bugs” approach to the description does not help to isolate these issues one by one.
I use an ancient 2012 Mac Pro that runs opencore Monterey and use just the core audio for that machine (I do have a proper music making PC running many DAWS and two interfaces) . On the old Mac I have not encountered any show-stopping bugs yet while using CB 13, but I can understand your frustration as I’ve often encountered issues when things don’t work out as planned. I’m sure you’ll get to the bottom of this.
Hi there, it just shuts down the Cubase immediately with no impact on any other software. I admit that my setup is more complex and I run larger templates, but these problems did not occur in previous versions of Cubase.
I’ve had a few crashes here and there, on both Mac and PC, but it’s usually something that seems fleeting — a one time thing. I’m not always gentle with the software either.
I understand the accidental crashes you’re referring to. However, the issue I encountered today with the new version of Cubase might not be the same. I’m not sure if it’s related to CPU compatibility or something else, but primarily, the audio feature seems to be stuck."
Most probably, this is a known issue. But we would need more details. If this is the same issue the other users reported, then this is supposed to be fixed in the next maintenance update. But we would need more details to know if your use case is the very same.
What exactly do you do, please? Could you attach the *.ips file, please?
What exactly do you do, please? Could you attach the *.ips file, please?
Could you please clarify what you mean by an “*.ips file”?
Regarding the audio warp issue, Cubase shuts down immediately without providing any additional information.
For the Chord Track issue, it displays a message stating, “Cannot add more tracks. The Chord track count is at the limit,” before Cubase abruptly closes.
The Chord Pad issue results in the same immediate shutdown as the first one mentioned.
It’s written in my post above. Same as the way (and the path), how you can find it.
The important part is, we have to know, which *.ips file is linked to which issue.
This has been fixed already, or it’s going to be fixed in the next maintenance update. The issue happens only if the Chord Track is in the folder.
We know the result, but we still don’t know, what do you do to come to it. Again, please, describe (as precisely as possible) what you are doing (step by step) and attach the *.ips file.
No messages can be found in Crash Reports, and only .diag file(s) can be found in Diagnostic Reports. Please check the attached Screenshots.zip (696.4 KB)
screenshots.
This is already interesting information and a behaviour, which is not common.
I woul like to have a look at the *.diag file(s), you provided. But unfortunately, you have sent the alias files, not the source files. We need the real *.diag files, please.
