Saving Ram in Studio One

[Touch The Universe]

Funny thing, my task manager RAM is showing 2 gigs (of 8 gigs) used but the performance meter inside studio one is showing 90-95 Ram, depending how long I'm working on the track. Without trying to understand the reason or cause, I figured I would just work with the program as is for now.

Is there anything I can do to intelligently save ram on this project? I know in fl studio, for instance, I can remove all unused samples from the playlist option to reduce ram. I tried clearing the cache for unused samples but it saves no ram. A lot of the tracks have empty space in them, I deleted that but it doesn't help. I'm sure studio one is preserving them since I can slide past the audio part to see the empty space again.

So what to do... Is there a smart way to remove all that empty space in the audio files? Maybe convert it to a musicloop loop or must I bounce everything single track and reload If there is a more time efficient approach, I would love to hear about it, thanks

[jdnz]

are you sure youv'e got the 64-bit version of Studio One installed? It thinking it's nearly out of RAM (when you've got 6g free) would tie in with running the 32-bit version (on 64-bit windows)

[Touch The Universe]

That's right, I'm using a 32 bit version for this song, thanks for reminding me. The 64 bit version won't open all the vst, even though the 64 bit versions are installed as well. I will try to narrow it down which effects won't open, then stream the track in the 32 bit version and remove the effect and try reloading in 64 bit. Thanks, this should do it If there is another method, I'd love to learn about it while I'm at it, thanks.

[incubus]

How odd (about the x64 version not opening)

But in the 32 bit world you CANNOT squeeze more ram. That's why there is x64

Bottom line: Doze takes about 1.7gb just to run. You do not have access to the full 4 GB outside of that so maybe you have 1.5gb left? I tried jumping through those hoops years ago. No go. X64 is your only hope.

[BojanKerkez]

The 64 bit version won't open all the vst, even though the 64 bit versions are installed as well.

There are several possible reasons for that. The first one is, of course, that in "Options/Locations/VST Plug-Ins" the folder(s) of your 64-bit plugins is/are not included. And if they are, have they been scanned? Maybe "Scan at startup" checkbox is not checked? Maybe they've been blacklisted? Click on the "Reset Blacklist" button and let S1 rescan those folders again. If everything's ok with your plugins, that should solve it.
There is one more possible reason for plugins not showing, though that one probably does not apply in your case, and that is manually rearranging of plugins in S1's browser. Deleting PluginPresentation.settings file in "[YOURUSERNAME]/AppData/Roaming/PreSonus/Studio One 3" (on Windows; I don't know the location of that folder on MacOS) should reset it, though then you will have to create your favourites all over again.

[garryknight]

Maybe he/she means that it won't open 32-bit VSTs. And this is correct. You'd need to run a 32 to 64-bit bridge to use 32-bit plugins in the 64-bit Studio One as it doesn't have bridging built in.

[Touch The Universe]

I originally made the track in 32 bit studio one using 32 bit plugs (no choice since studio one can't bridge). I have 64 bit version of all my 32 bit plugs (all possible anyway). When it came time to open the project using 64bit Studio One, 95% of the plugins found there 64 bit counterpart automatically. The rest showed effect missing and a screen popped up showing which ones. The 64 bit plugins are there in the folder, which is checked in the vst location, and also work in other daws. They even work inside studio one! They show up in the vst browser and everything. It just won't load when the song starts up.

I even renamed them to see if that would work. Sometimes a .dll is "plugin"_x64.dll. I would remove the _x64 so it reads just like the 32 bit one, but no joy.

All is well now though, thanks everyone. I already finished up the song It was a simple matter of converting all the tracks, whose effect were not read in 64 bit, to audio in studio one without preserving its plugin state (or it might still show the plugin missing). Once I did that far all tracks it opened without hitch in 64 bit