Colossus and East West Strings weren't staying in my Libraries tab so I went to
Mac HD > Library > Application Support > Native Instruments > Service Center

None of the libraries that are in my Libraries list within Kontakt are listed in the Service Center folder.

All I see in there, oddly enough, are Arturia XML documents. I have a legit version of Arturia that I installed last night.

Why aren't any of my libraries that are showing up in Kontakt in my Service Center folder?

 

I tried the suggestions in the pinned thread but to no avail.

Anyone have any suggestions on how to resolve this?

 

Have you tried with native access to get them reg and activated . I believe they stopped using service center and all is done in native access .in my Mac all my libraries get a receipt in native access folder now

 

I'm using Kontakt 5.x to "Add Libraries". I've blocked any outgoing connection to Native Instruments via Little Snitch so even if I open the Native Access app, I figured I don't want it connecting to NI to prevent breaking my K'd app.

I have no Native Access folder in my HD > Library > Application Support > Native Instruments

I have one "Native Access" folder in my User > Library > Application Support > Native Instruments and it contains one file called "uret_cache".

Are you suggesting actually using the Native Access App and allowing it to connect to the NI servers?

 

Running Native Access won't disable your cracked versions of Kontakt. It just takes stock and keeps them in order. It also can help to wake up older libs that keep disappearing from the libs tab.

 

the xml part updated for these libraries is writen in Native Access.xml, containing all the products.

Spoiler: Colossus

<?xml version="1.0" encoding="UTF-8"?>
<ProductHints>
<Product version="6">
<UPID>baf0463e-a89f-44a9-883b-04ae05e8681b</UPID>
<Name>Colossus</Name>
<Type>Content</Type>
<RegKey>Colossus</RegKey>
<SNPID>752</SNPID>
<AuthSystem>RAS3</AuthSystem>
<Relevance>
<Application minVersion="5.6.8" nativeContent="true">Kontakt</Application>
</Relevance>
<ProductSpecific>
<Visibility type="Number">3</Visibility>
</ProductSpecific>
<Company>East West</Company>
<NKSEnabled>true</NKSEnabled>
<Icon>eastwest</Icon>
</Product>
</ProductHints>

Spoiler: SOStrings

<?xml version="1.0" encoding="UTF-8"?>
<ProductHints>
<Product version="6">
<UPID>01b1f957-9aaf-4d08-8cfa-d98bdfd392a4</UPID>
<Name>SOStrings</Name>
<Type>Content</Type>
<RegKey>SOStrings</RegKey>
<SNPID>711</SNPID>
<AuthSystem>RAS3</AuthSystem>
<Relevance>
<Application minVersion="5.6.8" nativeContent="true">Kontakt</Application>
</Relevance>
<ProductSpecific>
<Visibility type="Number">3</Visibility>
</ProductSpecific>
<Company>East West</Company>
<NKSEnabled>true</NKSEnabled>
<Icon>eastwest</Icon>
</Product>
</ProductHints>

Spoiler: SOStrings PRO XP

<?xml version="1.0" encoding="UTF-8"?>
<Product version="6">
<UPID>95572df0-bd2a-420a-9ed4-47b408e4c760</UPID>
<Name>SOStrings PRO XP</Name>
<Type>Content</Type>
<RegKey>SOStrings PRO XP</RegKey>
<SNPID>769</SNPID>
<AuthSystem>RAS3</AuthSystem>
<Relevance>
<Application minVersion="5.6.8" nativeContent="true">Kontakt</Application>
</Relevance>
<ProductSpecific>
<Visibility type="Number">3</Visibility>
</ProductSpecific>
<Company>East West</Company>
<NKSEnabled>true</NKSEnabled>
<Icon>eastwest</Icon>
</Product>
</ProductHints>

you can copy the data to edit a single east west library.xml by product in service center.
you can also edit the nicnt files to match with Native Access.xml. ras3 instead of ras2 (created with an old nicnt maker)

the mini nicnt maker i made for Kontakt 6.6.0 (windows) is updated to create ras3 data.

native access is your friend, it update the data of native access.xml at the opening.

the problem is Kontakt 5, reading the discontinued Product Hints.xml in service center instead of Native Access.xml.
all you can done is copy the Native Access.xml content and paste it into Product Hints.xml.
or rename Native Access.xml in Product Hints to update the content.

you can also add library directlly in K6 with a terminal script. it goes faster.

Spoiler: Mac Terminal script to add libraries in K6

#!/bin/sh
cd "$(dirname "$0")"
#xml=$(basename "$file" .nicnt).xml
xml=temp.xml
find "$(pwd)" -name "*.nicnt" -type f | while read file
do
awk '/ProductHints/, $NF ~ /\/ProductHints/' "$file" | xmllint --format --recover - > "$xml"
plist="/Library/Preferences/com.native-instruments.$(xmllint --xpath 'string(//Name)' "$xml").plist"
sudo rm "$plist"
ContentDir=$(echo $(dirname "$file") | tr /
sudo defaults write "$plist" ContentDir "${ContentDir#":"}:"
echo
for key in RegKey SNPID Name HU JDX UPID AuthSystem ; do
if [[ "$(xmllint --xpath "string(//$key)" "$xml")" ]]
then
sudo defaults write "$plist" $key "$(xmllint --xpath "string(//$key)" "$xml")"
fi
done
v=$(xmllint --xpath 'string(//ProductSpecific/Visibility)' "$xml")
sudo defaults write "$plist" Visibility -int $v
defaults read "$plist"
done

 

NEWBIE ALERT
In order to start using Native Access instead of Service Center for my k'd libraries, what steps should I take to avoid the abyss...? I now use Kontakt 6.6.0 in DEMO mode... In Mac, ergo sum.

Humbly, and in awe,
Glimt

 

Last edited: Jul 17, 2021

only kontakt is fixed
libraries are the same for everybody, untouched, originals.
use a unlocked Kontakt, not the player to get the libraries.

 

Brilliant, many thanks!