jBridgeM – troubleshooting

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

Last updated: 28/04/15

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?

Please check here. This mode has some limitations, but should improve your workflow a bit.🙂

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 ).

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 ).

10 – I am using OS X Mavericks ( 10.9 ) and I am having some poblems ( ie, my bridged plugins GUI is not being updated ).

Please check this section.

11 – The bridged plugin crashes when I try to load it inside Metaplugin or PatchWork:

Load the bridged plugin in a standalone VST host, and disable the “run in existing auxhost” option.

Alternatively, you can manually edit its bridging settings file in /Users/<your user>/Library/Application Support/jBridgeM/SettingsFiles and change the line

RUN_IN_EXISTING_AUXHOST 1

to

RUN_IN_EXISTING_AUXHOST 0

Also, make sure you’re using jBridgeM 0.93 or above.


One Response to “jBridgeM – troubleshooting”

  1. hi m8 thanks for all your work on this program it fucking saved my life!!! it works perfectly with Cubase 6.5 x64 on OSX 10.8! Specially the new gui follow thing works perfectly…thx wendel

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: