Is it safe to install KK 3.2.0 yet?

I've been running 3.20 flawlessly on my Windows 10 with Ableton even using my S88 MK3 for the last month or so. However, I've gotten rid of my previous version of KK and Kontakt 6 in order to not have any problems with trying to load VST2's into 3.20 project. For me it's just simpler and more bulletproof to do it that way. If I encounter and older project that used the previous version it shows up with the KK track showing a missing plugin. So it's very easy to replace it with the new KK and instance of the library and everything's working again and updated.

No, not what I said at all.

Of course you can browse presets but it is different in how it works than KK V2 which if you have used something for 10 years, daily, and then have the whole way in which you used it changed, it does not sit well.

The design of the new KK is based more on what suits the developers than the users and as usual, long time users are never top of the list of concerns, only new fresh blood is the target.

The browser is now a separate "panel" which you have to switch to and it is overlayed where the plugin is so you cannot browse presets AND view the plugin at the same time. THis was something many of us users likes to be able to do, it was fast and efficient to switch presets, test and adjust a few things all on-screen but now it is a constant back and forth hassle.

The second issue with this is that it use to be possible to browse your samples and one-shots and drag these into plugins like Battery to build kits. THis is now impossible to do.

The third is now the browser is a horizontal scrolling browser across the screen instead of a list vertically. When you want to scan a list of hanes it is proven to always be faster to scan down a page rather than a scrolling list across the page, so that too is now a major frustration.

Seems every time we ask if this will all be addressed it's basically ignored which means it will never improve. A few people dont mind but any serious user who has used KK for years likely finds it annoying AF.

So yes you can browse, but as I mentioned IMO the single strong function KK had has now been crippled worse than timmy.

To answer the OP, I'll put it this way:

1. If you have a heavy dependency on how things "used to work", then no. Maybe keep V2 for awhile longer. We're STILL only seeing 1 update each month. Even though they're fixing 5-7 items with each update, it's really only 5-7 items each month. That's a rapid pace, but in the face of the sheer number of issues, it's kind of slow (even if it IS the fastest anybody can work). So we may be not quite there yet, but there should be another release this week or next, if they're trying to keep the same rhythm.
2. But if you're like me and you have virtually ZERO dependency on how "things used to work", AND if you have a MK3 keyboard, then I say yeah, go for it. Just ignore all the stuff that's not there anymore, and start using the application and the sounds. You can make music with what you have or you can talk about not making music with what you don't have (or what you lost). It's up to you.

I value the old version and all of the stuff it used to do. I value what people did to contribute to the community with those old versions. But the fact is, I basically have zero need for the old ways RIGHT NOW, so I've moved to V3 and I don't plan to go back.

I just wish the fix pace was faster. But at the same time, I'll be the first to say that "Agile" development practices almost NEVER can make a bad release better. And this WAS a bad release, mostly because too many things didn't work and/or bricked too many units, and also because too many features were removed without a proper vetting between the V3 designers and the user base.

I know, I know, NI says they went off of the usage statistics to make a lot of decisions. But it may also be possible that NI is over-relying on the usage statistics being collected, while simultaneously UNDER RELYING on conversations with the user base.

It should also be noted that users can optionally turn OFF those statistics, and if a lot of people did that, then the NI designers might not be getting a true perspective. There's no substitute for TALKING TO EACH OTHER. The good news is that NI, at all levels of leadership, appears to be communicating much better and much more effectively now, so I'll take that as a silver lining.

I wasn't looking for an apology, and you certainly don't owe one to me or to anybody else as far as I'm concerned.

I was only suggesting that your reader of that prior post (SF_Green in this instance) took your meaning based on your wording, which you admit is based on your long-term disappointment, which is great indeed.

So yeah...message received (on the other person's part). But then you had to spend valuable time to correct his/her misinterpretation and re-center the discussion. All I'm suggesting is that maybe your wording sometimes does that...takes the conversation off-target, and that requires you to re-word yourself in order to feel like you were properly understood.

Even in your disappointment, you still want to be properly interpreted and understood. Anybody can see that that's important to you; hence my attempt to put all of this into words for you.

Again, no apology needed or intended. Only my respect.