How to use JBridge

If you are new here check this forum first, your question may have been answered.
Post Reply New Topic
RELATED
PRODUCTS

Post

Me problem is that I have windows 7 32bit and I'm using Ableton Live 9.0.3. And when I work on my projects it give me error "OUT OF MEMORY". I saw that I can't use more that 4GB in 32bit version. But somebody told me to use JBridge to risolve problem. Can anyone tell me how I can solve the problem?
KamaStep

Post

KamaStep wrote:Me problem is that I have windows 7 32bit and I'm using Ableton Live 9.0.3. And when I work on my projects it give me error "OUT OF MEMORY". I saw that I can't use more that 4GB in 32bit version. But somebody told me to use JBridge to risolve problem. Can anyone tell me how I can solve the problem?
Im not sure Jbridge will, it depends where you're out of memory. If its Ableton itself that is using it all Jbridge can't help. The most Ableton's process can see of your system RAM is 2Gb (or 3Gb depending on how its programmed. I cant remember for Ableton)

ANy plugins you run directly inside Ableton will also be using part of that 2gb/3Gb, but if you use Jbridge to wrap plugins (ie specifically those using a lot of RAM) you can set it to spawn each one in its own separate process, and each will be able to access up to 2Gb entirely for itself.
To do this all you need to do is point jbridge at a folder full of plugins, and tell it to make bridged versions in a different folder, then change a configuration setting for the plugins you want to run in their own process.

However your 32bit operating system will only see a maximum of about 3.25-3.5Gb of RAM altogether no matter how much you have fitted. jBridge wont help with that part of it; if its really a significant issue consider moving to a 64-bit version of Windows, and fitting more RAM. If you did that you could still run the 32bit version of Ableton and its plugins, and jbridge more processes into the extra RAM, or run the 32-bit version of Ableton and jbridge the 64-bit versions of the most RAM-hungry plugins, or run the 32-bit version of Ableton, use 64-bit versions of all the plugins you have which support it, and jbridge any legacy plugins which dont have 64-bit versions.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

Jbridge will work around your Live 32bit limits if your OS is 64bit you are using third party plugins and you have atleast 6Gb RAM.

Jbridge will run each plugin in ableton Live with its own process in Windows so Live will show as 200Mb in use and a sampled plugin will be in the list in task manager separate showing 1GB and so on so Live will remain around 200Mb in use as you add more third party plugins. This will stop Ableton Live 32bit crashing every time it reaches 3.2GB RAM use. I was using this trick before Live 8 64bit came out.

Get the Jbridge demo and make a new folder called Jbridged plugins.

Tell Jbridge where your 32bit plugins are and then tell it you want the jbridged versions in that folder you just made.

Get your DAW to scan that folder.

Only use the plugins from that Jbridged folder.

It's far less hassle if you install Windows 7 or 8 64bit and install Live 9 64bit. You are going to have to install Windows 7 or 8 64bit anyway to make this Jbridge trick work.
Last edited by Kaboom75 on Tue Aug 27, 2013 2:44 pm, edited 2 times in total.

Post

Kaboom75 wrote:Jbridge will work around your Live 32bit limits if your OS is 64bit and you have atleast 6Gb RAM.
why do you think you need at least 6Gb of RAM?
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

He's already using up 3.2 GB of RAM before his project finishes loading for live only then Windows + drivers is taking up another 1.5GB. If he goes over his RAM the project will slow right down by using space on the hard drive as RAM. So 4GB is not enough and the next upgrade has to be 6 or 8 GB RAM.

Post

Kaboom75 wrote:He's already using up 3.2 GB of RAM before his project finishes loading for live only then Windows + drivers is taking up another 1.5GB.
He's using a 32bit OS. Hance at most, he's already using 3.2Gb or so including Live and Windows and drivers.
So 4GB is not enough
Actually 4Gb might be sufficient, especially if plugins run in their own processes. We just dont know.
and the next upgrade has to be 6 or 8 GB RAM.
Strictly speaking the next upgrade could be 5Gb. 2x2Gb + 2x512Mb
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

He's got 8 Gb according to his other post.
http://www.kvraudio.com/forum/viewtopic ... 12#5467212

He just needs to upgrade the OS to 64bit so the OS can see more than 3.2 GB

Post

Kaboom75 wrote:He's got 8 Gb according to his other post.
http://www.kvraudio.com/forum/viewtopic ... 12#5467212

He just needs to upgrade the OS to 64bit so the OS can see more than 3.2 GB
Indeed. Its pretty self-defeating running a 32-bit OS if you have that much memory fitted. The OP could have mentioned it in this thread, though. :|
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post Reply

Return to “Getting Started (AKA What is the best...?)”