jBridgeM v0.99 released

•November 6, 2018 • Leave a Comment

Dear users:

jBridgeM has been updated to v0.99, you can get the update here:



– Fixed hangs with Studio One.

– Fixed crash with Ableton Live when duplicating tracks.

– Other minor changes.

jBridge 1.75 beta

•December 8, 2016 • 2 Comments

Dear users:

A new beta version of jBridge is available here:


This build should address the issues reported with Cubase 9. 🙂

jBridge v0.9 beta 2 now available

•October 18, 2014 • Leave a Comment

Dear users:

A new beta version of jBridgeM is available here.

This build should address the issues reported with OS X Yosemite amongst other bug fixes. 🙂

jBridge, jBridgeM and PluginFlipFlop updated

•April 25, 2014 • 2 Comments

Dear users:

jBridge, jBridgeM and PluginFlipFlop have been updated. 🙂 Please check the relevant pages for more information.


jBridgeM v0.82 released

•November 4, 2013 • Leave a Comment

Dear users: this update is recommended for all OS X versions and can be obtained here.

jBridgeM 0.82d beta:

– Safer starting/ending routines.´
– Better module loading / unloading.
– Improved stability for 32bit plugins bridging.
– Fixed a problem where in some systems where the jBridgerM tool would not create the bridging files.
– Added a new option to place the plugin’s window floating above the main host’s window.
– Added an option to force the bridged plugin’s window refresh. This is to overcome a problem observed in OS X Mavericks (10.9) with some plugins, were the GUI’s would stop being updated when the window goes into background.
– Other minor tweaks/fixes.

jBridge 1.6 beta available

•October 29, 2013 • 1 Comment

Dear users:

A new beta version of jBridge (1.6) is available here. 🙂 This one should work a bit better with Windows 8.

A workaround for the loss of play/stop triggering through PC keyboard when tweaking bridged plugins in Ableton Live

•May 1, 2013 • Leave a Comment

Unfortunately, due to limitations of the bridging process, you may lose the ability to use your PC keyboard to start/stop the sequencer in Ableton Live.

This is because PC keyboard input will be routed to the secondary process that hosts your bridged plugin when you’re tweaking its GUI,  until you click anywhere in Live’s GUI again  ( which is actually how it’s supposed to work between two different processes, but not what we want here ).

James created a Max for Live patch that allows the user to map any button on a control surface (e.g a keyboard, MIDIfighter or APC40) to the ‘start/stop’ function of Ableton Live’s transport bar.

You can get it here.

Please read the included documentation for instructions on how to use it, if you have any questions regarding its usage, please contact James ( you can find his email in the included documentation ).

A big thanks to James for this clever workaround! 😉