I have Bitwig in order to natively run both 32 bit and 64 bit VSTs - not AUs - on a Mac or PC, hence I use this solution if I by chance would like access to old plugins. I intend to keep running my old Win XP PC's as I am now regardless, so being I can continue to run all my 32 bit software & hardware on them, I stand to lose nothing reallyįrom what I've read, running 32 bit AUs can be problematic performance-wise across multiple spectrums, whether in Logic or other AU-based host.

I guess others are too, and that's why they end up going 64 bit all the way. This is confusing being I have no 1st hand experience with this.

a 64 bit PC, with either 32 & 64 bit DAW software, FX's & VSTi's. The above brings to mind with using a 64 bit PC and the ability to use ram.is it best to use a 64 bit DAW software with 32 bit FX's & VSTi's, than with a 64 bit PC with 32 bit DAW software & 32 bit FX's & VSTi's? And how can one way or another be able to use/not use all the available ram? All I know is that people have reported using any combinations above. He did say something about he wished he could use all his ram. He didn't mention using any kind of wrapper though I assume he does. But his DAW program is 32 bit, as well as his plugins (FX's & VSTi's). I just talked to someone the other day who's using a 64 bit PC. I had gathered that J-Bridge and others were less successful than this. Sampltude's internal bridging scheme works well, but is not 100% either.By 'plugins' you ARE talking about effects AND virtual instruments? If so that's good to hear. I've tried it with Pro Tools (using Bluecat Patchwork to do a second bridge to AAX) and recently trying it with Studio One. My experience is that at least 95% of the plugins out there will work fine with JBridge, at least on the PC.

Absynth vst 32 bit