VST3 to VST2

[AnX]

bump

[kingtubby]

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:

https://www.xlutop.com/buzz/zip/vst3shell.zip

Not really sure how to use that, are there any instructions on how to use.

Just copy the files to your vst2 folder.

all of them? there are quite a few, with the same names?

There are 3 files each, depending on whether you are using a 32 or 64 bit host. I put the 3 x64 files in a sub-folder in my vst2 location and works very well so far. It appears to directly access the vst3 folder and will load either vst3 effects or instruments seamlessly.

[AnX]

ok, thanks for that, I will give it a try later (have to install a few vst3 synths first)

does the shell show up in the instruments list, you load that then the synth via the shell?

[kingtubby]

ok, thanks for that, I will give it a try later (have to install a few vst3 synths first)

does the shell show up in the instruments list, you load that then the synth via the shell?

I just tried it in Bidule. In the vst2 list there appears 'vst3shell' under which all your vst3 fx or instruments are listed and can be loaded directly from there.

[AnX]

[Harry_HH]

There are more and more developers no longer supporting VST2

I am curious - which ones?

AudioThing, Mellowmuse to name a few. I know there are more but cant remember.

Is this really the case? What does this mean in practice - new products, upgrade etc. ? I don’t believe that Audiothing abandons all the existing vst2 customers. I own 10 Audiothing plugins, all are running as vst2?

[Halonmusic]

There are more and more developers no longer supporting VST2

I am curious - which ones?

AudioThing, Mellowmuse to name a few. I know there are more but cant remember.

Is this really the case? What does this mean in practice - new products, upgrade etc. ? I don’t believe that Audiothing abandons all the existing vst2 customers. I own 10 Audiothing plugins, all are running as vst2?

i have no idea tbh. I just think it means that they AudioThing) wont do vst2 versions of new plugins, but they would (should really) update previous plugins they made in vst2 format.

[AnX]

ok, thanks for that, I will give it a try later (have to install a few vst3 synths first)

does the shell show up in the instruments list, you load that then the synth via the shell?

I just tried it in Bidule. In the vst2 list there appears 'vst3shell' under which all your vst3 fx or instruments are listed and can be loaded directly from there.

well, tried it here, i can see and load the shell, but it doesnt detect any vst3 plugins

shame, no big deal tho.

[kingtubby]

ok, thanks for that, I will give it a try later (have to install a few vst3 synths first)

does the shell show up in the instruments list, you load that then the synth via the shell?

I just tried it in Bidule. In the vst2 list there appears 'vst3shell' under which all your vst3 fx or instruments are listed and can be loaded directly from there.

well, tried it here, i can see and load the shell, but it doesnt detect any vst3 plugins

shame, no big deal tho.

I'm assuming it looks in the standard vst3 location i.e
C:\Program Files\Common Files\VST3
If that's where you have your VST3 plugins it should be ok..

[AnX]

yes, I checked that

more than likely a host issue

[Super Piano Hater 64]

Is this really the case? What does this mean in practice - new products, upgrade etc. ? I don’t believe that Audiothing abandons all the existing vst2 customers. I own 10 Audiothing plugins, all are running as vst2?

There's another thread discussing the fate of the VST2 format. In short, Steinberg really wants everyone to switch to VST3, and may have legally compelled some developers to give up their VST2 licenses.

[Harry_HH]

Is this really the case? What does this mean in practice - new products, upgrade etc. ? I don’t believe that Audiothing abandons all the existing vst2 customers. I own 10 Audiothing plugins, all are running as vst2?

There's another thread discussing the fate of the VST2 format. In short, Steinberg really wants everyone to switch to VST3, and may have legally compelled some developers to give up their VST2 licenses.

I have taken part in that thread, as well.
Still, what does this really mean in practice, and in what time table, seems to be unclear for most of the end users (and developers).

[qb0000]

with Native.Instruments.Kontakt.Factory.Library.2.v1.0.4
i really don't know how to use the wrapper from Polac's VST3SHELL

Version 1.2 released at 25-Oct-2021
How to install:
Copy all files to your dedicated vst2 folder. Depending on your host you have to scan for new vst plugins.


Reason does not support VST3
does anyone have clear instructions how to get this working?

do i put the files into the VST of some Native Instruments or Native Access folder?
or
do i put the files into some Reason VST folder?
either way, nothing worked for me.

thanks in advance

[whyterabbyt]

i really don't know how to use the wrapper from Polac's VST3SHELL

The expected method is that the contents of the vst3shell zip file should be placed inside the path that's your appropriate VST2 plugin folder (.x64 files in your 64-bit VST2 folder for 64-bit VST3s, the rest in your 32-bit VST2 folder if you have 32-bit VST3s), then you should rescan for plugins from your host.

That will then create a 'shell' plugin similar to those for Waves plugins, ie one .dll which contains multiple plugins.

However I do it differently, and also use the Polac Shell2VST utility, so that I can have one .dll file per plugin. See the link for that here: viewtopic.php?t=512395
If your host doesnt handle Shell type plugins well, that might be your best route too.

Im only using it for 64-bit plugins, so I create a separate folder -not in my VST path- for the x64 VST32Shell files, and then copy shell2vst64.exe into that folder as well.

So it contains

vst3shell.x64.core
vsti3shell.dll
vst3shell.dll
shell2vst64.exe

Then drag and drop the two .dll files onto shell2vst64.exe

That should create a subfolder called VST3 containing one .dll file per VST3, of about 5K in size.

You can then drag -those- .dll files out of the VST3 folder and into your VST2 path.

[qb0000]

thanks for your quick reply
you write "inside the path that's your appropriate VST2 plugin folder".
this is the "host" DAW VST folder?
I will need to decipher the rest of what you wrote