When Pro Tools did this (I think it was version 11?), the CPU efficiency got a pretty huge boost. I don’t know if it’s undergoing a major rewrite, but I do know that something like CPU efficiency requires a major core refresh. New mixer here, new Window management there, I sometimes wonder how they manage to keep it running.Ĭubase 9 has been a good experience for me, I’m not complaining.īut I do fear a little what the future brings, I’m looking forward to the next version to see what direction Steinberg will be going.
They are just doing it on a running platform bit by bit, instead of starting from scratch. I’m not crying here, am just wondering why I can get so much more horsepower from these other two DAWs even on the latest flagship version of Cubase (same thing with Nuendo when I recently tried it)?īut isn’t Cubase undergoing a major rewrite ? So we can take “Cubase sounds better!” out of the equation.
#Reaper vs cubase mod
I know this has been discussed here in depth, with no solid answer as far as I’ve seen…but I’m hoping that a mod might step in and explain why this is still the case with C9? I exported both the Reaper mix and the Cubase mix (Cubase worked when exporting offline), and there is no discernible difference at all audio-wise between the two (they don’t null each other completely, but almost) – they both sound as huge, wide, and dynamic as the other.
Pro Tools is also more CPU efficient than Cubase in my extensive use of it but it uses a different plugin type, which shouldn’t matter, but does in conducting the most accurate comparison test possible. Both Reaper and Cubase were at 512 buffer size (ASIO Guard on high for Cubase, which is the best combination for CPU use on my setup) in this particular test. Reaper was and is between 20 - 35% or so better with CPU efficiency than Cubase in my direct comparison testing. This happened when I was trying out Reaper about a year ago as well. I recreated precisely the same routing, inserts, and audio (no VSTi’s in this session, it was just a mix). This is using the exact same VSTs from the exact same folder as Cubase. I was noticing again that Reaper seemed to be using a lot less CPU than Cubase in my testing sessions, so I recreated an exact mix setup that was very complicated and brought Cubase completely to its knees (maxed out CPU, constant dropouts) – Reaper was sailing happily at only about 70% CPU.
#Reaper vs cubase mac
Since I’ve been off of Cubase for new projects until the Mac GUI problem is fixed, I’ve been mostly back on Pro Tools reluctantly, but have also been checking out Reaper again.
0 kommentar(er)
