Hello, thanks in advance for any help I might get here! This forum has been a lot of help over the years, I'm just a lurker usually. With that being said, I have quite a bit of experience with using different releases of Kontakt. I've made custom .nicnt's, .xml's, and I've also edited registry entries - all in effort to get libraries to work. Alas, I have finally found my match lol

I tried to add NOVO (modern strings) through the Bob Dule Kontakt 6.6.0 release, as shown here:

The library proceeds to add correctly:

Upon loading Kontakt 6.6.0, the library does not populate:

Checking the Library Manager within Bob Dules Kontakt interface, I find that NOVO is showing:

Checking KLM 3, I see that there is in fact no library registered as NOVO, and that the slot is somehow showing as open:

From here, I decided to do a hard code edit of the nicnt and xml files, as well as manually edit the registry entries accordingly (within these registry entries I made sure to input the proper snpid, HU, and JDX). I also checked within the Bob Dule interface to see if there were any SNPID duplications, and there aren't any. At this point in this post, I have ran out of image uploads, so I will share the code snips in the reply section.

At any rate, after editing all of the relevant files and reopening Kontakt I am once again greeted with no NOVO library. At this point, I deleted all of the registry entries as well as the xml.

I then decided to add NOVO directly through KLM. Upon opening up Kontakt, I found that NOVO had actually populated this time, and I could actually see the nki files. However, when I try to load one it gives me the classic: "this library is not activated" error. From here, I went into the code again, and made sure that the HU and JDX codes were in place within the registry. I then opened up Kontakt again, and found the same error was still present.

I then decided to use KLC to make a completely new nicnt: new library name, new registry location, ext... This library populated within Kontakt, but gave the same "this library is not activated" error. I once again added the proper HU and JDX - no luck. Reverting this nicnt to a new version of the one I had replaced (ie. changing it to be a fresh copy with the same SNPID as the base release of NOVO) also didn't fix things.

I have tried every combination I can think of to get this library to work, and nothing has proved truly fruitful yet... I tried to find a copy of Kontakt 5.6.6, to see if I could add the library the good old fashioned way, but I can't find a copy of 5.6.6 that actually installs correctly. I found 5.6.5 and got it working, but the associated 5.6.6 update ruins the install (and NOVO was made for the 5.6.6 release specifically).

I did find a portable copy of Kontakt 5.6.6, and I can actually get NOVO to work and play within that copy (since they use different source files, registries, and xmls), however it is very inconvenient to use it like that.

Anyone know what's going wrong here and how to fix it within Kontakt 6.6.0?

I think the issue is that the library isn't loading into the library manager correctly, but how would I correct this when KLM can't even do it? For reference, I have successfully added VENTO, FORZO, and the three NOVO packs.

 

Here are the code snips:

 

first I saw - you have old nicnt.



this is proper data for NOVO.nicnt:

Code:

  <Product version="14">
    <UPID>10a226f9-0503-4934-a49d-0978f968021a</UPID>
    <Name>NOVO</Name>
    <Type>Content</Type>
    <RegKey>NOVO</RegKey>
    <SNPID>358</SNPID>
    <AuthSystem>RAS3</AuthSystem>
    <Relevance>
      <Application minVersion="5.5" nativeContent="true">Kontakt</Application>
      <Application minVersion="2.4" nativeContent="false">Maschine</Application>
      <Application minVersion="1.5" nativeContent="false">KKontrol</Application>
    </Relevance>
    <PoweredBy>Kontakt</PoweredBy>
    <ProductSpecific>
      <HU>F865D68C8CFC720CBE4E4EDFCAB1982E</HU>
      <JDX>44429A4AC43EE7653363EF3FA63D95CCC6ABED005CE2FFEE71A33479B5596F45</JDX>
      <Visibility type="Number">3</Visibility>
    </ProductSpecific>
    <Company>Heavyocity</Company>
    <NKSEnabled>true</NKSEnabled>
    <Icon>
      <Data>iVBORw0KGgoAAAANSUhEUgAAAGQAAAAWCAYAAAA2CDmeAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAtJJREFUeNrsWIGNm1AMRacbgBHY4LJBGSGdIGQDboLQCdJMQDoB1wmgE3AbJBuQDShIRnp9sj8fktylLZasy/HB39/PzzY8BW5pRctgkXvJqtNG4nwKFkA+XWqI8/qjAUmW+P8hKcS46C88d5rJ4rnT44iBzLH21um7Yz3sdC+/KwDn0ul3j/3eZQ8N5EjxIRYd9niTM1rS37sBW8NzX2GfjfzeyllCz8D/UGLb77ODfbY+LOC11qG5BzuwTp7g2dhx/6ANBWuovy3YDeXayfCxUIIYyvmsc8WQHHitnagr2re0StWtAGmVgKEwABnT1eGwdV9NNrFBWloTKDWtn2TvQbMbAYLxXbvOPgeQAkoCqkXhteJcSMGLHJmvZRMGaCgfCHoGNldkI1ds1AZTAwMQ1JRs41oBaymdu9FiNgeQbGLzKo1SwEEdJFcCi4fgUTGkEpd5+BEBgM0IuzVAuP9YezMAxdhUhZmYkU4tWZpDK+oDyLKI1kLRVsmg1LATE4iNI6hrCoZv/7sGEK1CWGXaO8hTAOGA5ETZmrIU1xMHazSm7ZW1sREdAzeF8dcAEhAzGqu8P8+cn/ux9ZdjPZIRM6Lx9ih/h4zsx75vcM+O7Bzo/y1MaRd5FkfUQJlmmK04Rg/y5QPeOQ5Qoirw18yYWmlW1/aQPWVFqWR5ZPSYfOLLakpMHMtS3je+M0Ni3/jdq6mHHiMoTiW+I7TlL++XEmNz5dmYEib5bEDmlqyNB81DqJN9efhJ6ztoeK9C4xgofZ7o0/C2WwA791A6A+WtuJIymoivuWhllOFbycutGTJVtXLAo23iWT7Gvq+tHcwsjR6zv/I8UxlSzmVIRQ2wmpENF+O5A2Tdixxk57jf8kn7plYJMBE9Z9l9FX8SzwbPDfkMts/X0ueRPrEn//AX4djnHeT5wZw+Bv+HmF+Jn4JFHkoWQBZAFlkA+YvktwADADxhK0T79Q9qAAAAAElFTkSuQmCC</Data>
    </Icon>
  </Product>

 

