Omnisphere memory problem

[David Polich]

I'm running DP 8.01, in 32-bit mode, for a project - and having trouble with Omnisphere again. If Omnisphere is the first VI I load, no problems. However,
if I've loaded a couple of instances of, say, Kontakt, and maybe an Arturia synth or two, and then after recording their tracks as audio and removing them from the project, I'll launch Omnisphere and it won't load any patches.
I get a message saying "Error - could not load any patches. 0.0mb of memory available". The same thing sometimes happens with Trilian (though not as often), and never happens with Stylus RMX.

This has got me stumped. Does this mean DP does not empty out samples from
its memory even after the sample-based VI's have been unloaded from a project? And if so, is there a way to "flush" DP's memory?

If DP 8.01 is in 64-bit mode, no troubles of course because I have more
memory available for Omnisphere.

[doodles]

That certainly seems the the way that it is in DP 7.24. When you reach the out of memory bit, the only way to deal with it is to closer the file and reopen.

[SixStringGeek]

I'm running DP 8.01, in 32-bit mode, for a project - and having trouble with Omnisphere again. If Omnisphere is the first VI I load, no problems. However,
if I've loaded a couple of instances of, say, Kontakt, and maybe an Arturia synth or two, and then after recording their tracks as audio and removing them from the project, I'll launch Omnisphere and it won't load any patches.

And this is why I own VEP.

I had the same problem with Ivory 2.

64 bits baby. That's what I'm talkin bout. Never looking back.

[doodles]

depends how you use it.

I use VEPro on all my slaves for templates, but I do occasionally load up omnisphere into DP for a q-specific sound. That's when I run into this problem.

[ccrane]

This has got me stumped. Does this mean DP does not empty out samples from
its memory even after the sample-based VI's have been unloaded from a project? And if so, is there a way to "flush" DP's memory?

When you un-enable a VI track or remove it, it should return most of its ram to the computer. To monitor if this is happening, do you look at Activity Monitor? That is the best way to see how much "Real Mem" DP is using at anytime. Anything above 2 GB is entering unstable territory. I can usually push it to about 2.30 GB before a crash or out of memory message.