Is JBridge Better Than Mixcraft 8 Internal 32-Bit Plugin Handling?

[Thomas]

As far as I can tell, all the MC included plugins are 32-Bit. Most of the free plugins available in the marketplace are also 32-Bit as far as I know. From reading these boards, MC 64-Bit can open a 32-Bit plugin, but uses some sort of "wrapper" to do so and there is a performance hit.

I am considering the use of JBridge to handle the 32-Bit plugins. Can anybody tell me what the difference is in how JBridge handles 32-Bit plugins vs MC 8s own internal method? Does JBridge suffer the same performance hit? Pros and cons of each? No difference? I am trying to optimize my system in preparation of future projects.

[Anorax]

You're essentially swapping the internal MX8 32-bit wrapper for the JBridge wrapper. Between the two, the in-house wrapper generally has better support from Acoustica

[chibear]

I used jBridge in Mixcraft 6. When Acoustica came up with it'sown bridge everything went smoother

[Anorax]

...that being said, if you're someone who uses multiple DAWs, getting jBridge might be worth it, especially since some DAWs are moving away from 32-bit support altogether (looking at you, Ableton Live 10).

[Thomas]

So it sounds like MC is doing pretty much the same thing as jbridge. Just using MC for now, so I will not bother with jbridge. Thanks guys.

[Anorax]

So it sounds like MC is doing pretty much the same thing as jbridge. Just using MC for now, so I will not bother with jbridge. Thanks guys.

That's pretty spot-on, yeah.

[Torton5]

No.