The CPU usage and especially load distribution per all cores is extremelly well done in Bitwig.
I made a set of 8 non identical but very heavy on cpu channel strips processing some audio tracks. Non identical, because i wanted to simulate real life conditions.
Bitwig managed to run 3x those tracks - so 24 (almost same for ableton live - 23) Cubase was chocking at 14-ish Regardless the buffer size, guard etc. Studio one could run just 12. Reaper 12-13.
In real life, in my projects I can run way more cpu-heavy plugins in Bitwig which in Cubase I could only dream of.
So cubase’s engine is (still) extremely underoptimized for today’s multicore cpus.
antic604 wrote: Sat Sep 19, 2020 8:36 amHave you tried disabling VST guard (or something)? One thing people rarely get is DAWs like Cubase or Reaper seem to offer better performance than Live or Bitwig is because they use tricks like that - bigger buffers for unarmed tracks, pre-rendering of stuff in the backgroud, etc. at the expense of fluid playback when stuff changes.Reefius wrote: Fri Sep 18, 2020 9:46 pm What Cubase really needs is gapless playback. It's so annoying that the audio gets interrupted every time I add a plugin, configure a send, add sidechain, ....