DP6 , Omnisphere , Trilian memory problem

[Aramis]

Hello !
I have installed recently Spectrasonics Trilian on my Mac Pro and DP 6.02 which I use with BPM , Ethno and Omnisphere .
Doing this , I am having memory limit messages and DP crashes .
Has anyone found a solution for this !!!!
I tought all of those were using hard disq streaming .


Aramis

[dpdan]

Hi Aramis, I installed Trilian just the other day and I too get a bunch of memory errors.
Silly,
Dan

[Aramis]

Ok , I will try on Spectrasonic Forum

Maybe they will have to solve this on a new version


Aramis

Hi Aramis, I installed Trilian just the other day and I too get a bunch of memory errors.
Silly,
Dan

[Tim]

Same here dammit.

[Aramis]

I have sent an email to Spectrasonics !!!!

I am on hold

[

quote="dpdan"]Hi Aramis, I installed Trilian just the other day and I too get a bunch of memory errors.
Silly,
Dan[/quote]

[cloudsplitter]

I stream omnisphere from a separate hard drive and don't have any probs. the new omnisphere update has streamlined sounds that are less cpu intensive..I would suggest downloading that and see if it helps

[Aramis]

Hello !
I am up to date with all of those plugs ! And I do stream from a Raid system !

I stream omnisphere from a separate hard drive and don't have any probs. the new omnisphere update has streamlined sounds that are less cpu intensive..I would suggest downloading that and see if it helps

[Vlacarus]

aramis, i am having the same issue but with Omnisphere alone.
no matter what i set the memory settings at, i still get errors.

I've heard it has something to do with Omnisphere not releasing the memory after loading different sounds, and or moving from chunk to chunk.

[Aramis]

Here is what I have received from Spectrasonic
Hi Aramis,

If you are running out of Virtual Memory in Omnisphere or Trilian, the first thing you should do is use turn on Lite Version in the Patch Browser.

Here are some suggestions for keeping track of your virtual memory usage:

1) Reduce the memory used by the host. Most hosts have some kind of setting for determining how much memory to allocate per track.

2) Reduce the memory used by other plugins. Specific actions here can include either reducing the number of plugins or reducing the amount of memory used by each plugin. For example, any streaming instruments will probably have settings related to the amount of memory dedicated to streaming.

3) Increase the amount of memory available to the process. If using windows you can do this with the /3GB switch or by using a 64 bit version of cubase or sonar or bidule (there may be others that offer 64 bit support).

4) If you are using windows, set the paging file to let windows manage it.

5) In Omnisphere or Trilian, consult the streaming settings FAQ and try reducing the pre-load memory size. And, of course, make sure you have streaming turned on! RMX doesn't have streaming, however it's important to note it does require a certain amount of Virtual memory.

If you are sure that you are getting "out of memory" errors when you are not out of memory, please provide the following information. This is on XP, but you can do the same thing with the Activity Monitor utiliity on the Mac: Locate the Virtual Memory column for the host process. See the Activity Monitor below for an example which shows 722MB for Logic. Also note it's slightly different on Vista:

Bring up the task manager, use the view menu to display VM size (Commit Size on Vista), select the Processes tab, make sure the host is displayed in the list, and capture the screen immediately before and immediately after loading Trilian/Omnisphere/ RMX. See the example below. In addition, send me the project file and the screenshots so I can see what plugins you are using.

In the following example, you can see Live is using about 120MB at startup. It will grow to a maximum of about 1500MB as you add plugins before it will run out of memory. That maximum number can vary from host to host. Sometimes you can get to nearly 2000MB. On cubase, the max is sometimes as low as 1300MB. Omnisphere or Trilian uses about 300MB for the first instance before you start loading soundsources, So, if that number is over 1000MB before adding Trilian, Omnisphere or RMX, you may encounter "out of memory" errors when loading soundsources or blank load-ups. Using the 3GB switch, you can expect that maximum to increase by about 1000MB, so it's quite effective. On the mac, the max is typically around 2500MB, so the problem on the mac occurs less often than on windows.

Stylus RMX uses a similar amount of memory, but less than what Trilian or Omnisphere will use. Multiple RMX's, if not managed correctly can quickly sap your available virtual memory. Especially when using powerful EFX and other features in RMX.

aramis, i am having the same issue but with Omnisphere alone.
no matter what i set the memory settings at, i still get errors.

I've heard it has something to do with Omnisphere not releasing the memory after loading different sounds, and or moving from chunk to chunk.

[doodles]

