![]() Assuming you've already made 64-bit versions of your 32-bit VSTs, and Logic is booted up, create an instance of MetapluginSynth on an Instrument track. Instruments & Effectsįirst things first, though. And as we'll see in a moment, it's a useful thing to have for any DAW, not just Logic. But the crucial piece of the jigsaw is the use of the $39 Metaplugin from an unusual plug-in that exists to host other plug-ins. Then you'll still need to splash out a few quid on jBridgeM at and make 64-bit versions of those ageing VSTs. It also relies on having VST versions of your 32-bit AUs available, so it's possible you might need to do a bit of reinstalling if your setup is otherwise Audio Unit-only. Since then a few more solutions have emerged, but by far the most promising is this one, suggested by a user (thanks TreyM!) on the KVR web site. Another used the third-party utility jBridgeM to generate 64-bit 'wrapped' versions of 32-bit VST plug-ins, ready to be hosted in Plogue's Bidule application or plug-in. One approach involved opening virtual instrument AUs in third-party host applications. In last month's Apple Notes I suggested a few ways that Logic Pro X users could continue to use 32-bit plug-ins, now that the application no longer supports them. Here I'm running a bunch of languishing (or defunct) 32-bit VSTs in the 64-bit version of Presonus's Studio One 2. Its flexible MIDI and audio routing abilities make it hugely useful in any DAW, though. Metaplugin (in conjunction with jBridgeM) currently looks to be the most reliable and cost-effective way of running 32-bit plug-ins in 64-bit DAWs like Logic Pro X. A new program makes it possible to use your favourite 32-bit plug-ins in any 64-bit DAW.
0 Comments
Leave a Reply. |