Cubase 14 crashes while running old projects - MacBook Pro M1 2021 - Sequoia

Hi everyone, i’m new here so thanks for this opportunity first of all.

I’m a Mac M1 user and yesterday I downloaded the upgrade of Cubase 14 from 13; I was having troubles while running old projects I’m working on because the software was crashing all the time before to open the project window. I firstly thought it was for the version of my Mac (Monterey) so today downloaded and installed Sequoia 15.1 but problem persist, below the log :

Process: Cubase 14 [7645]
Path: /Applications/Cubase 14.app/Contents/MacOS/Cubase 14
Identifier: com.steinberg.cubase14
Version: 14.0.5.125 (14.0.5.125)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-11-09 17:12:59.7728 +0100
OS Version: macOS 15.1 (24B83)
Report Version: 12
Anonymous UUID: A596D525-431F-0110-C07E-4A0AEE048564

Sleep/Wake UUID: F494DFD8-29D4-4216-8475-85ECB1D7DD4B

Time Awake Since Boot: 5400 seconds
Time Since Wake: 4516 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Cubase 14 [7645]

Application Specific Information:
abort() called

Someone can help me please ?

Kind regards,

MP

1 Like

Hey MP!

Could this be related to this problem we are fixing?

You can test this by simply renaming the project you try to open to something very simple without special characters. Something like “hello”.
If that opens the project, than please try to rename old projects to not inlcude special characters as a workaround. This problem will be fixed in the coming update.

Best regards,
Alex

2 Likes

Hi Alex,

big thanks for your help, now i can open that project!
Just to let you know, the name was “Sinner_+” , telling you because “_” and “+” usually are not considered “specials” .

Thanks again and regards,

MP

2 Likes

Hey MP,

thanks! Yes they are very common characters. “_” shouldn’t be a problem, but “+” is colliding with some code-changes we made. Which it shouldn’t. :sweat_smile:

Best regards,
Alex

2 Likes

Good morning, I also bought Cubase 14, especially for the new score editor, the 12/13 versions were unusable, full of bugs and with Setup windows that didn’t open completely and many other problems, grrr, ok the C14 score editor it’s better, but for example the arpeggio, glissando and forte piano “Fp” symbols are missing while there are many that very few users will use… furthermore I miss the possibility of writing lyrics over a piano part, they always end up in the middle of the staves and they can’t be moved, also I think it would be useful to have some text that you can move wherever you want… but the biggest problem is that it crashes very often, I used C12 and C13 templates, could that be the reason?
I’ve already written to Steinberg and I have to say that I’m a bit angry because from 12 onwards there have always been bugs (on Mac M1) that have never been resolved!!! I worked for many years with C5 which had problems, but I was able to work very well with the audio, with a bit of effort in the score editor, but I was able to finish the jobs with dignity…
I would like to become a beta tester for Mac, probably many bugs would be fixed before the release of new versions…

Greetings

I forgot, I have been working with Cubase since the first version on Atari in the 80s/90s, I would like to remain a pro Cubase user for many years, but the latest versions have disappointed me a bit, I have written many emails to report the C12 problems but I have everyone found themselves on C13, this thing needs to be improved…

Hey dd!

Unfortunately this is not my domain. If you have crashdumps, we can take a closer look, but it’s nothing I can decide. It’s cool that you want to engage as a beta tester, unfortunately that doesn’t fall into my responsibilities as I am just a developer. I believe there is an application website for that.

I understand your anger, but there is unfortunately nothing I can do for you directly.

Best regards,
Alex