11 posts
Page 1 of 1
Ok so I have a new computer with a fresh system and I installed all the plugins I could in VST3 when I had the choice.
Thing is, I used to work with VST2 versions of some of those plugins in multiple song projects.
When I open one of those projects, Studio One 6 marks them as missing, even though their VST3 version is installed.
To be more specific, VST3 plugins work fine on their own, I can use them. The issue is Studio One doesn't seem to "link" the previously VST2 versions I used in projects to their newly installed VST3 equivalents.
I'm sorry if it isn't clear, it's a bit difficult to explain.

Apart from installing the involved plugins in VST2, do I have any other alternative to make things work ?
Specs :
- Studio One 6.1 Pro
- Windows 10 x64 is updated to last version
User avatar
by bailatosco on Tue Mar 28, 2023 8:12 am
I THINK this is the expected behavior. Do you use another DAW that doesn't behave like this?

Intel i7 - 11700k 5.0Ghz / 32Gb RAM
WIN 10 Pro 64bit
Studio One v5.4.0 Professional
Presonus Studio 192 USB 3.0
User avatar
by PreAl on Tue Mar 28, 2023 8:12 am
Whenever I've moved from VST2 to VST3 I've used the plugins alongside each other side by side and manually copied the settings. Occasionally I export the preset from VST2 and import the preset in VST3 and hope it works, but I prefer to do it manually (old school).

Maybe you could run your two computers alongside each other and do it that way, or install the VST2 versions on your new computer and remove them when done.

Others in these forums may offer a far better solution than I can. I'm not aware of any other way.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by jBranam on Tue Mar 28, 2023 8:21 am
well all the ones missing will show in red so they are easy to find but vst2 and vst3 are different formats which means they ARE different plugins (but your confusion is understandable) in the eyes of any program not just S1. sadly you will have to go in and replace the vst2 with vst3 versions then you will have to redo all the settings.

in this case here is what i would do...

i would install the vst2 versions you need temporarily to get things to work. then instantiate the vst3 versions and do all your previous settings or maybe just make presets of your vst2 settings per plug that way the vst3 versions should be able to load the presets which will save you a little time. then when all is done you can safely remove the vst2 versions leaving only the vst3 versions. that way you can always go back to the project in the future.

or the simple fix is to just install all the vst2 versions and finish the project but that will not help in the future unless you want to leave all the vst2 versions on the computer.

i too am trying to get transitioned over to only vst3 when possible

“Life is so constructed, that the event does not, cannot, will not, match the expectation.”

Knot Hardly Productions
¯\_ { ͡• ͜ʖ ͡•} _/¯
User avatar
by neurolepticofficial on Tue Mar 28, 2023 8:52 am
bailatosco wroteI THINK this is the expected behavior. Do you use another DAW that doesn't behave like this?

I don't use any other DAW, but it seems it's the expected behaviour indeed according to the other answers.

Thank you all for your help and suggestions. It seems all this needs a bit of work and time then, but moving to VST3 will probably be worth it for the future !
User avatar
by jBranam on Tue Mar 28, 2023 9:06 am
yeah it will eventually... they will be phasing out vst2. might as well get over the humps now as opposed to later ;)

cheers

“Life is so constructed, that the event does not, cannot, will not, match the expectation.”

Knot Hardly Productions
¯\_ { ͡• ͜ʖ ͡•} _/¯
User avatar
by AAV on Tue Mar 28, 2023 9:41 am
jBranam wroteyeah it will eventually... they will be phasing out vst2. might as well get over the humps now as opposed to later ;)

cheers


