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.
Vlacarus wrote: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.
