So many issues... [RESOLVED]

[nickysnd]

A short follow up: I removed Omnisphere and StylusRMX from my project (moved them to Bidule) and DP doesn't crash anymore. Just wanted to say.

I still get that "Ran out of memory" odd message though every now and then, while my memory usage is low: around 1GB of RAM, having 8 more gigs available. It's harmless though, it asks me to configure the hardware driver, I do it and then it leaves me alone for half an hour or so. Then it pops up again, and so on... Don't know what's the deal with that, anyone has any idea?

[dang47]

I can only remember a few versions that were truly frustrating for me, and even the worst of them never stopped me from making progress.


except for DP6......... which has been left for dead!!

[cowtothesky]

I have had memory problems with Omnisphere ever since I got it. I love the sounds on it, but when I'm working on a score, I will save any Omnisphere tracks as my last thing to do. Basically, I mix everything down to a stereo audio file and open up a new DP project and lay down the Omnisphere tracks using the bounced audio file. This helps a lot, but is a major pain in the ass. I wouldn't even think of opening more than 1 instance of it and even with 1 instance open, I can only get about 5 or 6 Omnisphere tracks before DP starts crashing. I really wish there was a way that I could open up the Omnisphere sounds in Kontakt or something more stable.

I keep hoping they will update Omnisphere and finally resolve this issue.

[cbergm7210]

I have had memory problems with Omnisphere ever since I got it. I love the sounds on it, but when I'm working on a score, I will save any Omnisphere tracks as my last thing to do. Basically, I mix everything down to a stereo audio file and open up a new DP project and lay down the Omnisphere tracks using the bounced audio file. This helps a lot, but is a major pain in the ass. I wouldn't even think of opening more than 1 instance of it and even with 1 instance open, I can only get about 5 or 6 Omnisphere tracks before DP starts crashing. I really wish there was a way that I could open up the Omnisphere sounds in Kontakt or something more stable.

I keep hoping they will update Omnisphere and finally resolve this issue.

Mr. Cow, how much RAM do you have? (perhaps fill in your signature with your vitals for us)

Make sure you are running the latest version of Omnisphere as it has a great memory server. If so, make sure it is running in Server mode to take advantage of this feature. Also, don't forget you can load "Light" versions of patches and then load the full ones later when you go to print the tracks.

[Shooshie]

A short follow up: I removed Omnisphere and StylusRMX from my project (moved them to Bidule) and DP doesn't crash anymore. Just wanted to say.

I still get that "Ran out of memory" odd message though every now and then, while my memory usage is low: around 1GB of RAM, having 8 more gigs available. It's harmless though, it asks me to configure the hardware driver, I do it and then it leaves me alone for half an hour or so. Then it pops up again, and so on... Don't know what's the deal with that, anyone has any idea?

That hardware driver dialog thing is very strange. I don't like the sound of that.

As for moving those plugins to Bidule, what format are the running under in Bidule? AU? VST? ?? It could be an AU wrapper problem if they are running in another format in Bidule.

[cowtothesky]

I have had memory problems with Omnisphere ever since I got it. I love the sounds on it, but when I'm working on a score, I will save any Omnisphere tracks as my last thing to do. Basically, I mix everything down to a stereo audio file and open up a new DP project and lay down the Omnisphere tracks using the bounced audio file. This helps a lot, but is a major pain in the ass. I wouldn't even think of opening more than 1 instance of it and even with 1 instance open, I can only get about 5 or 6 Omnisphere tracks before DP starts crashing. I really wish there was a way that I could open up the Omnisphere sounds in Kontakt or something more stable.

I keep hoping they will update Omnisphere and finally resolve this issue.

Mr. Cow, how much RAM do you have? (perhaps fill in your signature with your vitals for us)

Make sure you are running the latest version of Omnisphere as it has a great memory server. If so, make sure it is running in Server mode to take advantage of this feature. Also, don't forget you can load "Light" versions of patches and then load the full ones later when you go to print the tracks.