Still a lot of small vst producers who haven't jumped to vst3 yet. And Steinborg (!) have been (deliberately?) vague on details pertaining to their sdk for vst3 while simultaneously dropping support for VST2 in Cubase. I have several multi output vsti's in vst3 format where aux I/O are not recognized in Studio One due to disagreement between the developers on what Steinberg means. For others the VST2 still behaves better/more reliably.
So I install both the VST2 and the vst3 versions here and use whatever works "better". Fortunately they don't take a lot of room so I don't personally consider it a big problem. I prefer the option to try a VST2 for example if I have a particular vst3 is giving me a problem, or vice versa. (Just my opinion- but the problem with some multi output vsti3's in Studio One is real (not picking sides between DAW and plug developers).

Studio One 6.5.2 Pro, Audient ID4 mark II,
Gigabyte Designair Z390, 32GB DDR4 3200, Intel i9-9900K 4.8 GHZ, 2 TB & 1 TB SSD, 3 x 1TB 7200 rpm HDD, Windows 11 Pro 64 22H2
User avatar
by Vocalpoint on Tue Mar 28, 2023 9:52 am
AAV wrote Still a lot of small vst producers who haven't jumped to vst3 yet. And Steinborg (!) have been (deliberately?) vague on details pertaining to their sdk for vst3 while simultaneously dropping support for VST2 in Cubase.


Once Steinberg rolls out Cubase 13 and the next major version of Nuendo - I would expect VST2 to be gone completely and once that happens - these small VST producers will either need to get in line with VST3 or pack up shop.

VST2 (as a format) will be dead and gone to Steinberg by the end of 2023 as previously announced.

I also expect we (S1 users) are at moving to the end of this too - fair to say the v6 lifecycle for Studio One will continue to support VST2 and then it's gone for us.

VP

DAW: Studio One Pro 6.5.1.96553 | Host OS: Windows 10 Pro 22H2 | Motherboard: ASUS PRIME z790-A | CPU: Intel(R) Core(TM) i5-13600K | RAM: Corsair Vengeance LPX 64GB | Graphics: Intel UHD 770 (HDMI) | Audio Interface: RME UCX II (v1.246) | OS Drive : Samsung 990 PRO (1TB) | Media Drive: Samsung 970 EVO Plus (500GB) | Libraries: Samsung 970 EVO+ (2TB) | Samples : Seagate FireCuda (2TB) | Monitoring: Presonus Monitor Station v2 + Presonus Eris 5 | MIDI Control: Native Instruments Komplete S61 & Presonus ATOM
User avatar
by jBranam on Tue Mar 28, 2023 10:13 am
yeah no one really knows the end of vst2. i am sure it will linger for quite some time but it is coming eventually.

and yeah that is what i did on my last sys... installed both vst2 and vst3 just in case... but with this new sys i am only installing vst3 versions where available. i think i have less than a dozen plugs and instruments i use that still only offer vst2 versions lol so you see there WILL BE stragglers.

cheers

“Life is so constructed, that the event does not, cannot, will not, match the expectation.”

Knot Hardly Productions
¯\_ { ͡• ͜ʖ ͡•} _/¯
User avatar
by Vocalpoint on Tue Mar 28, 2023 11:28 am
jBranam wroteand yeah that is what i did on my last sys... installed both vst2 and vst3 just in case... but with this new sys i am only installing vst3 versions where available. i think i have less than a dozen plugs and instruments i use that still only offer vst2 versions lol so you see there WILL BE stragglers.


While I am looking at a full summer refresh of my main DAW - in Studio One using Plug-In Manager - I have hidden ALL VST2 plugs that are still on here so there are no chances of any VST2 slipping into a project that may take a while to wrap up.

It will be VST3 only for the new build this summer.

VP

DAW: Studio One Pro 6.5.1.96553 | Host OS: Windows 10 Pro 22H2 | Motherboard: ASUS PRIME z790-A | CPU: Intel(R) Core(TM) i5-13600K | RAM: Corsair Vengeance LPX 64GB | Graphics: Intel UHD 770 (HDMI) | Audio Interface: RME UCX II (v1.246) | OS Drive : Samsung 990 PRO (1TB) | Media Drive: Samsung 970 EVO Plus (500GB) | Libraries: Samsung 970 EVO+ (2TB) | Samples : Seagate FireCuda (2TB) | Monitoring: Presonus Monitor Station v2 + Presonus Eris 5 | MIDI Control: Native Instruments Komplete S61 & Presonus ATOM
User avatar
by jazzundso on Tue Mar 28, 2023 11:51 am
neurolepticofficial wroteOk so I have a new computer with a fresh system and I installed all the plugins I could in VST3 when I had the choice.
Thing is, I used to work with VST2 versions of some of those plugins in multiple song projects.
When I open one of those projects, Studio One 6 marks them as missing, even though their VST3 version is installed.
To be more specific, VST3 plugins work fine on their own, I can use them. The issue is Studio One doesn't seem to "link" the previously VST2 versions I used in projects to their newly installed VST3 equivalents.

Yes, that's the correct behavior. Studio One can't make the link between a VST2 plug-in and its VST3 version. This has to be supported by the plug-in by using the same VST UIDs. Otherwise, if the plug-in didn't support this and Studio One still used a different variant of the plug-in, your plug-in preset data saved within the song with be lost.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate

11 posts
Page 1 of 1

Who is online

Users browsing this forum: Demious, iliravdyli and 63 guests