With support for VST2 now ending, that’s not going to get any better. But backwards compatibility is always an issue, and everybody knows that trying to open older DAW projects can be a huge PITA. What do you think? I’m a bit torn – I’m not usually one to oppose change, and I think it’s understandable that Steinberg wants to move on and devote the resources needed for VST2 support to new developments, especially since VST3 has been around for so long. Users on the Steinberg forum were quick to compile a list of plug-ins that have yet to transition to VST3. As of now, it looks like those will become obsolete for good when they’re no longer supported in Steinberg’s host applications. The problem is, if you’re like me, you probably have a couple of older plug-ins in your plug-in folder whose developers have discontinued support or – even worse – ceased to exist. There’s hope that those that have yet to transition to VST3 will do so in light of Steinberg’s announcement. So what does this mean if you rely on VST2 plug-ins for your workflow? I think that most popular plug-ins by major developers shouldn’t really present an issue. Within 24 months, all of Steinberg’s hosts and plug-ins will support VST3 only. Meanwhile, Cubase and the company’s other host applications continued to offer support for VST2 plug-ins, and Steinberg also continued to compile VST2 versions of some of its own plug-ins like HALion, for example. To my knowledge, Steinberg hasn’t given out VST2 licenses to new developers since at least 2018. But some developers have been slow to adopt the new platform, even though the VST2 SDK (software development kit) hasn’t been updated in a long time. Which shouldn’t come as a surprise, as VST3 has been around since 2008 – an eternity in the world of software. It’s long been known that Steinberg was moving towards supporting VST3 only. Steinberg announced yesterday that it plans to phase out support for VST2 plug-ins over the next 24 months, marking the final step in the transition to VST3. With support for VST2 now ending, that’s not going to get any better.If you’re still using VST2 plug-ins in Cubase, Nuendo, Dorico or Wavelab, it’ll soon be time to switch to VST3 for good.
If you’re still using VST2 plug-ins in Cubase, Nuendo, Dorico or Wavelab, it’ll soon be time to switch to VST3 for good. Furthermore, Steinberg’s own plug-ins will be available as VST3 versions only. This means that you’ll no longer be able to use VST2 plug-ins in upcoming versions of Cubase, Nuendo, Dorico and Wavelab.
If you buy a new DAW and need to set it up, simply define this folder as your Plug-in folder and all installed Plug-ins from all manufacturers should be visible for your Software.
Universal audio plugins are not in steinberg folder install#
'DAW Plugins' and install all your Plug-ins inside this folder. Steinberg has announced that support for VST2 plug-ins will be phased out in its host applications within 24 months. Just create a new folder at a location where you don't stumble over it all the time, call it e.g.
0 kommentar(er)
