Any news on progress re the core handling issue? As I am affected by this in my mixing sessions, I am very much interested in seeing this addressed in the foreseeable future. The modern multicore processors are already years old, and still Cubase cannot make full or correct use of these modern cpus.
It would be fantastic if Asio guard would not max out at marginal total cpu use, as it does today. I don’t think it is unreasonable to expect that Cubase should handle this much better than it does today.
So, I am bumping this question to the fore again, eager to hear about any progress.
imo….imo….imo ….Fabio already said a couple of important things to you here 20 days ago that (at least in my own perception) are broadcast loud & clear……
anything….anything that happens during a maintenance cycle will not only NOT be hinted at beforehand in any sort of calender reference, but will also, upon whatever release date, likely be….from my perception of his response to you and history we already have…. minor tweaks….as NO one knows (dev or otherwise) how even minor maintenance tweaks may/may not work out across the masses of various-computer configurations. Including your computer when/if…..unless you then see the Steinberg truck pull up in front of your house with techs coming in to analyze your exact pc to see how the update did/didn’t do
Based on that first point he mentioned, I personally interpret that I may sit out the next couple of years of updates…..take a look at where the state of things are out there at Cubendo 17/18 or so….even then, taking a conservative approach in updating my Cubendos from 14. Maybe Cubendo 20 is where I re-enter. Only the engine team knows how many ver cycles may be necessary …and I’m sure it’s an estimate on their part as well.
No way are the devs going to get more detailed than we’ve already heard here this year….imo.
All things being considered at any rate…..I don’t generally have issues with my ver14 (Win 11 based) synchronized/slaved systems….usually buy each year updates for each (until now) more from loyalty than anything. But, maybe I’ll sit out now.
I applaud those… like Takfat……who keep the important discussion going.
I applaud those… like Takfat……who keep the important discussion going.
As do I. Also like you, I usually - always, actually - buy the yearly version updates. For my part, that is mainly out of loyalty with the daw that I use.
Maybe Steinberg are unimpressionable. Or maybe they will listen, and speed things up. I’d like to believe that.
Again, like you, I thought to sit version 15 out and remain on 14. But I version updated. Out of loyalty.
Thank you for the quick reply, @Matthias_Quellmann, and for confirming that nothing is in the short-term pipeline. This is what I feared.
I love Cubase, and the workflow I have in it, with its seamless integration with Spectralayers Pro, which I use a lot. Also, as a Cubase user for over a quarter of a century, it pains me to see this serious shortcoming persist from iteration to iteration of the app.
I sincerely hope that this will finally be solved in Cubase 16. If not, I will have to start looking elsewhere for my mixing and composing duties, since Cubase today cannot make use of the processing power at my disposal.
@awesomeaudio I don’t see any reason for pointing out amount of RAM as it has nothing to do with core handling issues. Both my systems are equipped with 32 GB of RAM and I never had it filled more than 60%. I also rarely reach more than 20% CPU usage while ASIO subsystem often goes over 75%.
Though admittedly clunky -would using Project Lasso and Audiogridder allow one to get the desired/expected computer performance while keeping on using Cubase?
Audio gridder locally is the answer, you can max out your machine this way. It’s actually not that much of a pain either as everything is local on the machine. Only thing I find is that you can’t see what’s actually being used inside the AG plugin on the mixer insert…
Being able to rename plugin inserst would be a useful feature for this workflow.
I already use Audiogridder locally. So what I want is Cubase to not need these kind of crutches. As you say, AG is great, but not without its quirks.
It is not unreasonable, I think, to suggest that Cubase should be able to distribute processing load evenly to all cores in a modern cpu. It is, after all, 2026, and this technology is not brand new anymore.
This is a very serious shortcoming of Cubase, and Steinberg will have to address it sooner or later. I am hoping for sooner…
I completely agree Magnus. Reaper has the best processing distribution but it’s not without its quirks as well. The big issue really for me is it doesn’t have EUCON and I’ve got an S3 a dock and avid control here in the studio.
I really like being hands on when mixing and EUCON is the best protocol by far.
Due to competition. Microsoft recently announced plans to update Windows 11 to try and make it more optimized for gaming. Some of the things that were mentioned was improving background tasks and CPU scheduling.
CPU roadmaps look like there will be significant architectural leaps in the next few generations.
My personal speculation would be to hope that Steinberg makes significant improvements in this area within the next 4 years.
Well i’m just assuming that improvements to the windows scheduler to help reduce things like stuttering and delays etc. would also be beneficial for real time audio as well. However I could be wrong.
Reaper uses Windows’s own thread scheduler, and performs much much better than Cubase, which uses its own thread scheduling.
So, as is explained in detail earlier in this thread, this is really a Cubase issue that needs to be fixed by Steinberg. The thread scheduling in Win 11 is fine.
Interesting, I didn’t know that. I was just thinking that future updates would have to be designed around these recently announced Windows scheduling changes.
….Fabio already said a couple of important things to you here 20 days ago that (at least in my own perception) are broadcast loud & clear……