@Martin.Jirsak might be able to help with Process Explorer.
It would help if @deleted_by_self added basic system OS in your profile.
The post made to @Thor.HOG says nothing about your issue. It’s just a rant. If you sincerely desire to address your specific issues, then you need to clearly communicate them or find a DAW that works for you.
I’ve used the hell out of process explorer. Nothing makes sense, nothing fixes this.
I’m saying that Steinberg needs to be developing its own diagnostic tooling as part of testing and tech support.
@DrWashington Have you tried another DAW and got the performance you require?
M
This is probably Intel´s P/E-core issue, since I haven´t seen AMD users complaining performance issues
I am enjoying Tokyo Lament with my morning coffee 
Thanks for your kindness in the forum and your great music !
Yes, I’m very much starting to believe this may be a P-core/E-core issue, too. Just absolutely blows my mind that one of the biggest DAW makers in the world has not figured out how to work with these chips, by, I dunno, actually working with Intel and Microsoft to make sure the scheduler doesn’t zoinc up. But, here we are.
Had I but known how awful Intel is lately, I would’ve absolutely gone with AMD. But finding reliable info on the Internet about who has their poopies together lately is damn-near impossible. Everyone’s got an opinion, and you know what they say about those.
In any case, I’ve noticed Ableton is quite a bit better behaved. Not perfect, but this obnoxious spiking isn’t really a thing. So, I’m trying to migrate my workflow, but it’s hard: Cubase still has me spoiled with how powerful some of the tools are. It can be frustrating to work with because some of the features are clumsy, laborious, and not very intuitive (e.g. MIDI Remote as a whole), but the power is certainly there. It’s a hard habit to break.
But with this spiking I’ve found my desire to sit down and make music steadily deteriorating. It’s unbelievably annoying and I really feel like my productivity has gone right off a cliff. I’m also trying to migrate to my MacBook, but it’s like I have this Pavlovian response to Cubase I’m now fighting: I just now it’s gonna zoinc up somehow, and zoinc up it does, even on the Mac: lots of crashes. The application just suddenly goes poof and I lose all my poopies.
It’s truly a terrible state of affairs for serious electronic musicians in Steinbergland lately. I mean, from my perspective, it could hardly be worse.
If the plugin format allows individual developers to code serious abuses into their offerings and Cubase doesn’t blink, just runs it, then Steinberg has a serious problem on its hands.
I’m pretty intrigued by the CLAP format. It’s obvious that much of the rest of the industry has had quite enough of Steinberg’s arrogant, gatekeepy bullshit in designing these formats, which they absolutely are guilty of. They think they know best when often they make very, very questionable decisions.
I remember how much trouble so many developers including u-he had implementing the basics like MIDI learn when VST3 first came out, and then even years into it being out. There’s no excuse for that: the format was poorly designed–designed to cater to Steinberg’s own internal poopies it was foisting on the rest of the industry, or trying to, but the industry wasn’t having it for good reason, and Steinberg was eventually forced to backpedal and change things.
This is what happens when you have people who don’t actually have to use the software daily making the final decisions in meetings with a bunch of software engineers who think they know better than these very people.
There is, in my humble opinion, also way too much emphasis on catering to the wants & needs of traditional (say, acoustic/electric) musicians and not enough attention paid to what really matters for electronic musicians. At least the likes of Hans Zimmer have had some positive influence in this direction, I reckon, but it’s not enough.
If you’re going to release a major, flagship DAW and the biggest CPU manufacturer is releasing CPUs with these infernal E-cores, then the maker of this DAW needs to ensure it’s actually usable for most people with standard computers based on these CPUs before releasing it.
13 and 14 have both been an unmitigated disaster for me, and there’s nothing particularly special about my setup. Very mainstream parts. The only thing I can think to consider is the fact that I have a lot of SSDs and two RAID 1 HDD pairs. But none of this should really matter, and that is my point.
There are no good diagnostic tools that can pinpoint why this is happening so I’m in this perpetual holding pattern with this machine hoping in vain the situation will improve, getting ever more pissed off as the years pass with no changes. I do not want to strip this system down to nothing only to find that it doesn’t matter, that it’s just this CPU series being horrible for music production.
I don’t care if you agree or disagree with me: I find this situation deeply unfair, and I especially don’t care to hear you wax poetic about how very, very lucky we are to have such amazing tools that run so well on YOUR system. Good for you! I’m happy for you, I truly am! (If not more than a little envious). But I don’t need it rubbed in my face and I don’t need to be told to calm down. You’re not helping me, you’re only making me resent you.
I just think they lack of devs, seen here in forum some devs do two different program, which is imo bad idea for coding even though the dev might be the best for the job… also all the OS’s are going in bad direction by adding all AI stuff everywhere…
I don’t know why you assume having lots of SSDs shouldn’t really matter. How many exactly do you have, and how many are being accessed simultaneously, and what busses are they connected to in your PC? Are you using lots of external disks on your new M4 Max as well (given that you say that beast of a machine is also regularly crashing)? Are you using RAID HDDs (not SSDs) to hold VSTis or sample libraries? Does your disk cache on the Cubase performance meter reach a high level?
Steve
@deleted_by_self do you have a project you could share so perhaps one of us could try it on a similar system and see if ti exhibits the same issue?
I’m sure none of us come here to rub your nose in it as you say. I can only speak for myslef ,but I can tell you with my hand on my heart that I only comment to try and help you in whatever way i can.
.There are plenty of electronic/pop musicians who put food on the table everyday using Cubase, so it’s not that Cubase only works with acoutic/electric music at all.
Artists like: Tinlicker, Gareth Emery, Ferry Corsten, Zedd, Tiesto, Madeon, Junkie XL, Paul Van Dyk, Infected Mushrooms all use Cubase , you cold include Ian Kitkpatrick as well as a very sucesfull electronic/pop artists.
try creating a similar problem project in Reaper and see what happens at least you can then rule out Hardware, although i suspect if your Mac is also causing problems then it’s not that.
The big difference between Cubase and Reaper , and this is very important… Reaper lets the OS deal with the threading/core loading whereas Steinber overide this and have their own threading/core loading. This has it’s plusses and minuses.
So try reaper as a comparison of how the 2 different aproaches suit your palate.
M
Maybe there’s AI to set your Hard- and Software configuration right.
Just a guess.
Thank you. I appreciate your measured response. And I’m already aware of these electronic artists, though I have to confess not being much of a fan of any of their current work. I was at one point with some of them, though.
Either way, I’m pretty down in the dumps, I have to be real. Maybe eventually I’ll be able to focus on this again. I also own Reaper but have never liked the workflow or UI very much. Maybe I should give it a shot, at least for testing purposes. Ableton seems much better behaved, but just not as feature rich.
This whole situation is spilling over into my personal life now, so I’m really quite teed off at Steinberg for dragging their asses on addressing this for years now. I feel like giving up, frankly. I’m hoping that’ll change eventually, but part of me wonders if I even care anymore and if “hoping” is just an automatic manner of speaking.
Either way, thanks for the kind offer, and cheers.
I’ve been suggesting this to Steinberg for literally years now. Machine learning has incredible potential to figure out what’s going on with live audio streams and what’s interfering, and if given the correct root permissions, the ability to automatically correct the issues. Nobody is really even entertaining this approach to this day, though. It’s sad.
I’ve also been suggesting at the bare minimum that Steinberg develop deep diagnostic & metering tools that WE could run on OUR OWN systems that report directly to the mothership exactly what is happening in great detail. This would be a massive, massive boon to customer satisfaction, but no, pushing out more and more broken-ass features is the priority. Don’t even get me started on the unmitigated disaster that is the half-assed MIDI remote that is still, to this day, laden with bugs that for example break MIDI controllers ability to transmit under certain conditions, such as my Yamaha Montage in MIDI Remote mode. There’s an entire other thread on it that Steinberg hasn’t even touched.
THEY DO NOT CARE.
All they want is the perception that they’re ahead of their competition in terms of FEATURE COUNT.
That’s it. That’s what sells software.
So zoinc them and zoinc this whole industry.
I have some frustrations with Cubase too, but your statements go a little too far. Maybe time to drop the computer and pick up a guitar?
Just kidding a bit, but good luck and hopefully you will turn your frustrations into amazing music down the road !
I certainly hope so. I think I have to get out of the U.S. somehow, too: the political stress has gone exponential. I can’t stand it anymore. These people are making it very hard to focus.
Mine is a complete mess, the dropouts are out of control, I’m getting crazy stutteing when using certain plugins, random crashes, midi stops reading, automation stops working, the list goes on and on. 192gb DDR5 7950x and all fast NVME drives,
PC user all my life, but just awitched to Mac M4 pro 24gb + VEP pro, 2x pc’s hosting all VSTs.
Funnily, cubase 14 pro ran smooth on my PC set up, but using brand new Mac to host just cubase 14 pro and large orchestral template, i get inconsistent intermittent behaviour. For example, today my track heights randomly changed height and also menu items would be highlighted even though my mouse was highlighting another a different option…
These random eve ts occurr when ram usage gets upto about 16gb, mac usage monitor shows no stress on the system. Indeed there is a 8gb ram headeoom and cpu usage low as only vst use on the mac is VEP pro, no other vsts
The other day i was unable to open any menus. These are just a few of the annoying things i have noticed in the past week or so.
I bought the mac to increase my work speed, but at the moment the unpredictable nature is worrying. Like i say, it worked on my PC set up.
@melph I experinced similar strange, graphic inconsistencies when I switched to an M1 Max mac . After a 3 month honeymoon period i went back to my then newly upgraded 9950x and it’s been smooth sailing ever since.
M
Thats really intereting. Looks like potential bugs cubase with m series chips.
Im going to trial Logic pro and see how that goes…i see theres probably loads of problems there too from reading forum posts!
Hopefully i can make do u til Steinberg sorts this out.
Studio one 7 is no better…horrendous performance with large templates.
@melph the other thing I’ve seen from people using new M4 series macs and Windows machines is Cubase will ‘poof’ to the desktop on MacOS from time, unlike on windows where I’ve found it very very stable.
M
It makes me snile that i changed to mac for improved work flow!!! Hopefully it gets fixed soon.