Did you try updating Native Access?

If your <SNPID> matches then 99% of the time it can be solved just by updating the Native Access.

 

Thanks for the example code from your library Talula, I appreciate the help! I replaced the code in my nicnt and xml files, and double checked my registry entries, the library is still missing from Kontakt. I removed the library as well and redid everything to no avail. It's sadly still doing the same thing it was doing in my original post.

Thanks for the reply, I appreciate the assistance Claude! Here is the code within my NativeAccess.xml:

Code:

  <Product version="14">
    <UPID>10a226f9-0503-4934-a49d-0978f968021a</UPID>
    <Name>NOVO</Name>
    <Type>Content</Type>
    <RegKey>NOVO</RegKey>
    <SNPID>358</SNPID>
    <AuthSystem>RAS3</AuthSystem>
    <Relevance>
      <Application minVersion="5.5" nativeContent="true">Kontakt</Application>
      <Application minVersion="2.4" nativeContent="false">Maschine</Application>
      <Application minVersion="1.5" nativeContent="false">KKontrol</Application>
    </Relevance>
    <PoweredBy>Kontakt</PoweredBy>
    <ProductSpecific>
      <HU>F865D68C8CFC720CBE4E4EDFCAB1982E</HU>
      <JDX>44429A4AC43EE7653363EF3FA63D95CCC6ABED005CE2FFEE71A33479B5596F45</JDX>
      <Visibility type="Number">3</Visibility>
    </ProductSpecific>
    <Company>Heavyocity</Company>
    <NKSEnabled>true</NKSEnabled>
    <Icon>
      <Data>iVBORw0KGgoAAAANSUhEUgAAAGQAAAAWCAYAAAA2CDmeAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAtJJREFUeNrsWIGNm1AMRacbgBHY4LJBGSGdIGQDboLQCdJMQDoB1wmgE3AbJBuQDShIRnp9sj8fktylLZasy/HB39/PzzY8BW5pRctgkXvJqtNG4nwKFkA+XWqI8/qjAUmW+P8hKcS46C88d5rJ4rnT44iBzLH21um7Yz3sdC+/KwDn0ul3j/3eZQ8N5EjxIRYd9niTM1rS37sBW8NzX2GfjfzeyllCz8D/UGLb77ODfbY+LOC11qG5BzuwTp7g2dhx/6ANBWuovy3YDeXayfCxUIIYyvmsc8WQHHitnagr2re0StWtAGmVgKEwABnT1eGwdV9NNrFBWloTKDWtn2TvQbMbAYLxXbvOPgeQAkoCqkXhteJcSMGLHJmvZRMGaCgfCHoGNldkI1ds1AZTAwMQ1JRs41oBaymdu9FiNgeQbGLzKo1SwEEdJFcCi4fgUTGkEpd5+BEBgM0IuzVAuP9YezMAxdhUhZmYkU4tWZpDK+oDyLKI1kLRVsmg1LATE4iNI6hrCoZv/7sGEK1CWGXaO8hTAOGA5ETZmrIU1xMHazSm7ZW1sREdAzeF8dcAEhAzGqu8P8+cn/ux9ZdjPZIRM6Lx9ih/h4zsx75vcM+O7Bzo/y1MaRd5FkfUQJlmmK04Rg/y5QPeOQ5Qoirw18yYWmlW1/aQPWVFqWR5ZPSYfOLLakpMHMtS3je+M0Ni3/jdq6mHHiMoTiW+I7TlL++XEmNz5dmYEib5bEDmlqyNB81DqJN9efhJ6ztoeK9C4xgofZ7o0/C2WwA791A6A+WtuJIymoivuWhllOFbycutGTJVtXLAo23iWT7Gvq+tHcwsjR6zv/I8UxlSzmVIRQ2wmpENF+O5A2Tdixxk57jf8kn7plYJMBE9Z9l9FX8SzwbPDfkMts/X0ueRPrEn//AX4djnHeT5wZw+Bv+HmF+Jn4JFHkoWQBZAFlkA+YvktwADADxhK0T79Q9qAAAAAElFTkSuQmCC</Data>
    </Icon>
  </Product>

