Does anybody else notice the slow, laggy gui when i.e. editing (quantizing) real drums hit by hit?
The more slices there are visible in the project window the slower it gets.
Especially scrolling and zooming seems really sluggish to me. If I hide the drums in a folder or just scroll down to where they aren’t visible anymore it gets smoother again.
Seems like Cubase can hardly handle that many tracks/slices displayed at once?
It does not seem to be dependent on plugin count, or even project track count, only amount of audio slices.
Its weird a PC like mine could run 4k resolution 3D games on best settings, but begins to lag when having lots of 2D audio events.
Also it does not change with or without graphic card. GPU usage is always near 0% (windows task manager).
Anybody knows how other DAWs perform when having lots of audio slices?
When I am editing drums I have 16 tracks in a folder with group edit enabled and do quantize the drums, or edit them by hand.
When quantizing, every drum hit gets edited, so you end up with approx 1200 cuts per 4min drum performance. Thats 1200*16= 19200 audio slices.
Yes I know thats a lot, but when dealing with real quantized drums you will have that many slices.
It gets worse when recording multiple songs in one project.
Running Cubase 10.5 on a
- Windows 10 (always up to date)
- i-8700k (overclocked to 4,5ghz, all powersaving modes off)
- 16gb RAM
- MSI GeForce GT 1030
- separate SSDs for OS/project/sample libraries
But also had the same problem on a much slower notebook before (hoped the problem would be gone when using a much more powerful CPU).