Subject:JBridge

Posted by: donde

Date:11/28/2015 7:54:50 AM

Has anyone tried using JBridge? From what I've reading it allows you to use 64b VSTs with 32b DAWS, vice versa... AND 32b with 32b while maintaining a separate memory space for each VST (so no 2G limit, in theory).

Type JBridge VST into Google. - Don

Subject:RE: JBridge

Reply by: VMP

Date:11/28/2015 1:30:05 PM

Yes I have used it with AP7.

Also mention it here third post from down: http://www.sonycreativesoftware.com/forums/showmessage.asp?messageid=935420

VMP

Subject:RE: JBridge

Reply by: donde

Date:11/28/2015 6:52:26 PM

I presume that means it works. And if so... a no brainer of a purchase.
TY VMP
- Don

Subject:RE: JBridge

Reply by: Vocalpoint

Date:11/29/2015 1:12:47 PM

I presume that means it works. And if so... a no brainer of a purchase.

It seems to work as long as the plugin being used behaves...but if the plug is troublesome - this will not help.

Cannot see why you would want/need to attempt a 64bit plugin within 32bit ACID. Not sure the advantage is really there or not.

VP

Subject:RE: JBridge

Reply by: donde

Date:11/29/2015 2:30:44 PM

Cannot see why you would want/need to attempt a 64bit plugin within 32bit ACID. Not sure the advantage is really there or not.

This came up when I investigated the upgrade to KitCore. Their full boat but older upgrade "DrumCore" at v3 is 32b, but latest v4 one is 64b. I also have Sonar X2 64b.

I also have Garritan Personal Orchestra (32b). Ideally it would be nice to get the latest VSTs and play them on any DAW... keeping my options open.

- Don

Subject:RE: JBridge

Reply by: pwppch

Date:12/1/2015 8:23:54 AM

Cannot see why you would want/need to attempt a 64bit plugin within 32bit ACID. Not sure the advantage is really there or not.

For a bit-bridge like this to work - i.e. host a 64 bit plugin in a 32 bit host- J-Bridge has to run in a separate process. Since the VST/VSTi is running in a separate 64 bit process, it will have the full mem foot print of a 64 bit app available to it. The connection between ACID and it will use a share memory or some type of pipe to move the MIDI data to from it as well as the audio data.

So, if a 64 bit VST/VSTi is designed to use the memory space of a 64 bit app it will have it. ACID will just send/get buffers of MIDI/Audio data through the 32 to 64 bit bridge.

I have tried J-Bridge. Other than setup and dealing with the flakiness of some plugins, it did work. It was some time ago, so maybe it has improved its set up and support of plugins.


Peter

Subject:RE: JBridge

Reply by: tascolas

Date:12/11/2015 6:17:50 PM

I have worked with JBridge and AP 7 for a long time the previous 2-3 years or so. It works exactly as Peter described. It would be the ultimate solution for people like me who need more ram for their VSTis if only for a big downside. Somehow in AP7 the bridged plugins cannot be automated. The automation button is greyed out for all bridged plugs. Tried the same setup in Win 7 x64 and Win 8.1 x64. I exchanged some e-mails with JBridge's author who was eager but finally unable to help. Seems like automation works fine in other even older 32bit hosts like Cubase 5.
An Acid Pro x64 is badly needed. Send midi to plugins as well. Midi learn on all and drag audio to plugs from the arrange window too. A better resolution for more precise audio zooming and editing and drag to stretch audio to fit a certain length like Vegas. Smart devs learn from the competition like Ableton Live. I do remember back when Live was first released, its devs admitted to be Acid users and their goal was to make an Acid like app that functioned much like a sampler workstation instrument as well, MPC style. Their current status in the market and extensive use by all sorts of professionals only proves they hit their goal. But you know these already so cheers.