- jBridge 1.2 -
Note: jBridge supports Windows-compatible VST plugins only ( up to the 2.4 spec ). This program allows you to "bridge" a 32-bit vst plugin to a 64-bit vst host, a 64-bit vst plugin to a 32-bit vst host , or even to a 32-bit vst host (allowing you to overcome the memory limitations of a single x86 process, in this last case).
System requirements: - Lots of RAM and a powerful CPU, with lots of cores. - Windows XP / Vista / 7
How to use (getting started): Please note: If you're using the latest version of Cantabile 2.x, VSTHost or Sonar 8.5.x, they provide built in support for jBridge.
If you’re using SONAR 8.5.x: - Go to Tools->Cakewalk Plugin-in Manager, scan your plugins normally. Then, select the VST plugin you wish to use with jBridge, and in the Vst Configuration part click on “Plugin-in Properties” . Enable the option “Load using jBridge wrapper”.
If you’re using Cantabile 2.x or VSTHost: - No additional configuration is needed after jBridge’s installation, they will use it automatically.
For all the other hosts, you'll need to use the jBridger utility: - jBridger is an included utility that will automatically prepare the needed files for bridging your plugins. You can launch the utility from the Start menu, under jBridge's program folder. Follow the on-screen instructions to create the needed bridging files, which will need to be scanned by your host afterwards.
Program options / settings ( depending on the GUI mode, some settings may not be available ): Performance mode: Audio is processed asynchronously with one buffer of extra latency. It can improve the performance by helping to balance the load on multi-core systems ( and making all the cores being used in single core hosts ) , but it may introduce audio artifacts with some plugins / hosts.
1 - EnergyXT 1.4.1 running 16 instances of Kontakt 3.5 (natively) – multi processing not used in main host and plugin.
2) EnergyXT 1.4.1 running 16 “jbridged” instances of Kontakt 3.5, with “performance mode” enabled – multi processing not used in main host and plugin.
audiomasterGetTime hack: time info requests from the plugin are done in the processReplacing calls, which could help to reduce IPC overhead. Use thread safety measures in auxhost: Try enabling this option if a bridged plugin crashes frequently and/or randomly. Switch to integrated/separated GUI mode: If you enable this option, the plugin's GUI will switch to separated or integrated mode the next time you load it ( according to the current mode ). Sluggish GUI hack: If you're experiencing extremely slow response or any error message when operating a bridged plugin's GUI, try enabling this option.; Dirty close: As the name suggests, it does a little “cheat” when you remove a bridged plugin. This option should only be enabled as a last resource, if nothing else works. Run in existing auxhost: All the plugins with this option enabled will run in the same auxhost ; This is intended for plugins that for some reason have problems running multiple instances on different processes - Restart the bridged plugin for this change to take effect.
Integrated GUI mode additional options:
Prevent main host control when the GUI window is closed: If you're experiencing "dispatcher opcode 15 failed" errors, try enabling this option. Force whole GUI refresh: Try enabling this option if parts of your bridged plugin's GUI aren't correctly displayed. Force child window clipping: Sets additional window flags to prevent the GUI from being partially displayed. Another alternative / complement to the previous option. I am getting a dispatcher opcode 19 error message: If you're getting an error message refering this dispatcher opcode, or your bridged plugin's GUI causes a permanent hang, try enabling this option."; Separated GUI mode additional options:
Auto-close GUI: Auto-closes the plugin's GUI ( if open ) when you close jBridge's GUI. GUI always on top: Self – explanatory. :-)
Bridged plugin in separated GUI mode ( plugin's GUI will be displayed in a separate window )
Bridged plugin in integrated GUI mode
Known issues – Reaper users, you must disable "Close audio device when stopped and application is inactive", in the audio preferences. Otherwise Reaper's sound engine could be stopped when operating a bridged plugin's GUI.
- If you're using Windows Vista or 7, you may need to set auxhost.exe / auxhost64.exe to run with Administrator privileges, as well as the jBridger tool's *.exe and your main host *.exe. Some users have reported not saved registry data due to the fact that the process was blocked from accessing the registry. Right click each auxhost *.exe and under the compatibility settings, enable it to run in Administrator mode. (see next page-->)
– Plugins that use fancy protection mechanisms may not work with jBridge. In that case, you may see a message similar to this one:
No solution / support can be provided for plugins whose protection mechanism prevents them from being bridged.
– If you're using Cubase 5, make sure you disable this option (otherwise the sound may be disabled when operating a bridged plugin's GUI):
A periodically updated troubleshooting section for jBridge can be found here: http://jstuff.wordpress.com/jbridge/jbridge-troubleshooting/
Contact The latest version of jBridge can be found at http://jstuff.wordpress.com/jbridge. For any comments, inquiries, suggestions, or bug reports:
[email protected]
Credits A big thanks to: Brad Robinson, for all the advising and help. :-) - http://www.cantabilesoftware.com/ Cakewalk - www.cakewalk.com Steinberg - http://www.steinberg.net Image Line - www.image-line.com/ FXpansion - http://www.fxpansion.com/ Brainspawn - www.brainspawn.com
