Sorry ive edited the other post please take a look if you will .
It was a separate report about the Vst3plugin set
Ok , i feel a bit of an idiot as it seems as thou i have been working a little bit of a track count hack without knowing it .
One HALion 7 track has been active monitoring all the time and not showing the true level of the project and when activating the monitor and the asio guard becoming active the meter goes down by half . So my dumb understanding is if you want a high track count have one track of Halion 7 active BUT it comes with a high price tag because the Asio guard seems not to like third party over sampling of any vender and causes the asio to spike to the non active position from what i can crudely make out here ,(this does not happen in C12 , the asio guard is stable hence getting away with high track count ) i might be a total idiot and have it totally wrong but that’s what it looks like BUT there are still Asio spikes ( in my defence ) which takes the Asio up to peaking and past .
Also no matter which way i adjust the Asio while the track monitor is active or not it makes no odds ,no difference .
So i still think there’s an issues here with plugins that have over sampling .
Valium come tooo me be know !
I’m on a Max M1 Studio Max, I too have the CPU spiking even at low CPU load, in projects that had no problem in 12. I seem to have it tracked to, as you say, oversampling plugins.
I experimented with freezing the tracks that had oversampling in the Soothe 2 plugin, which were all oversampled. I then played the song and there were no spikes. I put an instance of Soothe2 back on one track, oversampled it it and played again. 5 CPU spikes within the first minute.
So, I have to agree, I think the spiking may well have something to do with plugins having oversampling. (I tried on other plugins and Instruments and got the same results in CPU Spikes) You have to wonder how this got missed in testing? Or is this the testing period?
2 Likes
Ahhhh , thanks for confirming ,and you are on Mac, so it’s a cross platform issue .
Yes the Asio doesn’t seem to like the over sampling for some reason , im sure they will sort the issue out ,even if it’s just putting an over sampling limiter on the Asio Meter 
, seriously thou , im sure there will be a resolve , i appreciate the feed back and you adding to the thread , im not going as mad as i thought . 
2 Likes
Not to be the smart arse here but…Rule of thumb is to never upgrade to a xx.00 version anyways. There are always problems. A beta test prior to release could alleviate a lot of issues. Steinberg choose not to do it. Im still on C11. I know its old-isch but it works and none of the new ‘features’ will make anyone’s music better.
One thing to add to all this is ;
Too me it really seems like the Asio guard is at fault , on my system it doesn’t matter which option you choose ALL three have exactly the same results , disabling the Asio guard the project peaks out , unusable .
Is the reaction time of the Asio broken , it can’t react quick enough to all the OS plugins which causes the glitches , but if that’s the case why the slow ramping , is that because the Asio guard is slowly loosing it’s ability and going to the original project state .
My way of Nutter mad thinking is with the Asio guards options , there should be a way of balancing between the toggle of Active and Inactive track monitoring , but this seems not to be the case , it’s either very low , or original track state but still with spikes .
Is thinking out aloud good or can i expect and Ambulance at the front door with a loooovely white jacket with long arms and buckle straps 
I understand what you’re saying here, because software somehow gets a pass on QC because it’s traditionally been sort of OK or at least accepted with an air of resignation that there will be issues and problems not found in testing.
I’ve never agreed that that was acceptable and I don’t think it’s helpful to support that idea, because IMO, it lets them off the hook. A dot release shouldn’t have gaping and fundamental issues like this and it shows improper testing and a kind of disregard for the customer.
This comes from the top and is a combination of commercial “imperatives” and the huge efforts and hard work by the PM, analysts, developers and testers to meet commercial and usually unrealistic deadlines, but ultimately, it’s always that both testing cycles suffers and then decisions at the top to go Live with a product that isn’t really fit for purpose, but they (usually the Exec.) accepted the reputational and commercial risk. (Well, they say they do, but they don’t mean it )
2 Likes
I had really hoped that these issues would be made a priority and properly addressed with the transition from Cubase 12 to 13. Stability and optimization should be King.
M1 max Mac Studio here. Newly set up. I am experiencing the exact same performance issues on Apple silicon as I did on an Intel based Mac, and an Intel based Win11 pro system, at 48Khz sample rate and 128 sample buffer. UAD Apollo Twin MK2 audio interface.
Certain plugins and virtual instruments cause the Cubase performance meter to become unstable and erratic, especially at low latencies.
I have started to experiment with hosting instruments or plugins that are wrecking the Cubase performance meter outside of Cubase 13, inside of Audiogridder, hosted locally on the same machine.
The Eastwest Opus patch that was bringing Cubase 13 to it’s knees, hosted externally in AudioGridder doesn’t effect the performance meter at all!
How am I supposed to conclude anything other than this is an issue/conflict with how Cubase 12/13 is hosting 3rd party software?
The same software, at the same sample buffer, is working fine in Logic Pro, Studio One 5, in stand-alone mode, and now hosted in Audiogridder locally on the same machine, inside of Cubase, but not in Cubase 12/13.
To be clear, it is not all software that is effected, just some software, but much of them are very popular sample library players and VST plugin brands, and they all work just fine in other DAWs without the same crippling performance issues.
It is too easy to point the finger at the 3rd party plugins and instruments as being the cause of the issues, but when it is objectively true that they work fine in other DAWs at the same settings, it seems fair to conclude that Cubase is the problem.
I am gathering all of the facts and evidence and conflicting software/performance issues and uploading them to Youtube. Lots of people commenting that they are having exactly the same experience.
It really shouldn’t be up to the end user to figure this stuff out and identify these issues for Steinberg. It should have been figured out and addressed during the early beta phase.
I am in several beta programs for companies, and I would have identified these issues very early.
It’s really bad to offload these issues onto the paying customer so that it interferes with their creativity.
7 Likes
The processor affinity seems to play a role in here. To carry out the optimizations for the newer hybrid CPU environments, we had to change the behaviour and older non-hybrid CPU systems might have been affected negatively by these changes. At least, this is our first assumption that we are having a closer look at now. However, this may not be applicable to all the different reports in this topic but we have to take one step after the other now. Thank you for your patience in advance.
6 Likes
I have to say, installing Process Lasso and taking Cubase off CPU 0 has made a world of difference, it runs smoothly now, no crackles. Graphical issues still remain, flashing whitening of the GUI from time to time, but I assumne that’s a different issue.
2 Likes
Thank you for your input. A question: Are you referring only to C13? I run a 8700k still, so no hybrid tech, with N12.0.70, and everything is running fine. If that’s the case, upgrading to N13 would mean upgrading the whole system, then…
Thank you Ed
As mentioned about my complete re-install i will keep you posted on the results , this is insures a completely clean OS with only C12 and 13 plus the peripherals install with Total optimisation . So will be able to get a better scope on the magnitude of the problem on a brand new OS
Cheers
Is there away you could add a tick box for choosing your pre and post hybrid processors ?
I’m not sure if you’ve also see a thread I started that turned out to be related to this:
Short summary is that adding a HALion (or other softsynth) track to a project that was dropping out badly made the project play back just fine, assumedly due to its adding a real-time ASIO path, which ended up on the first CPU, which had been badly overloaded compared to other CPUs prior to adding the thread, and that lessened the load on the first CPU while spreading the load more evenly to other CPUs. (I also tried changing processor affinity for Cubase13.exe in Task Manager to avoid the first CPU, but that did not seem to stick like when I’d tried it in the past, probably with SONAR at the time. Not sure why, but that prevented me from seeing whether getting Cubase to avoid that first CPU would make a similar difference.) My CPU is decidedly not one of the newer ones - it is i7-5820K @ 3.30 GHz.
Hello, Ed!
I have a question about hybrid cpus.
In Gregs last two videos on Youtube he is talking about hybrid cpus and that you can change behaviour in the settings where asio guard is.
I cant find this option! I have an i9 13900k and should be able to see this.
Is there something wrong?
1 Like
Ok
Total fresh install today :
New i9 9900k processor swap out form the i7 so ,
Windows endorsed IT engineer ( 30 years on the tools ) completely did the ground up install , Bios checked and totally reconfigured .
Windows installed on the M2 C drive with every latest driver for everything you can think of .
No bloatwares , totally optimised and only Steinberg software and 4 venders of plugins going on here .
Tomorrow i will load the Plugin venders one by one and Test before going any further .
As it stands this thing flies . Latency is in the single digit’s so im excepting good results . If not i will be loading a competitors Daw and my IT expert will be going over the problems with a fine tooth comb because i’m not willing to spend another full week sorting out issues that were not there before an automatic download from the Download manager . One whole week of not earning a penny just because of a number of a program changes by 1 digit .
Also my experience with latency mon is if you don’t get some sort of spike immediately and the ISR max stays single digits you can leave it for hours and it still the same
3 Likes
I have an m1 max studio (monterey) and unfortunatly CPU-spikes too. In my case it was ni kontakt - since the update to version 7.7 (the last one) the spikes are gone.
2 Likes
FWIW, testing C13 on an old rig (i5-6600), no problems, CPU and ASIO meters are lower on all projects.
2 Likes
I was so happy when spikes issue was solved with version 12.0.70
But same here, in version 13.0.10 spikes are back, very unfortunate, because I bought the update because ‘Steinberg did put a lot of efforts in having better support for hybrid CPUs’… I’m glad 12 is still installed for the time being.
Running on Dell 7670, i9 12950HX, 64GB and fast SSD raid.
1 Like
Hi Ed, I can’t get anywhere with these CPU Spikes, it’s unusable for me. Please can I just get my money back?
1 Like