PLUG-IN HOSTING & CRASH PROTECTION IN BITWIG STUDIO
With the release of Bitwig Studio 2.5 we made our VST plug-in support even better. Watch the video and read on to learn all about it.
Bitwig Studio plugs right into your existing setup. With modern software architecture, 32-bit and 64-bit plug-ins (VST2.4 and VST3) are natively supported, no third-party bridging necessary. And as part of the VST3 standard, we proudly support per-note expressions and sample-accurate automation.
Never again will a single plug-in take down your entire project. The “sandboxing” feature built in to Bitwig Studio ensures plug-in crashes will not interrupt valuable production time, or your performance on stage. Bitwig Studio protects your workflow while efficiently running your VSTs for non-stop creativity.
Full Hosting Control
In the Bitwig Studio Dashboard you can choose the setting that is right for you – from light on resources to super-secure. The default setting is Together. And if all of this sounds like a spanish castle to you just leave the setting there and go and make music until you have a reason to come back.
Here are the 5 modes explained:
Within Bitwig. Plug-ins are loaded along with the audio engine. This requires the least memory, but any single plug-in can crash all audio.
Together. Plug-ins are sandboxed together, separating them from the audio engine.
By manufacturer. Individual sandboxes are created for each plug-in manufacturer. (This can be necessary when plug-ins need to communicate with one another.)
By plug-in. Individual sandboxes are created for each plug-in used. When a plug-in is used multiple times, its instances are sandboxed together, sometimes reducing the required memory.
Individually. Individual sandboxes are created for each plug-in used. This is the most memory-intensive option, but the safest.