OK, after working with N10.2 for two days I’m finding Nuendo is now a real memory hog, at least I think so as my Kernel_task uses up all remainder RAM available causing my video playback to stutter.
Running a large TV movie session with multiple videos on the video track takes about 15 to 20 minutes to hit the bottleneck. Closed that session and then opened a small session with no video track does not seem to release any RAM till I quite Nuendo.
This difference in performance was instantly noticeable after the upgrade.
Unfortunately, I no longer have 10.1 installers to roll back to.
Does anyone know where to find the older version of Nuendo?
If you guys are using Nuendo’s “Fullscreen” default video player, I would suggest you get a separate dedicated video playback card to do it, such as Blackmagic Design’s Decklink Mini Monitor. This will help offload all resources of video playback to the card itself, rather than your CPU or RAM.
Leave your computer’s resources all dedicated to audio.
Thanks for the note GNP, I am using a Blackmagic card, I have noticed some improvement by changing my Video files from Apple ProRess 422 Proxy to Avid DNxHD. still no explanation of why the change in the amount of RAM being used. but the Avid DNxHD files don’t stutter even when the RAM is maxed out.
It seems that Nuendo 10 is not releasing memory resources properly. I noticed, even with 10.1, if I run Nuendo on my Windows 7 PC, and then close out Nuendo completely (even remove the dongle from the USB port), I still find multiple instances of Nuendo showing up in Windows Task Manager and the memory it is still “holding”. I rebooted, ran Nuendo 10.2 for about 45 minutes, closed Nuendo and checked. I had 4 instances of Nuendo 10.exe showing up using 200,000 K to 400,000 K each. The only way to release that is to reboot the machine or take a chance and use the “End Process” function.
I must note today that Nuendo (on the same session) seems to be less of a memory hog, I’m wondering if the update of N10.2 re-scans all the databases in the background maybe explaining the excess memory use.
I wonder if it’d be detrimental to anything to just create a batch script that shuts down those processes (?). It’d be easy enough to write something like that and leave it on the desktop… double-click and done… at least it’d maybe save a complete reboot.
Hi,
I have a memory leak bug, a serious one.
I’m on mac mini, the latest i7 with Mojave.
I need to compose music on a mp4 video. I started to work in “repeat” mode but after each repeat the RAM weight increased. (I saw it afterwards in the Activity Monitor)
After some repeats I had the message that I’m running out of memory (I have 32 Go), but ok, let’s restart and retry! When I killed Nuendo I recovered the RAM.
What is strange is that my hard drive was filled with something in the same time. My HD is full and I don’t know where are the files.
So I’m pretty much stucked with my production machine and the HD filled 100% with some cache RAM files…
Any Idea where I could find this crap and delete it manually???
Thanks so much for your help guys, I’m slaughtered…
Some of this sounds an awful lot like a problem I had before.After a while Nuendo froze before being able to fully shut down, and eventually even opening up a project could take a lot of tries and restarts.
First of all I’ve noticed that Steinberg - full stop - is extremely sensitive to drivers to function well. A wee program called Driver Easy swiftly and nicely took care of that problem.
Secondly, and this has haunted me for quite some time, every single issue I had with these things disappeared completely after I back-tracker the logs after an especially frustrating boot, and tried to disable the VST2’s that was loading when the damn thing froze up during initiation. Long story short - I now have a lot of VST2-plugins I will never ever use again, and my system is now rock solid. For some reason though I’ve never had to disable VST3’s, not counting Brainworx before its major update, that simply killed the channels altogether instead, and a few weird small things I’ve got from sales from what turned out to be pretty terrible developers anyway, but none of these things ever prevented a boot up or proper shut down, they only became issues when trying to open the channel for some good ol’ editing .
Most of the fritzy VST2 plugins were either free or pretty cheap ones, but some years ago huge culprits were lots of different Waves, everything Brainworx/Plugin Alliance, and AudioEase Altiverb. Waves got its poop together (at least technically) like 10 years ago by now, but both Brainworx and Altiverb sorted out their issues pretty recently, with Altiverb 7 being their first release that has run flawlessly on my systems. Or more or less flawlessly; if I resurrect an old project with Altiverb 5 or 6 I better make sure my current version is not in its intended folder when I try to remove the old instances or it will kill my session like a rat-back in a rat-trap… But in itself, it’s rock solid.
Unfortunately, my recent experience recording and editing midi for a few hours that the graphic rendering of the midi notes both in the docked and non-docked midi event editor window are failing to draw notes as I resized, or undid something that resized or moved the note.
When something like that works when first launching the software and slowly degrades over time points to something like a memory leak or an overlooked release or cleanup of resources. I hope it’s found and fixed. (latest software, latest directx, latest gpu drivers… - which usually is the culprit here) - posted this on it’s own thread but may be related.
I didn’t read through the whole thread, but maybe you are missing something important.
And it might explain some of the issues reported.
When the user loads a plugin within Nuendo, the plugin calls it’s memory through Nuendo => OS.
When the plugin is unloaded or when less memory is needed, the plugin needs to ask the OS to release the used memory.
Nuendo can’t “order” the OS to release memory that is claimed by a plugin.
Even when you remove the plugin from Nuendo, it is still the plugin that needs to tell the OS to release the used memory.
Not saying that this is the case here, and I am not 100% sure that I have the details correct in the above.
But I know this was a hughe problem some time ago.
Ah, although I’ve got no real experience in programming things like this (years of Commodore 64 and Mac Plus doesn’t really translate into modern stuff) I was actually convinced this was the case as all my problems disappeared with a bunch of poorly coded plugins.
Cheers for the heads up, nice to have it in black and white!
Wonder though, I’ve never had problems like this with VST3, is it a more…um…“self contained” architecture, or have I just had a downright inhuman luck so far? Was the whole issue just a DLL-thingy maybe?
Regarding the problem with some plugins crash/kill Nuendo (and Cubase), especially PluginAlliance and some others (in my case also softube and McDSP), i found this rather weird workaround at gearslutz:
It’s said that opening an instance of Soundtoys Microshift plugin in the control room and set it to bypass should fix the problem.
