Please stay on topic everyone. It doesn’t help anyone to make this a PC<->MAC mud fight.
1 Like
The next update will have an option to turn off GPU acceleration. The issue is in the AMD driver which Apple has fixed for the current macOS version. I doubt they will update any older macOS version.
Hey luke7020,
which mac and which graphic card are you using. We are not aware of issues like this with Big Sur yet.
Maybe I missed it - is Cubase good to go on Big Sur?
Thanks Arne,
I’m actually using the latest version of Big Sur and still have the issue?
Cubase itself is Big Sur ready from begin. Only Retrologue and Groove Agent SE have UI artifact issues.
But you have to make sure that all your other plug-ins and hardware drivers work on Big Sur.
This may be another issue then. Do you get this by just using Cubase without 3rd party plug-ins? And what’s your setup (mac, GPU, etc…)
It happens with no plugins loaded, I only have to start scrolling through the media browser for it to happen.
So BigSmo, which system do you have exactly?
If you look at his post much earlier in the thread, it appears he is using the exact same 10 core iMac Pro as I have (not sure which GPU he has).
And the GPU is exactly the info I’m most interested in.
iMac Pro (2017)
Processor 3 GHz 10-Core Intel Xeon W
Memory 32 GB 2666 MHz DDR4
Graphics Radeon Pro Vega 56 8 GB
Really hope this helps.
Hi Arne
2020 Mac Pro 16 Core 48 gbs ram -AMD Radeon Pro W5700X 16 GB - latest Big Sur latest Cubase Pro - crashes on every single start up ( second load up works ), have trashed prefs - gone through every 3rd party plugin etc etc
and of course spinning beachballs constantly
Please post the crashlog. Your setup should not exhibit spinning beachballs in Bug Sur (according to Apple).
How many screens do you have attached and which resolution do they have?
Same problem here with Cubase 11. iMac Pro 10-core, 64 gig memory, Radeon pro Vega 64 16 gig. Catalina 10.15.7. I also have a Kensington trackball connected. Maybe less problems with the trackball disconnected?
Occurs randomly when I use the mouse, click on something etc. Freezes for 5-10 s. The sound keeps on ok.
I just heard from another user that he has this issue only when Final Cut Pro is running at the same time. So it looks like that some other applications can affect the performance of Cubase. Do you have any other heavy GPU program running at the same time as Cubase?
I also have the Radeon Pro Vega 56 8GB graphics and have the same problem.
I don’t have any other heavy gpu apps open. Only safari and pages. Though I used to have fcpx open in the background with no issues with 10.5 and Catalina.
But regardless I’ve tested it without and balls are still there. Having said that over the last few days I’m noticing the balls are less. They are still there. But noticeably fewer. I cannot deduce any pattern of what May be causing This. 
Also the crash on load up has now ceased. For the moment. Very confusing why it seems to happen sporadically. No pattern behind it.
Glad I found this thread as I wondered if it was just me!
As above - spinning beach ball at apparently random times. This is even with a direct audio in from my guitar through an external Boss unit, so no plug ins at all.
iMac Pro 2017, 32GB RAM, Radeon Pro Vega 56 8 GB. Big Sur 11.1.
I am having the same issue with Big Sur and Cubase 11 on a 24-core Mac Pro and the base AMD gpu. It happens even with only a single track with Halion on it, so it’s not third-party VSTs (I also tried physically removing all non Steinberg VSTs and made no difference). For me it most often happens when Cubase has been inactive for a while and I press play or record - spinning beach ball sometimes as long as five minutes and the UI freezes, but the audio will often begin to play even while the beachball continues spinning. I also tried Cubase 10.5 on the same Mac Pro and have the same spinning beachball so I’m not sure what’s going on.
I also notice that the CPU use seems to be way too high. A single instance of Halion with a couple of patches playing will overload the cpu and the audio will stutter. Changing the buffer size makes no discernible impact.