KVR Audio

Juljan · Post by **Juljan** » Wed Feb 03, 2016 7:08 pm

Hey guys,

I would really like to change my whole setup by using Pro Tools 12 instead of Fl Studio 12.
My problem is that all my plugins are installed as VSTs, only a few have AAX format, too.
I saw Dave Pensado explaining the Metaplugin by DDMF but I'm not sure if this is the right thing for me.

Because:
- how is the CPU usage? I mean ninety percent of my plugins are VST so that I would use this plugin for nearly everything

- does it support 32- and 64-bit as well as VST2?

- why do I need jBridge for that thing?

Hope you can help.
Thanks a lot.

Juljan

Juljan · Post by **Juljan** » Thu Feb 04, 2016 1:30 pm

Nobody?

whyterabbyt · Post by **whyterabbyt** » Thu Feb 04, 2016 1:53 pm

Juljan wrote: - how is the CPU usage?

Pretty trivial. Unless you use the 2x oversampling option, in which case, double, obviously.

- does it support 32- and 64-bit as well as VST2?

Nope. But it does support VST3.

- why do I need jBridge for that thing?

Because bit-bridging is a different thing.

docdued · Post by **docdued** » Fri Feb 05, 2016 11:20 am

Not quite right (as also explained via email): Metaplugin does support VST2 and VST3 (and AU on Mac as well, while we're at it), and also 32 and 64 bit in the sense that there is a 32 bit version and a 64 bit version. Each of these versions can only load plugins with the same bit-format, though, so if you have a host like PT12 that is a pure 64 bit host, you will need jBridge to first create a 64 bit version of your 32 bit VST plugin before you can load it into ProTools via Metaplugin.

whyterabbyt · Post by **whyterabbyt** » Fri Feb 05, 2016 11:28 am

docdued wrote:Not quite right (as also explained via email): Metaplugin does support VST2 and VST3 (and AU on Mac as well, while we're at it), and also 32 and 64 bit in the sense that there is a 32 bit version and a 64 bit version.

ProTools 12, though, is a 64-bit-only AAX host; there is no 32-bit version of PT12. Hence my reply; the only possible version of Metaplugin he would be able to use in PT12, the 64-bit AAX, cannot load 32-bit plugins unless they are bitbridged.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Feb 05, 2016 2:53 pm

[DELETED]

whyterabbyt · Post by **whyterabbyt** » Fri Feb 05, 2016 3:30 pm

TheoM wrote:
whyterabbyt wrote:
docdued wrote:Not quite right (as also explained via email): Metaplugin does support VST2 and VST3 (and AU on Mac as well, while we're at it), and also 32 and 64 bit in the sense that there is a 32 bit version and a 64 bit version.
ProTools 12, though, is a 64-bit-only AAX host; there is no 32-bit version of PT12. Hence my reply; the only possible version of Metaplugin he would be able to use in PT12, the 64-bit AAX, cannot load 32-bit plugins unless they are bitbridged.
but it can load 64 bit vst2.. you said nope, but vst3. The dev corrected you. I trust the dev on this one

Sorry to be pedantic, but reread the question and the reply. My emphasis added:

- does it support 32- and 64-bit as well as VST2?

Nope. But it does support VST3.

I wasnt saying it can't load 64-bit plugins. I was saying it cant load '32- and 64-bit as well as VST2'. He was bringing jbridge up, so in that context it appears like he was asking if this was a substitute for that, capable of handling both.

And it cant load 32-bit and 64-bit plugins. The 32-bit version can load 32-bit plugins, the 64-bit version can load 64-bit plugins, but neither can load both.
And as I say, since the OP was talking about PT12, then he'll have to use the 64-bit AAX, and that cannot load 32-bit plugins.

His choice of language, in retrospect, is ambiguous. That informs what you think his question was, though, not whether my question correctly answers what I think his question was.

(and the fact i use vst2 plugins in metaplugin myself)

I've also successfully jbridged vst2 32 bit plugins like vanguard into 64 bit versions then loaded them into meta

So have I. For two or three years now.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Feb 05, 2016 3:36 pm

[DELETED]

whyterabbyt · Post by **whyterabbyt** » Fri Feb 05, 2016 3:55 pm

TheoM wrote:my god you really are pedantic.

yes I was being pedantic. I said so, up front. A supposed mate of mine seemed to have jgot the wrong end of a particular stick so I was explaining myself quite carefully and precisely.

to anyone reading INCLUDING the dev, that seemed exactly like you were saying that it doesn't support vst2 plugins. That's *exactly* how it reads.

Im not responsible for how you read it, but the least you could do when I take time out to explain myself properly is not have a go at me for it.

Why can't you just accept the way you worded it was confusing? That said, why do i bother I was just ribbing you and i got the usual sermon. all good, i should have known better.

There's a lot of irony in that Theo. You joined in specifically to accuse me of being wrong about something based on your misunderstanding, but I start off being self-depreciating, I tried to explain what I was saying as clearly and precisely as possible, admitted the possible confusion, and peppered the post with smilies. And despite that, you're leveraging that to have a go at me, and blaming me for trying to explain myself?

Cheers. Always good to have someone kick you in the balls for no good reason. "I should have known better", eh? Hmmm. Thanks for the benefit of the doubt, always appreciated.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Feb 05, 2016 4:00 pm

[DELETED]

whyterabbyt · Post by **whyterabbyt** » Fri Feb 05, 2016 4:22 pm

TheoM wrote:A normal answer would have been, no it does not support 32 and 64 bit simultaneously, just either or, but it does support both vst and vst3.

Im sorry I dont meet your standards when Im spending my time voluntarily trying to help people. Perhaps you should have helped them instead.

Dude you are going way OTT here, way.

indeed; Im still trying to explain myself to someone who's having a go at me for no understandable reason other than being given an explanation of something.

I would have thought my big LOL in my first message was a clue that i was ribbing.

And the self-depreciating start, and the smilies in my post were clearly an indicator of not getting that.

but you went into a mega sermon. But again i am in the wrong .

Hmmm. Because I called you 'really pedantic', accusing you of making 'mega sermons', and commenting on how I should 'know better' when talking to you. Uhuh.

All I've done so far is try explaining something to you, and yet you're responding with a series of personal attacks Yes, I'd say that's its you in the wrong. Ive said nothing to you or about you that could even slightly be perceived as a rationale for those comments.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Feb 05, 2016 5:12 pm

[DELETED]

Juljan · Post by **Juljan** » Tue Mar 22, 2016 1:55 pm

Hey guys,
thanks for all your advice.

One little more question: Blue Cat's MB-7 is only for mixing (=effect, not synthesizer) purposes, isn't it?

Juljan · Post by **Juljan** » Wed Mar 23, 2016 12:23 pm

Noone?

whyterabbyt · Post by **whyterabbyt** » Wed Mar 23, 2016 12:55 pm

Juljan wrote:Hey guys,
thanks for all your advice.

One little more question: Blue Cat's MB-7 is only for mixing (=effect, not synthesizer) purposes, isn't it?

As far as I know, yes, its only an effect plugin, not a synthesiser plugin. BC Patchwork comes as both, though.

With some hosts (eg Bidule) it doesnt matter, in that it basically lets you route MIDI to any plugin, and if the plugin can process MIDI note data like an instrument, it, it will. I dont know if that's the case for MB-7, but you can route MIDI to an effects plugin which is an insert on an Instrument Track in PT

DDMF Metaplugin for FLS --> PT12