Ever since Cubase 13 was released, when using it I’m experiencing frequent “freezing” of the UI, every minute or so, when using it. It makes it incredibly frustrating to use, so I often find myself reverting back to using Cubase 12 to be productive. The UI freezes due to me getting the spinning beachball - the mouse pointer continues to move (although being a spinning beachball), but no input is processed. Then when the spinning beachball clears, the last few commands are processed in quick succession (like the UI is “catching up”). It happens when I’m editing MIDI (mostly what I’m doing), playing back, interfacing with MixConsole, and many other usage scenarios; it doesn’t really seem to depend what I’m doing.
I have auto-save interval to 5 minutes, but (a) I experience UI freezes MORE often than that, and (b) I don’t get UI freezes in Cubase 12 when auto-save is occurring.
I consistently also get this when I initially start up Cubase 13. My first attempt to use the UI (usually trying to close the Quick Start window by hitting the Cancel button) always results in a spinning beachball for 5-10 seconds.
I have tried to be patient to see if Steinberg could work out the kinks in Cubase 13 Pro, but we’re not several versions past 13.0.0 and this is still happening. Is it something impacting Intel Macs only perhaps? Is Cubase 13 leveraging some Apple Silicon only code that is tripping up Intel Macs?
Quite often I’m using Vienna Ensemble Pro (latest version 7.3.3725) but today I’m working in a project not leveraging any VEP MIDI tracks, and the issue continues to impact me.
In Cubase 12, it doesn’t occur.
Is anyone else experiencing this using Cubase 13 Pro on an Intel Mac?
Not sure Activity Monitor is much use, since the entire Cubase application is listed under one link item there - the problem is stemming from a sub-system of Cubase, which causes the entire app to freeze.
I also need to revise something I said earlier, it IS happening with Cubase 12 also.
I captured Console messages for Cubase 13 on MacOS during a freeze (which occurred at 09:08). Do any of these look problematic?
Actually, having done more testing in Cubase 12 and Cubase 13 it might be the auto-save feature causing this. It’d be great if this didn’t freeze the UI for 10-30 seconds every time, but I guess there’s no way around it
To me, this looks like a component trying (unsuccessful) to update a cursor position via inter process communication (xpc) and thus blocking the Cubase UI from updating. The component is calling a function of the JUCE framework (scheuduleUpdateCursorPosition), which let’s me assume, that the component in question is a 3rd party plugin UI, which causes this 9 sec hang. @EX1MUS , is there a plugin window open, when the hangs happen (not neccessarily has to be visible, though)?
Fascinating @Chriss - thank you for your insight. I’d love to hear any further thoughts you have on tracking down the source of this disruptive issue.
Most of the time there is not a plugin window open when this occurs. But I’m sure this behavior has occurred while a plugin window is open too.
For any VST where a VST3 version is available, I have meticulously hidden/disabled the VST2 version from being used in Cubase via the Plugin Manager. The main plugins that I use often and don’t have a VST3 available for are SonarWorks Reference 4 (I’m required to upgrade to SoundID Reference to get the VST3 version), and 2C Audio plugins (I heard the company went under so no updates available ).
My usual working state with Cubase is using 5 x 4K screens connected to the Mac Pro 2019, 2 on upper shelf of desk, 3 on lower surface of desk. The Project window is open on the upper right screen. The Event Editor / Piano Roll is open on upper left screen. Mix Console is open on lower right screen. Vienna Ensemble Pro 7 is open on lower left screen. Plugin windows are open on lower central screen (if any are open), so as not to be accidentally hidden by other windows. I generally have < 5 plugin windows open at a time, usually Kontakt 6 or 7, SINE, or OPUS.
All software is updated to latest available versions (other that aforementioned plugins).
I know at least Sonarworks use JUCE in their plugins (don’t know, if in all). You may want to report the issue to them, if you find more evidence, that it’s their plugins causing the hang.
To find the culprit, you can use the Console app as you did, but remove the Cubase filter and log “Errors and Faults” for all processes. The causing plugin may show up in the log when you experience the next hang. Good luck!
Thanks so much @Chriss - your insights have been so helpful.
I bit the bullet and upgraded to Sound ID Reference yesterday, since I know SonarWorks are no longer doing development work or bug fixes on their Reference 4 “legacy” product (which did have at least one known graphics bug).
I’ll see if I continue to experience this behavior with Sound ID Reference. I have completely uninstalled Reference 4 from my system.
).