I assume you are on Windows?
My guess is its a CPU core affinity issue. The main reason I went to mac this year.
It’s a very long topic. Are you bios tweakin? If not there maybe some things you could do. One is, try turning off hyperthreading.
There is a difference between v13 and 14 in the way it deals with cpu resources of the newer CPUs that have ecores.
If you dont want to wait until SB/MS finally get it right you might want to try the free Bitsum Core Parking app to turn off core parking or freemium Process Lasso app which helped me a bit. But SB has their own power setting which needs trialing together with them.
Great thanks for the tips. I’m running and AMD 7950x CPU which I believe does not have p or e cores. they’re just all flat-out. I have clocked the ram upto 6000MHz and I’m running an expo profile, expo 1 I think.
I have my suspicions it’s a memory leak problem. When I open my session it’s using about 16GB of RAM. after working for a while not steadily climbs up to about 50GB and becomes unstable.
This same session template never had this problem in N13. Same plugins etc.
I am running some VST 2 plugins which is unavoidable at the moment. Altiverb 8’s presets sound different to 7 due to different default channel formats in 8. It starts with 5.1 but 7 was using quad, lcr etc as defaults, and when I call up the legacy formats in 8 Nuendo’s VST / Asio guard meter freaks out and it won’t play at all. This means I need to stick with 7 which is VST 2. Not sire if this is relevant.
I would happily roll back to N13 but annoyingly I have done a bunch of clip based volume graph drawing which does not translate from N14 back to N13 so I’m stuck in crash land for the rest of the job.
If i need to run VST2 plugins I now use Audio gridder to host them (locally)
I’ve transitioned to JUST using VST 3 plugins and I’m sure it’s helped with stability etc on the most recent version of Cubendo 14.
Give it a try. it also gives you a huge performance boost loading heay plugins via audio gridder as they load outsied the Cubendo process so can maximise your CPU fully.
ASIO guard can hit the red with as little as 25% cpu usage on a 7950x, you have 75% wasted… AG can use that 75%
Could be a number of things causing this.
Maybe first thing is to give N14 brand new preferences (not copied from N13) so temporarily rename 13 preferences folder and then copy over what you need after.
If a project started in 13 then this could possibly add to the issue? resave with N14 (and N14 as part of project name). The thing about PC systems is the sheer amount of hardware variables!
If you have memory creeeping up over time this could be a VST plugin causing it?
try this app: and set a clean up limit:
(i’ve used in the past)
copylink>>>Reduce Memory v1.7
Terrific thanks, I’ll give it a go. It may well be a plugin.
Yes, so many variables with a PC I agree.
The behaviour is odd. The memory usage sits at about 17GB and dosn’t move but when I start skipping around in the session it starts racing up. Each time I stop and scrub a bit of audio it jumps up another GB and before I know it I’m up around 50GB, and then it crashes.
I don’t think this has been a problem before with this template I’m using and with the plugins the same as what i use in n13.
Well at least you aren’t using a whole ton of plugns:-)
That memory really is shooting up, very strange.
Are you using Kontakt that might be loading a commercial instrument in background and maybe acting strangely in N14?
Hahaha what the hell did i type there. Sorry, typing on my phone, very wonky and obviously rushed.
Yeah there are a couple of kontakts, about 18 instances of indoor, 4 or 5 altiverbs, buckets of dynamics from all sorts of vendors and a few cedar dns1’s. Also a horrendously convoluted bussing setup trying to cover all possible streamer deliverable’s in one pass. So printing to about 12 or so x 5.1 and approx 12 x stereo plus maybe 10 x 5.1 and stereo optional tracks, all coming from hundreds of source tracks.
One problem is the fact that the sound designer i have hired only cuts on protools. So when he gives me a layup with heaps of tracks full of heaps of events, you then have to deal with all the tiny fade clips which just bogs things down. I’m running this job on a Samsung T9 4TB on USB 4 which is stupidly fast so that helps a bit.
I’m gonna do a little test tomorrow and disable all 3rd party plugins and see if it still happens. I don’t believe there is 50GB of material being used in this session initially but once i print all the deliverables it’s getting up there.
One test I did was to scrub a bunch of 5.1 printed clips at random points through the program, and each time I did this, the RAM filled up by another 300 or 400 MB. It looks like N14 is loading its buffer to enable smooth scrubbing, but it looks like it hangs onto everything and doesn’t dump anything out of memory until it becomes critical. I have no idea, really; it just looks like it.
I just disabled third party plugins and N14 is hovering around 13 GB of memory usage, not skyrocketing up to 50 GB so it looks like it’s happening in plugin land.
I have just removed Nugen Vislm2 from my session and saw memory usage improve dramatically. I’m going to give YouLean Pro a shot and see if stability improves.
I gave this a go but I couldn’t seem to get dynamic automation working and it had trouble scanning some of my plugins. When things slow down a bit I’ll take a closer look at it. Thanks!!
this is handy but I’m gonna have a shot removing Niugen VisLM2 first and see if that helps. I’m a little worried about it clearing the ram whilenI’m exporting or printing and causing dropouts. I know I can turn off auto mode but I’m hoping I won’t need it at all. Thanks for suggesting it
yes, but also using it locally you can access all your CPU which makes a Huge difference in Cubendo. I have a mix test i use as a bench mark and i could load 168 more heavy plugins …across my main mix groups using AG locally to host the plugins oposed to fully native. In fact I gave up at an extra 168 plugins loaded as it proved my point and i still had CPU to spare.
compare the cubase meter on the projects.
On the Ag project each AG instance is hosting all 3 of the off line bus plugins…making 168 extra over the native test…
@KMT333
Yes I can, you have to first assign the parameters of the plugin in the Automation menu of AG. Right click on the plugin header in the AG plugin window and you’ll see ‘Automation’ , then click assign all and you’re good to go.
Curious @Norbury_Brook , I gave this a try today locally but for some reason it sees the local server but won’t connect through plugin in Nuendo. Anything special that needs to be done to run this Locally? I installed the server and plugin on the same win11 computer. Maybe its not supporting well my current system. Thanks for any help.
