I'm glad to present you my new project
# GrandBridge FX Beta
**GrandBridge FX Beta** is a Windows VST3 plugin that works as a format bridge, CPU offload layer and sandbox host for effects.
It lets you load effect plugins of different formats inside a single VST3 plugin and run them outside the host process in a separate worker process.
## What GrandBridge is for
GrandBridge is designed around three main use cases.
### 1. Format bridging
GrandBridge lets you use several effect formats through one VST3 plugin:
- VST3 FX 64-bit
- VST2 FX 64-bit
- VST2 FX 32-bit via a separate worker32
- JSFX FX with GUI and @gfx support
In practice, you insert GrandBridge into any VST3-compatible host, then load a VST2 effect, an old 32-bit effect or a JSFX effect inside it.
### 2. CPU offload
The hosted effect runs in a separate `bridge_worker` process instead of running directly inside the host’s main audio processing path.
This can help to:
- reduce pressure on the host’s main realtime thread;
- distribute heavy plugins more flexibly across CPU cores;
- work around situations where the host stacks a heavy insert chain onto one core;
- handle large numbers of heavy plugin instances more reliably.
### 3. Sandbox and isolation
Because the hosted plugin runs in a separate process, it is less tightly coupled to the main host process.
This is useful for old, unstable or risky plugins: if such a plugin misbehaves, it is less likely to take down the whole project or the host itself.
## Automation
Hosted effect parameters are exposed to the host through GrandBridge automation slots.
This applies to all supported formats:
- VST3 parameters;
- VST2 parameters;
- VST2 32-bit parameters;
- JSFX sliders.
Parameters can be assigned, exposed to the host and automated.
## CPU profiles
### Auto / Balanced
The recommended default mode.
GrandBridge softly spreads worker processes across CPU cores without forcing a hard affinity lock. This is a good choice for most projects, especially when using multiple heavy instances.
### Keep DAW responsive
Similar to Auto / Balanced, but keeps the first CPU cores freer for the host and its user interface.
Useful when the project is heavy but the host still needs to remain responsive.
### Heavy plugin
A more dedicated mode for one particularly heavy plugin.
Useful when a specific effect is very CPU-hungry and should be moved into a dedicated CPU slot.
### Windows Native
GrandBridge gives no scheduling hints to Windows.
This is a fallback mode with completely standard Windows scheduler behavior.
## What works in this beta
- VST3 FX 64-bit hosting;
- VST2 FX 64-bit hosting;
- VST2 FX 32-bit hosting via worker32;
- JSFX hosting;
- JSFX GUI / @gfx support;
- hosted plugin GUI;
- parameter and slider automation;
- project restore;
- multi-instance usage;
- safe plugin switching and reload during playback;
- per-format plugin browser statistics.
## Current scope
This is the **FX-only** version.
Instrument, VSTi and MIDI support is planned later, after the FX version is released and tested more widely.
## Compatibility
GrandBridge works in any VST3-compatible Windows host.
This is a public beta. Compatibility may depend on the specific plugin, especially with old VST2 plugins, 32-bit effects or plugins with unusual GUI behavior.
## Short version
**GrandBridge FX Beta** is a VST3 bridge, CPU offload layer and sandbox host for FX plugins on Windows.
Supported formats:
- VST3 FX 64-bit
- VST2 FX 64-bit
- VST2 FX 32-bit
- JSFX FX with GUI / @gfx
GrandBridge lets you load effects of different formats inside one VST3 plugin, run them in a separate worker process, automate their parameters through GrandBridge slots and reduce the risk of host crashes caused by problematic plugins.
drive.google.com
# GrandBridge FX Beta
**GrandBridge FX Beta** is a Windows VST3 plugin that works as a format bridge, CPU offload layer and sandbox host for effects.
It lets you load effect plugins of different formats inside a single VST3 plugin and run them outside the host process in a separate worker process.
## What GrandBridge is for
GrandBridge is designed around three main use cases.
### 1. Format bridging
GrandBridge lets you use several effect formats through one VST3 plugin:
- VST3 FX 64-bit
- VST2 FX 64-bit
- VST2 FX 32-bit via a separate worker32
- JSFX FX with GUI and @gfx support
In practice, you insert GrandBridge into any VST3-compatible host, then load a VST2 effect, an old 32-bit effect or a JSFX effect inside it.
### 2. CPU offload
The hosted effect runs in a separate `bridge_worker` process instead of running directly inside the host’s main audio processing path.
This can help to:
- reduce pressure on the host’s main realtime thread;
- distribute heavy plugins more flexibly across CPU cores;
- work around situations where the host stacks a heavy insert chain onto one core;
- handle large numbers of heavy plugin instances more reliably.
### 3. Sandbox and isolation
Because the hosted plugin runs in a separate process, it is less tightly coupled to the main host process.
This is useful for old, unstable or risky plugins: if such a plugin misbehaves, it is less likely to take down the whole project or the host itself.
## Automation
Hosted effect parameters are exposed to the host through GrandBridge automation slots.
This applies to all supported formats:
- VST3 parameters;
- VST2 parameters;
- VST2 32-bit parameters;
- JSFX sliders.
Parameters can be assigned, exposed to the host and automated.
## CPU profiles
### Auto / Balanced
The recommended default mode.
GrandBridge softly spreads worker processes across CPU cores without forcing a hard affinity lock. This is a good choice for most projects, especially when using multiple heavy instances.
### Keep DAW responsive
Similar to Auto / Balanced, but keeps the first CPU cores freer for the host and its user interface.
Useful when the project is heavy but the host still needs to remain responsive.
### Heavy plugin
A more dedicated mode for one particularly heavy plugin.
Useful when a specific effect is very CPU-hungry and should be moved into a dedicated CPU slot.
### Windows Native
GrandBridge gives no scheduling hints to Windows.
This is a fallback mode with completely standard Windows scheduler behavior.
## What works in this beta
- VST3 FX 64-bit hosting;
- VST2 FX 64-bit hosting;
- VST2 FX 32-bit hosting via worker32;
- JSFX hosting;
- JSFX GUI / @gfx support;
- hosted plugin GUI;
- parameter and slider automation;
- project restore;
- multi-instance usage;
- safe plugin switching and reload during playback;
- per-format plugin browser statistics.
## Current scope
This is the **FX-only** version.
Instrument, VSTi and MIDI support is planned later, after the FX version is released and tested more widely.
## Compatibility
GrandBridge works in any VST3-compatible Windows host.
This is a public beta. Compatibility may depend on the specific plugin, especially with old VST2 plugins, 32-bit effects or plugins with unusual GUI behavior.
## Short version
**GrandBridge FX Beta** is a VST3 bridge, CPU offload layer and sandbox host for FX plugins on Windows.
Supported formats:
- VST3 FX 64-bit
- VST2 FX 64-bit
- VST2 FX 32-bit
- JSFX FX with GUI / @gfx
GrandBridge lets you load effects of different formats inside one VST3 plugin, run them in a separate worker process, automate their parameters through GrandBridge slots and reduce the risk of host crashes caused by problematic plugins.
GrandBridge_FX_Beta_v0_1_114a_public_beta (1).zip
drive.google.com