KK 1.5 update available from NI Service Center.
 
If you have a KK S series controller there is also a firmware 67 update in the downloads area of the NI website.
http://www.native-instruments.com/en/support/knowledge-base/show/1058/how-to-update-the-firmware-of-your-ni-audio-interface-or-controller/
 
Read the read-me.txt prior to install...
 
After KK 1.5 is installed you may need to update the locations of your vst's and re-scan for things to load properly.

I knew they would do this since the Controller Update came out this morning...
Of course they couldn't do BOTH at the same time 

- I'm still not sure if they are finished yet. The KK 1.5 update may force some other NI provided instrument updates... The price of progress?

I'm sure they're not...but nothing showing up yet....YES
most definitely the price...

I did the update and now I'm getting "Loading Issue. Could not load Plug-in" when choosing a preset.
NI knowledge base says I'm getting the error because I've moved my NI plug-ins after the initial installation.  
Which I haven't.

So now it looks like I'll have to relocate the NI plug-ins using an NI relocation tool and then change how Sonar finds the plugs.

Anyone run into this?
 
Bjorn

I see they've also come out with a weighted action 88 board so I'm pondering the situation. Would like to know how "in kontrol" these things really are.

bjornpdx
I did the update and now I'm getting "Loading Issue. Could not load Plug-in" when choosing a preset.
NI knowledge base says I'm getting the error because I've moved my NI plug-ins after the initial installation.  
Which I haven't.

So now it looks like I'll have to relocate the NI plug-ins using an NI relocation tool and then change how Sonar finds the plugs.

Anyone run into this?
 
Bjorn

I ran into it and discovered that KK did not pick up my vst scan locations properly. IIRC, I had to go into the prefs and delete the bad scan paths and add the proper vst scan paths. I then had to click the re-scan button and everything came back up properly. YMMV

I ran into it and discovered that KK did not pick up my vst scan locations properly. IIRC, I had to go into the prefs and delete the bad scan paths and add the proper vst scan paths. I then had to click the re-scan button and everything came back up properly. YMMV

 
 
Thanks, I got it running. I didn't notice the Preferences menu.
 
Bjorn

Glad you got it sorted!

Had the same issue....but dumping the existing (wrong) paths 
and adding the correct ones seems to have fixed it.  They must
have messed something up...but it's sorted...