Typically, though not always, there are 32bit AUs available. I'm surprised the AU alternative 32Lives (Mac) doesn't come up more often when Jbridge on Macs is discussed.
But who said music production should cost about nothing? On the other hand updating a large library to 64bit can be costly. However, if you have tracks that rely on old 32bit plug-ins what are you going to do for performances and all? Learn to use anything else you can choose is a viable option, I suppose.
And ignored the plugins that didn’t have a 64 bit version, and in almost all cases I was already ignoring them anyway. Went and updated the plugins I cared about, long overdue regardless. It forced me to do a long overdue cleanup of my plugins. I didn’t panic or look for some bridging option.
You spent less than $20 on a piece of software that's in BETA! and your'e throwing a shit fit that it works as advertised?īeats me wrote:I stopped using 32 bit plugins when Logic Pro X came out because there isn’t a 32 version. You're completely utterly overreacting, period. It's more likely to have problems with Audio Ease Speakerphone, but Audio Ease do not recommend using bit bridges. I use it with AAS plug ins and it's flawless. Yes it's the most likely thing to crash, it's a fix for a problem between dozens of companies. It works fine on my computers, both Macs as well. I am going to be making you tubes of these crashes and sharing to spread the word that jBRIDGE IS UNRELIABLE and that guy will just keep taking peoples money and HE WILL NOT GIVE YOU A REFUND EVER. Just froze my whole computer not only crashing ableton. They need to support 32 bit or just tell people you will not be able to use 32 bit plugins on Ableton 64. Had to just go ahead and delete all 32 plugins since it was so unreliable.Ībleton really needs to stop suggesting it to its users/buyers as a fix and making it look like its the answer to the problem. You can read about other software users (like Reaper) discussions about VST 3 here: Īny plans to support VST 3 or higher (3.0 came out in 2008 and 3.Kompletemail wrote:Such a piece of crap piece of software should not be sold because its not ready and the developer doesn't really care to advance it as I asked him before.Īnd all I am running is ONE sylenth thats it. Most companies making VST 3' also make a VST version (as Nectar does). "VST" : iZotope Nectar 2.dll (this works in Band-in-a-Box 2015, including 64 bit and 32 bit )Īnd "VST 3" : iznectar2.dll (this is a 'VST 3' format plugin, so not supported at all in Band-in-a-Boxīand-in-a-Box supports VST plugins, but not "VST 3" plugins. The Nectar Plugins come in various plugin types, including Note that the name of the DLL to use for the 64 bit version is iZotope Nectar 2.dll (not iznectar2.dll as you noted above).
That's both the 64 bit version and the 32 bit version. We tested Band-in-a-Box 2015 with Izotope's Nectar 2, and it's working fine for us with Band-in-a-Box 2015 with jbridge. > There's several plugins that come with Nectar2. But please try it with "iZotope Nectar 2.dll" and it should work fine. The issue likely arose because you chose a different plugin name, that is iZNectar2.dll which is a "VST 3" and not a VST plugin. The plugin to use is "iZotope Nectar 2.dll" (this works in Band-in-a-Box 2015, including 64 bit and 32 bit ).
In our testing, the 64 bit plugin that you mentioned works fine in Band-in-a-Box 2015 with jbridge. : Hi Sonny Ray: Please see my detailed reply at the bottom of this thread. Win7Pro / 8GB RAM / 1.3G Hard Drive / BIAB/RB EverythingPK / Should the JBridge program folder be in the BB Folder? Should I delete and reinstall - how do I do reinstall? (So many questions!)
I'm not sure how to proceed or troubleshoot.
I tried to install a 64bit VST Nectar2 plugin in both BIAB and RB but I still get the same "won't work" message as before, that is, pre-2015 BB/RB.