NI go VST 3

[chk071]

A few plugins' installers let you choose where to install the VST3, but, that's rather the exception.

That said, I'd always opt for a bigger system drive. It's not only an issue with VST3, but, many application put their libraries to the user's Documents or AppData folders. Or... you install Visual Studio, and all those libraries get installed to C anyway. In my experience, it's bet to have 256 GB for the C: drive, better 512 GB.

My next PC will probably have a 1 TB SSD, so, I won't have issues in that regard anymore. I used to have a 100 GB SSD for C: in my current PC, and, that was pretty hopeless...

On the topic, it's nice to see NI migrate all their plugins to VST3. Also the older ones. Great to have resizable GUI options for Replika XT as well!

[thecontrolcentre]

I just updated Raum but got no choice about install locations. Native Access put the vst2 in C:Program Files/Native Instruments/VSTPlugins 64 bit. The vst3 went where I expected. I cant find any option to update my other NI products, Replika, Supercharger & Driver

[BJ]

Battery 4 was also updated but no vst3?

[LoveEnigma18]

Great to have resizable GUI options for Replika XT as well!

Is it? Well, I missed that. Really nice. Next year will be interesting and perhaps they are targeting Komplete 14 for getting these things ready for most plugins if not all.

[chk071]

I just updated Raum but got no choice about install locations. Native Access put the vst2 in C:Program Files/Native Instruments/VSTPlugins 64 bit. The vst3 went where I expected. I cant find any option to update my other NI products, Replika, Supercharger & Driver

You can set the install location in Native Access. I guess you'll have to reinstall Raum after that though. I don't think it moves already installed plugins after you changed the location. Not sure though.

[EvilDragon]

VST3 folder can be moved anywhere you want by using symbolic links. I have all my VST3s on D: drive, away from system NVMe SSD.

You create your VST3 folder on your non-system drive, then create a symlink to that folder and place it instead of the VST3 folder in C:\Program Files\Common Files\

Useful tool for creating symlinks via context menus: https://schinagl.priv.at/nt/hardlinkshe ... nsion.html

[dannyhawaii]

I see they've updated a few more plugins to VST3, some with nice new resizable GUIs, like the distortions and modulations

Mod Pack and Crush Pack were resizable since their initial releases.

[aMUSEd]

I'm pretty sure that's not what's gonna happen. Non-NI plugin VST3 support is a given to happen at some point.

Then why do they only allow their own vst 3 plugins in Maschine and not open for other vst 3 plugins?

Because they want to make sure it works first with plugins they know inside out before opening it up to anything

Do you have any source for this information?
I find it weird that they add vst 3 support only to test their own plugins as they keep adding them.
After they added a few of them like they have now the vst 3 implementation should already be good to go.
Testing the vst 3 implementation by only locking it to their own products seems abit fishy to me but i hope you and Mr. E Dragon are correct and i am wrong on this one.

I have never seen other Daws doing this when they added vst 3 support.

I think you have to bear in mind NI have some very specific challenges moving over to VST3 - not only do they make plugins, they also make hosts (Komplete Kontrol and Maschine), but those hosts are not your standard 'DAWs', rather they are designed to have very tight integration with their plugins through the NKS 'ecosystem', where they function as librarians and controllers for the whole of NI's catalogue, as well as instruments and production tools. I guess this is one reason why it took them so long - they almost painted themselves in a corner by tying NKS to VST2 but now need to carefully get themselves out of that. So they need to test thoroughly the process of shifting their plugins to VST3, and making their hosts and NKS work nicely with that, because clearly their aim is for clicking on any NKS preset in KK and Maschine that previously loaded a VST2 version to now load a VST3 version of the same plugin. This makes sense from a future proofing standpoint. So for now they want to gradually get their whole ecosystem working smoothly first before opening it up to third party plugins, which they can't entirely predict the behaviour of or troubleshoot internally when things don't work.

[chk071]

VST3 folder can be moved anywhere you want by using symbolic links. I have all my VST3s on D: drive, away from system NVMe SSD.

You create your VST3 folder on your non-system drive, then create a symlink to that folder and place it instead of the VST3 folder in C:\Program Files\Common Files\

Useful tool for creating symlinks via context menus: https://schinagl.priv.at/nt/hardlinkshe ... nsion.html

Good stuff.

I just took a look though, and my VST3 folder is avout 2.11 GB. No real reason to move it here.

[EvilDragon]

Well, there are a few very good reasons. Having an enforced path is better for proper content placement. There were far too many "I installed this plugin but I don't see it in my DAW" type of issues with VST2 throughout the years.

Plus, it's nothing new, either. AAX and AU also have enforced plugin paths and nobody objects there.

[Echoes in the Attic]

I'm pretty sure that's not what's gonna happen. Non-NI plugin VST3 support is a given to happen at some point.

Then why do they only allow their own vst 3 plugins in Maschine and not open for other vst 3 plugins?

Because they want to make sure it works first with plugins they know inside out before opening it up to anything

Do you have any source for this information?
I find it weird that they add vst 3 support only to test their own plugins as they keep adding them.
After they added a few of them like they have now the vst 3 implementation should already be good to go.
Testing the vst 3 implementation by only locking it to their own products seems abit fishy to me but i hope you and Mr. E Dragon are correct and i am wrong on this one.

I have never seen other Daws doing this when they added vst 3 support.

