The project plays through without a hitch and is using up 2.029 GB after some intervention it’s up to 2.15 GB and still stable. I did get the memory warning from Nuendo, but I disregarded it again and it didn’t crash or break the load in. I just patched the N5-32 executable with the 4GB utility and I was able to load the exact same 64-bit project in N5-32 without issues.
I tried loading a project worked under N5-64 in N5-32 last week, and it basically exploded: a memory limit warning from Nuendo was unheeded and serveral C++ runtime crash popups ensued. I found a simple utility that patches a 32-bit executable to allow it to use up to 4 GB of memory space under W7-64.Why is this happening? And more importantly: is it normal? I looked at this while working and the memory footprint actually goes up AND down. Nuendo 64-bit (N5-64) also seems to increment it’s memory use, but it’s a lot slower in comparison. By looking at the Task Manager I’ve noticed that Nuendo 32-bit (N5-32) keeps eating away at memory at a rate of about 256k every 8-10 seconds regardless of whether a project is loaded or not.
#4gb mem patch Pc#
This regards Nuendo 5.2.2 PC 32-bit under Windows 7 64-bit. These came up in another thread and I thought they deserved a closer look in their own.
0 kommentar(er)
