N.I. Kontakt goes VST3

[attention ♥]

I should have addressed it directly to the peanut gallery. They're the only ones who read my posts anyway. (I suspect my shrink reads some of them, and mercifully gives me a discount when I make sense...)

On a serious note public internet spaces may not be the best place to be at. Stay around people you know and trust if you're able to.

[pixel85]

So for some it's not deleting vst2 and for some it does? Looks like Native Access has some clever AI that recognises who want to keep vst2 who doesn't

I got info in update notes that vst2 will be deleted and indeed, less and less dlls in my vst2 folder.

[Sindikhate]

I wonder if NI may decide to jump into MX2 altogether...

Woot?... Why? MX is a mere 2 years old.

Sure, but I bet it'll at least 3 years old when a big update arrives. I wonder, given how competitive this market has become, if wouldn't be smarter to just release it as version 2. Just look at Pigments!

When people come up with ideas such as "they should release a new version number of the synth!" I instantly think they have some sort of financial fetish where their pockets get emptied for a v2 v3 v4 and so on while the updates and maintenance could still be happening on v1 FOR FREE!

I wonder if people think before they suggest such stuff.

[Sindikhate]

So for some it's not deleting vst2 and for some it does? Looks like Native Access has some clever AI that recognises who want to keep vst2 who doesn't

I got info in update notes that vst2 will be deleted and indeed, less and less dlls in my vst2 folder.

Were you using 32bit versions at all?

[xbow]

So for some it's not deleting vst2 and for some it does? Looks like Native Access has some clever AI that recognises who want to keep vst2 who doesn't

I got info in update notes that vst2 will be deleted and indeed, less and less dlls in my vst2 folder.

Were you using 32bit versions at all?

Vst2 and 32 bit are not the same thing, there are 64bit VST2 and 32bit VST2.

The updates remove the 32bit versions.

[Sindikhate]

So for some it's not deleting vst2 and for some it does? Looks like Native Access has some clever AI that recognises who want to keep vst2 who doesn't

I got info in update notes that vst2 will be deleted and indeed, less and less dlls in my vst2 folder.

Were you using 32bit versions at all?

Vst2 and 32 bit are not the same thing, there are 64bit VST2 and 32bit VST2.

The updates remove the 32bit versions.

I never said they are the same. I only asked if he used 32bit versions as the update removed them if I am not wrong.

[xbow]

I never said they are the same. I only asked if he used 32bit versions as the update removed them if I am not wrong.

My remark wasn't aimed at you specifically. Somebody earlier stated vst2 are removed without making the distinction and this seemed to cause some confusion, including the post by pixel85 that you quoted.

[chk071]

So, I guess what pixel85 really meant was that the 32-bit versions of the plugins are being removed?

Sounds like a plus for me. I never liked it that the 32-bit versions get installed by default. I don't use 32-bit.

[4damind]

For me, at least with missing 32bit versions, it shows a "Repair" as status. Apparently they are still expected?

This "Native Access" tool is crap... For me many plugins are on "Repair" status, an option what to install exactly (64Bit/32Bit VST2/VST3) is not there either.
This reflects a bit the current state of NI. I almost suspect that they have their best time behind them. Much is outdated, other poorly implemented and really new from their own development is not there for years.

[pixel85]

So, I guess what pixel85 really meant was that the 32-bit versions of the plugins are being removed?

Sounds like a plus for me. I never liked it that the 32-bit versions get installed by default. I don't use 32-bit.

Yep, that's what I meant I shouldn't write when I'm drunk

Sorry for causing confusion.

[xbow]

For me, at least with missing 32bit versions, it shows a "Repair" as status. Apparently they are still expected?

I had this issue too after manually deleting 32bit versions (before the vst3 updates came). It wasn't much of a problem though, besides the status in Native Access. With the updated products, that does not seem to be an issue any more.

[chk071]

So, I guess what pixel85 really meant was that the 32-bit versions of the plugins are being removed?

Sounds like a plus for me. I never liked it that the 32-bit versions get installed by default. I don't use 32-bit.

Yep, that's what I meant I shouldn't write when I'm drunk

Sorry for causing confusion.

No worries.

[chk071]

For me, at least with missing 32bit versions, it shows a "Repair" as status. Apparently they are still expected?

Did you remove them manually? I don't see an option to not install the 32-bit versions, when you install plugins via Native Access... If there were 32-bit plugins on your system, and you manually removed them, then it's no wonder that Native Access shows a "repair" status, because, obviously, it expects them on the hard disk, when they have been installed.

Not a fan of Native Access either, and, it caused a lot of issues for me, but, the thing you describe seems normal and expected to me.

[4damind]

Yes unfortunately there is no option for this, I manually removed the 32bit versions. This of course does not remove any settings or entries in the registry. therefore surely the status "Repair".

[jancivil]

only thing I recognize regarding 32-bit is Reaktor 5 won't authorize here. NA sez it can't install it but does, with no avenue for activating it with Service Center - wait there's two - as no-exist.
doesn't matter. the only things which read "Repair" are things I have activated in the past but don't have installed, or reside on a drive that isn't always connected.
it appears to do different things on Mac vs Windows; nothing 32-bit is possible here, you'd have to go back a couple iterations.