True true. The annoying delays I was getting when editing audio event volumes with the scroll wheel do not happen in 10.2
Also, I think we need an option to separate the volume from the fades when using the mouse scroll wheel. I keep scrolling to adjust the volume but half the time I end up adding a fade out or in, which I most definitely did not want to do.
Hahaha! I have definitely considered the works of the Adversary when trying to stop those CPU spikes. Perhaps the Lord of Hosts was allowing Satan to mess with me ala the Book of Job to see if I’d renounce Steinberg? Haha! I would not. Never. To counter the evilness, I simply have to find a previous ‘unimproved’ version that lacks the “improvements” that, to me, are hardly that.
On some systems, there is a benefit, on other systems, there is a disadvantage.
Also depends on which plugins youa re using and how many VSTi’s you have in your system; latency, etc …
Fredo
For what it’s worth, 10.3 is running seamlessly on my Mac systems-- High Sierra on this laptop, and Mojave on my 5,1 12 core at home. Significantly more reliable than the last couple of versions-- hangs leading to crashes were a problem for me, and they’ve pretty much disappeared here. Don’t know how or why, and this is purely anecdotal, but it is my experience.
Chewy
How should somebody know all this? Many, like I do, use hundreds of different plug ins over time and even the main plug ins change for different project styles (stereo production, VR production, etc.) We cannot do research to find out when, what is properly or improperly used. If this would be such a weak function I doubt Steinberg would have implemented it.
Reading the manual might be a good start.
Fredo
Ahahahhahaahhah
Best reply ever…
You succeeded in presenting your character quite nicely.
Of course, you knew what I meant, the unpredictable combination of plug ins and workflows, all not covered in any manual.
Next time, you can spare your destructive comment.
I think that depends. Have you thoroughly read the manual regarding all aspects of Asio-guard, VST3 Suspend, Multicore CPU, Power Scheme, etc?
If so I would simply say so and that it was not helpful. If not, maybe Fredo has a point? Another thought would be to ask where he learned about this subject. Maybe you could too.
I’m not trying to be offensive here, just logical.
Are you kidding me? The Nuendo manual is not the Kabbalah. I just had a look again - this is the sentence about VST3 suspend:
“Suspends VST plug-in processing in passages where no audio is passing through the plug-in. This can improve system performance noticeably.”
Maybe you have a look into the manual one day, then you would know there is nothing explained in detail between the topics you mentioned. There is nothing discussed about a correlation of ASIO-Guard with VST3 Suspend, etc.
I work with Nuendo since 20 years or something - your remark is not even entertaining. “Power Scheme” … haha, give me a break.
Come on guys, you can put one and one together, no?
Are you using a lot of vst3 plugins with low latency, yes or no?
A lot of VST2 plugins?
So only this information can give you a clue if vst3 suspend is applicable for you or not.
And best of all, just try the different settings.
Same for ASIO guard.
The description in the manual should give you enough clues if you need it or not.
ASIO-Guard
The ASIO-Guard allows you to shift as much processing as possible from the ASIO real time path to the ASIO-Guard processing path. This results in a more stable system.
The ASIO-Guard allows you to preprocess all channels as well as VST instruments that do not need to be calculated in real time. This leads to fewer dropouts, the ability to process more tracks or plug-ins, and the ability to use smaller buffer sizes.
ASIO-Guard Latency
High ASIO-Guard levels lead to an increased ASIO-Guard latency. When you adjust a volume fader, for example, you will hear the parameter changes with a slight delay. The ASIO-Guard latency, in contrast to the latency of the audio hardware, is independent from live input.
Restrictions
The ASIO-Guard cannot be used for:
Real time-dependent signals
External effects and instruments
Same thing: test and tweak to your linkings.
I have machines where activating ASIO guard gives me better performance, I have machines that suffer from it.
And to conclude:
I suggested to check if those settings were not changed during the upgrade.
The proper answer would be: Yes, or no.
On that basis we can try to identify the problem.
HTH
Fredo
I put one and one together but that still doesn’t explain all the CPU spikes that started with Nuendo 10.3, same as it started with Cubase 10.5.
Nothing in your post explains or offers a solution. And like one poster above stated so eloquently, the manual is not the Kabbalah, a book on Jewish mysticism.
Folks on OSX having problems- what interface are you using?
Folks on OSx having still producing content instead of troubleshooting- what interface are you using?
I’m using a Focusrite Red4Pre- Problems with 10.3
Ted, if spikes are the main issue to make you quit N10.3, have you tried toggling on and off the Delay Compensation button?
I do that as part of my work flow, because not only spikes get worse as the project grows,
but my CPU measurement starts getting higher too.
So what I do is turn off Delay Compensation - spikes go back to zero, then
after 5 seconds or so turn it back on. It usually calms spikes for a while.
I do that specially before exporting.
Exactly!! Worse as the project grows!!
I’ll try your suggestion. Thanks for trying to help. Sometimes I feel like John the Baptist here - a voice crying out in the wilderness. Ha.
Lol!
I know what you mean, but try not to lose your head. 
Try also a buffer of 512 and not lower, until you are done troubleshooting, or at least until
the system stabilizes a bit (no pun intended).
It’s been impossible for me to use it. I tried, but had to move back to 10.2.
Crashes nad crashes all the time. Loading plugins crashes everything. It’s been a nightmare.
Any solution yet??
PC or Mac, and which OS?
No, still in 10.2. Not nice.
I really hope your problems will be gone soon, but I would like to state that as a general rule asking a technical question on a forum, you should provide all the specifications of your system with it first, otherwise it is really hard to solve it together with you.
And as you can see, people ARE really trying to be helpfull.
So, edit your signature text and provide all the essential data you have, at least:
Thanks in advance!