So I use Studio One v2, and so will need JBridge to use some plugins. My question is should I run the 32 bit version and bridge a few hefty plugins to get more RAM, or run in 64 bit mode and bridge all 32 bit plugins. I figure once the box arrives I'll be determining what really needs to get installed and what I should abandon. Any thoughts?

well honestly if you have ALOT of 32 bit plugins that don't have 64 bit versions, then just bridge the few sample based memory hogs 64 bit versions into the 32 bit host.

If you have only a few 32 bit plugins and most are 64 bit, bridge the 32 bit versions into the 64 bit host.

cheers

i.e the name of the game is to always bridge as least as possible. Just do the math and work it out but my advice is solid i promise and j bridge's bridging works absolutely fine either way

Math? I have to do MATH?

I agree. Unless most are x64; there isn't a reason for a host per se to be x64. It's plugins that need the memory address and to be outside the hosts process to get there.

"the name of the game is to always bridge as least as possible." I reckon that implies a bridge is less stable?

I made the error of posing VE Pro vs JBridge here and it was pointed out to me that technologically there is no difference. I never embraced 'the bridge' since I saw too many report of stablity being affected.

i mean add the plugin amounts (including how often you are likely to use them )

for example, say in ableton if i was to use that, i would use the 32 bit version on mac because 1) kontakt has an external memory server and 2) the only other sample stuff i have is toontrack which i could bridge using j bridge into 32 bit ableton and give them their own memory space

I might use 1 or two instances of a toontrack.

but even though the ONLY 32 bit plugin i care about is sylenth, i would use maybe 20 instances of it...

so it makes sense in any case to use 32 bit ableton and use native sylenth rather than bridging sylenth. This is just an example that would be accurate in my case if i wasn't transitioning 100% to reason

oh and of course i would use native 32 bit everything until i started realising my project was a heavy one and i needed memory.

cheers.

PLUS, 32 bits sound better than 64

Well basically I will be using Trilian a lot, and Kontakt Player a lot more than I have. I have Sampletank but it is very good with RAM, and I figure the whole DAW will just benefit from having 8GB instead of 4 even if if it is in 32 bit mode. Anyhow i will only have those 8 GB to start with anyhow, if the DAW can fully give 3 GB to normal plugins I'll be able to send the big ones out to grab the other available memory. I have one concern though and that is how much RAM Synthedit plugins seems to take up, it seems excessive in Studio One but I guess I could bridge the worst of those too. So I guess I should stick with 32 bit host then? Is that reasonable?

Oh also BFD ECO. But that doesn't seem too hungry anyhow. Honestly once Trilian is bridged i doubt I'll have too many RAM woes.

just to be as clear as I can, there is no benefit to the DAW itself in 32-bit mode by booting in x64 kernel. that is just about memory access in that scenario. I don't know about counting on a full three gigs plugged in; that is theoretical. I don't know your host but if I have that much in Cubase I expect problems.

I would put kontakt 4 x64 in the bridge rather than use KMS, no question. unless JBridge is hinky. my experience using VE Pro and in Cubase, has been smoother, nicer in the sandbox without KMS.

Sorry that wasn't so clear You are saying that there is no real benefit for running in 64 bit mode except for memory availability, is that right? That is why I plan to run in 32 bit, so I have less plugins in the bridge. And you are saying Cubase does not do well when it has a lot of RAM? Sorry I'm dense so please clarify


Thanks, I'll keep that in mind

at around 2GB used by the process 'Cubase', I would start to manage the project differently. I don't reckon it's just Cubase. That's a factoid you see around, that ~3GB but I wouldn't expect it to be practical. I would only have anecdotal reportage per other hosts but... I wouldn't count that chicken before it's hatched. But aside from samples-based, two gigs is a goodly amount.

the whole point of x64 is to get that memory address AFAIK. Anyway the 32-bit process is running as 32-bit, the boot kernel is irrelevant per that. there is no real benefit for running in 64 bit mode except for memory availability per the other process, 'JBridge'.

I think you have the concepts.

If you install the 64-bit version of the DAW+64-bit versions of any plug-ins available now, it will be easy to upgrade your plug-ins to 64-bit as they become available (or find alternatives).

If you lock yourself into a 32-bit DAW and use 32-bit versions of plug-ins even when 64-bit is available, it will be a much bigger project once you decide to move to 64-bit.

That is definitely worth consideration. Also I have hears the 64 bit versions of some apparent seem more cpu efficient. I dont know if that is actual or what but your point is well noted.