Our experience with wrappers was that they work quite well, but some of them still suffer from bugs. A wrapper does also come with a slightly more CPU since the audio data has to be moved between processes. There is indeed the risk of additional compatibility problems, since a wrapper acts as an additional host like a middleware.
We experienced some minor problems with the Logic 32 bit wrapper.
Hi Markus,
I am using jBridge v1.5 with Cubase 4/5, Orion 8.5, Project5, Cantabile 2 and Sonar X1d (all 32bit versions on Win7 64bit)
Cantabile and Sonar have embeded support for jBridge.
jBridge offers many options and adjustments for "problem-plugins". If you found the correct adjustments for all the pluguns you are using with jBridge, the host and jBridge-services running really rock stable.
I am working every day with 20-46 bridged plugins in one of the above hosts.
For other hosts I can't give any proof if they work there without compatibility-issues.
I have an AMD 6 core processor at3.7 Ghz and it uses 5% less power if performance-mode is enabled to 40 bridged plugins.(assyncron processing for plugins when they don't send MIDI-out) compared to no bridged use.
If performance-mode is disabled to all bridged plugins the processor uses 5% more power. (seen in the Task-Manager). If you don't need MIDI out from plugins you can even save 5% processor power also when using 40 bridged plugins !!!
Also ElectraX, FireBird and AkustiX works jbridged without problems with the above hosts. Only FireBird needs some special adjustments in the jBridge-options (slow GUI-problem and dispatcher opcode 19 (slow response or possible crash)).