The code has been updated to the new example code that Talula provided. Not sure if this is what you meant when you said update Native Access? I have also ran the "NI Key Adder" as well as the "SNPID Lister" that is provided within Bob Dules release, all keys are correct and no duplications exist - Kontakt also shows the NOVO SNPID as listed properly within the database. Those are the closest things that I'm aware of, with regards to updating Native Access. Please do clarify if you meant something entirely different![/QUOTE]

 

run native access (you don't need to login to your account), wait one minute and close it.
this will update NativeAccess.xml
after that run kontakt and look for library

 

btw, on macOS xml files creating only for libraries that were installed with native access or with installer.
libraries that comes as archived pack working without xml file after adding with "add library".

 

the old nicnt is still working, even the R2R library manager take it.

check if the library option is selected.


because it load normally in many kontakt versions without editing the nicnt.

it can also come's from a home made library using the same snpid, but usually the last added is seen, hidding the other.

 

I ran an update on Native Access, oddly enough the update was ticking up to 400% complete, at any rate the update failed. Should have been enough to fix the .xml file though.

I'm running Windows 10, so I'm not sure if xmls are still needed? Forzo and Vento don't have one, so my guess is that my file is redundant. Just added it in while I was brainstorming solutions before I came to the forum.

I attached a snip of my libraries tab, where Novo should populate. Still no luck, it also dosen't show under the library manager after adding it through 6.6.0.



*Note: Nova is a library by Triple Spiral Audio, not to be confused with Novo

I can manually add the library using KLM, but when I try to open a nki it informs me that the library is not activated (despite the fact I manually added the HU and JDX codes into the registry). This added KLM version also appears to be recognized by Kontakt as a new library that just happens to carry the old name and SNPID. Perhaps it is over-riding the original SNPID associated with Novo, making it to where I can't revert back because Kontakt is still trying to find the newly associated Novo that was added by KLM?

 

WF,
I am a Mac person so I can't give you PC level advice but I have another idea you can try.

You may have a situation on your system where another library is using the SNPID number you are trying to use on this library.

1. For a library to work in Kontakt the SNPID# must match in both the .xlm file AND the .nicnt file.
2. The SNPID# must also not already be in use by different library.

I suggest using one of the various utilities that list all the SNPIDs in use on your system and which libraries they are assigned to. There is one called "SNPID Lister" for PC on the other site. There are several others if you look around. I have one for MAC that will make list of all SNPIDs and automatically assign new non-conflicting numbers to orphaned libraries.

Good luck.

 

your maschine seems to be broken
re install native access if the auto update fail
install NOVO from the iso setup, it don't need to edit/add anything.
google bob dule for iso links.

if you got a msi installer error,
try this windows tool to repair install/uninstall
https://download.microsoft.com/down...oftProgram_Install_and_Uninstall.meta.diagcab

i checked it on the NOVO setup not installing on one machine previously revo cleaned, now all is ok.

 

Thanks for the reply, I have ran a SNPID check and no other library is running this code. This is the weirdest Kontakt problem I've ever had, and I've had a lot of them lol

For this NOVO library I've been using, as well as with its expansions and related products, I never actually got an install file. It seems to be hit or miss whether or not I get an install file from the cites I frequent these days. Thanks for the tip about using your cite, I didn't know there were so many files on it! I'm gonna download the iso right now and see if I can get it to work - if not I'll use the windows tool you linked.

Thanks for all you do for the community, and thanks for your help here! Will update this thread after I try these out!

 

Damnnnnnn,no luck, most likely there is some issue deeper within my machine. I'm just gonna accept that NOVO isn't gonna work on my PC. Thanks for all the help though, genuinely great stuff. The tech support on this forum is light years ahead of actual tech companies, and I'm not exaggerating!