are you guys using quite a few chunks in your sequence? and is omnisphere/trilian in each chunk, or as a V-rack. Don't forget that each VI in each chunk whether the chunk is active or not) still gets loaded into DP. As these 2 guys are memory hogs, that might be it?

Just a thought

[Vlacarus]

are you guys using quite a few chunks in your sequence? and is omnisphere/trilian in each chunk, or as a V-rack. Don't forget that each VI in each chunk whether the chunk is active or not) still gets loaded into DP. As these 2 guys are memory hogs, that might be it?

Just a thought

this is my issue, in my sequence i have around 15 chunks, and each one has an instance of Omni in it.( not fully decked out though)

regardless, this has become increasingly frustrating. I am sure all of us here have some form of high end system . To still have memory and resource issues, is aggravating to say the least. My entire system runs perfectly fine running DP, Bidule and hosting some VIs in DP and/or bidule....UNTIL i bring in Omni. I am not going to sacrifice my other VI stream/memory settings in order to get this thing to run smoothe.
As great as spectrasonic's instruments are...they need to fix this. Especially the ability for Omni to RELEASE memory when it's not even being used in a chunk.

and when the heck is motu going to stop releasing small updates/new versions, and spend some quality time rewriting DP to work in 64bit.

ok, sorry for the early morning rant =).
time to get back on the battlefield with Omni and write some music today.

kevin r.

[doodles]

are you guys using quite a few chunks in your sequence? and is omnisphere/trilian in each chunk, or as a V-rack. Don't forget that each VI in each chunk whether the chunk is active or not) still gets loaded into DP. As these 2 guys are memory hogs, that might be it?

Just a thought

this is my issue, in my sequence i have around 15 chunks, and each one has an instance of Omni in it.( not fully decked out though)

regardless, this has become increasingly frustrating. I am sure all of us here have some form of high end system . To still have memory and resource issues, is aggravating to say the least. My entire system runs perfectly fine running DP, Bidule and hosting some VIs in DP and/or bidule....UNTIL i bring in Omni. I am not going to sacrifice my other VI stream/memory settings in order to get this thing to run smoothe.
As great as spectrasonic's instruments are...they need to fix this. Especially the ability for Omni to RELEASE memory when it's not even being used in a chunk.


kevin r.

hey dude

you might want to check out this thread
http://www.motunation.com/forum/viewtop ... 96#p229496

This is the reason why I don't work with chunks - it's not just a spectrasonics thing, it's the way DP works with VI's. I'm on DP 5.13, so I don't know whether it's been changed in the latest versions or not.

[David Polich]

The posts in this thread reminded me that some companies will
always tend to write the most CPU and RAM-hungry VI's they
can get away with. Obviously, the Spectrasonics products, awesome
as they are, are memory hogs that you use at your own risk, so
to speak.

It isn't affordable to everyone, but the best solution I've found
is to run VI's on a separate machine, preferably a Windows PC,
and access that machine via simple MIDI connections. I've done this
for years and even if I get a new MacPro Quad or 8-core in the
next year, I'll continue to do so.

You can pick up a used Intel Core 2 Duo PC relatively cheap these
days, and if you want a new one, any of the dedicated "Music PC's"
available from Sweetwater or through other sources will be just fine
for running VI's.

If I hadn't been running VI's on a separate PC, my G5 would have gone
in the garbage bin four years ago. It basically just runs audio, so
I've been able to keep using it for much longer than I could have if I
depended on it for everything.

[David Polich]

I might further add, if a second computer isn't an option, there's always the old tried-and-true solutions to the Spectrasonics memory hogging issue -

Record a stereo mix of everything except the Spectrasonics VI's you want to use. Then, with the exception of the mixdown track and the VI's you want to play around with, take the multiple tracks and put them offline.

When you are happy with the patch you call up, freeze that VI track.

Or print the output of the VI track to audio and remove the instance of the VI.

[Aramis]

Hey David ,
I have been using Omnispere since longtime with no issues at all .
And , only recently after adding Trilian , I have started to get problems .
So , I am not looking for workarounds for now . It has to work .
I really think something is wrong .

This week-end , I will verify a couple of things and I will follow up with Spectrasonics support .

Aramis

I might further add, if a second computer isn't an option, there's always the old tried-and-true solutions to the Spectrasonics memory hogging issue -

Record a stereo mix of everything except the Spectrasonics VI's you want to use. Then, with the exception of the mixdown track and the VI's you want to play around with, take the multiple tracks and put them offline.

When you are happy with the patch you call up, freeze that VI track.

Or print the output of the VI track to audio and remove the instance of the VI.