I think you have to bear in mind NI have some very specific challenges moving over to VST3 - not only do they make plugins, they also make hosts (Komplete Kontrol and Maschine), but those hosts are not your standard 'DAWs', rather they are designed to have very tight integration with their plugins through the NKS 'ecosystem', where they function as librarians and controllers for the whole of NI's catalogue, as well as instruments and production tools. I guess this is one reason why it took them so long - they almost painted themselves in a corner by tying NKS to VST2 but now need to carefully get themselves out of that. So they need to test thoroughly the process of shifting their plugins to VST3, and making their hosts and NKS work nicely with that, because clearly their aim is for clicking on any NKS preset in KK and Maschine that previously loaded a VST2 version to now load a VST3 version of the same plugin. This makes sense from a future proofing standpoint. So for now they want to gradually get their whole ecosystem working smoothly first before opening it up to third party plugins, which they can't entirely predict the behaviour of or troubleshoot internally when things don't work.

I'm not sure if NI could even match the VST3's to the former VST2 presets? No other DAWs can do this as they are totally different plugins. Plus plugins that have NKS presets are all coming out with VST3' at different times. But I guess it's possible that as they are released NI will manually match them up, but I doubt it. I would think they'd lave it to the plugin devs to provide updated VST3 versions of the NKS presets. So NI would just have to provide VST3 compatibility. Come to think of it, I hadn't noticed what NI are doing with their own internal VST3's as far as NKS presets. I see that both versions of NI plugins are listed in the menu. But do the NKS presets for Massives and Kontakt and effects now use VST3?

[aMUSEd]

I'm pretty sure that's not what's gonna happen. Non-NI plugin VST3 support is a given to happen at some point.

Then why do they only allow their own vst 3 plugins in Maschine and not open for other vst 3 plugins?

Because they want to make sure it works first with plugins they know inside out before opening it up to anything

Do you have any source for this information?
I find it weird that they add vst 3 support only to test their own plugins as they keep adding them.
After they added a few of them like they have now the vst 3 implementation should already be good to go.
Testing the vst 3 implementation by only locking it to their own products seems abit fishy to me but i hope you and Mr. E Dragon are correct and i am wrong on this one.

I have never seen other Daws doing this when they added vst 3 support.

I think you have to bear in mind NI have some very specific challenges moving over to VST3 - not only do they make plugins, they also make hosts (Komplete Kontrol and Maschine), but those hosts are not your standard 'DAWs', rather they are designed to have very tight integration with their plugins through the NKS 'ecosystem', where they function as librarians and controllers for the whole of NI's catalogue, as well as instruments and production tools. I guess this is one reason why it took them so long - they almost painted themselves in a corner by tying NKS to VST2 but now need to carefully get themselves out of that. So they need to test thoroughly the process of shifting their plugins to VST3, and making their hosts and NKS work nicely with that, because clearly their aim is for clicking on any NKS preset in KK and Maschine that previously loaded a VST2 version to now load a VST3 version of the same plugin. This makes sense from a future proofing standpoint. So for now they want to gradually get their whole ecosystem working smoothly first before opening it up to third party plugins, which they can't entirely predict the behaviour of or troubleshoot internally when things don't work.

I'm not sure if NI could even match the VST3's to the former VST2 presets? No other DAWs can do this as they are totally different plugins. Plus plugins that have NKS presets are all coming out with VST3' at different times. But I guess it's possible that as they are released NI will manually match them up, but I doubt it. I would think they'd lave it to the plugin devs to provide updated VST3 versions of the NKS presets. So NI would just have to provide VST3 compatibility. Come to think of it, I hadn't noticed what NI are doing with their own internal VST3's as far as NKS presets. I see that both versions of NI plugins are listed in the menu. But do the NKS presets for Massives and Kontakt and effects now use VST3?

As the link says they are already doing it - if you load a NKS preset now for Kontakt in Komplete Kontrol it opens the VST3 instead of the VST2, and same for the new VST3 versions of the Massives and I presume the FX too (harder to tell as I can't display their 'about' screen that shows the plugin type in KK). So far this has worked smoothly for me. I'm pretty sure this is possible with the NI range because they all use the same shared KK/Maschine readable preset format (variations on .nksf) whether VST2/3 or AU version. Clearly this is not a case of someone at NI having gone through each preset and resaved it because it works for imported third party Massive presets and my own too, and also for some third party Kontakt libraries I had imported, so I guess this is more a case of the host substituting the VST3 version for the VST2 (KK already had something similar with the 'prefer latest version' option in settings for people with Reaktor 5 and 6 or earlier versions of Kontakt on their systems and I can think of a couple of DAWS that allow one to prefer the VST3 version over the VST2 when you have both).

Whether this will be the case for third party VST3 plugins when opened up though is still an open question - I can imagine all sorts of complications potentially, if NI pull it off as well as their own internal transition seems to be going so far then hats off to them. I can certainly see why they want to start with doing it all internally first though.

[aMUSEd]

Komplete Kontrol and Maschine are released to day with VST3 support on the host side finally implemented (and Apple Silicon). I have posted this on the NI forum too - a pack of templates made to create NKS versions of various plugins that are VST3 only or VST3 preferred on MacOs

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

[soulata]

I've plenty of NI's 32bit plugins installed. It's probably safe to delete those.

Any other cleanup ideas concerning NI?

[aMUSEd]

I've plenty of NI's 32bit plugins installed. It's probably safe to delete those.

Any other cleanup ideas concerning NI?

Well don't ditch the VST2 versions yet as not all migrate from VST2 to VST3 seamlessly. It's on the developers to implement that, some have but many haven't