KVR :: Hosts (Sequencers, DAWs, Audio Editors, etc.) » Studio One RAM usage and Synthedit [View Original Topic]
There are 6 posts in this topic.
braj - Thu May 10, 2012 5:51 pm
I'm on 32 bit Vista with 4 GB RAM, and I quickly run out of RAM running just a handful of Synthedit plugins in Studio One v2. I can run twice as many and more in Reaper and it still reports plenty of memory available for use. I understand that the reporting mechanisms are different but Studio One will start giving memory errors at a certain point and so it is not just a difference in the meters, but actual performance issue. I am wondering if there is a way to optimize Studio One's RAM usage in any sort of way.
LeVzi - Thu May 10, 2012 6:19 pm
Any repeat offenders in the plug-ins you use ? One of them not bugging out , memory leak ?
braj - Thu May 10, 2012 6:27 pm
LeVzi wrote:
Any repeat offenders in the plug-ins you use ? One of them not bugging out , memory leak ?
no it is a general thing with SE plugs and S1 it seems. It can be any of them they just chew up RAM and S1 doesn't really make use of all the free memory on the machine, 4 gigs Ram and it may only use 1 and the say it is out of memory. I actually think it may be a bigger issue with their vm memory system or maybe even something wrong with my system's ram. Anyhow I tried Reaper and the difference is significant. But I'm used to Studio One otherwise and so Reaper was a little hard to bear 
rough around the edges but still way more powerful in many ways. Anyhow it is not a deal breaker for S1 just an annoyance. I hope S1 starts to mature a bit more quickly. I did send in a support ticket. I found a memory leak in the rewire service as well so possibly there is some collateral issue and if they are working on that memory leak maybe this one can be addressed in the same update. braj - Fri May 11, 2012 1:21 pm
Well Presonus is looking into it, looking at my System information .nfo file, and hopefully they will have some resolution. I wish I could run vsts as separate processes like in Reaper. Anyhow freeze is my friend and Studio One's implementation is easy to bear.
rasmusklump - Sat May 12, 2012 12:18 am
Buy Jbridge.
I have bought it to use 32 bit plugins in a 32 bit host. The run as separate process. Befor, Nuendo would not work when it used more than 1,2 gb. Now I have bridged Kontakt and Superior Drummer and Nuendo does not go over 800 mb.
braj - Sat May 12, 2012 1:53 am
rasmusklump wrote:
Buy Jbridge.
I have bought it to use 32 bit plugins in a 32 bit host. The run as separate process. Befor, Nuendo would not work when it used more than 1,2 gb. Now I have bridged Kontakt and Superior Drummer and Nuendo does not go over 800 mb.
I have bought it to use 32 bit plugins in a 32 bit host. The run as separate process. Befor, Nuendo would not work when it used more than 1,2 gb. Now I have bridged Kontakt and Superior Drummer and Nuendo does not go over 800 mb.
Hey now that's a good idea, I'll need it also once I switch to 64 bit anyhow. CAn anyone say how well it works in Studio One?
There are 6 posts in this topic.