I have a sluggishness issue when I navigate my finder via Cubase on Mojave. If I navigate to project folders directly on my Mac finder, it’s smooth and fast but if I go through Cubase > File > Open… it takes 5 or 6 seconds between each click to realize I have selected a file. So when you navigate within a big tree of files, it takes forever. Also, the mediaBay has become so sluggish since the 10.5 update. I trashed preferences and rescan the whole structure but still sluggish. Even takes like at least 4 seconds when I press F5 until the MediaBay window shows up. It was much faster with Cubase 10. And it’s not my hard drives as they have an average speed of 397MB/s for both writing and reading.
Agree with your sentiments above. I definitely am rooting for Steinberg and hope that they get their act together soon. Cubase has been my main DAW for 15 years and I love it when everything runs smoothly but with every new update comes bigger and more serious bugs. Sadly this past year I’ve been exploring other alternatives and it’s been pretty eye opening how bloated Cubase is. Feature-wise it’s still unrivaled. I wish that they would rebuild cubase from scratch to get rid of all the bloat accumulated over all these years.
I’m on 10.5.11 and finding that while the memory leak is gone from previous versions, it is now totally locking up much more often.
Often without beachballs - just causing the computer to become completely unresponsive several times a day - something that has not ever come up in using Cubase for around 20 years.
Still something pretty major going on.
Does the same thing with one instance of Halion.
My CPU spikes when using Addictive Keys at anything below 192 buffer, crazy, Same on 10.0.50 as well
Installed 10.5.11 - Still fails with that stupid Steinberg Library manager error. Urgh
I’m getting slightly worse audio spikes and cut outs on average (over)load, than I was previously. Can’t seem to pin it down to anything (VST / VSTI) in particular just happens on any project… and of course on the mac it if difficult to trace it monitor wise. Still getting Cubase not exiting properly and crashing on some large projects (Cubase stopped working - Process).
Not getting overloaded CPU / Mem. and I have not had a crash in project which seems a little better. I used to have them all the time before this in 10.5. however I am still paranoid of losing work - I never used to feel like this with Cubase.
Do I move away from MACOS and move to windows 10? or do I do a dirty and move elsewhere… hmmmmm
P
On 10.5.11, on some project the audio performance window shows around 80%, the same project with 10 is around 10 %.
Display in Score Editor looks better in 10.5.11 but performances are very bad while they were correct (for me in my daw) in 10.5.
Until Cubase 10 updates were bringing improvements, but now with 10.5 it seems like if something is better on one level, another thing elsewhere is worse (I’m not sure I’m clear …).
Steinberg Team: are you sure 10.5 can’t work with High Sierra…? I cannot write a single line of code but I think all the problems are got to come from Apple’s Open GL abandonment for the benefit of Metal.
Also now hangs on quit for good measure.
Although exiting the program seems to be going well.
But I have to delete the preset folder, otherwise I can’t run the program.
At present, there are new faults, and a large number of “unknown” plug-ins are blacklisted. Including but not limited to: ozone 8, super drummer 3, battery 4.
These plug-ins have little in common, but they all fit the category that Cubase supports. 64BIT，VST3/2.6。 Attempting to reactivate in the plug-in manager can cause the program to crash suddenly.
Sad, can only return to 10.0 version work.
No hope for 10.5.
Cubase 10.5.11 on Mac mojove
I am getting spikes particularly when soloing ( even with suspend VST3 off), returns to normal when unsolo.
Listen button is just soloing the channel yet mute buttons are not lit. So listen function does not seem to be working.
Performance bar is starting to reach maximum after 20 minutes or so when project was using about half resources at startup.
If quit and re start Cubase then will revert back to half resources used for 20 minutes or so, so I guess there is some memory leak problem still…
Grouping and making folder track does not graphically display properly as folder shows some tracks are inside but on another block does not display any data from the overview.
I think 10.5.10 seemed to work better…
This whole 10.5 issue has been one the biggest mess ups since I been using Cubase on Atari.
Every new update or hot fix you guys release brings new huge issues. Sessions don’t open. Cubase blacklists a ton of plugins for no reason. Trying to reactivate them just crashes Cubase. I mean what a HUGE mess you guys created here.
Is there an installer how to get back to the earliest version of 10.5 or do I have to make yet another time machine reset because of you guys?
I really hope you manage to sort this mess out. Some of us use Cubase for work after all
Screw it.
I’m doing yet ANOTHER time machine restore because of you guys and how bad this whole Cubase 10.5 situation is.
It takes real skill to screw this up so bad.
Won’t trust you guys again with any of the updates and “fixes”.
We need those crash reports. Please have a look here:
I totally understand your frustration, but we can’t fix it without your help. The blacklist issue cannot be reproduced on any of our systems so far. So please send us the crash logs as described in the post.
There are a bunch of users complaining here on the forums about blacklisted plug-ins, but we haven’t received one single crash log from anyone who complained. We cannot fix it as long as we cannot reproduce it.
That’s the funny thing, on the crashes I have been having I haven’t been getting one crash report pop up.
I have reset my entire Mac now. It’s still doing it for another 20 hours.
I have to do urgent work and haven’t got time unfortunately to search for possible solutions that might take days or weeks.
I’ll go back to Cubase 10 and will sit 10.5 out altogether now.
The problem is that it’s not Cubase that is crashing but the VST scanner (as described in the post). That is why there are no Cubase crash logs. The plug-ins get blocked by Apple due to the Hardened Runtime and the VST scanner doesn’t get any response and crashes. Unfortunately we cannot reproduce it on any of our systems.
But you can still help us if you send us the VST2 file of one of the plug-ins that are (or were crashing before in Cubase 10.5.11) crashing (or that are getting blacklisted) to info (at) Steinberg (dot) de with Blacklist in the subject line.
We really need you help!
I remember for sure that my Korg Legacy was one of them as I event checked that I had the latest installer.
Once my system restore is done I won’t risk another update and stick to Cubase 10.5.5 and 10.
Could you please send us the VST2 file of the Korg Legacy VST to info (at) Steinberg (dot) de with Blacklist in the subject line?
Yes, once the restore is complete I’ll send it over.
By the way, it would have been nice if “hardened runtime” had been mentioned in the release notes of the updates. I would have stayed away from it and it would have saved me a lot of trouble.
We didn’t see it coming. As I said there wasn’t any issue on any of our systems and we still cannot reproduce it.