jBridgeM - troubleshooting

Note: This troubleshooting section is for jBridgeM ( Mac OS X ) , if you’re using jBridge ( for Windows ), please click here.

Last updated: 14/04/12

1 – How do I use jBridgeM?

After the installation, run the jBridgerM tool, to prepare bridging files for your plugins, for a usage example, click here.

2 – What do the options do?

-Auto-close GUI: Closes the plugin’s window when you close the jBridgeM’s window

-Performance mode: Audio buffers will be processed asynchronously, can improve performance with some plugin/host combinations

-Run in existing auxhost: Disable this option for plugins that you want to run in their own auxhost ( by default, all the plugins run in the same auxhost, may be worth disabling this option for a 32bit plugin that uses a considerable amount of RAM ).

-Sluggish GUI hack: Enable this if your bridged plugin causes audio stutter when operating its GUI.

-Use thread safety measures in auxhost: Try enabling this option if you’re experiencing random crashes when running your bridged plugin.

-Bridged plugin’s GUI always on top: Creates the plugin’s window as always-on-top ( Will require that you close and re-open the plugin’s window for this change to take effect ).

-Dirty close: Bypasses some de-allocation routines, enable if you’re experiencing crashes when removing/unloading the plugin.

3 – How do I completely remove jBridgeM?

Open a terminal ( go to Spotlight, enter “Terminal” ) , then copy/paste and execute the following command:

sudo /Applications/jBridgeM/config uninstall

Reboot your machine in the end and it’s done. 

4 – Is it possible to have the plugin’s window in the VST host’s window?

At this stage, I still don’t know if this is possible, sorry. :-/ So far I still haven’t found a way of achieving this, but I’ll keep trying ( but please expect it to remain this way ).

5 -  Why do I lose the keyboard shortcuts in my VST host?

- This is ( unfortunately ) a limitation of this implementation, your bridged plugin will be running in a different application,
which will get focus everytime you do any operation in the plugin’s interface.

6 -  I don’t like the icon in the dock, can I run this without it?

- Some plugins will only accept mouse/keyboard input if they’re running in an application that has a dock icon, it seems. :-/ This is the best compromise possible currently, although I am still checking if it’s viable to make this optional or not.

7 – My plugin crashes when I unload it.

- Try enabling the “Dirty close” option, while in some cases it may not prevent the crash completely, it should not compromise any of your work, at least.

8 – I am experiencing abnormally high CPU usage.

- Try enabling the “performance mode” option.

9 – My plugin doesn’t work at all or crashes all the time when bridged.

Please make sure that you can run the plugin natively in your system ( without jBridgeM ), and that it runs without any problem that way. If yes, then it’s probably an issue with jBridgeM, please contact me with a detailed description of the problem ( please refer the plugin, the VST host you’re using, how does the crash happens, and your OS X version ).