So at this point I just use them in a DAW with bridging. Or run Waveform 32.
Bridging
-
- KVRAF
- 3735 posts since 17 Sep, 2016
I guess I am just lucky that I have found 64-bit versions for most of my plugins. A couple of 32-bit only instruments that I don't wanna let go of are Tone2 Firebird (now free) https://www.tone2.com/firebird2.html and MiniMogue VA. http://www.vst4free.com/free_vst.php?id=405
So at this point I just use them in a DAW with bridging. Or run Waveform 32.
So at this point I just use them in a DAW with bridging. Or run Waveform 32.
Windows 10 and too many plugins
-
- KVRAF
- 1728 posts since 21 Sep, 2007 from USA
In general, running bit-bridged 32-bit VST plug-ins in a 64-bit DAW, is less than optimal. That said, it is still very useful to have the capability in a DAW, and built-in bit-bridging is not an uncommon feature for a modern 64-bit DAW to have. Many recent 64-bit DAWs (such as Cockos Reaper, Cakewalk Sonar, Image Line FL Studio, Steinberg Cubase, MAGIX Samplitude Music Studio, and Open Labs Stagelight, to name a few) have built-in VST bit-bridging.
I have tried using the jBridge demo in the past and found it to be too clunky and unreliable.
Using a 32-bit and 64-bit version of the same DAW simultaneously is not an efficient option.
As a side-note, it would also be useful if VST plug-ins and standalone hosts (e.g. Blue Cat Patchwork, Image Line Mini Modular, etc.) provided native VST bit-bridging support; not sure how feasible it is to implement as a VST-hosting VST plug-in.
I have tried using the jBridge demo in the past and found it to be too clunky and unreliable.
Using a 32-bit and 64-bit version of the same DAW simultaneously is not an efficient option.
As a side-note, it would also be useful if VST plug-ins and standalone hosts (e.g. Blue Cat Patchwork, Image Line Mini Modular, etc.) provided native VST bit-bridging support; not sure how feasible it is to implement as a VST-hosting VST plug-in.
[Core i7 8700 | 32GB DDR4 | Win11 x64 | Studio One 7 Pro | WASAPI ]