jBridge.v1.74 & ReWireBridge.v1.3

• 32-bit → 64-bit VST Bridging — Run legacy x86 VST plug-ins inside x64 DAWs.
• 64-bit → 32-bit Bridging — Supports the reverse architecture where required.
• VST 2.x Compatibility — Designed for plug-ins using the VST 2.x specification.
• Separate Bridged Processes — Uses inter-process communication to isolate bridged plug-ins from the main host process.
• Legacy Plug-in Preservation — Extends the practical life of discontinued or older VST instruments and effects.
• Configurable Compatibility Options — Provides user-selectable bridging options for problematic plug-ins and unusual host configurations.

jBridge addresses a common compatibility problem in digital audio production: modern 64-bit DAWs can no longer natively load many older 32-bit VST plug-ins. Rather than replacing an entire legacy plug-in collection, jBridge creates a bridge between the plug-in's architecture and the host, allowing supported 32-bit VST instruments and effects to remain available in a 64-bit production environment.

Its architecture relies on inter-process communication, which separates the bridged plug-in from the main host process. This approach can also help overcome the memory limitations associated with a single 32-bit process. Compatibility nevertheless varies by plug-in and host, and major DAW manufacturers generally treat third-party bridging as an unsupported configuration.

• Architecture bridging

  • 32-bit VST → 64-bit VST host
  • 64-bit VST → 32-bit VST host
  • 32-bit VST → 32-bit host with separate-process capabilities

• VST 2.x support

  • Intended for Windows VST plug-ins up to the VST 2.4 specification.

• Inter-process communication

  • Bridged plug-ins can operate outside the primary DAW process, helping separate legacy plug-in execution from the host.

• Custom bridge locations

  • Bridging files can be generated into a dedicated directory rather than mixed directly with the original plug-in collection. Steinberg specifically recommends maintaining separate original and bridged VST directories when using jBridge.

• Compatibility configuration

  • jBridger provides configuration options that can be adjusted when a plug-in does not bridge correctly using the default settings. The developer's troubleshooting guide recommends starting with the standard configuration and changing options only when necessary.

• DAW integration

  • The resulting bridged plug-in directory must be included in the DAW's VST scan paths.

| Specification | Details |
| ------------------------- | --------------------------------------------------------------------------- |
| Developer | J's stuff / João Fernandes |
| Version | 1.74 |
| Platform | Windows |
| Architecture | x86 / x64 bridging |
| Plug-in standard | VST 2.x, up to VST 2.4 |
| Primary purpose | Legacy plug-in compatibility |
| 32-bit VST in 64-bit DAW | Yes |
| 64-bit VST in 32-bit host | Yes |
| Standalone | No — bridging utility rather than an audio plug-in |
| macOS | No — this entry is the Windows edition |
| Typical hosts | Cubase, Nuendo, Reaper, FL Studio, Cantabile and other compatible VST hosts |

Steinberg documents jBridge as a third-party solution for loading older 32-bit plug-ins in 64-bit environments, while also noting that it is not officially supported by Steinberg.

For an organized installation, keep the original 32-bit plug-ins in a dedicated legacy/x86 directory and place the generated jBridge files in a separate bridged directory. This prevents the DAW from scanning duplicate versions of the same plug-in.

Installation

1. Install or extract jBridge v1.74 using the files supplied with the release.

2. Keep your original 32-bit VST plug-ins in a dedicated folder, for example:

   • VST Plugins (x86)

3. Launch the jBridger utility.

4. Select the appropriate VST host architecture.

5. Select the folder containing the plug-ins you want to bridge.

6. Select a separate destination folder for the generated bridge files.

7. Allow jBridger to analyze and create the bridge files.

8. Add the destination/bridged VST folder to your DAW's plug-in scan paths.

9. Rescan the plug-ins in the DAW.

10. Test each bridged instrument or effect individually.

The developer's current troubleshooting documentation follows essentially this workflow: select the host type, select the source plug-in directory, create the bridge files, and then add the resulting directory to the VST host's scan paths.

Recommended Folder Structure

VST Plugins  
├── VST Plugins (x86)  
│   ├── LegacyPlugin1.dll  
│   └── LegacyPlugin2.dll  
│  
└── VST Plugins (jBridge)  
    ├── LegacyPlugin1.dll  
    └── LegacyPlugin2.dll  

Only the appropriate bridged directory should normally be scanned by the 64-bit DAW. Steinberg recommends this type of separation specifically to avoid duplicate plug-in entries and compatibility problems.

Troubleshooting FAQ

Q: Can jBridge make a 32-bit VST work in a 64-bit DAW?
A: Yes. This is its primary use case.

Q: Does jBridge convert the original plug-in from 32-bit to native 64-bit?
A: No. It provides a compatibility bridge between the plug-in and host architectures rather than recompiling the original plug-in.

Q: My DAW does not detect the bridged plug-in. What should I check?
A: Verify that the DAW scans the folder containing the generated bridge files, then perform a plug-in rescan.

Q: Should the original 32-bit VST folder also be scanned by my 64-bit DAW?
A: Usually no. Maintaining separate original and bridged directories helps prevent duplicate entries.

Q: Will every old VST work correctly?
A: No. Compatibility depends on the individual plug-in, host, GUI implementation, licensing system, and other technical factors. Steinberg explicitly notes that results can vary with third-party plug-ins.

Q: Is jBridge officially supported by Steinberg or other DAW manufacturers?
A: Generally no. Steinberg explicitly states that jBridge is a third-party solution and is not officially supported by Steinberg.

Q: Does jBridge support VST3?
A: The jBridge Windows application described by the developer is designed around Windows VST plug-ins up to VST 2.4; it should not be catalogued as a VST3 bridge.