Import Content Option in Kontakt 8 Gives "Incompatible Files" Error on Almost All Libraries

Donovan1979
Donovan1979 Member Posts: 5 Member

Almost every library I own that worked perfectly as a tile in the library browser in Kontakt 7 can not be imported into Kontakt 8 without giving me a "Incompatble Files" error on hundreds of files ending in .ncw

This is happening to multiple libraries from Zero G, Sonuscore, etc…

Batch resave doesn't resolve this either.

«1

Comments

  • zudeth
    zudeth Member Posts: 1 Newcomer

    yep…. same here… tried a batch resave and to no avail all my third party libraries are incompatible and some dont even show up in the list at all after import i tried manually loading those and batch resaving again no dice i regret upgrading now the garbage i got in NI instruments doesnt make up for not being able to use 100s of dollars of 3rd party plugins i use regularly so disappointed.

  • VSTerranova
    VSTerranova Member Posts: 7 Member

    same here and not only 100s of dollars of 3party plugins also NI own instruments, very disappointed too

  • Donovan1979
    Donovan1979 Member Posts: 5 Member

    Ok, so it's not just me then. How do we get NI's attention on this matter?

  • 2Mylent
    2Mylent Member Posts: 5 Member

    Idem concernant bbls 8Dio….

    Same for the 8Dio bbls….

  • JBlongz
    JBlongz Member Posts: 19 Member

    How could they not know already if there was a beta test? This is frustrating.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,021 mod

    I just tried it and I got the same so evidently there is a bug but the import worked all the same so just dismiss the errors

  • TheNeil
    TheNeil Member Posts: 3 Newcomer

    Exactly the same here. Got Kontakt 8 and imported my instrument collection as step 1 - tons of 'Incompatible Files' errors for collections which produced 0 errors on v7. All supposedly problematic files are .ncws.

    8Dio Songwriting Guitar is one such impacted instrument for me, to echo earlier comments. Pretty hilarious that the error seems specific to .ncw files, which are NI's own proprietary compressed wavs.

    The only 'fix' I've found is to use File > Collect samples / Batch compress to re-save the impacted instruments' samples as 'Uncompressed WAV/AIFF'; but I do NOT want to do that: massive time-waste, and a potential performance hit too.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,021 mod

    Like I said it looks to me like the bug is the error message, but the import process itself has so far worked for me with libraries I had previously also imported into K7. So you can dismiss the error message and continue the import.

  • Gilbo
    Gilbo Member Posts: 21 Member

    Same here but the libraries seem to work (I didn't check them all).

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,021 mod
    edited September 24

    Exactly, I suspect the bug is the false error message, not the import process itself

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,021 mod
    edited September 24

    It is nice that once imported the older libraries also appear in the new side browser eg:

    I just wish they would consolidate this browser with its much better drag and drop functionality and extra functions and tools, with the tagging in the 'Library' browser which in my view wouldn't really be needed if it were not for the additional tags and search features, which could be easily added to the side browser.

  • Donovan1979
    Donovan1979 Member Posts: 5 Member

    Does anyone know how to tag a NI admin so they can fix this issue?

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,021 mod

    Don't worry it's been reported and NI devs are aware of it

  • WhoFlipped
    WhoFlipped Member Posts: 2 Member

    When loading a 3rd party librarty, I am also getting a prompt to locate the .nki file on load. I select "Browse for files" and even though I click on the correct .nki file, it fails to load. So similiar, but not the same as the above error (which I am also getting).

  • TheNeil
    TheNeil Member Posts: 3 Newcomer

    Sadly not fixed in v8.0.1; but hopefully soon if you say the dev's are aware.

Back To Top