Blakus
Midi Magician
Clock speed is no longer king in Cubase?
I thought I might start a new thread on this topic, as for me it has proven to be a game changer.
(TL:DR - additional cores are better than just purely focusing on clock speed with ASIO Guard)
So, I just upgraded from an i7 3770k, 4 cores @ 3.5GHz, to a 6800k, 6 cores @ 3.4GHz base. I am using the exact same hard drives (except a new m.2 drive for my operating system), and went to 128gb of RAM.
Being the same clock speed, I would have expected that my ASIO/CPU performance in cubase would have been not much different at all, based on the "clock speed is king" theory that seems to be prominent. My experience with Cubase Pro 9 has been the exact opposite. Projects that used to bring my old 3770k to its knees, now open with only 60% cpu/asio usage - and I'm not exaggerating here. Unless there's some other voodoo going on, I am fairly sure that more cores are better than many think (at least in Cubase). I'm running hundreds of plugins, hungry synths etc, 300 kontakt instances, all with no problems now.
My "hunch" is that Cubase and ASIO guard have a lot to do with maximising core efficiency. ASIO guard effectively means that the entire template isn't required to run at intensely low latency, only the tracks that are currently being selected/recorded. So, most of the template is running with buffers that give 98ms latency, but I never feel this, because my actual live latency is 6ms (with 256 buffer). That 98ms provided by ASIO Guard is crucial, as the majority of the template no longer becomes so dependent on the clock speed required to deliver instantaneous, realtime performance. There is now time for cores to kick in with even distribution, much more effectively.
I think that for live performance, or other DAWs that still are required to run all tracks at live latency without features like "ASIO Guard", clock speed is king. But I am not convinced this is the case for Cubase with ASIO guard.
I just ran a test in Cubase with a large project that is running at around 60% ASIO meter - plenty of room for many more plugins/polyphony etc, it runs flawlessly. I just disabled ASIO Guard. Woah. The project will not even play at all and the core distribution is poor!
Anybody else singing ASIO Guard's praises? :D
I thought I might start a new thread on this topic, as for me it has proven to be a game changer.
(TL:DR - additional cores are better than just purely focusing on clock speed with ASIO Guard)
So, I just upgraded from an i7 3770k, 4 cores @ 3.5GHz, to a 6800k, 6 cores @ 3.4GHz base. I am using the exact same hard drives (except a new m.2 drive for my operating system), and went to 128gb of RAM.
Being the same clock speed, I would have expected that my ASIO/CPU performance in cubase would have been not much different at all, based on the "clock speed is king" theory that seems to be prominent. My experience with Cubase Pro 9 has been the exact opposite. Projects that used to bring my old 3770k to its knees, now open with only 60% cpu/asio usage - and I'm not exaggerating here. Unless there's some other voodoo going on, I am fairly sure that more cores are better than many think (at least in Cubase). I'm running hundreds of plugins, hungry synths etc, 300 kontakt instances, all with no problems now.
My "hunch" is that Cubase and ASIO guard have a lot to do with maximising core efficiency. ASIO guard effectively means that the entire template isn't required to run at intensely low latency, only the tracks that are currently being selected/recorded. So, most of the template is running with buffers that give 98ms latency, but I never feel this, because my actual live latency is 6ms (with 256 buffer). That 98ms provided by ASIO Guard is crucial, as the majority of the template no longer becomes so dependent on the clock speed required to deliver instantaneous, realtime performance. There is now time for cores to kick in with even distribution, much more effectively.
I think that for live performance, or other DAWs that still are required to run all tracks at live latency without features like "ASIO Guard", clock speed is king. But I am not convinced this is the case for Cubase with ASIO guard.
I just ran a test in Cubase with a large project that is running at around 60% ASIO meter - plenty of room for many more plugins/polyphony etc, it runs flawlessly. I just disabled ASIO Guard. Woah. The project will not even play at all and the core distribution is poor!
Anybody else singing ASIO Guard's praises? :D
Last edited: