KVR Audio

braj · Post by **braj** » Mon Jul 09, 2012 5:42 am

I keep hitting walls regarding RAM in Studio One, and am wondering if I am missing anything regarding optimizing the application to get the most out of available RAM. I already asked this both in the Presonus forum and to their support staff, and was basically told to 'buy a new computer'. I am on Vista 32 bit with 4 GB RAM. I'm having issues with Kontakt and could improve Trilian's consumption too that would be great. Also SynthEdit plugins generally use a lot more RAM than other synths.

standalone · Post by **standalone** » Mon Jul 09, 2012 6:15 am

Some of the points here may apply

http://helpcenter.celemony.com/essentia ... mance.html

hibidy · Post by **hibidy** » Mon Jul 09, 2012 6:34 am

I know you don't want to hear it, but there is only ONE way around this: Is it

1) don't use stuff that takes up ram
2) freeze ram heavy tracks (wait, I don't think S1 does that....)
3) go x64 and have at least 8 GB of ram

Ok, smartassedness aside, it's 3!

I did this in Feb of 2010 and it's BLISS! No more problems. I have not run into one single ram issue since doing so

Trust me, it was a constant problem prior!

braj · Post by **braj** » Mon Jul 09, 2012 6:40 am

Yeah S1 does freeze tracks, anyhow I am just wondering if there is something about my particular system that is having issues, the particular setup, and if there are any simple things I'm missing. Hopefully I can upgrade this year, but I want to get the best possible system for my cash so am wanting to spend at least $1K, which is a chunk of change for me.

hibidy · Post by **hibidy** » Mon Jul 09, 2012 6:45 am

I don't think it's "you". When I was on vista 32 with cubase, I ran into ram issues CONSTANTLY. Many a kvr thread I started trying to get around it. Superfetch or not, vista take up somewhere around 1.2gb just to be on. Then, 32 bit systems DO NOT use all 4 GB.

There is the 3gb hack, but that isn't always stable. There isn't a way around it.

standalone · Post by **standalone** » Mon Jul 09, 2012 12:10 pm

I also bridge my sample based plugins with jBridge in order to use all the RAM avaliable. This way my host can reach more than 3.5GB RAM on my 32 bit system.

braj · Post by **braj** » Mon Jul 09, 2012 12:12 pm

standalone wrote:I also bridge my sample based plugins with jBridge in order to use all the RAM avaliable. This way my host can reach more than 3.5GB RAM on my 32 bit system.

Yeah I've been considering doing that.

standalone · Post by **standalone** » Mon Jul 09, 2012 12:17 pm

Just do it. The difference is enormous.

braj · Post by **braj** » Mon Jul 09, 2012 12:20 pm

standalone wrote:Just do it. The difference is enormous.

The think is S1 never really gsts past 1.5 GB or my RAM

I know your suggestion will solve this, but it makes me wonder what is really going on. It seems like a bug to me in its process that determines how large to make its virtual memory block. I wish I could set it manually and be done with it. Anyhow I'll look into getting jBridge soon, I'll need it anyway once I go 64 bit.

Zombie Queen · Post by **Zombie Queen** » Mon Jul 09, 2012 6:06 pm

standalone wrote:I also bridge my sample based plugins with jBridge in order to use all the RAM avaliable. This way my host can reach more than 3.5GB RAM on my 32 bit system.

How is that possible? To address RAM that system can't see?

standalone · Post by **standalone** » Tue Jul 10, 2012 8:52 am

braj wrote:
standalone wrote:Just do it. The difference is enormous.
The think is S1 never really gsts past 1.5 GB or my RAM I know your suggestion will solve this, but it makes me wonder what is really going on. It seems like a bug to me in its process that determines how large to make its virtual memory block. I wish I could set it manually and be done with it. Anyhow I'll look into getting jBridge soon, I'll need it anyway once I go 64 bit.

Zombie Queen wrote:
standalone wrote:I also bridge my sample based plugins with jBridge in order to use all the RAM avaliable. This way my host can reach more than 3.5GB RAM on my 32 bit system.
How is that possible? To address RAM that system can't see?

There is a limit of 2 GB RAM for any given process inside Windows 32 bit, and then there are limits for virtual memory too. That's why S1 can't use more than 1.5 GB. The same thing happened to me with Cubase too.

What jBridge does is to start a new process for every bridged plugin, each one with its own 2 GB RAM limit. This way, it creates a host for every plugin and then makes a bridge so they appear as plugins inside your Daw.

I can use up to 3.5 GB of my 4 GB RAM for my Daw because my computer was build for audio and it's highly optimized. Normally you could use around 3 GB on a normal computer.

Zombie Queen · Post by **Zombie Queen** » Tue Jul 10, 2012 10:30 am

You wrote "more than 3.5 GB".

standalone · Post by **standalone** » Tue Jul 10, 2012 2:11 pm

Zombie Queen wrote:You wrote "more than 3.5 GB".

To be precise, 3.56 GB

Kaboom75 · Post by **Kaboom75** » Thu Jul 12, 2012 9:06 pm

I think Vista 32bit can give 3.2GB to a DAW
Win XP was limited to 2GB per software.

Win 7 64bit Home version can use 16GB so around 14 GB spare for your Mix but if your DAW is 32bit then it is limited to 3.2GB for your DAW. Jbridge is a workaround for 32bit DAWS.

I know a few presets in Trilian use over 2GB you have no choice but to get more RAM and install Windows 7 64bit to eliminate these problems.

Jbridge will allow you to use more than 2GB in your mix.

You could record the trilian track on it's own then use the bass WAV file in the mix.

RAM tips for Studio One?