Logic Pro uses a validation tool to ensure that only plug-ins that fully comply with the Audio Units plug-in specification are used in Logic Pro.
So just use VST like everything elseâŚ
Yes, and you can join the chorus here if you want to help: Feedback - Logic Pro â Apple However, Logic Pro doesnât support VSTs as of now and likely wonât in the near future.
At the moment the reality is there are many plugin formats: VST2, VST3 and AU most commonly, as well as AAX and sometimes LV2 along with a few in the new CLAP format. Iâd love it if there was just one format, but thatâs not the reality we live in. @Vortico has stated that an AU version of VCV2 Pro would be coming soon so itâs fair for us to ask.
1 Like
Just to say - âsoonâ is a VERY relative term in VCV land 
1 Like
Yes, apple has no interest in compatibility. Logic was a acquisition, the first thing Apple did with it was kill off the Windows version. This was 10 or 20 years ago. If they wanted VST, they would have it by now. They clearly do not want to.
1 Like
Logic could load VST plugins on mac OS9. Apple bought Logic in 2002 and removed both the Windows version and with the switch to OSX also VST support.
apple has always been about the walled garden and incompatibility with anything non-apple. they would adopt their own walled internet (with proprietary protocols) and electricity net (with a different voltage and proprietary plugs) if they could get away with it.
2 Likes
they also acquired one of the better pro compositors - maybe shake? and immediately killed the linux version.
I might be missremembering but I seem to remember adverts for some kind of Apple net offering in the early 90s that was there own thing.
They all had them, remember MSN? This was before it was clear that the Internet and TCP/IP was a winner. But yeah, itâs pretty much a law that all companies will seek to acquire a monopoly on something, itâs the ultimate prize.
1 Like
Apple never promised they would make VST usable in Logic
VCV Rack team promised there would be an AU version.
There is a difference 
1 Like
I donât recall promising an Audio Unit plugin version of VCV Rack (please correct me if Iâd said otherwise), but this is certainly a feature weâd love to look into in the future.
3 Likes
I took from this this post and the VCV2 page which has said âother plugin formats coming soonâ since launch that an AU plugin was in the works.
From your reply it sounds like an AU release isnât a near-term likelihood?
3 Likes
Itâs true that technically you havenât promised AU or given dates. But with wording like âMore plugin formats coming soonâ on the download page, youâre certainly raising expectations for buyers, that something will happen âsoonâ and itâs anyoneâs guess what the next format is. You might want to adjust that wording to calibrate expectations, and make it more concrete as to what and roughly when. If nothing else because disappointment is bad business.
7 Likes
I think I remember seeing âAudio unit coming soonâ, but just rechecked it says âother formats coming soonâ.
Iâd assume AU version is part of âother formatsâ, as itâs pretty normal format. Pretty much all plugins, made now a days has an audio unit version, so I find it pretty reasonable to believe an audio unit would be in the works.
Ivâe seen other devs use vst/vst3 version and kind of hard âwrapâ it as an audio unit. There are many audio units, that if you right click on them and select âshow package contentâ there is actually vst version inside the audio unit, itâs just wrapped up to also show as an audio unit. I donât think that necessarily is too hard to do and would probably work as intended since itâs not loaded in another plugin, like when using Patchwork and similar.
An example that I think is actually a vst behind the curtains is ADVerb from Audio Damage, which can be downloaded here and itâs free:
I have seen a few plugins that looks like this behind the curtains. And I am pretty sure that Cardinal version does the wrapping like this, cause the dev mentioned it at some point, cause I asked about it. He said that he could make an audio unit version, by just wrapping the vst up as an audio unit. So I am pretty confident that it is possible to do this with VCV Rack too
But since there was not an audio unit in Cardinal at that time, I went and bough VCV Rack 2, cause I kind of thought âother formats coming soonâ surely would include an audio unit version and it would be coming soon. I would also like to support the original development.
1 Like
I would have thought the first priority would be VST3 because surely no one would have bought Rack Pro if they didnât have some way to use it and a number of Cubase users looking to upgrade to the new version would suddenly find Steinberg had stopped it being VST2 compatible.
Unless they changed tack from what they said was going to happen with the latest version.
To be honest yeah I think vst2, vst3 and Audio unit should all be there, all of them at the same time!
Absolutely, those are basic standard formats that ALL plugins comes in these days. Without a question. But in VCV world it seems to be an issue, which is not very understandable. If there is an issue, then hire someone to make it work, since poeple pay now, there should be money for that kind of stuff.
VCV is a paid pro software now, it even states it in the name, VCV Rack 2 PRO, so I think people are justified to ask for more formats as it is stated that there will be more formats.
Itâs not open source anymore, itâs not about goodwill and âplease do us a favour and implement thisâ, people paid for it, thatâs where the big difference is from before making VCV paid software and now. The dev took the step and went âproâ. Taking peoples money for a software, comes with a lot bigger responsibility than releasing open source software.
People also have the responsibility to check the specs before buying something, goes both ways.
There is only one main developer on VCV. If heâs having to spend his time developing, maintaining and supporting multiple different plugin formats then heâs not adding any benefit to users like me and the vast majority of us here who can happily work with a VST2 version.
With their incompatible M1 release alone Apple have eaten up a huge amount of developer time across a slew of products that could have been put into fixing outstanding issues or adding sexy new functionality for those of us who didnât wish to jump on their monopolistic bandwagon. Seems to me that entitlement - oh you all just have to support these arbitrary changes weâre making - shouldnât be allowed to trickle down to their user base without anyone calling it out.
Appleâs walled garden approach to everything really rubs me up the wrong way.
5 Likes
We did. It said other formats. If it was just one single other format coming, it would say ANother format. It says âother formatsâ, which is more than one. Once again assuming that a plugin will come in more than one format in 2022 is not being unrealistic. Being a developer and thinking releasing a plugin in a soon to be outdated format vst2 is enough, is on the other hand being majorly unrealistic!
2 Likes
Not my problem, I answered that in my last comment. Itâs a paid software now, which comes with a responsibility. He makes money now from VCV, he can hire someone to do it. Thatâs what pro developers do.
1 Like