I have updated my info. Been meaning to do that - thanks for the reminder! - I have the latest Omnisphere update and still have major problems as mentioned above. I have talked to a Spectrasonics representative and made the suggested changes and I still have problems with it. I have just learned to live with it and I just don't load up Omnisphere on projects. If I really want to use Omnisphere, I do what I said and mix the original track down and open up a new project only loading Omnisphere to play with the stereo track of the mix.

I wish I could fix this. I would really like to use Omnisphere on a regular basis. I am thinking about adding another 8G ram, but I don't think that is my problem here as no other programs give me problems. Thanks

[GlennO]

fyi, if you're running Omnisphere in server mode, it is only using about 10% of your available memory (unfortunately, DP does not yet support 64 bit addressing which would eliminate this problem entirely). So, if you're running out of memory, that means you were using almost all of your available memory before you loaded Omnisphere. In that case you'll have to look elsewhere to solve your problem by finding ways to reduce your overall use of memory. For example, your other plugins might have a sample file server like Omnisphere does, that you can use to reduce their memory usage. Or, offload your memory intensive plugins to another host like Bidule.

Glenn Olander
Spectrasonics

[cowtothesky]

Thanks Glenn. I must say that you have done a great job answering any Spectrasonic related problems here at Motunation. Thanks so much. I am really impressed with all of the Spectrasonic products and I have no doubt that a 64 bit version of DP would eliminate many of these problems.

The one thing I don't understand is how quickly I run out of memory with Omnisphere. Literally, I can load up 100 pretty intense sounds using Kontakt and have no issue with memory. Then, on another project, I may have only 2 instances of kontakt with 20 sounds and load up Omnisphere and after about the 4th or 5th Omnisphere track, I'm getting memory issues and crashes. Using the preview mode helps a little, but not as much as I thought it would. I am not getting this problem with other engines, such as VSL, addictive drums, or soft synths.

Since I have a few weeks until my next project, I will give it another go and look at my settings closer and see what I can do. I am amazed by some of the Omnisphere sounds and would love to get Trillian, but will wait until I fix this memory problem. One a side note, I wish I could load up Omnisphere in stand-alone mode. Any chance of that happening in the future?

[GlennO]

Using the preview mode helps a little, but not as much as I thought it would.

It sounds like there may be a misunderstanding here. Preview mode doesn't reduce memory usage.

The sampled soundsources in Omnisphere and Trilian are unapologetically rich and detailed. But, that doesn't mean you necessarily have to consume all the available memory in your DP process to use them. See the "memory issues" FAQ at support.spectrasonics.net for techniques available to mitigate this problem. I especially recommend the video tutorial mentioned there. And, if all else fails, you can always offload memory intensive plugins to another host like VEPro.

Glenn Olander
Spectrasonics

P.S. With so many lightweight hosts available (AULab, VSTLord, Bidule, RAX, etc.) that effectively turn any virtual instrument into a standalone instrument, there isn't much need these days to offer a standalone version of a virtual instrument.

[cowtothesky]

Using the preview mode helps a little, but not as much as I thought it would.

It sounds like there may be a misunderstanding here. Preview mode doesn't reduce memory usage.

The sampled soundsources in Omnisphere and Trilian are unapologetically rich and detailed. But, that doesn't mean you necessarily have to consume all the available memory in your DP process to use them. See the "memory issues" FAQ at support.spectrasonics.net for techniques available to mitigate this problem. I especially recommend the video tutorial mentioned there. And, if all else fails, you can always offload memory intensive plugins to another host like VEPro.

Glenn Olander
Spectrasonics

P.S. With so many lightweight hosts available (AULab, VSTLord, Bidule, RAX, etc.) that effectively turn any virtual instrument into a standalone instrument, there isn't much need these days to offer a standalone version of a virtual instrument.

Thanks Glenn. I'll take another look at that. Months ago, I was trying to sort it out and tried some of the memory recommendations, but maybe I missed something there. I'll look at it again. I haven't taken the bidule plunge yet, although I have looked into it. I understand where you are coming from on the standalone. Thanks again.

[cbergm7210]

Mr. Cow, if you had the means to make a short movie of what is going on with your system in reference to this problem, that could be another clarifying tool with this issue.