VST3 to VST2

[aMUSEd]

btw I put together a list of plugins so far tested that do migrate on the NI forum

https://community.native-instruments.co ... ist#latest

those that don't include Arturia, u-he, Spectrasonics, Tone 2, Softube, Rob Papen, G-Force, Audiodamage (partially) - off the topic of my head those are the 'bigger' names out of the ones I have tested anyway - some of those I know already are working on it

[Sam Briacatu]

I released a vst3 to vst2 wrapper some years ago for Jeskola Buzz, here is a download link for the wrapper, works also with other vst2 hosts:

YOU ARE A F^^KING WIZARD BRO!!! to be able to thank you I had to register as a user on this forum... but if I met you I would offer you an all you can drink ... you have no idea how much anger and frustration I've suffered in the last 2 weeks fighting with this thing... and then you come along and with a snap of your fingers you solve everything... in just ONE minute, at FIRST attempt, and only 407KB

[Ah_Dziz]

You won't ever actually "change a VST3 to a vst2" in any simple way. You can use subhosts (I'm sure patchwork has been mentioned here already and it's my go to) to host entire chains of vst 3 and 2 plugins. You can maybe run your current host in another host as a plugin and learn your way around something new. Unfortunately VST2 is a dead format and you'll be seeing less and less support for it moving forward. It struck me as odd that Steinberg decided to kill it so severely but it's their SDK I suppose.

Anyway I'll add that as a nondeveloper, my use of VST3 plugins has been overall far more positive than VST2. VST3 also does a few things that weren't possible with VST2 and that are extremely useful for me in my work.

[ilovemusicjake]

With the release of Serum 2 I've been put in a similar situation here. I actually brought this old account back to life to find a workaround or see if I have to just upgrade my DAW, and it seems upgrading the DAW is probably the way to go. I can only hold on to software from 8 years ago for so long it seems. LOL.

[IvyBirds]

VST2 came out in 1999, VST3 came out in 2008

It's time to move on the format that came out 17 years ago and leave behind the one that came out 26 years ago

[josb]

It's time to move on to the format that came out 3 years ago and leave behind the one that came out 17 years ago.

[whyterabbyt]

It's time travel to move on to the format that comes out 3 years from now ...

[xiaosicp]

One of the files this plug-in needs cannot be found, please reinstall orcontact technical support for assistance [Ox2]

[k2006]

if this doesn't work you can try Kushview Elements (free/patreon) for using vst3 in older DAW.

[MrJubbly]

It's time travel to move on to the format that comes out 3 years from now ...

That plugin format will still be CLAP. The new standard for the next 20+ years.

[IvyBirds]

It's time travel to move on to the format that comes out 3 years from now ...

That plugin format will still be CLAP. The new standard for the next 20+ years.

Why? It is not supported by the majority of DAWs and most developers that support it make the same exact plugin and then just compile it into different formats

VST3 is the industry standard and has been for decades. It supports the overwhelming vast majority of users quite well, with the exception of people who use DAWs with proprietary formats like Pro Tools and Logic but those users are not going to migrate to CLAP either

People with older vintage computers, and/or people using old software might have issues with VST3 but CLAP would also cause them issues so there is no advantage there either

In order for CLAP to become new standard it first has to become the standard and currently it's a fringe product and offers no compelling reason to use it, other than people lying about Steinberg's support for VST3 and VST2 over the years

VST2 came out in 1999 and was made obsolete in 2003 it's time to let it go

[whyterabbyt]

It's time travel to move on to the format that comes out 3 years from now ...

That plugin format will still be CLAP.

CLAP wont come out 3 years from now, so that'd be impossible. I suspect you may not have read my post closely enough.

[seafire]

VST2 came out in 1999 and was made obsolete in 2003 it's time to let it go

Still use it everyday here, and new stuff is still being released in vst2 format, so its absolutely not obsolete.

[whyterabbyt]

most developers that support it make the same exact plugin and then just compile it into different formats

What exactly about developers targetting multiple plugins formats stops CLAP from becoming a standard? Obviously many were targetting multiple standards when VST3 became available, so if, as you allege, that became a standard under those conditions, why doesnt that same scenario hold for CLAP?
Are you saying that because multi-format plugins are possible, supporting additional formats will be less likely?
What is it about VST3 that exempts it from the logic you're applying to CLAP?

VST3 is the industry standard and has been for decades.

But according to you, CLAP cant be an industry standard because it isnt supported by the majority of DAWs, and VST3 certainly wasnt supported by the majority of DAWS for decades.
What is it about VST3 that exempts it from the logic you're applying to CLAP?

with the exception of people who use DAWs with proprietary formats like Pro Tools and Logic but those users are not going to migrate to CLAP either

Why not? Surely you're aware that not everyone only uses one single DAW? Or that some people use wrapper or bridge solutions to access plugin types that their DAW doesnt directly support?

