The latest Cubase 11 update is working fine for me. It's not native, but it's your plugins, not the DAW, that put the greatest load on your cpu. And very few 3rd party plugins are native at this point, so it doesn't matter much whether the DAW is native or not.
Glenn, you are without a doubt much more versed in these issues. However, I must respectfully disagree about Cubase. It was written in and for Windows 10, where as Logic Pro was rewritten for the M1 chip
Your point about VSTs is true, 3rd party plug in compatibility and native porting is still a ways to go, however, with that said, Cubase 11 will be taking more resources and over time - especially with more plug ins that may not be native - it will tax the CPU....
I am simply saying you are better off with Logic Pro if you can start fresh. as you know Glenn, I am a Steinberg enthusiast, I not only think they are the best programmers and coders, but I think they have been done an injustice not being recognized as the true forebears of the gold standard of modern recording (pro tools was given that, but to be fair, digidesign and pro tools back in the 90's is different than avid now) - so anyway
You are right, until everything is native, your going to run into a little extra CPU stress/load. However, using a native and optimized DAW versus using the Rosetta enabled cubase is not doing the m1 justice IMHO - one 3rd party plug in (which is the only non native Logic Pro plug in I use, XLN addictive drums 2) isn't going to tax it much at all - where as porting an entire DAW (especially one as vast and complete as Cubase 11) will cause extra overload, on top of whatever 3rd party plug in
So I don't mean to be contrary, especially because you know your stuff, but I think you might do yourself even a service by ditching cubase 11 and getting Logic Pro dude...I mean, you can sell it easily and still have enough for Logic Pro plus extra for a VST lol
I respect your input always
@GlennO