
Is the fact that the preset refers to a VST2 plugin hardcoded in the NKS format? If so, does that mean that all (hundreds of thousands of) NKS presets people will have need to be updated or is there something u-he can do @ their end?

Is the fact that the preset refers to a VST2 plugin hardcoded in the NKS format?
man, that sucks for you guys!tasmaniandevil wrote: Tue Nov 15, 2022 5:38 am nt, if you switch the NKS host to Rosetta mode, it will be able to load VST2 plugins, and everything will work again.
Right click on the application icon, select the info panel, then tick the check box to run in rosetta modeekwipt wrote: Tue Nov 15, 2022 11:35 amman, that sucks for you guys!tasmaniandevil wrote: Tue Nov 15, 2022 5:38 am nt, if you switch the NKS host to Rosetta mode, it will be able to load VST2 plugins, and everything will work again.
Is that a setting in Komplete Kontrol? I actually was searching the forum, because I booted up Maschine which I haven't used for a while, and was faced with the same issue.
Do you know if it's a setting in there, that I can change?
Also will u-he be porting NKS over to VST3 or AU Component?
as odd as this sounds, I hope they don't.
AFAIK they have no current plans to support CLAP. There's still hope though.
Very unpopular opinion you've articulated there, but just chiming in that I 100% agree.40watt wrote: Fri Nov 18, 2022 6:03 pm I can't help but feel that really you would not have this much technical debit if you hadn't gone off and invented your own plugin format with one DAW manufacture.
I have hardly been involved in CLAP's design process. A few meetings and a few more chats at best, but if you look at the pull requests in the repository, not a single one comes from u-he. It's mostly abique and a few people from the Open Source community.40watt wrote: Fri Nov 18, 2022 6:03 pm That sounds very like the hard sell to NI to support CLAP.![]()
However, here's where I bring up a matter that's been slightly irritating me recently, and I suspect I'll get shot down in flames by the Bitwig users but....
Recently I asked why MFM2 didn't have NKS support on release and was informed the goal was eventually to have all the instruments ported and it will be available at some point, in fact I got the singular impression that you would not be releasing any legacy updates with NKS until all the updates had been tackled due to "technical debit".
I also purchased Uhbik well about 3 years ago on the strength of some betas and while they are technical betas they are still very usable, but here's where I get a bit miffed....
I can't help but feel that really you would not have this much technical debit if you hadn't gone off and invented your own plugin format with one DAW manufacture. Yes, I get all the reasons why, but it really only helps Bitwig owners at the moment, and there are a vast number of non Bitwig users that having been patiently waiting for years, for promises like we fully support NKS and we hope to have this out in the next few weeks. I'm seeing regular CLAP updates on some instruments, so you guys are obviously busy, but is it on stuff you promised 3 years ago.... I don't think so.
I'm sorry I don't want to moan, I'm a big fan of your work, its great... and I understand the difficulties and frustrations, but I just can't help but feel just a little bit cheated recently and that's not a feeling I have ever had before from Uhe. Sorry and please feel free to tell me I'm wrong in every way as you're still my favourite developer.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026