Workload Distribution Across CPU Cores
GrandBridge distributes the work of multiple plug-ins across available CPU cores. This helps avoid the situation where one core is already overloaded while others are still free.
A VST3 bridge for audio plug-ins
GrandBridge — the Universal Bridge Between Your DAW and the Full Power of Your Computer
GrandBridge loads in your DAW as a standard VST3 plug-in. Open any FX or instrument inside it, and the intelligent scheduler distributes its workload across CPU cores. As a result, any plug-in — old or new — becomes part of a true multicore system. GrandBridge bypasses a major bottleneck shared by all DAWs: uneven core utilization, where one core is already overloaded while others remain idle.
- Multicore Offload
- GPU Zoom
- Sandbox
- VST3 Shells
- VST3
- VST2 64-bit
- VST2 32-bit
- Waves
- JSFX
How GrandBridge Distributes the Workload
Available CPU cores
FX and instruments
The DAW passes selected plug-in processing to GrandBridge. GrandBridge distributes that work across available CPU cores while latency, automation and project recall continue to behave as expected.
Schematic illustration of core utilization, not measured data.
A Complete Plug-in Workflow
Native-Style VST3 Shells
Create a dedicated VST3 Shell for any hosted plug-in. It appears in the DAW under the plug-in's own name and opens directly, without an extra browser or manual selection step.
Host & Global MIDI Control
Map hardware MIDI CC controls to GrandBridge Auto slots or Macros. Use MIDI already routed by the DAW, or select one physical controller globally for the active GrandBridge instance.
Macros & Automation
Expose hosted parameters to the DAW, group several controls behind one Macro and keep mappings available across FX, instruments, formats and generated Shells.
GPU Zoom for Plug-in GUIs
Scale plug-in interfaces that were never designed for modern displays. GrandBridge GPU Zoom works around the lack of a common VST zoom standard and keeps the original plug-in interactive.
Sandbox Isolation for Every Plug-in
Each hosted plug-in runs separately from the DAW and the other plug-ins. If one freezes or crashes, GrandBridge contains the failure inside its Sandbox and lets you recover that plug-in without restarting the entire session.
Inside the Interface
Captures from the GrandBridge window.
Dedicated VST3 Shells
Selected plug-ins get their own Shells, which appear in the DAW under the plug-in’s own name.
Automation Slots
Auto slots bind to the parameters of the hosted plug-in and reach the DAW as ordinary automation.
Format-aware plug-in browser
Format, manufacturer, category and path in one list, with fast scanning and a metadata cache behind it.
Fast scanning and the metadata cache
Fast Scan rebuilds the index, Update re-scans only what changed, Metadata Scan separates FX from instruments.
Built for Real Projects
FX and instruments, modern and legacy formats, direct GrandBridge hosting or dedicated VST3 Shells.
The largest CPU gains appear when a project contains several heavy, independently processable plug-in instances. Results vary with the DAW, buffer, plug-in topology and the plug-ins themselves.
Measure the Difference in Your Own Project
Use the same DAW, the same plug-ins and the same project. GrandBridge is designed to prove its value in a real session, not in a marketing benchmark.
Windows macOS — planned