It supports the overwhelming vast majority of users quite well

How does a plugin standard support users?
If two plugin standards provide the same functionality, surely they support users equally well?

What is it about VST3 that exempts it from the logic you're applying to CLAP?

People with older vintage computers, and/or people using old software might have issues with VST3 but CLAP would also cause them issues so there is no advantage there either

And no disadvantage either, obviously.

In order for CLAP to become new standard it first has to become the standard

Well, yes, that circular logic is obvious.

and currently it's a fringe product

And yet VST3 was once a fringe product too.
What is it about VST3 that exempts it from the logic you're applying to CLAP?

and offers no compelling reason to use it,

Since you're a fan of circular logic, then you do need to consider that it certainly offers compelling enough reasons to use it for the people who, ahem, use it.

other than people lying about Steinberg's support for VST3 and VST2 over the years

Lying eh? What, like saying something has been a standard for decades just because it was released decades ago? Something like that?
What is it about VST3 that exempts it from the logic you're applying to CLAP?

VST2 came out in 1999 and was made obsolete in 2003 it's time to let it go

If it was made obsolete in 2003, why was it that the only way Steinberg could get developres to stop using it was to forcibly revoke their legal right to do so? Asking for a friend.

[IvyBirds]

most developers that support it make the same exact plugin and then just compile it into different formats

What exactly about developers targetting multiple plugins formats stops CLAP from becoming a standard? Obviously many were targetting multiple standards when VST3 became available, so if, as you allege, that became a standard under those conditions, why doesnt that same scenario hold for CLAP?
Are you saying that because multi-format plugins are possible, supporting additional formats will be less likely?
What is it about VST3 that exempts it from the logic you're applying to CLAP?

I see you want to put words into my mouth and engage in logical fallacies.

The point I am making is simple.. VST3 is the current industry standard. Steinberg developed VST3 22 years ago because it offered improvements over VST2

For CLAP to become an industry standard it has to offer advantages over VST3 and those advantages have to see real world use in the vast majority of plugins and DAWs. If that were to happen I would gladly use it. However the fans of CLAP like to engage in half truths and logical fallacies to promote it as you are doing here

Currently if a plugin I buy is available in VST3 and CLAP it makes no sense to download and use the CLAP version because doing so limits your options when it comes to which DAWs and/or hosts you will be able to use it in. There is no compelling to use the CLAP version

VST3 is the industry standard and has been for decades.

But according to you, CLAP cant be an industry standard because it isnt supported by the majority of DAWs, and VST3 certainly wasnt supported by the majority of DAWS for decades.
What is it about VST3 that exempts it from the logic you're applying to CLAP?

Only I never said that, there you go again with the half truths and logical fallacies

with the exception of people who use DAWs with proprietary formats like Pro Tools and Logic but those users are not going to migrate to CLAP either

Why not? Surely you're aware that not everyone only uses one single DAW? Or that some people use wrapper or bridge solutions to access plugin types that their DAW doesnt directly support?

I notice you are hilariously attacking me and are not able to actually articulate what advantages CLAP has over VST3.

It supports the overwhelming vast majority of users quite well

How does a plugin standard support users?
If two plugin standards provide the same functionality, surely they support users equally well?

Because you have to have a compelling reason for people to abandon VST3 in favor of CLAP if CLAP is to become the industry standard. You know the thing you are avoiding actually doing

What is it about VST3 that exempts it from the logic you're applying to CLAP?

That's simple VST3 is currently the #1 format of audio plugin formats and is the industry standard. For CLAP to ever become the industry standard there would have to be a compelling reason for people to make the switch. Currently there is no reason and VST3 offers the largest reason not to make the switch and that is it will work on just about every DAW with the exception of a few proprietary DAWs

People with older vintage computers, and/or people using old software might have issues with VST3 but CLAP would also cause them issues so there is no advantage there either

And no disadvantage either, obviously.. sir

But you are not going to make the switch to CLAP just so you can't use it in your older computer with old software are you? See there you go again with your logical fallacies

Which brings me to my last point so thanks for making it for me

If it was made obsolete in 2003, why was it that the only way Steinberg could get developres to stop using it was to forcibly revoke their legal right to do so? Asking for a friend.

Thanks for pointing out that Steinberg supported VST2 for decades after it was made obsolete by VST3.

The #1 silly argument made to support CLAP by it's very small but vocal user base is that somehow Steinberg dropped support for VST so people should move to CLAP. The person I was responding to has made that exact claim right here on KVR that they are using CLAP because after 22 years Steinberg wants people to move to VST

Most people who use software understand the idea that a software standard that came out in 1999 should probably not be used anymore when something better is available.

you are advocating people abandon VST2 in favor of a newer format. So why do you have an issue when Steinberg is doing the same thing? Looking for leads to your answer on that. Asking for a friend