@ Alexis & bluzkat :
bluzkat wrote:May I ask why you are running 32 bit Cubase with 16 GB of RAM and using Jbridge, instead of running 64 bit Cubase and eliminate the bridge?
Sure, the answer is easy : it works much better in my scenario.
I only use a handful of sample-based memory hogs, mostly Superior and Kontakt, everything else is small fry, FX anyway.
Those two are perfectly trouble free in jBridge, and each jBridged instance can use 4GB independently from Cubase's own approx. 4GB, multiple instances of the same jB VSTi are possible.
On the other hand I rely a lot on 32bit only (yet) plugins like the excellent Variety of Sound series, some others are notorious for having issues with 64bits, and we all know and love Cubase's built-in bridge ...
So in the end it comes down to using two known good bridged plugs vs a multitude of potential bridged troublemakers, believe it or not, I've been running virtually crash free for years this way.
And I don't see me switching to full 64bits anytime soon, nothing to gain atm, though it certainly is the future.
Likewise, I still use VST2 rather than VST3 versions wherever possible since I need a tidy, sorted plugin menu.
I don't think in terms of legal company names, most companies don't, either - or why would most of them "own" several folders - much like the revolutionary groups in "Life of Brian" ...
Whoever invented that forced "intelligent" VST3 auto-sorting shall rot in deepest hell.
To get back on topic, Jamstix has got fantastic memory management - it sure is not a likely candidate for bridging.