Also this is a complete new install of C13 , no update from C12 , i haven’t even loaded C12 yet . I might not even add C12 as this could of been most of the issues thinking about it , what with all of the broken Graphics2dll problems that plagued C12 for sooo many users .
More testing
Happiness ,at last , you can all fight amongst yourselves for the blame , all i know is :
Bios redone - NEW
Windows installed by pro
Win optimising -DONE
Graphics Card setup - DONE
All programs and vsti’s loaded - DONE .
Full hog , no corners cut .
1 full week of Making this machine the best it can be for a new C!£ install .
AND THE RESULTS …
Happy to have been Forced into this situation because of just updating ONE version Cubase ? Not at all .
But im damn happy with the outcome , nerves of steel , cool head . Here’s some other things ive noticed
Supervision flicker : Try saving as default with the Spectral Intensity as one of your meters … for me the flicker stops
Loading Halion 7 now seems to no longer have the behaviour as from UPDATING from C12 ,and thats the crucial point here , C13 was the full installer .
If i add Halion 7 to screen 2 , it flickers out of control , move it to any other screen and it behaves .
For me it’s job done , will i go through this again for C14 or even C13.0.20 ? I’ve very nervous about that , for C14 defiantly not . for C13.0.20 it’s sit back and wait and see .
Nothing else will be installed on this machine from now apart from the brands i 100% trust for plugins
Now just to upgrade the cooler to the Scan Computers recommendation B quiet 240 silent loop tomorrow to give the i9 happy environment
2 Likes
Indeed.
1 Like
Hello,
i can absolutely confirm your experiences with AudioGridder, but under Win11pro, Cubase 12 pro, i913900k.
It’s astonishing and frightening at the same time, how much better the CPU performance is used by AG! It is absolutely illogical to run a second unit in the background to get significantly better Performance-results in Cubase, I would have expected exactly the opposite.
This suggests that Steinberg really has a big problem with Cubase here!
Thank you for sharing this, for the moment, in my opinion, its the best way to make my system much more powerfull and stable.
2 Likes
Well
After a very long stressful week i’ve struck the jackpot , my conclusion
As i mentioned right at the top of the thread ,first post ,i believed that Acustica Audio played a major part in blowing out of proportion the issue with the Over sampling issue in Cubase .
I haven’t got a clue what my Pro OS super hero has done BUT >
Halion now has normal behaviour , i can now open this project in a buffer 256 with NO spikes , it looks like for me the problems are solved so yes @MrSoundman was partially correct and certainly correct about the plugin vender in a chat we had a while back BUT , i really think that the C12 update Exe is not suitable for some machines and certain Oversampling half baked plugin venders total break the problemed install .
Im peeed off that i was Forced to go down this road but Holy Shite , it’s now worth it :
LOOK AT THAT ASIO METER (same project all the way through ) and Halion 7 has even been removed with NO adverse behaviour .
(Uploading Vids are restricted to 4mb hence being so short )
Really glad that it helped you! Yes, I agree that it is not logical that loading the VST externally through audiogridder causes the performance meter of Cubase to decrease so much, and become totally stable.
It is a clear indicator that something is not right in Cubase, with the way that it is hosting certain VST instruments/plugins. I hope that Steinberg can get to the bottom of it and resolve it.
4 Likes
Anyone got any ideas on how to fix this on a Mac m1 ? I really don’t want to do a clean install and have to redue all my preferences and shortcuts from what I have read. That will take forever.
I’d just wait. C13 generally has some performance issues, which are known to Steinberg. They’re gonna rework some things with the upcoming updates, so chances are this is gonna be fixed in a maintenance update.
1 Like
Yes as TJ says , i would just wait , i made the decision before purchasing C13 if anything was wrong then i would go down the path i have just so the new Generation of Steinberg software had the best chance to work but i didn’t expect all this 
First releases are always known to be a bit of a Beta testing time , they will eventually get there … BUT how look will it take ? Thats the question this time
been doing more testing today on my 12900 laptop.
Interesting findings that may have some baring on cpu spikes.
On windows 11 and using an 12900 CPU which has E and P cores, not unlike the M series Apple silicone chips which call them Firestorm and ice storm!!!
Now… I opened a busy mix and was starting to get cpu /ASIO spikes so i opened windows resource monitor only to see half of my cores were parked!
So I downloaded Park Control and set my machine to Bitsume highest performance with no parking and boom… ASIO meter was solid as a rock and stayed planted.
It also took my DPC latency down from being in the red to less than 100… obviously Mac’s don’t have DPC but, if they’re doing what the intel CPU’s do in regards to ramping up and down in frequency and parking cores then possible you’ll see similar performance issues. Despite my DPC latency being terrible i’ve not had issues with running it as a DAW machine over the last 2 years. It would seem that power management of these new CPU causes DPC latency, however , as they have so many cores yo don’t actually get audio dropouts like you did in the past.
Anyway , I thought this might be pertenent as I now have cubase 13 running on the laptop very happily with a very stable ASIO meter.
M
2 Likes
This really was about the old Processors Marcus but that’s great to know . One thing thou , as it was AA that totally broke my systems , even system restore couldn’t recover it im not even tempted to load the Aquarius any more .BUT im happy ,C12 is sooooo super stable now , im really surprised
You can save your pref xml file and put it back after an install. I think it is in user directors then your user, then ‘library’ and then ‘preferences’ and then ‘cubase 13’ then ‘presets’ then ‘configurations’. Something like that. If you save your settings they will pop up in that folder i think. Not sure where shortcuts come out but near the presets folder i would guess, there is a ‘KeyCommands’ folder inside presets so its probably that.
I know its no consolation but i have an M1 Max Studio and a 16” M1 pro and both are working exactly the same with C13 as they did with C12.
Maybe its a bad plugin C13 does not like. You could try creating a new folder and copying everything out of your VST3 folder and then introduce them back a batch at a time and trying C13 between batches to see if any VST3s are causing an issue. I would make a separate backup of your VST3 folder first.
A project i was really concerned about :
150 tracks - 40 mins long
Computer and C13’s not even breaking a sweat
1 Like
Thanks for this NB. I didn’t even know this was a thing!
I’ve installed Park Control and switched to the profile you specified and the spikes have gone with my i7-12700KF.
1 Like
Ah no problem, there are so many threads /users comments I’m not sure which one I was really replying to, if any, I thought it might be a general helpful bit of info .
regarding AA, I’ve been using them as my main plugins for a lot of years now and never had any real issues, the main one was stopping Cubase from closing down which became a PIA but was sorted by Steinberg eventually.
My current testing is basically openning old projects which have a lot of AA plugins and so far it’s NOT been an issue even adding newer OS versions. I’m still tsting to see if I can put C13 into a commercial session/project yet. I have a week to put it through it’s paces before I decide what to do, hence my involment here at the forum at the moment.
For those interested who have AMD cpu’s this is another way to stop core parking without using process lasso or Park control.
M
The underline problem certainly was a Steinberg thing with the UPDATE exe BUT installing ASH Ultra completely broken my system , no restoring NOTHING cured it so i was forced into a reinstall . G even recognised there was an issue Hence the release of a new update for the latest plugins released , BTW the two Cubase AA beta testers that like to let themselves known as beta testers really need to find another job . I no longer trust AA fullstop
sorry to hear this. I have Ash ultra and use it 4x AA OS and have no issues. Just goes to show it’s a tricky thing running a DAW at times.
M
Not at all , it’s tricky trusts plugin venders with strange frameworks
Also take a look at this imho important setting.
It helped me, as it was deactivated at install.
Now I can record-arm my tracks by default again (Mac M1).
Hope it helps somebody
Acustica stuff doesn’t play nicely at all with Cubase in my experience. I have stopped buying their software as a result. Sienna is unusable for me at 128 sample buffer. Completely unstable inside of Cubase, or running inside of Audiogridder locally.
I swore off buying any more of their plugins after my experience with Sienna. I made them aware of issues, and they did the bare minimum to get it to stop causing Cubase to hang on exit, or randomly freeze and that was it.
I did end up getting Mystic recently… I don’t even attempt to use their plugins until I have completed all tracking, and upped my sample buffer to 1024.
I tend not to believe the hype with Acustica. There are much better optimized algorithmic based plugins that have much smoother workflow, and either just as good, or better results.
Pulsar Audio, Pulsar Modular, Vertigo Sound, Wavesfactory, Relab, Universal Audio, Tone Projects…Etc.
1 Like