Hi there. You can see my specs in my signature. Running Mojave 10.14.6
I have machines powerful enough to run tons of plugins and whatnot, I used to run Cubase 8 or Nuendo AND middleware AND Unity without any issues.
Now, since I have upgraded to 10.5.20, i get random crashed ALL the time. Just now i gave up composing a track because its so damn frustrating.
And I am using external synths mostly, so its like 3 plugins on. Buffer is set to max.
What can cause this? Could it be dongle? But it is impossible that 8.5 was working with no issues and 10.5 is crashing every damn time I open it.
Steinberg, really, for the first time in two decades I am seriously thinking of working on other DAW. Due to the nature of my work, I have both PT and Logic, together with Cubase and Nuendo. Still, for my personal projects, i always start them in Cubase - anyone having similar issues?
This version is crashing on certain plugins as well (and not black listed ones).
Yup, same
Hi,
Attach the *.crash file, please.
This is something I’m also running into lately. Cubase 10.5 and especially 10.5.20 crashes all the time and I can’t seem to get a low enough buffer size to record audio without latency. I already made a ticket for support, but that’s has been almost 2 months ago without ANY reaction from Steinberg. It is really frustrating and I’m thinking about switching to Logic or Studio one just to be done with Cubase. But before it take this step I was wondering if someone on the cubase forums has a solution and can help me out.
so te problem in short is: cubase crashes randomly and always at startup at least one time, the buffersize can’t be lowered more then 192 before I start hearing pops and clicks, even if I put in one audio track without any processing. The CPU meter shows like 1/2% CPU usage but the overload light burns every few seconds (even when doing nothing). Any help would be great!
I’m running on a Mac mini 2018,Catalina 10.15.5
Processor: 3,2 GHz 6-Core Intel Core i7
Ram: 32 GB 2400 MHz DDR4
Soundcard: Focusrite Saffire Pro 40 + ScarletOctopre connected via Adat
Controler: Alesis V60 and Aurturia SparkLE
I’ve got the newest Elicener update and sound card software update. I’ve also added a crash report. Hope someone can find something!
Cubase 10.5_2020-07-09-141511_Mac-mini-van-Sean.crash (112 KB)
Hi,
The crash is in thread 2, there is no Cubase or any plug-in at all:
Thread 2 Crashed:: Dispatch queue: com.apple.CFNetwork.addPersistCacheToStorageDaemon
0 libobjc.A.dylib 0x00007fff6decb81d objc_msgSend + 29
1 com.apple.CFNetwork 0x00007fff33a18468 0x7fff33a0c000 + 50280
2 com.apple.CoreFoundation 0x00007fff352208d5 __CFDictionaryApplyFunction_block_invoke + 22
3 com.apple.CoreFoundation 0x00007fff351e641f CFBasicHashApply + 115
4 com.apple.CoreFoundation 0x00007fff351d6d67 CFDictionaryApplyFunction + 129
5 com.apple.CFNetwork 0x00007fff33a18408 0x7fff33a0c000 + 50184
6 com.apple.CFNetwork 0x00007fff33a17fed 0x7fff33a0c000 + 49133
7 com.apple.CFNetwork 0x00007fff33a19726 0x7fff33a0c000 + 55078
8 com.apple.CFNetwork 0x00007fff33b194b6 0x7fff33a0c000 + 1103030
9 com.apple.CFNetwork 0x00007fff33b20b19 0x7fff33a0c000 + 1133337
10 libdispatch.dylib 0x00007fff6f0256c4 _dispatch_call_block_and_release + 12
11 libdispatch.dylib 0x00007fff6f026658 _dispatch_client_callout + 8
12 libdispatch.dylib 0x00007fff6f02bc44 _dispatch_lane_serial_drain + 597
13 libdispatch.dylib 0x00007fff6f02c5d6 _dispatch_lane_invoke + 363
14 libdispatch.dylib 0x00007fff6f035c09 _dispatch_workloop_worker_thread + 596
15 libsystem_pthread.dylib 0x00007fff6f280a3d _pthread_wqthread + 290
16 libsystem_pthread.dylib 0x00007fff6f27fb77 start_wqthread + 15
Tnx Martin. When google-ing this it seems to have to do with the app that makes crash reports possible. Thats a funny twist. But it doesnt explain why cubase 9.5 (working on 9.5 again) does not crash if its a OS issue instead of a cubase issue. Or is that a to simplistic way of thinking?
And do you maby also know what is causing the extreemly poor audio performance in 10.5 and hoe to fix that?
Hi,
I find this line interesting:
Thread 2 Crashed:: Dispatch queue: com.apple.CFNetwork.addPersistCacheToStorageDaemon
Do you use Dropbox or iCloud by any chance? Do you store some data directly from Cubase to the Dropbox or iCloud (or a similar service)?
No dropbox, but i think icloud is used for my notes and agenda etc to share data between my devices. Might be usefull to turn that off and see if the crashes stop. Tnx, ill give that a try!
Is any solution available soon? I get constant crashes on my Mac. This way Cubase is unusable…
Hi,
Provide the *.crash file(s) please to be able to investigate where does Cubase crash on your side.
Mac: macOS Console utility > User Reports folder (or ~user/Library/Logs/Diagnostic Reports).
Here’s 3 of my crash logs from the last 3 days with 3 different plugins.
Mine crashes a lot when I close projects and then try to open them again. The project doesn’t open and Cubase just crashes. I’ve found the in hub if I select “Open Other” and select the .cpr file that it will usually open, but that shouldn’t be the case???
You can also see from the attached image that this happens frustratingly often compared to other programs 
Cubase 10.5_2020-07-10-103013_Steve-Palominos-MacBook-Pro-2.crash (116 KB)
Cubase 10.5_2020-07-11-201920-1_Steve-Palominos-MacBook-Pro-2.crash (143 KB)
Cubase 10.5_2020-07-12-160059_Steve-Palominos-MacBook-Pro-2.crash (134 KB)
Hi,
Please make sure your plug-ins are up to date. All 3 crashes are in plug-ins, every single one is in other plug-in:
- Xlnaudio rc20retrocolor
- Soundtoys EchoBoyJr
- ValhallaDSP ValhallaVintageVerb
I did this in the post I started on this subject. You replied that the crash I encountered was already reported
hello yes… that’s why I said it happens with 3 different plugins. They are all up to date.
Double checked a few days ago.
Have you looked at the system logs on the Mac ? Launch the console utility from under /Applications/Utilities, then on the l.h.s select “crash reports” though I think this only shows you what you already saw in the displayed log/backtrace. Also try selecting “log reports” in the list on the l.h.s and then look at the bottom/end of the system log after the crash happens. The system log is always being written to, but you should be able to see any Cubase related events towards the end of the log after the crash happens.
With 10.5.20 I still get the beachball of death with some of my plugins (NI Flair, Choral, Phasis). I am wondering if anyone of the Mac users actually use 10.5.20 for professional tracking or mixing sessions? I still don’t really trust it and use 10.0.60 instead most of the time.
I’ve gone back to using 10.0.60 on the Mac and make a habit now of keeping around older 10.X.X versions of Cubase for the Mac. it seems that with the start of 10.5.X releases for the Mac, there is always something I need to use that is broken in the Mac release, e.g., I posted that the text in the score settings window is unreadable now in 10.5.X (which apparently changed in the 10.5.X releases). I’m happy the moderator told me this was a known issue, so maybe there will be a fix in the next quarterly point release - the end of September? But I wish there was better support for the Mac. Given Cubase has a long history of being primarily a Windows only program, it would not surprise me that Q/A testing for Mac releases does not get as much attention as Windows releases, i.e., there are probably far more Windows users than Mac users.
Ditto. Seems to happen on mix down and when opening dynamics plugins most often.