If you use plenty of 32 bit vsts, you can have both versions of ableton installed. Create a template in 32 bit version if you use 32bits as main sound sources, then bounce stuff you made out and put into 64 bit because you'll get more power for further processing. You can also jbridge them and it works just fine if that plugin you use is some effect plugin, however it might be not too good for softsynths or something similar to them. You also would need to freeze/flatten that track which has that 32 bit plugin because bouncing entire project as master will crash Live completely. Solution - get rid of these tools and look for alternatives that has 64 bit version. Maybe some of those plugins were updated already?
Well, objectively, it's obvious who wins here: 64 bit. You get more memory allocation (something absurd like 2 million GB of ram) and it feels more powerful, in my experience.
But there can be some issues with 64 bit. Some 32-bit plugins don't work properly on 64 bit software, causing crashes and not working as intended. When I converted from 32 bit to 64 bit, some of the plugins that I used never worked at all on the 64 bit version of FL. I ended up having to never use them ever again, which is kind of upsetting, and I had to re-design my template.
32 bit is sort of more stable but 64 bit is more powerful. However, as Joem stated, more and more developers are pushing forward towards 64 bit so plugins will be more stable in the future (except for plugins that aren't supported anymore).
At this point now 32bit is just backwards compatibility. Eventually someone will produce something that is for plugins what DOS4Gw was for gaming.
Eventually a developer will produce something akin to Strindberg Bridge but in a VST wrapper that can be used in any DAW without worrying about instability.
I think also with the amount of power available now there's a real possibility to fire up a lean 32 VM with bare bones IO and then control from the host system via OSC. Although you'd need at least one external interface to record audio out, and two to do it with any decency.
I already use a trusty XP VM whenever I want to fuck something up with LiveCut... Can run live 5 with fairly little fuss. Would want more grunt to go deeper though. But a VM with 4GB on a 16GB+ system could reliably run 4 tracks and a couple of sends...
Any plugs that are only available in 32bit I bin without compunction. If the makers aren't invested in them, neither am
Some developers just can't offer 64bit versions right now since the platforms they use to develop the plugs don't support it afaik. Some actually give good support for 64bit even though their plugins are 32bit only. G-Sonique, for instance, sent me a different version for Twisthead really really fast (two days iirc) after I told them that I couldn't jbridge that plugin anymore after migrating to a new PC with Win 10...
@jbridge stability: I think it depends on the specific plugs used... I had some problems in the past, when I used it a lot, but I reduced my plugin list and only use jbridge for a few now and it seems pretty stable to me.
There's no reason whatsoever not to use jBridge on a 64 bit system, if you want to use those old 32 bit vsts. As has been already said, it's only like $10 or something..if you're not going to invest that much in yourself, then just turn your computer off now and walk away..you'll save yourself a lot of time and money.
jBridge is far more stable than it used to be and I can count on one hand how many vsts have crashed since I got it a few year back..so I think the whole stability thing has nearly been addressed at this stage.
In the end, though, it is kinda dumb to be clinging to a 32 bit way of doing things..be that your system or the vsts you use. I get there are those who just can't pay out for 64 bit versions..or even a 64bit system..but both are things you should be aiming towards doing and embracing, rather than ignoring or turning away from.
As the guys have already said, 64 bit IS how things are now being done and will be done for some time to come..and ALL vst makers know this already, regardless of what reasons they give for not offering 64 bit versions of their products.
I suspect in many cases, they just don't because they couldn't be bothered upgrading tgheir process or they don't have the funds needed to produce a 64 bit version..otherwise they would, as the 64 bit market is only going to keep growing, as more users update their systems.
its got a bigger number so its prolly better #manlogic
Yeah totes. As opposed to #girllogic where you say, "I'm not insecure about penis size. It really doesn't matter if you've got a small dick. It's about how I feel about you" and stick with 32-bit then at 3:14 am, 19 January 2038 (a Tuesday) you'll be back in 1970.
I'm not sure how it is with you guys but the bridging of 32 bit into 64 bit on Reaper isn't perfect and there's definitely a bit of lag when I use too many bridged plugins in a large session (all of them are large at this point and we're talking 70+ channels)...can anyone else confirm on another DAW or even Reaper?