I think you might be my Kontakt-twin I have the latest HCiSO running as well, though I'm a little over 250 libs (there might be 350) and I'm not going to update to K8 unless there's a working Fred Blogg's app that provides the opportunity. Anyways....the mutual update to 14.7.2 and not properly functioning KLU can't be a coincidence I think....

 

Hello than to my Kontakt twin! . Hmm.. Yeah, I'm not sure what the issue is here for you, as other then our chipset, we pretty much have the same scenario, but I'm not experiencing problems with KLU2, or it's audit, just slow populating search fields and whatnot in the Kontakt 7standalone app itself, but NOT in using the plugins au or vst3 in a host daw ... (and just so specifics are given, I'm still using the second to last HCiSO release in 7.10.6 (as there was some issue I believe I read or whatnot that was probably a pebkac for someone else, and I intend to update soon))...

so that is something I can live with, (as I generally just adhere to the practice of checking new libraries after adding via KLU2 in standalone prior to daw instantiation as it has been advised) .... I just don't know why its having that issue, which always is gonna bother me lol, but yeah, it did correspond to the same day I updated Sonoma to 14.7.2, ...so maybe there is something there, despite the fact our issues are different. I will check again later.

I'm just curious as I haven't seen either issue reported by anyone else, and surely, even while Kontakt 8 is out, and perhaps many have made the move to Seqouia, I know many people who have remained in Sonoma land for now, and Kontakt 7 land for now as advised and been remarkably stable (outside of what our separate problems are! )

Happy Holidays to you, and thanks always to Fred Blogg's for providing us with this great tool, and I hope he is having a great festive season as well!

 

Thanks a lot!!

 

I've never heard that before - what are you checking for, and what do you do after the check? If this is something that's advised I'm wondering if it's why I sometimes have weird problems with KLU2 and certain libraries.

 

Yeah, I can't remember exactly where I read that, whether it was something mentioned by Fred Bloggs (which I doubt, as I imagine it would be in his FAQ's/Read Me's (which maybe is, but I haven't read in awhile, as haven't had need of late), or someone else whose opinion I respect... and I can't vouch for it's veracity in import, but I will say I have had little to no problems adhering to a particular order of operations, some of which may be superfluous, some aren't, and perhaps a little over OCD, but with a new system and coming from many older systems and having libraries dating decades... this is what I do if I have a library I want to test or add via KLU2:

1. Open KLU2 and let it perform it's audit, read audit to see if anything is 'off'...

2. I usually only add a library or two at a time, and do so via KLU2 (and while tools exist to add artwork and change snipd's or create ninct files etc... I don't futz with that, as Talula and other providers have made some good arguments about how it could possibly lead to future problems so..).

(and note, I don't use the 'new' NI library view, as I'm used to the sidebar version, and despite the fact they have neutered certain navigational tools since v6 in establishing certain locations on different drives etc, I've come up with less elegant, but functional workarounds... although at some point I should probably invest a little time with the 'new' view, as I imagine it's not going away, although they tend to find a way to f up everything, and if set up properly with some time, could ultimately make my workflow faster.... (but having been burnt before by them with now extant features or ecosystems like Kore1/Kore2/Maschine central whatever etc.. I'm not to skippy on spending a lotta time invested on that..)

3. Close KLU2, and open standalone Kontakt. Go to library, open it, insure briefly that it is operating correctly and artwork and gui's are all fine, snapshots or whatever in place.

4. close then and open whatever daw, open the Kontakt vst3 or au and proceed with fun time.


Doing so, I've had everything of late work, the only issues I've had have been with some pre-ninct libs etc, or some other ancient relics etc.

And other things, like if I change locations of libraries from one drive to another, I always uninstall it via KLU2, and then reinstall in from its new location etc. The bulk move install/uninstall functionality may work just fine, I've never had to use it personally, and due to NI changing certain things under the hood that Fred Bloggs himself acknowledges he has to take a closer look at, and seeing others having issues with Kontakt 8 in some instances, whether self inflicted or something else, I've stayed on Kontakt 7.10x currently, as working just fine.

 

Hi Maybe I am stupid dog, I was able to run utility but I do not know how to fix all libraries that are shown in the list but not appearing in running kontakt app. Is there a button or so that can be used? I have read manual twice but I do not see that . Thanks for help

 

@Fred Bloggs KLU doesn't show any of my legit libraries that I have installed via Native Access. Is that normal?