Izotope Vinyl now managed by Native Access - and after update/reinstall VST2 is gone :(

[Sahul]

VST3 specification was released already in 2008, and the latest update on the spec was in 2017, version 3.6.7.

VST3 is still in development. Latest update to the SDK was 3.7.9, released about one month ago.
https://forums.steinberg.net/t/vst-3-7- ... sed/872156

[sakarik]

VST3 specification was released already in 2008, and the latest update on the spec was in 2017, version 3.6.7. VST2 was made obsolete back in 2013; so it's been quite a long time already. It might be annoying, but this is how it goes..

Is this a valid reason for deleting VST2 plugins from my HD without any warning and information and breaking some projects in which I potentially use them? I don't think so.
Luckily I resisted updating my Komplete 13 to 14.

Where is it written that the update dismisses VST2?
I looked at the Vinyl release notes within Native Access before updating, no notice at all.

And... from here:

https://www.izotope.com/en/products/vinyl.html

VST2 is still mentioned.

"
System Requirements
Operating Systems:

Mac: macOS Big Sur (11.7.9), macOS Monterey (12.6., macOS Ventura (13.5)*
* Supported on Intel Macs & Apple silicon Macs (Apple M-series chips) in Rosetta 2 & native.
Windows: Windows 10 – Windows 11

Plugin Formats:

AU, AAX, VST2, VST3, NKS.

All plug-in formats are 64-bit only.

VST2 is Rosetta only on Apple silicon Macs."

Maybe is Native Access only supporting VST3 now?

- Mario

Noticed the later post which I have nothing to say about, the AU (i know nothing about au). But to this VST2 -subject. Steinberg has given transition time of 10 years to move ahead replacing VST2 with VST3; in software world it's quite long time; Everyone who has requested a license for software development kit for VST plugins after December 2013 have had no choice but to go with VST3, for example. Of course, big companies like NI ja Izotope do have the older license and sdk that supports VST2, but they might also have some clauses on supporting VST2. As an example it could be that they must stop supporting vst2 in some time period. But who knows, and they probably won't tell. Not a biggie, though. Nevertheless, 10 years is such a long time that everyone should know already that VST2 will be dropped out (sooner or later); and considering VST3 is supported about everywhere nowadays, dropping vst2 plugin would not be a big deal in that light; as VST3 will provide the same functionalty and maybe even more for some things. Respectful companies of course would inform if that happens and when it happens (seen this already here and there). And yes, i'd like to see support for CLAP more widely, but it'll take it's time.

[sakarik]

VST3 specification was released already in 2008, and the latest update on the spec was in 2017, version 3.6.7.

VST3 is still in development. Latest update to the SDK was 3.7.9, released about one month ago.
https://forums.steinberg.net/t/vst-3-7- ... sed/872156

Yeah of course it is in dev, it's the current. Thanks for the latest version update, though. They are not abandoning VST3

[mabian]

Not advocating against passing to VST3 in general (though personally I'm not keen on that either, VST3 is not superior to VST2, but that's another matter).

I'm simply saying they're wiping their own VST2 versions from the customer systems without any notice...

- Mario

[Frankie.T]

That's why i avoid DRM as much as i can, because you buy something you have no power on. They are just asking you money for a licence they can throw away when they want changing whatever they want. Then sometimes companies goes out of business, or just they got acquired or everything else that can bring a change.

When you buy something with an installer and a SN or a key file that doesn't require any server connection, you own that product. Ofc if they will change something, going out of business or whatever, you will have no updates but at least what you have stored is still working and available every new installation you do.

Then with this system i don't have other things i don't need installed and running on my pc

[diroxe7660]

I updated via Native Access today and I have an updated VST2 DLL (timestamped 27th October 2023) in "C:\Program Files\Steinberg\VSTPlugins\". I added the VST2 and VST3 versions to a track in Reaper and both seemed to work fine.

[mabian]

Ouch, I haven't tried this path... maybe being an Izotope installer it ignores the custom paths as set in Native Access...?

Thank you for the information.

- Mario

[EvilDragon]

I am sure that iZotope's Vinyl 1.12.1 installer for Windows contains a selectable checkbox for VST2.

Confirmed this here, it definitely does have it when you go for custom install.

[EvilDragon]

BTW Mabian - this was not an intentional decision. I passed the issue on and it's being investigated internally.

[mabian]

BTW Mabian - this was not an intentional decision. I passed the issue on and it's being investigated internally.

Confirmed: VInyl VST2 has been installed in "C:\Program Files\Steinberg\VstPlugins" disregarding my Native Access VST2 64 bit path settings: "M:\Audio\Plugins\VST_x64\NativeInstruments"

- Mario

[EvilDragon]

OK so what is happening here is that the iZotope installers are still using iZotope installer tech, which also means they are not hooked up to NA custom user path settings, instead they go to the default paths that iZotope plugins used since forever. It also only affects Windows users.

This is not something that can be immediately and straightforwardly fixed, so I suppose for the time being users who have custom plugin paths should be using installers from iZotope website, which allow you to enter a custom path for VST2 plugins.

There will be a knowledgebase article about this soon.

[lolilol1975]

edit: how do you delete a post in this forum ?