I copied over a large C12 projects files into a new C13 project and saw CPU rise, but mine was down to the audio files coming in with musical mode enabled.
Obviously not your issue, but it’s worth being mindful of.
@Ed_Doll - please put me down, as well. Spent my entire Sunday exploring the unpleasant innards of Windows. I hate it. Just want to get some music done without audio deteriorating into a garbled mess for what seem like totally random reasons and spiking the VST meter.
I feel that Steinberg really, really needs to develop stronger relationships with the likes of NVIDIA and Microsoft and make absolute certain that while Cubase is running, nothing, NOTHING has more priority than any part of the processing chain Cubase relies on to deliver real time audio. NOTHING.
This current state of affairs, especially since Cubase 12, is just obnoxious. It’s never been perfect, but I’m just worn out dealing with it. I have a very badass, cutting edge computer with all the latest drivers, BIOS, etc. There’s no way I should be battling random latency spikes in 2023. Why is real time audio such a low priority for these monster companies? Seems like you & Yamaha should get together and force their hand somehow if they will not prioritize it, no pun intended, voluntarily.
7 Likes
Thank you Ed , while you are around i know things will get done , Thanks for your attention
3 Likes
I second that. Thanks.
1 Like
That’s something i can try tomorrow , render the tracks IF there are any Musical mode , can’t remember but its a good thought , any idea on the Retrologue and Groove Agent spikes when activated as you can see all third parties are fine even with Vital of Max performance . I had a crash with the Vst3 plugin set , i wonder if it’s connected .
Just started a new project today and it’s been stable apart from one ‘unexpected quit’ NO DMP as the safe mode shows .
But im happy , i just wanted all this logged , i like C13 apart from … you know what’s 
Experiencing the same issues on PC win 10 i7 6700k. I’ve also noticed my SSL UF1 controller is lagging when scrolling through tracks, which also freezes the fader meters while scrolling, something I wasn’t seeing in Cubase 12. I’ve made the decision not to use Cubase 13 until these issues have been resolved.
2 Likes
Hahaha…this is funny: 2 minutes after opening the project - but I hadn’t even pressed play even once (I turned it on, and started watching a movie)
(Yeah - I don’t panic, since I can finish my stuff in Cubase 12 
)
I didn’t get to take a screenshot until after it had spiked 
1 Like
We have a good relationship with Microsoft, but that doesn’t necessarily mean that Microsoft is going to change the operating system just for us. Priorities have to align and there are other types of applications with entirely different requirements. Nevertheless, it is of mutual interest to provide the most seamless and reliable experience on this platform. Let us take a closer look at the issue now. We’ll keep you posted.
6 Likes
And this , is why i tagged you specifically Ed , because i know you will do you best for resolving issues , not that i don’t trust other members of staff , your just the old school face i know and trust more .
Thanks . I’ll keep this thread just to posting practical new info or for other with the same issue
Really appreciate your time
2 Likes
Ok found something I think.
Glitch occurs when ever video card switches its power state , low to high or low to high.
This switching does not happen in Cubase 12 but does with the same project in Cubase 13
100% reproduceable here and also accounts for why forcing full power state on the video card cures it.
Hope this is of some use
Hippo
4 Likes
I don’t know if it’s just a coincidence, forgive me if it’s irrelevant, but I think it’s worth bringing this up, being the early days of 13.
I’m on W10. Yesterday, I closed down 13, and immediately went to shut down windows. A screen popped up, the one that says that an application is still running (Cubase 13) and if I really wanted to shut down anyway.
At that point I changed my mind, cancelled the shut down and launched Cubase 13 again. Fired up the same project I was working on 5 minutes before. And:
- Spikes and drop-outs. Interestingly enough, it was ASIO Guard that was bottoming out first.
- Moreover, no Halion. Not a “no entry” license issue, no. It’s just that the Mediabay thingy would not show most Halion stuff. Just the Electric Bass from absolute, some freebies like Guitar Harmonics and such. It would show “World instruments”, but not “World Percussion”, it was bizarre. I shut it down for the night.
I have my video card to prefer maximum performance, but I haven’t manually checked Windows Defender.
That’s all, sorry if it’s worthless info.
Which card Hippo , and how did you force the full power state ?
Appreciate it, Ed. I understand, but at the same time, again, it’s nearly 2024, and we’re still fighting our computers to get reliable real time audio. I’m watching Netflix right now with the app at 4K and the video slows, then plays back quickly to “catch up”. Sometimes it plays back perfectly without any such issues. No idea why, and I’m not going to spend anymore evenings or weekends trying to figure it out.
The whole thing is just sad: this is a top-of-the-line computer (as of early-mid 2023, anyway, still very nearly so) and there are some things that should just be very rigorously tested by all parties involved and it’s clearly not happening. Or this wouldn’t be happening.
So tired of the finger being pointed at some very esoteric setting or some other company and not the state of the industry as a whole and it very simply prioritizing the wrong things: “innovation” at the expense of the basics. Tale as old as software, and almost as irritating.
2 Likes
Yes, ive noticed you have to allow all processes to stop before shutting down now , no biggy if you know but … Great get this posted , it could be a potential
We have one hell of s sick puppy audio engine . Here’s what ive tried today :
-
Rendering and removing the only Musical mode track in the project = NO CHANGE
-
Removing tempo track as this track was not needed , the longer project has tempo change = NO CHANGE
-
Adjusting fades on tracks that had no faded = a little difference ,slower ramping in stead of spiking
NOW for the really really Bizarre behaviour :
The ONLY and by mistake midi track i imported into the project was a Halion 7 track with the monitor Button enabled (and that is the important part the enabled ) .
Turning the enabled button off cause the project to peak to NEARLY 100% use even without the project playing . Strange aaahhhhh . Here’s a vid …
So i thought i would delete the track from the project and this would be problem solved aahhhhhh ? TOTALLY wrong . .vid 2
The project has now DOUBLED with Asio and nearly unusable . I think im going to spontaneously combust at this point , so , save the project under a different name and reopen should solve it right ? OOOOHHHH SOOOO WRONG
I had to disable 17 plugins to be able to get back to anywhere close with the Asio meter
17 , that’s a big SEVENTEEN . Vid 3
I’m absolutely lost for words here , this is beyond belief , how the hell did this SICK PUPPY audio engine ever make into past the first stage of Beta testing , im not joking heads should roll for this , this really is a disgrace ,sorry but ,very very disappointing .
Cubase 12 still runs this project absolutely perfectly , no hassles at all . Im now totally lost for words
Im done , need a break , fed up , peed off , worn out
1 Like
Hi Ed,
How seriously you consider DAWbench? I remember that in Cubase 9.5 era there are some discussion about MMCSS fix at that time. Since I am mostly on DSP i noticed that amount of plugins that I can load on C12 is higher than on C13 (12900k), I would like your opinion on that and generally we are all curious how do you benchmark performance while supporting hybrid cpus and in practice that doesn’t means that C13 is performing better than C12 but yet opposite which is subject of this topic.
Thx
@Highly-Controversial , could you provide some additional information, please?
It is obvious that there is an issue with switching plug-ins away from the ASIO Guard into the real-time path by activating the monitoring on the channels.
The general behaviour seen in the first HALion 7 video is to be expected as the plug-in and the complete channel moves back to the ASIO Guard, hence the increase in the performance meter. Whether this significant jump is to be expected or not, cannot really be answered as this is nothing that we can reproduce here.
We would like to have one of your projects that shows this behavior if possible. Also, while running the project, please create a plug-in report from within the plug-in manager in Cubase.
Moreover, a Windows system information file (.nfo) would be helpful.
You could send a pm my way.
There was also a discussion on GPUs in here. If there is more than one GPU available, usually Windows decides which GPU to use. This can be changed rather easily in Windows 11 and Cubase could be assigned to one or the other. Here is a rather lengthy description on how to do that. Perhaps this yields a positive result for one or the other. How to choose the default GPU for games or apps in Windows 11 (digitalcitizen.life)
Retry :
Re-inmported all tracks without tempo track and Halion 7 . Performance : through the roof .
Exaclty the same project , look at the meter , good yeh ? No look at the mixer
All tracks third party vst’s removed , not only that , control room completely remove , two super visions , 3 sonarworks
ALL just to get the performance back for deleting halion 7 . Someone book me a room in the local mental institute please
1 Like
Ok , you can have to project no worries there and ill get the nfo file . Im sorry im not washing it about Gpu’s , i upgraded to the Rtx 3060 because of the fantastic results of Spectralayers , are you telling me that even thou Speactralayers is now a Steinberg product the RTx 3060 may NOT be suitable for C13 where it was for 12 , and my old HD7900 was suitable for 12 years before that ?
I had nothing but problems with C12 and choosing graphics card because of the COMMON graphic 2dll issue that plagued C12 for soooo many people and now you may suggest having to change again ?
What’s more i had a crash with the Vst3 plugin set and Martin confirmed and reported it , any chance that could be the culprit ?
I can also confirm the same behaviour in Cubase 12 with the amount of Asio used .
So basically with Halionloaded and active , the Asio is lying about how much has been used ? And this is why when you activate Retrolouge your getting the true reading ?
So if you build a project with HALion thinking you have only used 50 % of the asio you are completely mistaken ,it’s actually near 85% is that correct ? and this is where the spiking or ramping is coming from because the Asio is trying to go back to the true reading ? Sorry im totally confused now @Ed_Doll .
1 Like
The GPU part of my reply was rather meant for some other posts on this topic.
Regarding the crash dump, I don’t see any confirmation by Martin in here. It was a crash in the Cubase plug-in set.
2 Likes